16
1

Teaching translation technology at UCL - Learning by getting your hands dirty

  • Upload
    hkbu

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

1

2

3

4

5

6

7

Here is the Top Ten Objects document as currently available from the Grant Museumwebsite.

8

Here is the Spanish translation produced by our students.

9

And here is the Chinese translation. Both translations have been made available to theMuseum.

10

In our case the E-Learning project consisted of designing an app to help translators findmonolingual or bilingual glossaries or terminology lists.The group was formed of 11 people, there were 10 students coming from very differentbackgrounds, but al of them from the MA in Translation Theory and Practice, and onelecturer, Mark.We used technology to communicate with each other, bring together our ideas and keeptrack of the progress.In our case we could combine this project with the ‘App-ortunity’ scheme. This schemeputs people in College with an idea for an app in touch with students from theDepartment of Computer Science.There was some money allocated to the project that we are using to pay for someservices, like an App Store licence.

11

This is our provisional logo.As I said, our project consisted of designing an app for translators. This app will allow theuser to look for monolingual or bilingual (parallel) lists of specialized terminology inabout 64 languages.It will be available free of charge in the App Store and Google Play Store, so that it canbe used on any device running iOS or Android.

12

How did we do it? We started by studying some of the existing tools, which were mainlywebsites, such as babel.net or multilingual.ch. Some of the members of the group wrotereports on these resources.Then from these reports and our experience as translators we decided what the scopeof the app should be. We realized that although there are many sites that look for singleterms, there are not many that allow the user to search entire terminology lists orglossaries, which sometimes is really helpful for translators, because if they are doing aspecialized translation sometimes they might not even know exactly which term theyare going to need, and this will provide them with a general vocabulary on the subject.Then we defined the specific functions that the app should include.And finally we sent them to our Computer Science colleagues, who told us which ofthese functions were feasible and which we should modify or forget about.

13

Google Docs: This is a Google docs spreadsheet. This screenshot is from the early stagesof development. In order to make the app available in 64 languages we needed totranslate some words into all these languages. This for example is an array containingthe names of all 64 languages translated into every other language. We needed that totranslate some words in the interface but also to make it work properly. There is also apage with search keywords that need to be translated into every language so that wecan obtain the best results. Here the Green rows have already been corrected and thegrey and White rows still needed to be revised.Wiki platform: This is one of the tools that we used to communicate with each other. Weused this platform to keep a track of the project, so everything is here. At the bottom wehave some links to the minutes of the meetings we held and to the reports that I toldyou about. As you can see now we are in the appearance and design stage, so we arespeaking about how to display the information in the interface and our colleagues fromthe Department of Computer Science are developing the app.

14

I will now show you a couple of videos from the app prototype.

15

Thank you very much for coming. We hope that the app will soon be available todownload. In the meantime you can follow us on Facebook or subscribe to our blog.

16