CAT翻译工具学习计划

我们是根据以下要求，以小组形式进行操作的。我的实践报告也会以此为依据，根据时间顺序写。

Week 4 group work summary

Groups 1 and 3 will work on Greenpeace Campaign 1. Groups 2 and 4 will work on Greenpeace Campaign 2.

1.Download the appropriate Version 1 Greenpeace zip file to your P Drive, expand it and inspect the file and folder structure of the mini

website.

2. Create and share, including with AR and SR, a Google Sheet in which your whole group will record its Source 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 through each ST in 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 a term - generally, either a 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 the 30 most important SL terms in the spreadsheet as you go. All terms should be recorded in citation form (e.g. singular for nouns, infinitive for verbs) and in lower 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 teams should make their own shared copy of the group's terminology spreadsheet, adding columns for Target 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 basic bilingual termbase. 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

terminology spreadsheet in Google Sheets. Don't 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 a project manager (PM), whose job will be to coordinate the group's work, and

a chief terminologist (CT), to organise and look after the group's termbase. In

addition, each language team should identify a language 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. Don't worry if you aren't 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 summary

The objective of this week's group work is for each Project Group to agree and implement in MultiTerm a termbase structure for its future multilingual TB.

Each language team will then use that structure to build and populate

a bilingual MultiTerm TB containing its terminology data for the

Greenpeace project. By next week's 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 the structure of your MultiTerm TB (which descriptive fields

do you want? at what level? will any be mandatory or multiple? will you have any multimedia objects? what about picklists?). Note the importance of

including an accurate reference to any external material you cite. As a

minimum, you should include the following:

?Entry level: Domain (with picklist); Graphic (multimedia); Reference

?Term level: PoS (mandatory, for all languages); Definition (English only? or all languages?);

