CAT翻译工具学习计划.docx

我们是根据以下要求，以小组形式进行操作的。我的实践报告也会以此为依据，根据时间顺序写。Week 4 group work summaryGroups 1 and 3 will work on Greenpeace Campaign1.Groups 2 and 4 will work on Greenpeace Campaign2.1.Download the appropriate Version 1Greenpeacezip file to yourP Drive, expand it and inspect the file and folder structure of the mini website.2. Create and share,including with AR and SR, aGoogleSheet in which your whole group will record itsSource Language terms. There should be a column labelled SL Terms and a second labelled Discussion in which you record arguments for and against inclusion of individual items, as necessary. You will be able to sort the terms into alphabetical order at any time.3. Read througheach STin turn to identify the terms they contain (remember that some may be multi-word terms). All members of the group need to cooperate in identifying terms - discussions could be carried out by email, text or chat, via Blackboard or in meetings of 2 or more members. The important thing is to identify what constitutes aterm- generally, eithera specialised word or phrase used only in a specific technical domain, or an ordinary word or phrase which has a specialised sense in a specific technical domain. There will always be borderline cases.4. Record the30 most important SLterms in the spreadsheet as you go. All terms should be recorded incitation form(e.g. singular for nouns, infinitive for verbs) and inlower case(except in the case of proper names such as trade marks). If a term is almost always found in the plural it is permissible to record the plural form.5. Once the group has an agreed list of terms,language teamsshould make their own shared copy of the groups terminology spreadsheet, adding columns forTarget Language terms(TL Terms) and Notes. They should research and record the TL equivalent for each term, together with any other relevant information (e.g. gender), to create a basicbilingualtermbase.Every language team member should play a full role in this process.6. By next week, each language team should have a fully populated bilingual terminologyspreadsheet inGoogleSheets.Dont forget to make regular backups of all data!7. By then you should also have arrived at an agreed distribution of roles. For Phase 1 of the project (SDL Trados), each group needs to identify aproject manager (PM), whose job will be to coordinate the groups work, and achiefterminologist(CT), to organise and look after the groupstermbase. In addition, each language team should identify alanguage lead (LL)whose job will be to coordinate the translation and revision of the website and liaise with the project manager as necessary.We will ask you to confirm the names of all these people next week. Dont worry if you arent taking on one of these roles this time round: there will be a second opportunity in the middle of the module.Week 5 group work summaryThe objective of this weeks group work is for eachProject Groupto agree and implement in MultiTerma termbase structure for its future multilingualTB. Eachlanguage teamwill then use that structure to buildand populate abilingual MultiTermTBcontaining its terminology data for the Greenpeaceproject. By next weeks class you should have a complete bilingual TB which you will then use in the translation of Version 1 of the website. The steps for this week are:1. (Group)Decide on thestructureof yourMultiTermTB (which descriptive fields do you want? at what level? will any be mandatory or multiple? will you have any multimedia objects? what aboutpicklists?). Note the importance of including an accuratereferenceto any external material you cite. As a minimum, you should include the following: Entry level: Domain (withpicklist); Graphic (multimedia); Reference Term level:PoS(mandatory, for all languages);Definition(English only? or all languages?); Example (usageof the term in context); Reference; Note (this can be Multiple, and added at al levels.) Any other fields needed for your different languages (e.g. Gender)2. (Language Team) Build an empty MultuTerm TB for your language pair with the structure decided on by the group. Adjust the column headers in your Excel spreadsheet so that they correspond EXACTLY to thefieldnamesyou have chosen.NB: How will you solve the problem of needing several Reference columns?3. Use SDLMultiTermConvert to turn your Excel data into XML and XDT files suitable for importing into SDLMultiTerm.(The instructionsfor usingSDLMultiTermConvert are in the handout from last week).4. Create a new (empty)MultiTermTB using the XDT file generated by the Convert process.5. Import the XML data into your new TB.6. Populate any empty fields (e.g. Definition,PoS, Referenceetc.) as appropriate, so that you have a complete TB to work with by next week.Week 6 group work summaryAim: by the class in week 7, eachlanguage teamshould have usedSDLTradosStudio 2017to produce a draft translation of the web pages in the first version of their Greenpeacesite. You should also have a single Translation Memory (TM) inTMX formatfor eachlanguage pair, and a fully populatedbilingualMultiTermtermbase.The steps in this process are as follows(NB: you should keep detailed notes, including screen shots, of what you do - these will be very helpful when it comes to writing your final report):1. Decide among the language team who will produce the first draft translation of each ST page and who will revise it (next week);allocate the individual pages to translators.2. Each translator then sets up their ownStudio Projectwith an empty TM and the teamsMultiTermTB, and imports their allocated ST page(s) into it.3. Translate your own page(s), making full use of all the terminology and TMproposals produced by the system.4. Note howAutosuggestandQuickplacework: how and when do they help?5. Export yourTTsand check their appearance (are the graphics visible?), formattingetc.6. Export yourTMinTMX format, then find a way of combining your teams TMX files into a single TM database.7. Send yourTTsand combined TMX to your project manager (PM), who will store them appropriately onGoogleDrive.Week 7 group work summaryProject next steps: (NB: dont forget tokeep notes,screenshotsetc.of what you are doing):By the class in week 8, everybody should have completed the following steps:1. Translators should exchangeProject Packagescontaining their own individual TM, and the Greenpeace V1web page(s) they have translated forReview;2. Each student should then open their package,reviewtheir colleagues pages usingtracked changes and comments, Concordance Searchto check phrases, etc., then return their work to the original translator in aReturn Package;3. Each studentshould then open the Return Package, accept or reject all the changes,Sign offthe translation(s) and update the TM;4. All signed off work should then be sent to the PM in a Project Package for storage;5. Language teams should export their TTs so that they have a complete TL website (dont worry if pictures and layout are not correct, the important thing at this stage is the text);6. Finally, teams should combine their TMs into a single TM per language pair, using TMX exports. You may need to work out how to handle duplicate translations for the same segment.Week 8 group work summaryEachgroupshould now have a complete set of the following GreenpeaceV1 data files, stored in the cloud:1. For each language pair, afully populatedbilingualMultiTermtermbase(TB);2. For each language pair, asingle Translation Memory(TM) containing fullyrevisedandsigned offTUsof the V1 website;3. For each language pair, afull set ofexportedV1TT web pages.Before next weeks class, each group/team should perform the following additionaltasks using SDLTradossoftware:1. Download and extract the appropriate set ofGreenpeaceV2website files;2. Under the guidance of the Project Manager, createa single multilingualStudio 2017 projectcontaining the newSTsandtheTMfor each language pair;3. Analyzethe newSTsagainst each bilingual TM and note (screen capture) theleveragestatisticsfor each TL;4. Under the guidance of the ChiefTerminologist, runSDLMultiTermExtracton GreenpeaceV2files against each language teams TB and see how many new terms it can find (experiment with different Noise and Silence settings, and add terms,preferablywith examples, to your TB automatically)5. Read through the newSTsto identify and agree any terms that Extract did not manage tofind, and agree among the whole group which new terms are to be added to the TB;6. Using anInput Model, add the new terms and their translations to the teams TB, completing the population of the descriptive fields as well.In addition, by next week please ensure that you individually have become as familiar as you can at this stage with the general principles ofMemsourceCloud. In the course of the week you should receive an email from your Project Manager giving you details of yourMemsourcelogin.Week 9 group work summary (Memsource)The main objectives this week are a) tomigrateyour groups TM and TB datatoMemsourceformats; b) set up your groupsMemsourceprojectusing these sharedonlineresources; c)analyzeand record the TM leverage that you can expect when translating the Greenpeaceversion 2 website;and d) complete thefirst draft translationof the new website using theMemsourceCloud editorand the shared TM and TB.Detailed steps this week:1. Eachlanguage teamshould exportits SDLTradosStudio TM to TMX format and at least the SL and TL fields of its bilingualMultiTermTB to Tab-delimited text (.TXT) format. Open the TXT file in Excel, check column alignment and add a header to identifying languages (en-gb, deetc.). Any Descriptive fields to be transferred must have the header Note, or (for usage examples)ExampleUsage. It is possible to have several columns called Note and Example Usage. Save the spreadsheet in the old .XLS file format (not .XLSX).2. InMemsource, thePMswill also ensure that every Linguist has the relevantworkflowstepsenabledin their profile,i.e. Translation, Revision.3. With assistance from other members of the group, the PM should create a multilingualMemsourceproject.4. The PM should also create an empty bilingual TM and TB per language pair, andimporttheTradosTMX files into theMemsourceTMs and the .XLS terminologyspreadsheets into the Memsource TBs.5. The PM should assign tolinguistsfortranslationST page(s)that they did not originally translate(this is so that everyone has the experience of working with someone elses data).6. All translators should then translate their web page(s) in theMemsourceCloud Editor,making maximum use of their translation options,including MT proposals from Microsoft Translator,exploringall features of the software andaccepting/editing all TM matches and TBproposals, andrunning QA.Please note: there should be relatively little new translation work, and many proposals from the system, so you should workslowly, taking time to assess the value of the different proposals and theeffort needed to correctthem.7. Once the first draft is complete, each translator should mark the project ascompletedso that their PM is automatically notified by email fromMemsource.Week 10 Group work summary (Memsource)By now each language team should be using itsonlineTM and TB to perform a first draft translation of theGreenpeaceversion 2 website, updating its shared TM. The main aim of this weeks work is for each team member to revise the draft translation of another translator.1. The PM in each group should keep track of the automatic email notifications and ensure that everybody has completed their translation, as well as keep track of the progress of the revision tasks.2. Each translator should log in toMemsourceand make full use of the QA/revision features of the software,always bearing in mindthe objective of achieving a consistent website that will look as if it had been translated by a single person(how easy is this to do?).3. Each translator should ensure they havedownloadedand savedthe completed MXLIFF bilingual files to a desired locationbeforemarking the work as Complete. Each translator should save their MXLIFF files for data backup purposes and send a copy to the PM.4. When the revision is finished, revisers should mark the task as Completed (online),so that the PM is automatically notified by email.5. All Language Leads should export the final version of theTBto