Difference between revisions of "Wordfast Classic User Manual"
(→Dictionary) |
(→Concordance search) |
||
Line 83: | Line 83: | ||
== [[Concordance search Wordfast Classic | Concordance search]] == | == [[Concordance search Wordfast Classic | Concordance search]] == | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== TM and glossary management == | == TM and glossary management == |
Revision as of 00:53, 29 October 2017
- Quick start
- Introduction
- Disclaimer (must read)
- Do not print this manual
- Technical Specifications
- Installing WFC
- Removing WFC
- Upgrading WFC
- Buying a license
- Detailed instructions for use
- Segments with a red frame
- Provisional segments
Contents
- 1 Translation Memory
- 2 Terminology
- 3 Setup
- 4 Word/character count & billing
- 5 Special care
- 6 Fields and objects
- 7 Dictionary
- 8 Concordance search
- 9 TM and glossary management
- 10 WFC segmentation rules
- 11 Troubleshooting
- 12 Glossary of terms used in this manual
- 13 Appendix I - Understanding segmentation & TM
- 14 Appendix II - Language & spell check settings
- 15 Appendix III - Macro samples
- 16 Appendix IV - Advanced Find/Replace
Translation Memory
This section lets you select a TM or create a new one, define TM attributes, set TM rules, set up a Background TM, set up a remote TM with Wordfast Server or Wordfast Anywhere, and setup machine translation.
- TM
- Translation Memory Attributes
- Translation Memory Rules
- Background Translation Memory (BTM)
- Remote TM
- Machine Translation (MT)
Terminology
Setup
Word/character count & billing
Wordfast's way of counting words is slightly different from Ms-Word's statistics (Tools/Wordcount or Tools/Statistics). For example, in the following text:
Ms-Word will find 3 words, while Wordfast will find 5 words (a very similar word count is upheld by most translation tools). On average, Wordfast will find from 5 to 10% more words than Ms-Word, depending on the language. The difference is more striking with French, more modest with other languages. This way of counting is in keeping with most translation syndicates and unions in most countries using alphabetic languages.
Discuss the word count issue with your client before starting working on a project.
On tagged documents, tags are counted as one word (regardless of their number of characters or words) and their number is also reported in the analysis final report. A tag is defined as any contiguous series of characters (spaces included) that have the tw4winInternal style.
Note that (as opposed to word count), tags are not included in the character count, because a tag is counted as one word; tags are included in the word count.
The Wordfast word/character count, as with all CAT tools, is based on what the tool considers to be translatable text. This can depend on the way you set up your tool. For example, the use of the "SegmentAll" command will force Wordfast to consider any text as translatable, including isolated fields, figures, etc. which would otherwise be left out of the translation process.
The Wordfast word/character count includes all headers and footers, footnotes, but not fields. Pay attention to word count when auditing a project, or producing an estimate. Ask yourself the question (if applicable) of whether the document(s) contains bookmarks, and if it does, what the author/client wants to do of them; whether graphics or textboxes should be translated, whether headers and footers should be translated, whether the word count is based on source, or target (translated), text, how to count tags, if any (per piece? per word? per character? at what rate?), etc.
Special care
This section deals with expert uses of Wordfast for tasks that require special attention. Wordfast does not guarantees operation because of its very nature. Wordfast is an add-on to a complex program (Ms-Word) that handles documents which, in the course of their lives, have been handled very differently by different people using different version sof Ms-Word (on PCs or Macs), through different formats (DOc, Rtf, Html, etc.) and sometimes very ill-conceived (many people use textboxes when tables, or a much simpler layout, should be used).
The special care section deals with tasks that are possible with Wordfast, but which need special attention in their execution, as well as a good knowledge of Ms-Word. Beginners should train themselves, or seek professional training, before engaging in projects outlined in the Special Care section. It is out of question for any translator to accept a "Special care" job wihout a prior understanding of the risks involved.
Fields and objects
An Ms-Word document can contain fields or objects like hypertext links, buttons, graphics etc. Normally, fields should not be translated (unless specifically required by your client, like index fields, for example), but copy-pasted into the translation. Note that the display options in Tools/Options/View can toggle the two views of fields: either the result of the field (a field is an instruction processed by Ms-Word, usually resulting in some displayed text - the result), or field codes, which look like {DATECREATION \* FUSIONFORMAT}. I recommend using the icon that toggles the two views (use the View/Toolbars/Customise menu, click the Commands tab, then View in the list, then drag-drop the {a} icon into the toolbar of your choice), or the Alt+F9 Ms-Word shortcut.
To graphically understand this concept, set your current View mode to "Normal" with the View menu in Ms-Word. Press Alt+F9 right now a few times to grasp the concept behind fields (this manual's table of contents is a TOC field), and the two ways to look at fields (result or code). The following "Today's date" field: 26/09/2017 should toggle between the two views. This manual's Table of Contents is actually a TOC field. If you were to translate this manual, you would not translate the Table of Contents, but merely update it by having the cursor anywhere in the Table of Contents and pressing Ms-Word's F9 shortcut once the entire manual has been translated and cleaned-up.
When fields are present in the source text and no proposition comes from the TM, you may consider using Wordfast's Copy source icon to copy the source segment into the target segment, and translate by overwriting it, leaving fields or objects unchanged. Otherwise, individual fields and objects should be carefully copy-pasted into the target segment's translation, at the appropriate location.
Dictionary
Concordance search
TM and glossary management
WFC segmentation rules
Troubleshooting
Glossary of terms used in this manual
Appendix I - Understanding segmentation & TM
Appendix II - Language & spell check settings
A document can contain text written in different languages. In Ms-Word, the language is a text attribute, just as font, colour, etc. The Tools/Language menu is used to apply a certain language to a selection. This language setting is important, for example, when spell-checking. Usually, the client will send you a document where all the text has the source language (e.g. "English") as attribute. When translating, it is important that the target text receives the target language (e.g. "French") as attribute. This allows you to spell-check the target segments using the proper dictionary. This should be set up in Wordfast's Setup/Segments tab.
Wordfast will apply the specified target language (or default language, as specified in Wordfast/Setup/Segments) to the target segment. If, however, you have chosen the "leave unchanged" setting, Wordfast will not redefine the target language.
Appendix III - Macro samples
- Checking segment character count
- Checking segment visible length
- Checking quotes consistency
- Highlighting text with Shading
- Extracting the contents of textboxes into a new document
- From Text to Doc: a smarter approach
Appendix IV - Advanced Find/Replace
Note: the Wordfast Knowledge Base, accessible from http://www.wordfast.net has more contents on the following topic.
Ms-Word's Find/Replace feature (FR) accepts wildcards and advanced features. A good understanding of FR can save the day on numerous occasions. I had to oversee translation projects where, to my astonishment, translators were spending hours executing visual/manual Find-Replace actions that could have been safely executed automatically.
Sure, FR actions can be destructive if they're not executed properly, since they can modify unwanted parts of the document. On a short document, a visual/manual FR can be preferred, since setting up and testing a smart and safe FR can take a little while.
Note that PlusTools offers a FR feature that can be run over many files, both in manual and automatic mode, with the possibility to edit the document and restart the FR where it was interrupted.