? Example (usage of 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 the fieldnames you have chosen. NB: How will you solve the problem of needing several

Reference columns?

https://www.360docs.net/doc/759226202.html,e SDL MultiTerm Convert to turn your Excel data into XML and XDT files

suitable for importing into SDL MultiTerm. (The instructions for

using SDL MultiTerm Convert are in the handout from last week).

4.Create a new (empty) MultiTerm TB 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', 'Reference' etc.) as

appropriate, so that you have a complete TB to work with by next week.

Week 6 group work summary

Aim: by the class in week 7, each language team should have

used SDL Trados Studio 2017 to produce a draft translation of the web pages in the first version of their Greenpeace site. You should also have a single Translation Memory (TM) in TMX format for each language pair, and a fully populated bilingual MultiTerm termbase. 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 own Studio Project with an empty TM and

the team's MultiTerm TB, and imports their allocated ST page(s) into it.

3.Translate your own page(s), making full use of all the terminology and

TM proposals produced by the system.

4.Note how Autosuggest and Quickplace work: how and when do they help?

5.Export your TTs and check their appearance (are the graphics visible?),

formatting etc.

6.Export your TM in TMX format, then find a way of combining your team's TMX

files into a single TM database.

7.Send your TTs and combined TMX to your project manager (PM), who will

store them appropriately on Google Drive.

Week 7 group work summary

Project next steps: (NB: don't forget to keep notes, screenshots etc. of what you are doing):

By the class in week 8, everybody should have completed the following steps:

1.Translators should exchange Project Packages containing their own individual

TM, and the Greenpeace V1 web page(s) they have translated for Review;

2.Each student should then open their package, review their colleag ue’s pages

using tracked changes and comments, Concordance Search to check phrases, etc., then return their work to the original translator in a Return Package;

3.Each student should then open the Return Package, accept or reject all the

changes, Sign off the translation(s) and update the TM;

4.All signed off work should then be sent to the PM in a Project Package for

storage;

https://www.360docs.net/doc/759226202.html,nguage teams should export their TTs so that they have a complete TL

website (don't 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 summary

Each group should now have a complete set of the following Greenpeace V1 data files, stored in the cloud:

1.For each language pair, a fully populated bilingual MultiTerm termbase (TB);

2.For each language pair, a single Translation Memory (TM) containing

fully revised and signed off TUs of the V1 website;

3.For each language pair, a full set of exported V1 TT web pages.

Before next week's class, each group/team should perform the following

additional tasks using SDL Trados software:

1.Download and extract the appropriate set of Greenpeace V2 website files;

2.Under the guidance of the Project Manager, create a single multilingual Studio

2017 project containing the new STsand the TM for each language pair;

3.Analyze the new STs against each bilingual TM and note (screen capture)

the leverage statistics for each TL;

4.Under the guidance of the Chief Terminologist, run SDL MultiTerm Extract on

Greenpeace V2 files against each language team's TB and see how many new terms it can find (experiment with different Noise and Silence settings, and add terms, preferably with examples, to your TB automatically)

5.Read through the new STs to identify and agree any terms that Extract did not

manage to find, and agree among the whole group which new terms are to be added to the TB;

https://www.360docs.net/doc/759226202.html,ing an Input Model, add the new terms and their translations to the team's

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

of Memsource Cloud. In the course of the week you should receive an email from your Project Manager giving you details of your Memsource login.

Week 9 group work summary (Memsource)

The main objectives this week are a) to migrate your group's TM and TB

data to Memsource formats; b) set up your group's Memsource project using these shared online resources; c) analyze and record the TM leverage that you can expect when translating the Greenpeace version 2 website; and d) complete the first draft translation of the new website using

the Memsource Cloud editor and the shared TM and TB.

Detailed steps this week:

1.Each language team should export its SDL Trados Studio TM to TMX format

and at least the SL and TL fields of its bilingual MultiTerm TB to Tab-delimited text (.TXT) format. Open the TXT file in Excel, check column alignment and add a header to identifying languages (en-gb, de etc.). Any Descriptive fields

to be transferred must have the header Note, or (for usage

examples) Example Usage. It is possible to have several columns called Note and Example Usage. Save the spreadsheet in the old .XLS file format

(not .XLSX).

2.In Memsource, the PMs will also ensure that every Linguist has the

relevant workflow steps enabled in their profile, i.e. "Translation", "Revision".

3.With assistance from other members of the group, the PM should create a

multilingual Memsource project.

4.The PM should also create an empty bilingual TM and TB per language pair,

and import the Trados TMX files into the Memsource TMs and the .XLS

terminology spreadsheets into the Memsource TBs.

5.The PM should assign to linguists for translation ST page(s) that they did not

originally translate (this is so that everyone has the experience of working with someone else's data).

6.All translators should then translate their web page(s) in the Memsource Cloud

Editor, making maximum use of their translation options, including MT

proposals from Microsoft Translator, exploring all features of the software

and accepting/editing all TM matches and TB proposals, and running

QA. Please note: there should be relatively little new translation work, and many proposals from the system, so you should work slowly, taking time to assess the value of the different proposals and the effort needed to

correct them.

7.Once the first draft is complete, each translator should mark the project

as completed so that their PM is automatically notified by email

from Memsource.

Week 10 Group work summary (Memsource)

By now each language team should be using its online TM and TB to perform

a first draft translation of the Greenpeace version 2 website, updating its

shared TM. The main aim of this week's 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 to Memsource and make full use of the

QA/revision features of the software, always bearing in mind the 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 have downloaded and saved the

completed MXLIFF bilingual files to a desired location before marking 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 the TB to both TBX and

XLSX formats and send to the Chief Terminologist for overseeing and

safekeeping.

6.In order to finalize the project, PMs should select the completed file(s) from the

Projects portal, click on Download, then click on Completed file and save all completed translations to a desired location for safekeeping. With the same procedure, PMs will download the final versions of the TMX files too for

safekeeping.

Week 11 Group work summary (Memsource)

The final stages of the project involve reconstructing the TL websites,

and exporting your final TM data from Memsource into SDL Trados Studio 2017 TMs, prior to submission of the data by Zip file for assessment. You

should also add any new terms to the group's MultiTermTB. For a list of

the data file deliverables, please see p.2 of the Assignment Guide (above).

To reconstruct a working Greenpeace Version 2 website for each target

language, you will need to arrange the HTML pages in a single folder for the SL and each TL, with just one graphics folder for all the websites (including the SL English site). You should add a language marker to all TL web

page filenames so that they can be distinguished from the SL originals, and

adjust all hyperlinks to reflect the changed filenames. Graphics source tags in the HTML will need to be adjusted to point to the single graphics folder for your multilingual website. These steps will be covered in the Week 11 lab class.