Wordfast Wiki - User contributions [en]

Wordfast Classic User Manual

2017-11-06T07:14:10Z

Samar: /* Credits */

* [[Quick start Wordfast Classic|Quick start]]
* [[Introduction Wordfast Classic|Introduction]]
* [[Disclaimer Wordfast Classic|Disclaimer (must read)]]
* [[Do not print|Do not print this manual]]
* [[Technical specifications Wordfast Classic|Technical Specifications]]
* [[Installing Wordfast Classic|Installing WFC]]
* [[Removing Wordfast Classic|Removing WFC]]
* [[Upgrading Wordfast Classic|Upgrading WFC]]
* [[Buying Wordfast Classic License|Buying a license]]
* [[Detailed Instructions for Using Wordfast Classic|Detailed instructions for use]]
* [[Segments with a red frame Wordfast Classic|Segments with a red frame]]
* [[Provisional Segments in Wordfast Classic|Provisional segments]]

== 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.

* [[Translation Memory Wordfast Classic|TM]]
* [[Translation Memory Attributes Wordfast Classic|Translation Memory Attributes]]
* [[Translation Memory Rules Wordfast Classic|Translation Memory Rules]]
* [[Background Translation Memory (BTM) Wordfast Classic|Background Translation Memory (BTM)]]
* [[Remote TM Wordfast Classic|Remote TM]]
* [[Machine Translation Wordfast Classic|Machine Translation (MT)]]

== Terminology ==

* [[Glossaries Wordfast Classic|Glossaries]]
* [[Blacklist Wordfast Classic|Blacklist]]
* [[Find-Replace list Wordfast Classic|Find-Replace list]]
* [[Reference Wordfast Classic|Reference]]
* [[Other Wordfast Classic|Other]]
== Conversions ==
''Disclaimer: this feature converts from US Customary Units to Metric, and back. For other measures (such as British Units, or the older Imperial Units), the set of signatures must be modified. The default set of conversion signatures is an editable text file located in the same folder as wordfast.dot. It would be called WfCnv-en2fr.txt in our example below (English to French). Advanced users can edit that file for better accuracy.''
Wordfast Classic's AutoSuggest feature is equipped with an automatic conversion utility as of version 6.28, January 2016.

The mission statement for the WFC converter is:

*to detect possible units or measures in the source text based on a set of signatures;
*to suggest the most likely target-language conversion(s) to save time, with rounded values to save time;
*to work straight off the box with no configuration, yet be customizable by power users;
*to be a push operation, meaning, the conversions are automatically suggested to the translator based on an automatic detection process. There should be no pull operation, or the need to go get conversions by copy-pasting, selecting, pressing buttons, etc.

* [[Typical use case Wordfast Classic|Typical use case]]
* [[Financial formats Wordfast Classic|Financial formats]]
* [[Dates Wordfast Classic|Dates]]

==[[Tools Wordfast Classic|Tools]] ==

== Setup ==
* [[General Wordfast Classic|General]]
* [[Segments Wordfast Classic|Segments]]
* [[Quality Assurance Wordfast Classic|Quality Assurance]]
* [[View Wordfast Classic|View]]
* [[AS (AutoSuggest) Wordfast Classic | AS (AutoSuggest)]]
* [[UI (User Interface) Wordfast Classic | UI (User Interface)]]
* [[Pandora's Box Wordfast Classic|PB (Pandora's Box)]]

== [[Word/character count & billing Wordfast Classic|Word/character count & billing]] ==
* [[Languages that require Unicode Wordfast Classic|Languages that require Unicode]]
* [[CJK (Chinese, Japanese, Korean) Wordfast Classic|CJK (Chinese, Japanese, Korean)]]

== 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.
* [[Tagged files Wordfast Classic|Tagged files]]
* [[PDF Wordfast Classic|PDF]]
* [[Help files Wordfast Classic|Help files]]
* [[Footnotes Wordfast Classic|Footnotes]]
*[[Fields and objects Wordfast Classic| Fields and objects]]
* [[Translatable fields Wordfast Classic|Translatable fields]]
* [[Bookmarks Wordfast Classic|Bookmarks]]

== [[Dictionary Wordfast Classic | Dictionary]] ==

== [[Concordance search Wordfast Classic | Concordance search]] ==

== TM and glossary management ==
* [[introduction TM and glossary management Wordfast Classic|Introduction]]
* [[The TM/Glossary editor Wordfast Classic|The TM/Glossary editor]]

== [[WFC segmentation rules Wordfast Classic |WFC segmentation rules]] ==
* [[The WFC Translation memory format Wordfast Classic|The WFC Translation memory format]]
* [[Placeholders Wordfast Classic|Placeholders]]
* [[Tags in a WFC TM Wordfast Classic|Tags in a WFC TM]]

== [[Troubleshooting Wordfast Classic|Troubleshooting]] ==
== [[Glossary of terms used in this manual Wordfast Classic|Glossary of terms used in this manual]] ==
== Appendix I - Understanding segmentation & TM ==
* [[Segmentation Wordfast Classic|Segmentation]]
* [[Translation Memory Appendix I Wordfast Classic|Translation Memory]]
== 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 WFC's Setup/Segments tab.

WFC will apply the specified target language (or default language, as specified in WFC/Setup/Segments) to the target segment. If, however, you have chosen the "leave unchanged" setting, WFC will not redefine the target language.

== [[Appendix III - Macro samples Wordfast Classic |Appendix III - Macro samples]] ==
* [[Checking segment character count Wordfast Classic|Checking segment character count]]
* [[Checking segment visible length Wordfast Classic|Checking segment visible length]]
* [[Checking quotes consistency Wordfast Classic|Checking quotes consistency]]
* [[Highlighting text with Shading Wordfast Classic|Highlighting text with Shading]]
* [[Extracting the contents of textboxes into a new document Wordfast Classic|Extracting the contents of textboxes into a new document]]
* [[From Text to Doc: a smarter approach Wordfast Classic|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.

* [[Back to source Wordfast Classic|Back to source]]
* [[Turning US financial number formatting into French Wordfast Classic|Turning US financial number formatting into French]]
* [[From Text to Doc Wordfast Classic|From Text to Doc]]
* [[Replacing numbers Wordfast Classic|Replacing numbers]]
* [[Delete target segments that are just a copy of the source segment Wordfast Classic|Delete target segments that are just a copy of the source segment]]
* [[Associating macros with a shortcut Wordfast Classic|Associating macros with a shortcut]]
== Credits ==
All trademarks noted ™ are the property of their respective owners.

Ms-Word, Excel, Acces, PowerPoint are trademark of Microsoft Corp.

Translator's Workbench is a trademark of Trados Corporation

Wordfast Classic User Manual

2017-11-06T07:13:21Z

Samar: /* Appendix IV - Advanced Find/Replace */

Replacing numbers Wordfast Classic

2017-11-06T07:10:50Z

Samar:

A segmentation problem had produced segments where match values were often over 100. So the documents had such match values as <}833{> or <}944{> etc. It appeared that the last figure of the match value had been duplicated (these two segments should have been <}83{>.and <}94{>). How could this be fixed in many documents, in one pass, making sure other figures are not modified by the procedure?

The answer is:

{|
|-
|Find what ||(\<\})([1-9])(?)(?)(\{\>)
|-
|Replace with ||\1\2\3\5
|-
|Use Wildcards
|}

Explanation: When the "Match wildcards" checkbox is checked, "expressions" are anything contained within parentheses. The "Replace with" numbers actually refers to expressions located in the "Find what" argument.

The ([1-9]) expression in the "Find what" argument, for example, refers to any number in the range 1 - 9. In the "Replace with" argument, it is referred to as \1, meaning, "expression 2".

So the FR action can be read as:

Look for chunks of text made of the following 5 contiguous expressions:

#''<}'' followed by
#''Any number between 1 and 9'' followed by
#''any character'' followed by
#''any character'' followed by
#''{\>)''

If such a chunk of text is found, replace the entire chunk with expressions 1, 2, 3, 5.

As a result, the redundant number (expression 4) is deleted from match values, with no risk of upsetting the rest of the document. An added safety measure could be to set the style for the Search parameter to "tw4winMark".
Back to [[Wordfast Classic User Manual]]

From Text to Doc Wordfast Classic

2017-11-06T07:08:27Z

Samar:

Q: In my document, all lines end with a carriage return, even if they don't end a paragraph. What can I do to reconstruct a normal text flow?

A: There is no absolute answer, but a global FR can do most of the job; a last manual verification will restore paragraphs that are unduly cut. See the other, smarter, macro-based alternative in Appendix III, "[[From Text to Doc: a smarter approach Wordfast Classic|Text to Doc]]".
{|
|-
|Find what ||^p^p
|-
|Replace with ||<!?a$
|}

The above FR will preserve double paragraph marks (replacing them into a very unlikeky sequence of characters, which we here call a code)
{|
|-
|Find what ||^p
|-
|Replace with
|}
The above FR will turn all single paragraph marks into a space. A space has to be entered in the "Replace with" argument.
{|
|-
|Find what ||<!?a$
|-
|Replace with ^||p^p
|}
The above FR will restore double hard carriage returns.

This is a typical three-pass FR example. Note that when using wildcards, Ms-Word no longer accepts some characters such as ^p (hard carriage return), so two- or three-pass FR actions are often necessary to bypass this limitation.

But hey, wait a minute...

Actually, a one-pass FR can achieve just the same result, but don't tell anyone, because it's a secret:
{|
|-
|Find what || ([!^0013])([^0013])([!^0013])
|-
|Replace with ||\1 \3
|-
|Use Wildcards
|}
''(Note the space after \1)'' Amazing, right? Be cautious though – on some Ms-Word versions, ^0013 introduces a new line but not necessarily a ''paragraph'', as surprising as this may seem… Use this geeky method if you’re a geek yourself and know what you’re doing.
Back to [[Wordfast Classic User Manual]]

From Text to Doc Wordfast Classic

2017-11-06T07:05:47Z

Samar:

Q: In my document, all lines end with a carriage return, even if they don't end a paragraph. What can I do to reconstruct a normal text flow?

A: There is no absolute answer, but a global FR can do most of the job; a last manual verification will restore paragraphs that are unduly cut. See the other, smarter, macro-based alternative in Appendix III, "[[From Text to Doc: a smarter approach Wordfast Classic|Text to Doc]]".
{|
|-
|Find what ||^p^p
|-
|Replace with ||<!?a$
|}

The above FR will preserve double paragraph marks (replacing them into a very unlikeky sequence of characters, which we here call a code)
{|
|-
|Find what ||^p
|-
|Replace with
|}
The above FR will turn all single paragraph marks into a space. A space has to be entered in the "Replace with" argument.
{|
|-
|Find what ||<!?a$
|-
|Replace with ^||p^p
|}
The above FR will restore double hard carriage returns.

This is a typical three-pass FR example. Note that when using wildcards, Ms-Word no longer accepts some characters such as ^p (hard carriage return), so two- or three-pass FR actions are often necessary to bypass this limitation.

But hey, wait a minute...

Actually, a one-pass FR can achieve just the same result, but don't tell anyone, because it's a secret:
{|
|-
|Find what || ([!^0013])([^0013])([!^0013])
|-
|Replace with ||\1 \3
|-
|Use Wildcards

''(Note the space after \1)'' Amazing, right? Be cautious though – on some Ms-Word versions, ^0013 introduces a new line but not necessarily a ''paragraph'', as surprising as this may seem… Use this geeky method if you’re a geek yourself and know what you’re doing.
Back to [[Wordfast Classic User Manual]]

Turning US financial number formatting into French Wordfast Classic

2017-11-06T07:03:56Z

Samar:

This means changing US thousand separators (commas) into non-breaking spaces, and US decimal separators (full stops) into commas. Here is a two-pass method:
{|
|-
|Find what ||.([0-9][0-9])>
|-
|Replace with ||,\1
|}
::Use Wildcards

then,
{|
|-
|Find what ||([0-9]),([0-9][0-9][0-9])
|-
|Replace with ||\1^s\2
|-
|Use Wildcards
|}
This method is offered as sample in Wordfast's ''Pandora's box'' commands. Note that Wordfast's "FR" command executes FR actions ''only in the current target segment'', at segment validation time.

Use this FR in automatic mode ("Replace all") if the figures and numbers in your document are essentially financial. If, however, your document mixes scientific figures with financial figures, I recommend using this FR method with a visual confirmation for each replacement (in Ms-Word's "Find" dialog box, click "Find Next" and "Replace" rather than "Replace all").
Back to [[Wordfast Classic User Manual]]

Turning US financial number formatting into French Wordfast Classic

2017-11-06T07:03:18Z

Samar:

This means changing US thousand separators (commas) into non-breaking spaces, and US decimal separators (full stops) into commas. Here is a two-pass method:
{|
|-
|Find what ||.([0-9][0-9])>
|-
|Replace with ||,\1
|}
::Use Wildcards

then,
{|
|-
|Find what ||([0-9]),([0-9][0-9][0-9])
|-
|Replace with ||\1^s\2
|-
|Use Wildcards
|}
This method is offered as sample in Wordfast's ''Pandora's box'' commands. Note that Wordfast's "FR" command executes FR actions ''only in the current target segment'', at segment validation time.
Use this FR in automatic mode ("Replace all") if the figures and numbers in your document are essentially financial. If, however, your document mixes scientific figures with financial figures, I recommend using this FR method with a visual confirmation for each replacement (in Ms-Word's "Find" dialog box, click "Find Next" and "Replace" rather than "Replace all").
Back to [[Wordfast Classic User Manual]]

Turning US financial number formatting into French Wordfast Classic

2017-11-06T07:02:48Z

Samar:

This means changing US thousand separators (commas) into non-breaking spaces, and US decimal separators (full stops) into commas. Here is a two-pass method:
{|style="font-size: 9pt"
|-
|Find what ||.([0-9][0-9])>
|-
|Replace with ||,\1
|}
::Use Wildcards

then,
{|style="font-size: 9pt"
|-
|Find what ||([0-9]),([0-9][0-9][0-9])
|-
|Replace with ||\1^s\2
|-
|Use Wildcards
|}
This method is offered as sample in Wordfast's ''Pandora's box'' commands. Note that Wordfast's "FR" command executes FR actions ''only in the current target segment'', at segment validation time.
Use this FR in automatic mode ("Replace all") if the figures and numbers in your document are essentially financial. If, however, your document mixes scientific figures with financial figures, I recommend using this FR method with a visual confirmation for each replacement (in Ms-Word's "Find" dialog box, click "Find Next" and "Replace" rather than "Replace all").
Back to [[Wordfast Classic User Manual]]

Back to source Wordfast Classic

2017-11-06T07:01:36Z

Samar:

Q: Whoops! My documents have been pretranslated, and I don't have access to the originals. But now I would like to have the originals back, unsegmented. Apparently, it takes a lot of successive Find-Replace passes to un-segment documents...

A: Quite the contrary. It takes only one FR pass to do that.
{|
|-
|Find what || (\{\0\>)(*)(\<\})(*)(\{\>)(*)(\<\0\})
|-
|Replace with ||\2
|}
:: Use Wildcards
:: Set the replacement font format to "not hidden" (check, then uncheck, the "Hidden" checkbox).

The only limitation is, make sure source segments do not contain hidden text. But they rarely do.

'''''Note''': the the same result can be achieved with the Alt+Delete shortcut, pressed when no segment is opened.''
Back to [[Wordfast Classic User Manual]]

Back to source Wordfast Classic

2017-11-06T07:00:41Z

Samar:

Q: Whoops! My documents have been pretranslated, and I don't have access to the originals. But now I would like to have the originals back, unsegmented. Apparently, it takes a lot of successive Find-Replace passes to un-segment documents...

A: Quite the contrary. It takes only one FR pass to do that.
{|
|-
|Find what || (\{\0\>)(*)(\<\})(*)(\{\>)(*)(\<\0\})
|-
|Replace with ||\2
|}
:: Use Wildcards
:: Set the replacement font format to "not hidden" (check, then uncheck, the "Hidden" checkbox).

The only limitation is, make sure source segments do not contain hidden text. But they rarely do.

'''''Note''': the the same result can be achieved with the [[Alt+Delete shortcut]], pressed when no segment is opened.''
Back to [[Wordfast Classic User Manual]]

From Text to Doc: a smarter approach Wordfast Classic

2017-11-06T06:55:57Z

Samar:

The following macro attempts to rebuild a DOC-like document from a TXT document where all lines unconditionally end with a paragraph mark.

Text copied from the Internet, or from PDF files, suffer from this common problem.

Note that there is no sure-fire way of "guessing" how paragraphs should be rebuilt. The following macro uses a few methods that usually give good results, rebuilding most paragraphs correctly. But the final result must be visually checked before professional use.

Sub TextToDoc()

Dim S As Selection, D1 As Range, D2 As Range, IsPara As Boolean, T As String

If Windows.Count = 0 Then MsgBox "Sorry, no document open": Exit Sub

Set S = ActiveWindow.Selection: Set D1 = S.Range: Set D2 = S.Range

S.End = 0

Do While S.Start < S.StoryLength - 1

' Turn off screen refresh for better speed

Application.ScreenUpdating = False

IsPara = False

' We store the last letter of the line into the string T

S.MoveEndUntil vbCr: T = Trim(S.Text): T = Right(T, 1)

' A first attempt to determine if we do have an end of paragraph:

' the line ends with an end-of-sentence

If InStr(".!?", T) > 0 Then IsPara = True

If S.End < S.StoryLength - 3 Then

D1.SetRange S.End + 1, S.End + 2

If IsPara Then D2.SetRange S.End - 1, S.End Else D2.SetRange S.End - 2, S.End - 1

' If the last character of the line is lowercase and the first character of the next line is uppercase,

' we'll assume we've got a real paragraph.

' Disable this for languages that capitalize a lot, like German etc.

If D2.Characters(1).Case = wdLowerCase And D1.Characters(1).Case = wdUpperCase Then IsPara = True

' if the font name or size varies from the current line to the next, we'll also assume

' there's a new paragraph. Very often the case with text copied from PDF; not

' relevant with Txt files.

If S.Font.Name <> D1.Font.Name Then IsPara = True

If S.Font.Size <> D1.Font.Size Then IsPara = True

End If

' If we do not have a paragraph, then join the two lines into one and move on

If Not IsPara Then

S.Start = S.End: S.Delete: S.InsertAfter " "

Else

S.InsertParagraphAfter: S.MoveStart wdParagraph, 1: S.MoveStart wdParagraph, 1

End If

Loop

S.End = 0

MsgBox "Text to Doc conversion finished. Please check the document."

End Sub
Back to [[Wordfast Classic User Manual]]

Checking quotes consistency Wordfast Classic

2017-11-06T06:51:25Z

Samar:

The following macro compares source/target segment to make sure quotes are consistent (same types and numbers of quotes used). Add this macro to WFC/Setup/General, as a QA macro, or as a Post-segmentation macro.

When a quote discrepancy is found, WFC will warn the user, with a choice of getting back to the segment and correcting the problem, or just moving on to the next segment.

Sub CheckQuotes()

If Not ActiveDocument.Bookmarks.Exists("WfSource") Then Exit Sub

Dim I As Integer, Src As String, Trg As String, Quotes As String, Uq As String

Quotes = Chr(34) + Chr(171) + Chr(187) + Chr(147) + Chr(148)

Src = ActiveDocument.Bookmarks("WfSource").Range.Text

Trg = ActiveDocument.Bookmarks("WfTarget").Range.Text

For I = 1 To Len(Quotes)

Uq = Mid(Quotes, I, 1)

If (InStr(Src, Uq) > 0 And InStr(Trg, Uq) = 0) Or (InStr(Src, Uq) = 0 And InStr(Trg, Uq) > 0) Then

If MsgBox("Possible problem with quotes (" + Uq + ".) Fix it?", vbYesNo, "Wordfast") = vbYes Then

Selection.Bookmarks.Add "WfStop"

End If

Exit Sub

Else

If InStr(Src, Uq) > 0 Or InStr(Trg, Uq) > 0 Then

If InStr(Src, Uq) > 0 Then Mid(Src, InStr(Src, Uq), 1) = "*"

If InStr(Trg, Uq) > 0 Then Mid(Trg, InStr(Trg, Uq), 1) = "*"

I = I - 1

End If

End If

Next

End Sub
Back to [[Wordfast Classic User Manual]]

Appendix III - Macro samples Wordfast Classic

2017-11-06T06:47:52Z

Samar:

'''About all macros entered with Pandora's Box "Macro..." commands'''

'''''(PC only)''''': if instead of a macro name, you enter "Keys=" followed by a string of text similar to the one described in the [[Dictionary Wordfast Classic | Dictionary keys]] section, then Wordfast will execute the keystrokes you have defined. For example, using
{| border="1" style="border-collapse: collapse;"
|-
|Keys=L&H;^a{Delete}{SourceSegment}{Home}%tt{Ms-Word}
|}
in conjunction with the English version of L&H's Power Translator 7 text-to-speech function, will read aloud your source segment at the time it is presented for translation.

=== Creating macros ===
Macros should normally be entered in Normal.dot. To do so: in Ms-Word, use Tools/Macro/Visual basic editor (or press Alt+F11) to open the VBA window. In the left side of the window, double-click "Normal". If there is no module, use the Insert menu to add a module. Usually, a new module called "Module1" is added. Double-click it. A window should open to the right: this is where you should copy-paste the macros given below, and edit them as needed. These macros will be saved with Normal.dot when you exit Ms-Word.

The Wordfast hotline does not offer support on VBA and macros. Refer to your Ms-Word manual, or to literature on the subject.

In Wordfast/PB/Macro..., you should enter "Normal.Module1.CheckLength" if, for example, you want to try the first macro described below (either as a QA macro, or as a post-segmentation macro).

To associate a macro with a shortcut: use the View/Toolbars/Customise menu. Click "Keyboard". In the leftmost list, choose "Macros" as category. In the righmost list, click the macro name. Enter the Shortcut in the textbox, then click "Assign". Close the dialog box.

You should refrain from using the following statements or instructions in macros you intend to use with Wordfast:

*'''End''' (this ends all VBA processes, including Wordfast). You can use End in a "MacroMaiden" macro to stop a translation session from being started on certain conditions.

*'''Close''' (Close followed by a file number opened by you is all right, but Close alone closes all opened I/O files, including Wordfast's)

*'''Reset''' (closes all opened I/O files, including Wordfast's)

If you need to open and close I/O files on disk, remember to use the FreeFile() function to ask VBA for an available I/O file number. Otherwise, your macro may conflict with a file already in use by WFC.

If you want your QA or post-segmentation macro to refuse to validate the segment and prompt the user to correct the translation, your macro should add a "WfStop" bookmark anywhere in the document (simply insert a Selection.Bookmarks.Add "WfStop" instruction before ending the macro). If WFC finds such a bookmark, it will cancel segment validation, remove the bookmark and take the user back to the target segment.

Back to [[Wordfast Classic User Manual]]

Appendix III - Macro samples Wordfast Classic

2017-11-06T06:45:32Z

Samar:

'''About all macros entered with Pandora's Box "Macro..." commands'''

'''''(PC only)''''': if instead of a macro name, you enter "Keys=" followed by a string of text similar to the one described in the [[Dictionary Wordfast Classic | Dictionary keys]] section, then Wordfast will execute the keystrokes you have defined. For example, using
{| border="1" style="border-collapse: collapse;"
|-
|Keys=L&H;^a{Delete}{SourceSegment}{Home}%tt{Ms-Word}
|}
in conjunction with the English version of L&H's Power Translator 7 text-to-speech function, will read aloud your source segment at the time it is presented for translation.

=== Creating macros ===
Macros should normally be entered in Normal.dot. To do so: in Ms-Word, use Tools/Macro/Visual basic editor (or press Alt+F11) to open the VBA window. In the left side of the window, double-click "Normal". If there is no module, use the Insert menu to add a module. Usually, a new module called "Module1" is added. Double-click it. A window should open to the right: this is where you should copy-paste the macros given below, and edit them as needed. These macros will be saved with Normal.dot when you exit Ms-Word.

The Wordfast hotline does not offer support on VBA and macros. Refer to your Ms-Word manual, or to literature on the subject.

In Wordfast/PB/Macro..., you should enter "Normal.Module1.CheckLength" if, for example, you want to try the first macro described below (either as a QA macro, or as a post-segmentation macro).

To associate a macro with a shortcut: use the View/Toolbars/Customise menu. Click "Keyboard". In the leftmost list, choose "Macros" as category. In the righmost list, click the macro name. Enter the Shortcut in the textbox, then click "Assign". Close the dialog box.

You should refrain from using the following statements or instructions in macros you intend to use with Wordfast:

 End (this ends all VBA processes, including Wordfast). You can use End in a "MacroMaiden" macro to stop a translation session from being started on certain conditions.

Close (Close followed by a file number opened by you is all right, but Close alone closes all opened I/O files, including Wordfast's)

Reset (closes all opened I/O files, including Wordfast's)

If you need to open and close I/O files on disk, remember to use the FreeFile() function to ask VBA for an available I/O file number. Otherwise, your macro may conflict with a file already in use by Wordfast.

If you want your QA or post-segmentation macro to refuse to validate the segment and prompt the user to correct the translation, your macro should add a "WfStop" bookmark anywhere in the document (simply insert a Selection.Bookmarks.Add "WfStop" instruction before ending the macro). If Wordfast finds such a bookmark, it will cancel segment validation, remove the bookmark and take the user back to the target segment.
Back to [[Wordfast Classic User Manual]]

Appendix III - Macro samples Wordfast Classic

2017-11-06T06:44:00Z

Samar:

'''About all macros entered with Pandora's Box "Macro..." commands'''

'''''(PC only)''''': if instead of a macro name, you enter "Keys=" followed by a string of text similar to the one described in the [https://www.wordfast.net/w/index.php/Dictionary_Wordfast_Classic| Dictionary keys] section, then Wordfast will execute the keystrokes you have defined. For example, using
{| border="1" style="border-collapse: collapse;"
|-
|Keys=L&H;^a{Delete}{SourceSegment}{Home}%tt{Ms-Word}
|}
in conjunction with the English version of L&H's Power Translator 7 text-to-speech function, will read aloud your source segment at the time it is presented for translation.

=== Creating macros ===
Macros should normally be entered in Normal.dot. To do so: in Ms-Word, use Tools/Macro/Visual basic editor (or press Alt+F11) to open the VBA window. In the left side of the window, double-click "Normal". If there is no module, use the Insert menu to add a module. Usually, a new module called "Module1" is added. Double-click it. A window should open to the right: this is where you should copy-paste the macros given below, and edit them as needed. These macros will be saved with Normal.dot when you exit Ms-Word.

The Wordfast hotline does not offer support on VBA and macros. Refer to your Ms-Word manual, or to literature on the subject.

In Wordfast/PB/Macro..., you should enter "Normal.Module1.CheckLength" if, for example, you want to try the first macro described below (either as a QA macro, or as a post-segmentation macro).

To associate a macro with a shortcut: use the View/Toolbars/Customise menu. Click "Keyboard". In the leftmost list, choose "Macros" as category. In the righmost list, click the macro name. Enter the Shortcut in the textbox, then click "Assign". Close the dialog box.

You should refrain from using the following statements or instructions in macros you intend to use with Wordfast:

 End (this ends all VBA processes, including Wordfast). You can use End in a "MacroMaiden" macro to stop a translation session from being started on certain conditions.

Close (Close followed by a file number opened by you is all right, but Close alone closes all opened I/O files, including Wordfast's)

Reset (closes all opened I/O files, including Wordfast's)

If you need to open and close I/O files on disk, remember to use the FreeFile() function to ask VBA for an available I/O file number. Otherwise, your macro may conflict with a file already in use by Wordfast.

If you want your QA or post-segmentation macro to refuse to validate the segment and prompt the user to correct the translation, your macro should add a "WfStop" bookmark anywhere in the document (simply insert a Selection.Bookmarks.Add "WfStop" instruction before ending the macro). If Wordfast finds such a bookmark, it will cancel segment validation, remove the bookmark and take the user back to the target segment.
Back to [[Wordfast Classic User Manual]]

Wordfast Classic User Manual

2017-11-06T06:43:12Z

Samar: /* Appendix II - Language & spell check settings */

Translation Memory Appendix I Wordfast Classic

2017-11-06T06:42:20Z

Samar:

The natural complement of a segmenter is translation memory. Every time a segment is translated, it is stored in the TM. Thus, a TM is a database of Translation Units (TU). A TU records source & target segments, date of creation, languages used, and the ID of the TU's creator. It also has a usage counter that records how many times a TU was re-used. The more a TU is re-used, the more it is valuable.

Translation memory, mostly on technical documents, can save a lot of time, because WFC will recognise segments that were already translated and propose them - you only have to check, validate and move on.

When Wordfast has delimited a segment, it will scan the TM, searching for an exact or approximate match to the source segment. If a match is found, the TU's target segment (the recorded translation) is proposed. Wordfast will display a number, ranging from 0 to 100, that rates the degree of similarity between the document's source segment and the TU's source segment. A 100% match is considered exact. A match under 100% but equal to or above the (user-definable) [https://www.wordfast.net/w/index.php/General_Wordfast_Classic#1.Fuzzy_threshold.3D75 fuzzy threshold] is considered fuzzy; beneath that value, it is considered a no-match and will not be proposed.

If a translation is proposed, pressing Ctrl+Alt+M (Memory) will display the TU that was found during the TM's scan. In the case of a fuzzy match, differences between the document's source segment and the TU's source segment are highlighted. The [https://www.wordfast.net/w/index.php/Wordfast_Classic_User_Manual#TM_and_glossary_management TM management] section contains valuable supplementary information.

If Wordfast has found many matches, pressing Alt+Right/Left will display matches with lower/greater match value.
Back to [[Wordfast Classic User Manual]]

Segmentation Wordfast Classic

2017-11-06T06:38:45Z

Samar:

Wordfast considers a document as a set of segments, a segment being usually a sentence, ending with an end-of-segment punctuation (ESP) such as full stop, question mark etc (the ESPs are customizable in Wordfast's Setup/General tab). Paragraph marks, page breaks, end of cell, tabulators etc will always end a segment. I have highlighted the 10 segments present in the following example:
{|style="margin-left: auto; margin-right: auto; border: none; width: 500px;"
|-
|The mark-ups for retail are as follows: for class A stores, 10%. For class B stores, 15%. Please observe the following chart:
|}

{|style="margin-left: auto; margin-right: auto; background:#c8ccd1; border: 1px solid black; border-spacing: 0; width: 400px;"
|-
|Class
|style="background:#00FFFF" | Class A
|style="background:#00FFFF" |Class B
|-
|Mark-up. No exceptions.
|10%
|15%
|}

{|style="margin-left: auto; margin-right: auto; border: none; background:#FFFF00"
|-
|'''THESE MARK-UPS MUST BE APPLIED AT ALL TIMES.'''
|}
Note that the isolated 10% and 15% are not considered segments. A segment must have at least one translatable item (at least one letter). See the [https://www.wordfast.net/w/index.php/Quick_start_Wordfast_Classic#Translation_.26_Proofreading segment example]. ''It is possible, however, to force Wordfast to segment such untranslatable text: see Pandora's box "SegmentAll" command.
''
Even in the absence of translation memory, a segmenter saves time and boosts productivity. The problems, when translating from a printed document, are:

1. '''Eye strain.''' You will constantly move back and forth between the paper document and the computer screen. Your eyes will have to re-focus many times every minute. A lot of translators end up, after a number of years, with severe sight problems.

2. '''Brain strain.''' After having translated a sentence, you will have to look again at your paper sheet and locate the exact position of the last sentence and read the next one. This exercise requires attention and drains intellectual power.

3. '''Professional errors.''' Because of problem 2, it regularly happens that we skip a sentence, not to mention an entire paragraph, which is a serious professional error. Perhaps the document is made of a series of 100 nearly identical sentences, with slightly different numerical parameters, like

{|
|-
|Please apply the following mark-up for Class A: 10%
|-
|Please apply the following mark-up for Class B: 12% but exclude zone TT-001
|-
|Please apply the following mark-up for Class C: 11.5%
|-
|Please apply the following mark-up for Class F: 13%
|-
|Please apply the following mark-up for Class P: 9%
|-
|style="text-align: right;" |etc for 3 pages!
|}
If one line is forgotten, the translator becomes responsible for a serious professional error.

Working with a segmenter on an electronic original, you will not have to worry a second. The segmenter will faithfully segment the document and ask you to translate every segment, without forgetting a drop. Furthermore, in the above example, once you have translated the first line, Wordfast will actually recognise the next lines and pre-translate them for you.

4. '''More professional errors.''' Look at the second line, with the TT-001 parameter. This parameter should not be translated, but faithfully copied. Now, make sure you type Zero-Zero-One and not O-O-I. Seems easy? Technical documents are full of such Byzantine parameters. To us, they're annoying. To the customer, they're vital. Mis-type just one, and the customer ends up with a faulty manual.

Wordfast has a Quality Assurance algorithm that will warn you if the untranslatable parameters are not faithfully copied from source to target. It also has QA functions to help respect the customer's specs on typography.

5. '''Document layout.''' Look again at the above example on segmentation. If you translate from paper, you will have to re-create that fancy layout, fiddling with formats, tables, borders, colours, fonts etc. With WFC, every target segment is formatted like the source segment (this is true at segment level, the first source character defining the format of the target segment. WFC makes every effort to duplicate the styles of, for example, untranslatable elements; in somes cases, you may have to manually apply bold, italic etc within the segment).

6. '''Terminology consistency.''' Over a large project (say you receive 50 pages every month, so you work for this particular customer 5 days a month, for 12 months), every time you work, you will have to remember the customer's glossary. With WFC, you create and save a particular setup for each customer, which remembers TM and glossaries. WFC will warn you every time the translation's terminology is in conflict with the customer's glossary.

Back to [[Wordfast Classic User Manual]]

Segmentation Wordfast Classic

2017-11-06T06:36:18Z

Samar:

Wordfast considers a document as a set of segments, a segment being usually a sentence, ending with an end-of-segment punctuation (ESP) such as full stop, question mark etc (the ESPs are customizable in Wordfast's Setup/General tab). Paragraph marks, page breaks, end of cell, tabulators etc will always end a segment. I have highlighted the 10 segments present in the following example:
{|style="margin-left: auto; margin-right: auto; border: none; width: 500px;"
|-
|The mark-ups for retail are as follows: for class A stores, 10%. For class B stores, 15%. Please observe the following chart:
|}

{|style="margin-left: auto; margin-right: auto; background:#c8ccd1; border: 1px solid black; border-spacing: 0; width: 400px;"
|-
|Class
|style="background:#00FFFF" | Class A
|style="background:#00FFFF" |Class B
|-
|Mark-up. No exceptions.
|10%
|15%
|}

{|style="margin-left: auto; margin-right: auto; border: none; background:#FFFF00"
|-
|'''THESE MARK-UPS MUST BE APPLIED AT ALL TIMES.'''
|}
Note that the isolated 10% and 15% are not considered segments. A segment must have at least one translatable item (at least one letter). See the [https://www.wordfast.net/w/index.php/Quick_start_Wordfast_Classic#Translation_.26_Proofreading segment example]. ''It is possible, however, to force Wordfast to segment such untranslatable text: see Pandora's box "SegmentAll" command.
''
Even in the absence of translation memory, a segmenter saves time and boosts productivity. The problems, when translating from a printed document, are:

1. '''Eye strain.''' You will constantly move back and forth between the paper document and the computer screen. Your eyes will have to re-focus many times every minute. A lot of translators end up, after a number of years, with severe sight problems.

2. '''Brain strain.''' After having translated a sentence, you will have to look again at your paper sheet and locate the exact position of the last sentence and read the next one. This exercise requires attention and drains intellectual power.

3. '''Professional errors.''' Because of problem 2, it regularly happens that we skip a sentence, not to mention an entire paragraph, which is a serious professional error. Perhaps the document is made of a series of 100 nearly identical sentences, with slightly different numerical parameters, like

{|
|-
|Please apply the following mark-up for Class A: 10%
|-
|Please apply the following mark-up for Class B: 12% but exclude zone TT-001
|-
|Please apply the following mark-up for Class C: 11.5%
|-
|Please apply the following mark-up for Class F: 13%
|-
|Please apply the following mark-up for Class P: 9%
|-
|style="text-align: right;" |etc for 3 pages!
|}
If one line is forgotten, the translator becomes responsible for a serious professional error.
Working with a segmenter on an electronic original, you will not have to worry a second. The segmenter will faithfully segment the document and ask you to translate every segment, without forgetting a drop. Furthermore, in the above example, once you have translated the first line, Wordfast will actually recognise the next lines and pre-translate them for you.

4. '''More professional errors.''' Look at the second line, with the TT-001 parameter. This parameter should not be translated, but faithfully copied. Now, make sure you type Zero-Zero-One and not O-O-I. Seems easy? Technical documents are full of such Byzantine parameters. To us, they're annoying. To the customer, they're vital. Mis-type just one, and the customer ends up with a faulty manual.
Wordfast has a Quality Assurance algorithm that will warn you if the untranslatable parameters are not faithfully copied from source to target. It also has QA functions to help respect the customer's specs on typography.

5. '''Document layout.''' Look again at the above example on segmentation. If you translate from paper, you will have to re-create that fancy layout, fiddling with formats, tables, borders, colours, fonts etc. With Wordfast, every target segment is formatted like the source segment (this is true at segment level, the first source character defining the format of the target segment. Wordfast makes every effort to duplicate the styles of, for example, untranslatable elements; in somes cases, you may have to manually apply bold, italic etc within the segment).

6. '''Terminology consistency.''' Over a large project (say you receive 50 pages every month, so you work for this particular customer 5 days a month, for 12 months), every time you work, you will have to remember the customer's glossary. With Wordfast, you create and save a particular setup for each customer, which remembers TM and glossaries. Wordfast will warn you every time the translation's terminology is in conflict with the customer's glossary.
Back to [[Wordfast Classic User Manual]]

Segmentation Wordfast Classic

2017-11-06T06:32:34Z

Samar:

Wordfast considers a document as a set of segments, a segment being usually a sentence, ending with an end-of-segment punctuation (ESP) such as full stop, question mark etc (the ESPs are customizable in Wordfast's Setup/General tab). Paragraph marks, page breaks, end of cell, tabulators etc will always end a segment. I have highlighted the 10 segments present in the following example:
{|style="margin-left: auto; margin-right: auto; border: none; width: 500px;"
|-
|The mark-ups for retail are as follows: for class A stores, 10%. For class B stores, 15%. Please observe the following chart:
|}

{|style="margin-left: auto; margin-right: auto; background:#c8ccd1; border: 1px solid black; border-spacing: 0; width: 400px;"
|-
|Class
|style="background:#00FFFF" | Class A
|style="background:#00FFFF" |Class B
|-
|Mark-up. No exceptions.
|10%
|15%
|}

{|style="margin-left: auto; margin-right: auto; border: none; background:#FFFF00"
|-
|'''THESE MARK-UPS MUST BE APPLIED AT ALL TIMES.'''
|}
Note that the isolated 10% and 15% are not considered segments. A segment must have at least one translatable item (at least one letter). See the [https://www.wordfast.net/w/index.php/Quick_start_Wordfast_Classic#Translation_.26_Proofreading segment example]. ''It is possible, however, to force Wordfast to segment such untranslatable text: see Pandora's box "SegmentAll" command.
''
Even in the absence of translation memory, a segmenter saves time and boosts productivity. The problems, when translating from a printed document, are:

1. '''Eye strain.''' You will constantly move back and forth between the paper document and the computer screen. Your eyes will have to re-focus many times every minute. A lot of translators end up, after a number of years, with severe sight problems.

2. '''Brain strain.''' After having translated a sentence, you will have to look again at your paper sheet and locate the exact position of the last sentence and read the next one. This exercise requires attention and drains intellectual power.

3. '''Professional errors.''' Because of problem 2, it regularly happens that we skip a sentence, not to mention an entire paragraph, which is a serious professional error. Perhaps the document is made of a series of 100 nearly identical sentences, with slightly different numerical parameters, like

{|width="450px"
|-
|Please apply the following mark-up for Class A: 10%
|-
|Please apply the following mark-up for Class B: 12% but exclude zone TT-001
|-
|Please apply the following mark-up for Class C: 11.5%
|-
|Please apply the following mark-up for Class F: 13%
|-
|Please apply the following mark-up for Class P: 9%
|-
|width="330px" | || etc for 3 pages!
|}
If one line is forgotten, the translator becomes responsible for a serious professional error.
Working with a segmenter on an electronic original, you will not have to worry a second. The segmenter will faithfully segment the document and ask you to translate every segment, without forgetting a drop. Furthermore, in the above example, once you have translated the first line, Wordfast will actually recognise the next lines and pre-translate them for you.

4. '''More professional errors.''' Look at the second line, with the TT-001 parameter. This parameter should not be translated, but faithfully copied. Now, make sure you type Zero-Zero-One and not O-O-I. Seems easy? Technical documents are full of such Byzantine parameters. To us, they're annoying. To the customer, they're vital. Mis-type just one, and the customer ends up with a faulty manual.
Wordfast has a Quality Assurance algorithm that will warn you if the untranslatable parameters are not faithfully copied from source to target. It also has QA functions to help respect the customer's specs on typography.

5. '''Document layout.''' Look again at the above example on segmentation. If you translate from paper, you will have to re-create that fancy layout, fiddling with formats, tables, borders, colours, fonts etc. With Wordfast, every target segment is formatted like the source segment (this is true at segment level, the first source character defining the format of the target segment. Wordfast makes every effort to duplicate the styles of, for example, untranslatable elements; in somes cases, you may have to manually apply bold, italic etc within the segment).

6. '''Terminology consistency.''' Over a large project (say you receive 50 pages every month, so you work for this particular customer 5 days a month, for 12 months), every time you work, you will have to remember the customer's glossary. With Wordfast, you create and save a particular setup for each customer, which remembers TM and glossaries. Wordfast will warn you every time the translation's terminology is in conflict with the customer's glossary.
Back to [[Wordfast Classic User Manual]]

Segmentation Wordfast Classic

2017-11-06T06:30:21Z

Samar:

Wordfast considers a document as a set of segments, a segment being usually a sentence, ending with an end-of-segment punctuation (ESP) such as full stop, question mark etc (the ESPs are customizable in Wordfast's Setup/General tab). Paragraph marks, page breaks, end of cell, tabulators etc will always end a segment. I have highlighted the 10 segments present in the following example:
{|style="margin-left: auto; margin-right: auto; border: none; width: 500px;"
|-
|The mark-ups for retail are as follows: for class A stores, 10%. For class B stores, 15%. Please observe the following chart:
|}

{|style="margin-left: auto; margin-right: auto; background:#c8ccd1; border: 1px solid black; border-spacing: 0; width: 400px;"
|-
|Class
|style="background:#00FFFF" | Class A
|style="background:#00FFFF" |Class B
|-
|Mark-up. No exceptions.
|10%
|15%
|}

{|style="margin-left: auto; margin-right: auto; border: none; background:#FFFF00"
|-
|'''THESE MARK-UPS MUST BE APPLIED AT ALL TIMES.'''
|}
Note that the isolated 10% and 15% are not considered segments. A segment must have at least one translatable item (at least one letter). See the [https://www.wordfast.net/w/index.php/Quick_start_Wordfast_Classic#Translation_.26_Proofreading segment example]. ''It is possible, however, to force Wordfast to segment such untranslatable text: see Pandora's box "SegmentAll" command.
''
Even in the absence of translation memory, a segmenter saves time and boosts productivity. The problems, when translating from a printed document, are:

1. '''Eye strain.''' You will constantly move back and forth between the paper document and the computer screen. Your eyes will have to re-focus many times every minute. A lot of translators end up, after a number of years, with severe sight problems.

2. '''Brain strain.''' After having translated a sentence, you will have to look again at your paper sheet and locate the exact position of the last sentence and read the next one. This exercise requires attention and drains intellectual power.

3. '''Professional errors.''' Because of problem 2, it regularly happens that we skip a sentence, not to mention an entire paragraph, which is a serious professional error. Perhaps the document is made of a series of 100 nearly identical sentences, with slightly different numerical parameters, like

{|width="350px"
|-
|Please apply the following mark-up for Class A: 10%
|-
|Please apply the following mark-up for Class B: 12% but exclude zone TT-001
|-
|Please apply the following mark-up for Class C: 11.5%
|-
|Please apply the following mark-up for Class F: 13%
|-
|Please apply the following mark-up for Class P: 9%
|-
|width="250px" | |etc for 3 pages!
|}
If one line is forgotten, the translator becomes responsible for a serious professional error.
Working with a segmenter on an electronic original, you will not have to worry a second. The segmenter will faithfully segment the document and ask you to translate every segment, without forgetting a drop. Furthermore, in the above example, once you have translated the first line, Wordfast will actually recognise the next lines and pre-translate them for you.

4. '''More professional errors.''' Look at the second line, with the TT-001 parameter. This parameter should not be translated, but faithfully copied. Now, make sure you type Zero-Zero-One and not O-O-I. Seems easy? Technical documents are full of such Byzantine parameters. To us, they're annoying. To the customer, they're vital. Mis-type just one, and the customer ends up with a faulty manual.
Wordfast has a Quality Assurance algorithm that will warn you if the untranslatable parameters are not faithfully copied from source to target. It also has QA functions to help respect the customer's specs on typography.

5. '''Document layout.''' Look again at the above example on segmentation. If you translate from paper, you will have to re-create that fancy layout, fiddling with formats, tables, borders, colours, fonts etc. With Wordfast, every target segment is formatted like the source segment (this is true at segment level, the first source character defining the format of the target segment. Wordfast makes every effort to duplicate the styles of, for example, untranslatable elements; in somes cases, you may have to manually apply bold, italic etc within the segment).

6. '''Terminology consistency.''' Over a large project (say you receive 50 pages every month, so you work for this particular customer 5 days a month, for 12 months), every time you work, you will have to remember the customer's glossary. With Wordfast, you create and save a particular setup for each customer, which remembers TM and glossaries. Wordfast will warn you every time the translation's terminology is in conflict with the customer's glossary.
Back to [[Wordfast Classic User Manual]]

Segmentation Wordfast Classic

2017-11-06T06:28:07Z

Samar:

Wordfast considers a document as a set of segments, a segment being usually a sentence, ending with an end-of-segment punctuation (ESP) such as full stop, question mark etc (the ESPs are customizable in Wordfast's Setup/General tab). Paragraph marks, page breaks, end of cell, tabulators etc will always end a segment. I have highlighted the 10 segments present in the following example:
{|style="margin-left: auto; margin-right: auto; border: none; width: 500px;"
|-
|The mark-ups for retail are as follows: for class A stores, 10%. For class B stores, 15%. Please observe the following chart:
|}

{|style="margin-left: auto; margin-right: auto; background:#c8ccd1; border: 1px solid black; border-spacing: 0; width: 400px;"
|-
|Class
|style="background:#00FFFF" | Class A
|style="background:#00FFFF" |Class B
|-
|Mark-up. No exceptions.
|10%
|15%
|}

{|style="margin-left: auto; margin-right: auto; border: none; background:#FFFF00"
|-
|'''THESE MARK-UPS MUST BE APPLIED AT ALL TIMES.'''
|}
Note that the isolated 10% and 15% are not considered segments. A segment must have at least one translatable item (at least one letter). See the [https://www.wordfast.net/w/index.php/Quick_start_Wordfast_Classic#Translation_.26_Proofreading segment example]. ''It is possible, however, to force Wordfast to segment such untranslatable text: see Pandora's box "SegmentAll" command.
''
Even in the absence of translation memory, a segmenter saves time and boosts productivity. The problems, when translating from a printed document, are:

1. '''Eye strain.''' You will constantly move back and forth between the paper document and the computer screen. Your eyes will have to re-focus many times every minute. A lot of translators end up, after a number of years, with severe sight problems.

2. '''Brain strain.''' After having translated a sentence, you will have to look again at your paper sheet and locate the exact position of the last sentence and read the next one. This exercise requires attention and drains intellectual power.

3. '''Professional errors.''' Because of problem 2, it regularly happens that we skip a sentence, not to mention an entire paragraph, which is a serious professional error. Perhaps the document is made of a series of 100 nearly identical sentences, with slightly different numerical parameters, like

{|
|-
|Please apply the following mark-up for Class A: 10%
|-
|Please apply the following mark-up for Class B: 12% but exclude zone TT-001
|-
|Please apply the following mark-up for Class C: 11.5%
|-
|Please apply the following mark-up for Class F: 13%
|-
|Please apply the following mark-up for Class P: 9%
|-
| |etc for 3 pages!
|}
If one line is forgotten, the translator becomes responsible for a serious professional error.
Working with a segmenter on an electronic original, you will not have to worry a second. The segmenter will faithfully segment the document and ask you to translate every segment, without forgetting a drop. Furthermore, in the above example, once you have translated the first line, Wordfast will actually recognise the next lines and pre-translate them for you.

4. '''More professional errors.''' Look at the second line, with the TT-001 parameter. This parameter should not be translated, but faithfully copied. Now, make sure you type Zero-Zero-One and not O-O-I. Seems easy? Technical documents are full of such Byzantine parameters. To us, they're annoying. To the customer, they're vital. Mis-type just one, and the customer ends up with a faulty manual.
Wordfast has a Quality Assurance algorithm that will warn you if the untranslatable parameters are not faithfully copied from source to target. It also has QA functions to help respect the customer's specs on typography.

5. '''Document layout.''' Look again at the above example on segmentation. If you translate from paper, you will have to re-create that fancy layout, fiddling with formats, tables, borders, colours, fonts etc. With Wordfast, every target segment is formatted like the source segment (this is true at segment level, the first source character defining the format of the target segment. Wordfast makes every effort to duplicate the styles of, for example, untranslatable elements; in somes cases, you may have to manually apply bold, italic etc within the segment).

6. '''Terminology consistency.''' Over a large project (say you receive 50 pages every month, so you work for this particular customer 5 days a month, for 12 months), every time you work, you will have to remember the customer's glossary. With Wordfast, you create and save a particular setup for each customer, which remembers TM and glossaries. Wordfast will warn you every time the translation's terminology is in conflict with the customer's glossary.
Back to [[Wordfast Classic User Manual]]

Segmentation Wordfast Classic

2017-11-06T06:25:31Z

Samar:

Wordfast considers a document as a set of segments, a segment being usually a sentence, ending with an end-of-segment punctuation (ESP) such as full stop, question mark etc (the ESPs are customizable in Wordfast's Setup/General tab). Paragraph marks, page breaks, end of cell, tabulators etc will always end a segment. I have highlighted the 10 segments present in the following example:
{|style="margin-left: auto; margin-right: auto; border: none; width: 500px;"
|-
|The mark-ups for retail are as follows: for class A stores, 10%. For class B stores, 15%. Please observe the following chart:
|}

{|style="margin-left: auto; margin-right: auto; background:#c8ccd1; border: 1px solid black; border-spacing: 0; width: 400px;"
|-
|Class
|style="background:#00FFFF" | Class A
|style="background:#00FFFF" |Class B
|-
|Mark-up. No exceptions.
|10%
|15%
|}

{|style="margin-left: auto; margin-right: auto; border: none; background:#FFFF00"
|-
|'''THESE MARK-UPS MUST BE APPLIED AT ALL TIMES.'''
|}
Note that the isolated 10% and 15% are not considered segments. A segment must have at least one translatable item (at least one letter). See the [https://www.wordfast.net/w/index.php/Quick_start_Wordfast_Classic#Translation_.26_Proofreading segment example]. ''It is possible, however, to force Wordfast to segment such untranslatable text: see Pandora's box "SegmentAll" command.
''
Even in the absence of translation memory, a segmenter saves time and boosts productivity. The problems, when translating from a printed document, are:

1. '''Eye strain.''' You will constantly move back and forth between the paper document and the computer screen. Your eyes will have to re-focus many times every minute. A lot of translators end up, after a number of years, with severe sight problems.

2. '''Brain strain.''' After having translated a sentence, you will have to look again at your paper sheet and locate the exact position of the last sentence and read the next one. This exercise requires attention and drains intellectual power.

3. '''Professional errors.''' Because of problem 2, it regularly happens that we skip a sentence, not to mention an entire paragraph, which is a serious professional error. Perhaps the document is made of a series of 100 nearly identical sentences, with slightly different numerical parameters, like

''Please apply the following mark-up for Class A: 10%

Please apply the following mark-up for Class B: 12% but exclude zone TT-001

Please apply the following mark-up for Class C: 11.5%

Please apply the following mark-up for Class F: 13%

Please apply the following mark-up for Class P: 9%
etc for 3 pages!''

If one line is forgotten, the translator becomes responsible for a serious professional error.
Working with a segmenter on an electronic original, you will not have to worry a second. The segmenter will faithfully segment the document and ask you to translate every segment, without forgetting a drop. Furthermore, in the above example, once you have translated the first line, Wordfast will actually recognise the next lines and pre-translate them for you.

4. '''More professional errors.''' Look at the second line, with the TT-001 parameter. This parameter should not be translated, but faithfully copied. Now, make sure you type Zero-Zero-One and not O-O-I. Seems easy? Technical documents are full of such Byzantine parameters. To us, they're annoying. To the customer, they're vital. Mis-type just one, and the customer ends up with a faulty manual.
Wordfast has a Quality Assurance algorithm that will warn you if the untranslatable parameters are not faithfully copied from source to target. It also has QA functions to help respect the customer's specs on typography.

5. '''Document layout.''' Look again at the above example on segmentation. If you translate from paper, you will have to re-create that fancy layout, fiddling with formats, tables, borders, colours, fonts etc. With Wordfast, every target segment is formatted like the source segment (this is true at segment level, the first source character defining the format of the target segment. Wordfast makes every effort to duplicate the styles of, for example, untranslatable elements; in somes cases, you may have to manually apply bold, italic etc within the segment).

6. '''Terminology consistency.''' Over a large project (say you receive 50 pages every month, so you work for this particular customer 5 days a month, for 12 months), every time you work, you will have to remember the customer's glossary. With Wordfast, you create and save a particular setup for each customer, which remembers TM and glossaries. Wordfast will warn you every time the translation's terminology is in conflict with the customer's glossary.
Back to [[Wordfast Classic User Manual]]

Glossary of terms used in this manual Wordfast Classic

2017-11-06T06:22:22Z

Samar:

'''''(Terms that are already part of the Ms-Word environment are treated briefly - Refer to Ms-Word's Help or Manual for a more complete definition)'''''

== CAT ==
CAT stands for Computer-Assisted Translation. CAT broadly refers to software used by professional translators to boost productivity, and/or enjoy a more comfortable environment. Other acronyms have been added, which only create confusion. In the end, no acronym or naming is ever perfect, and CAT remains the most widely used term.

== TMX ==
TMX stands for Translation Memory eXchange. TMX is a gateway format that allows translation tools to exchange TM content. Most Computer-Assisted Translation (CAT) tools do not use TMX as their native format, but nearly all of them can import from, or export to, the TMX format. As in all conversions, a minor quantity of information may be lost, such as attributes (meta tags).

== XLIFF, TTX, TXML ==
Those are formats made to hold document content during the CAT process. Thus, filters have to used ahead of translation to transform a document (DOC, XLS, PDF, HTML, whatever) into one of those formats; when the translation and proofreading is complete, the same filter must be used to reconstruct the translated document into its original format. Those formats are usually written in XML.

== Translation Unit (TU) ==
A TU is a set of source and target segments. A TU also records creation date, plus optional attributes (see below).

== Translation Memory (TM) ==
A TM is a set of TUs - a database of TUs. Practically every translation tool has its own format. Wordfast has its own format but, unlike most other tools, it’s an open format, which can be edited with a wide variety of editors. The TMX translation memory format is a gateway between different TM formats. Wordfast supports TMX.

== Attributes ==
A TU is a pair of source and target sentences. TUs have built-in attributes that record information (creation date, languages codes, etc.). 5 user-definable attributes can be customized. A typical attribute is the identity of the translator who generated the TU. Other attributes can be subject, client, job number, etc. Each of the 5 attributes can have many values, stored in a drop-down list, visible in the Wordfast/Translation memory/TM Attributes tab. For example, the "Subject" attribute could have three possible values, such as "Scientific", "Literary" and "Business". The value that is visible in the drop-down list is said to be the "active" value.

Attributes can help organizing TMs. See the [[Translation Memory Attributes Wordfast Classic|Attributes section]] for more information.

== Match. ==
One purpose of a translation tool is to find "matches" in the TM for the source segment you are curently translating. When a fuzzy match is found, the segment will display a percentage rating the match’s resemblance with the TMs reference source segment. Bear in mind that this is a purely statistical and blind computational process, it has little to no semantic relevance. Some CAT tools evoke "semantic" neural networks or "linguistic" sense - those claims are as reliable as washing powder hype.

== Penalty. ==
When a match value is being calculated, penalties can be applied to lower the match value. Usually, these penalties are based on an attribute variance. See the relevant section on [https://www.wordfast.net/w/index.php?title=Translation_Memory_Attributes_Wordfast_Classic penalties].

== Microsoft Word (Ms-Word) ==

The application (or software) with which you are currently reading this manual. Ms-Word is generally used at a fraction of its capacities. A professional translator will gain a lot by learning a few advanced functions, such as smart Find-Replaces (see the [https://www.wordfast.net/w/index.php/Wordfast_Classic_User_Manual#Appendix_IV_-_Advanced_Find.2FReplace Appendix IV] below), customizing toolbars and shortcuts, and essential macro knowledge. Consider seeking expert help or training: this investment in time or money will be recouped very quickly.

== Microsoft Office ==
a collection of applications, usually sold and installed together, of which Ms-Word is a member. Ms-Office includes Ms-Word, Excel, PowerPoint, Access, FrontPage, Publisher, Outlook, OneNote, etc, although the restricted version of Ms-Office usually offers only Ms-Word and Excel.

==VBA ==
(Visual Basic for Applications) is a programming language shared by all Ms-Office applications. WFC is written in pure, original VBA, add-ons, OCX, etc - this is why it runs on both Windows and Mac, and is ready to be ported to other platforms.

== Macro. ==
An intensive use of Ms-Word can sometimes lead to highly repetitive tasks (imagine you have to change the first paragraph font on a hundred documents). The macro recorder can record a series of actions done in Ms-Word into a macro named by you; from then on, you can execute this macro as many times as necessary by simply calling the macro dialog box (Alt+F8) and executing the macro, or better, by assigning the macro a shortcut. Macros are written in VBA. Press Alt+F11 or use Tools/Macro/Visual Basic Editor to open the VBA editor window, where your recorded macros will appear, in the code module(s) of your "Normal" template.

== Macrovirus, or Ms-Word virus. ==
Any piece of executable code, in practically any language, is a potential virus. The only difference between an application and a virus is the fact that a virus was created to hurt, harm or destroy. Both Ms-Word documents and Ms-Word templates can contain VBA code, as well as many other formats, like graphics etc.

Use a recent, and if possible "major", antivirus application that handles "Ms-Word", "Office", "Macro", or "VBA" viruses. Serious antivirus developers will offer you regular updates through the web. They will also listen to you, since it is by listening to users under attack and finding answers that they can maintain their database of viruses. Please note that most oeprating systems released after 2010 are inherently protected, and do very well without an antivirus. Many antivirus programs place an immsens burden on the system and end up being worse than the ill they are supposed to cure.

Every release of WFC is scanned before being put on download. As of March 2016, over 35,000 registered users are using WFC, over 6,000 of them contribute daily to a public discussion group.

If your Antivirus reports that WFC is a virus. This happens with roughly one antivirus in 20. WFC holds lots of VBA code and antivirus applications with a shallow or unreliable virus-detection algorithm can falsely report WFC as virus. You should do any, or all, of the following:

Immediately test WFC with another antivirus - perhaps by asking a colleague equipped with a different brand of antivirus. If another antivirus of another brand also reports WFC a virus, then the matter is serious: WFC has perhaps been infected by an infected document or template. Kindly report this to sales@wordfast.net.

Contact the maker of your antivirus, report the alarm, ask them to download WFC as you have done, so they can also test it. Then they should (if they are serious and honest) modify their antivirus software, or prove that WFC is a virus - one of the two.

Contact the WFC hotline at info@wordfast.net. No need to post panicking mails in the mailing list: all such mails until now were proved to be false alarms, and an embarrassment for their authors.

== Documents and Templates ==
A document holds contents, i.e., text.

A Template is a model of document that proposes a preset layout, so that the user can concentrate on contents rather than on appearance. Templates can also be used as Add-Ins, extending Ms-Word's capacities. WFC is an Add-In.

Normally, a template is not opened as a document: it is either used to create new documents with a certain preset appearance, or it is added to Ms-Word's list of templates, using the Tools/Templates & Add-Ins menu. WFC belongs to this last category.

== Toolbars ==
(this is for Ms-Word versions prior to Ms-Word 2007. From Ms-Word 2007 onward, toolbars are contained in a so-called Ribbon, which can be either minimized (Ctrl+F1), or occupy substantial screen real-estate.)

Ms-Word’s "View" menu has a "Toolbars" option (right-click in the toolbar area to get there quickly) that lets you turn toolbars off and on. Turn off toolbars you are not using: they take up space and load the visual field, creating confusion. Use the same menu’s "Customise" option to customise toolbars. In the "Customise" dialog box, go to the "Commands" tab (the second one). Experiment by clicking in the list of commands, holding the button down, dragging a command. Drop its icon in a toolbar of your choice. You have just added a icon to your toolbar. If you make intensive use of a Ms-Word function and keep using menus, it is recommended to drop the corresponding command in a toolbar for quick access.

To remove an icon from a toolbar (the "Customise" dialog box being visible), drag its icon and drop it outside the toolbar: it will be removed.

I encourage WFC users to add the following two icons in either the "Standard" or the "Formatting" toolbar: Format/PasteFormat (play with it to learn how powerful it is. The icon looks like a brush, or a short broomstick); View/FieldCodes. Do not customise WFC’s toolbars.

== Selection ==
Dragging the mouse over text in a document while holding the left button (Windows) or the single button (Mac) will select a portion of the document, which then appears in reverse video, usually white on black. The insertion point (the blinking cursor) disappears when a selection is made. A selection can also be made by holding either Shift key down and moving the cursor by means of the arrow keys.

When a selection is cancelled, the insertion point, or cursor, appears again.

== Bookmarks ==
A bookmark, as in a paper book, is inserted at some position in the document so that we can get back there quickly at a later time. Use the Insert menu to insert a bookmark over the current selection, or at the insertion point. The bookmark has to be given a name. The bookmark will "remember" the selection's position and extent in the document.

Bookmarks are saved together with a document.
Ms-Word's Tools/Options/View dialog box can be used to have the position and span of bookmarks made visible with grey [brackets].

Bookmarks are part of the document, and play a crucial role in documents that have links, automatic indexes, table of contents etc. The translation process may require bookmarks to be transferred into the translated text, at the appropriate position, extending over a corresponding length of text, retaining the same bookmark name. Since two bookmarks cannot have the same name in the same document, WFC proposes ways to handle them during the translation process. Refer to the Bookmarks section.

Refer to Ms-Word's Help or Manual for more information on bookmarks.

== Fields ==
Fields can be inserted into a document using the Insert/Field... menu. A field usually contains a code that has to be calculated, computed or in some way, processed by Ms-Word. Thus, there are two ways of looking at fields: the code, or the result. Use Tools/Options/View to toggle field display modes, or use the Alt+F9 shortcut.

Note that fields are calculated at the moment when they were created. Placing the cursor over a field and pressing F9 will force the update (the recalculation) of the field.

A field that has not been updated may perhaps not show a correct value. For example, a Table of Contents, which is produced by a TOC field, may not necessarily be up-to-date.

If the update produces an error, the field will display an error message.

Refer to Ms-Word's Help or Manual for more information on fields.

== Tags ==
See the section on Tags for a thorough presentation of tags. This term refers only to special untranslatable elements (usually grey or red) found in a particular category of files known as "tagged files", pre-processed for translation with adequate software (Rainbow Horizon, PlusTools, Trados Stagger, etc).

Delimiters (segment delimiters): should not be confused with tags. Delimiters are the purple symbols that delimit the beginning and end of both source and target segments, such as '''(0>''' .

A bad segment is a segment where delimiters have suffered from deletion, addition, or edition. Bad segments create problems at cleanup time. They can be manually fixed by reproducing the set of delimiters found in a healthy segment. The protection of delimiters may have to be turned off (the shortcut is Ctrl+Alt+F12) before you fix delimiters.

== Segment ==
A segment is an elementary unit of translation. Segments are usually sentences. In some cases, it may be necessary to translate entire paragraphs rather than sentences, but this is rarely the case.

During a translation session, the current segment (with the coloured background for source and target segments) is said to be opened. Segments should be left opened only for the duration of the translation process. If you need to make a break, complete your current segment then press Alt+End to close both the segment and the translation session.

== Commit a segment ==
A segment is committed when the translator presses Alt+Down or Alt+End on an opened segment during a translation session, thereby "closing" the currently opened segment. At that moment, if the source/target pair does not exist in the TM, the pair of sentences will be added to the TM (subject to TM rules).

Shift+Alt+End (Close segment) will close a segment without committing it to the TM.

== Source, target ==
Translation is done from a source language (in)to a target language. A translation project may have one source language and many target languages. Most translators, however, deal with one source language and one target language, in which case, we speak of a language pair.

Back to [[Wordfast Classic User Manual]]

Troubleshooting Wordfast Classic

2017-11-06T06:03:28Z

Samar:

Note: the '''Wordfast Knowledge Base''', ''accessible from http://www.wordfast.net has more searchable contents.
''
== ''I installed Wordfast but I don't see the toolbar'' ==
*Press Ctrl+Alt+W.
*If no document is open, open a document.
*If the ''View/Toolbars menu'' has a "Wordfast" item, click it. Otherwise, use the ''Tools/Templates & AddIns''... menu to Add the wordfast.dot ('''dot''', not doc) template to your list of templates.
*See [https://www.wordfast.net/w/index.php?title=Troubleshooting_Wordfast_Classic&action=submit#Wordfast_refuses_to_start Wordfast refuses to start].

== ''Some, or all shortcuts, do not respond any more'' ==
The major causes are:

#A problem with permanent shortcuts assignments. Use Ms-Word's View menu, then "Toolbars/Customise/Keyboard/Reset all" to reset your shortcuts to default values.
#Another template (see Tools/Templates & Add-ins) is active and uses the same shortcut you're trying to use. Possible add-ons include ABBYY fine reader, PDF Writer, and a few others. Try disabling those concurrent add-ons in Ms-Word's Tools/Templates & Add-Ons dialog box, then reset shortcuts as explained in point 1 above, to see if your shortcuts are available again.
#Another application uses the same shortcut, and that application is active in the background. If that is the case, you must make a choice as to which application should use which shortcuts.
#A system utility (like a virtual screen driver) uses the same shortcut. Intel graphic cards, and other brands, use shortcuts such as Ctrl+Alt+left/right to rotate the screen (the screen may not rotate because no external monitor is detected, but the graphic driver still hijacks the shortcuts). This can be verified by right-clicking in an empty zone of your desktop and choosing Properties or Graphic properties (or starting the system's Control Panel, then Display), clicking on the "Advanced" button. Every graphic card designer has its own user interface; just look at the various tabs or submenus, trying to locate the one that sets up keyboard shortcuts that drive the graphic options, and disable them.
#Many translators have '''multiple keyboards''' (usually, the language code is visible in the taskbar like this: [[File:The language code.png]] ), and the system uses an Alt combination to toggle keyboards. If that is the case, in Windows, use the Control panel, then "Keyboard", then look at the shortcuts used to change keyboard: turn them off (this is recommended since keyboards are better changed with the mouse, willingly) or adapt them. Keyboard-changing shortcuts that work in combination with the Alt key interfere with Wordfast. ''You can also right-click the [[File:The language code.png]] icon in the taskbar, choose "Properties" to access keyboard settings and disable the Alt-based shortcuts.. On some systems, this setting could be in the Control Panel's "Regional options".''

If you tried all methods described above and shortcuts are not functional, exit Ms-Word, search for, then rename all Normal.dot files to Normal.old and restart Ms-Word.

With Word 2002.2003, the first key I type when a segment opens does not respond
See the "FirstKeyControl"command in Pandora's Box section.

== ''My keyboard keeps changing (shifts from one language to another)'' ==
See the previous point on shortcuts, list item 4.

If the first key you type when a segment opens does not respond, see the previous item.

== ''I can't type special, or accented, characters any more'' ==

Same as above.

== ''My Antivirus says Wordfast is, or contains, a virus'' ==

See the relevant section on [https://www.wordfast.net/w/index.php?title=Glossary_of_terms_used_in_this_manual_Wordfast_Classic&action=submit#Macroviruses.2C_or_Ms-Word_viruses macro viruses] in the Glossary of terms used in the manual section.

== ''Ms-Word 97'' ==
One known bug, documented by Microsoft at http://support.microsoft.com/default.aspx?scid=kb;EN-US;q162349 is that, if the document has graphics that were pasted into it (as it is often the case with screenshots), Ms-Word97 may not have the resources needed to display them, and the graphics could be
changed into empty boxes containing a red cross. All subsequent efforts to restore the graphics will fail.

This is likely to happen if the document was created, or manipulated, with a non-SR1 Ms-Word97 (SR-1 being a bug fix, or patch, distributed by Microsoft - see Microsoft, not Wordfast, support). Furthermore, having the "Allow fast save" option checked in Tools/Options/Save aggravates the situation.

I recommend turning off "Allow fast save" (and do frequent manual saves using Ctrl-S) with Ms-Word97, because this feature is known to drain resources and create problems.

== ''Microsoft Outlook'' ==

Some versions of Outlook can be a problem if they are set to use Ms-Word as email editor. If this is the case, uncheck the "Protect delimiters..." checkbox in Wordfast/Setup/Segments. Then, in Ms-Word, use View/Toolbars/Customize/Keyboard/Reset all to reset shortcuts. Close Ms-Word and Outlook and try again. If this does not solve the problem, you may have to either not use Wordfast and Outlook at the same time, or use Outlook's HTML-mode edition (not Ms-Word as an email editor), which offers most of the facilities provided by Ms-Word.

== ''The main Wordfast setup window does not display any text'' ==
Make sure the Tahoma font is available in your system. Normally, when Ms-Word is installed, the Tahoma font is automatically added to your system by Microsoft.

== ''I see lots of blue, or red, text with a line through in the middle'' ==
Turn off the revision ("Track changes") mode. Remove the protection, if there is one (Tools/Remove protection) before translation. Normally, documents in revision or "Track changes" mode should not be translated with a CAT tool until this mode is turned off.

== ''Wordfast (not Ms-Word) says "Sorry, this file is read-only"'' ==
This means your translation memory (not your document) has a read-only attribute. This usually happens if the TM was intentionally read-protected, or if the TM comes from a CD-ROM. With your disc explorer, right-click the file, click Property (with a Mac, use Option+i) and uncheck the read-only checkbox.

Also, on some recent systems, certain folders are write-protected. Make sure your TM is not located in an Ms-Office folder, or in any system folder. Create a folder for translation memories.

''Do not confuse this message with Ms-Word warning you that a document is in read-only mode.''

== ''Erratic behaviour during translation sessions'' ==
Some ''Pandora's box'' commands need to be turned off after use, like "BetterMatch=Write", "Skip" commands etc, because they may produce unwanted results on documents other than the ones for which they were set. The same consideration applies to macros: turn them off when they're no longer needed. If you never used ''Pandora's box'' commands however, there is no need to check this point.

Remember that some options set in Tools/Options and Tools/Autocorrect may also cause erratic behaviour (such as replacing quotes, changing text automatically etc).

Make sure some of Wordfast's shortcuts are not hijacked by another template.

If the first key you type when a segment opens does not respond, see the "FirstKeyControl" command in Pandora's Box section.

See the point on [https://www.wordfast.net/w/index.php?title=Troubleshooting_Wordfast_Classic&action=submit#Wordfast_refuses_to_start invalid or corrupted normal.dot].
See the point on multiple keyboards.

== ''My keyboard keeps changing'' ==
*See the point on multiple keyboards.
*Make sure you are not on "Automatic language recognition". This option can create problems and make Ms-Word "panic" during translation. Use Ms-Word's Tools/Language menu to make sure.

==''"Ms-Word does not look the same", or "After a translation session, Ms-Word displays paragraph marks or field codes or a strange font, or pictures are not displayed etc."'' ==
During translation, Wordfast has to modify some display options in order to function properly. When a translation session ends, your previous display setup should normally be restored. If this is not the case, don't panic - just click Ms-Word's Tools menu, then Options (Edit/Preferences in some Mac versions), click the View tab and check/uncheck the necessary options to restore your usual display setup. Get acquainted with the "Options" dialog box and the various View settings.

You may also have to use Ms-Word's View menu and change from/into the "Page" view.

== ''Ill-behaved documents'' ==
#Some customers send documents that were originally attached to a template (this can be checked by opening the document, then using the Tools/Templates & Add-Ins menu and looking at the top textbox). If a reference is made to a template that is not present in your hard disc, expect trouble. Contact your customer. ''Deleting the reference to a non-existent template will usually solve the problem, but should be done with the customer's consent and knowledge, so that the template attachment can later be restored.''
#If the Ms-Word document has many fields (Tools/Options/View/Field codes or Alt+F9 can be used to display field codes) that refer to non-existent graphics, indexes, links etc, you can have erratic document behaviour. If your customer cannot provide you with the referenced objects, make sure that Tools/Options/General does not require Ms-Word to update links when opening the document.
#Large RTF files with complex layout and/or fields, which were created with a different software, or even with just another version of Ms-Word, can behave strangely and cause Ms-Word to crash. In desperate cases, try importing a problem document into a new, empty document, (using copy-paste or Insert/file), with the client's consent.

Always inform the client if you have to fiddle with documents.
The bottom line is that the customer should provide the translator with a clean, stable document. A good third of service calls to the Wordfast hotline are actually caused by ill-behaved documents, and another third to systems, or Ms-Word installations, that are not stable.

== ''Ill-behaved templates'' ==
You are welcome to run Wordfast together with other templates or Ms-Word add-ins, but please understand that I cannot guarantee the reliability of such a practice. A lot of shortcut conflicts or mysterious behaviours with Ms-Word and Wordfast are simply due to the presence of other templates or Ms-Word add-ins that monopolise shortcuts.

Ms-Word templates and add-ins are programs that usually contain VBA code. There are many ways of writing VBA, some of which are not really professional, resulting in poorly engineered applications.

Microsoft has introduced a much more reliable and modern environment with the 32-bit VBA architecture of Word97 and higher versions. Unfortunately, many programmers still use antiquated techniques dating back to Ms-Dos (8-bit architecture), or Windows 3 (16-bit architecture) using, for example, absolute I/O file numbers, instead of using the FreeFile function offered by Microsoft, or WORDBASIC functions.

== ''A document was closed with an open segment:'' ==
Try starting a session by opening the segment that was left opened. If this does not solve the problem, close the document without saving it, go to the segment that was left opened and do the following:

#Open the Bookmark dialog box from the Insert menu. Delete all bookmarks that begin with Wf (such as WfTU, WfSource, WfTarget etc).
#Delete all paragraph marks '''within''' the problem segment. As a result, the coloured backgrounds disappear. If they don't, select the paragraph then use Ctrl-Q or Format/Borders and shadings to remove backgrounds.

Make sure the delimiters (the little purple symbols) are correctly set.

Save your document and resume the translation session.

== ''I want to service my TM, but I keep getting the message "This file is used by another process".'' ==
Most likely, the TM is being shared through a network, or in two simultaneous Ms-Word sessions, or the previous translation session was not terminated properly. Do not service a TM currently used across a network. If you're not networking, close Ms-Word. With your disc Explorer, find the folder where the translation memory is, and delete the translation memory file that has the ".net" extension - and only this file. If this does not work, reboot your system.

== ''Terminology recognition does not work:'' ==
Run the following checklist:

*your glossaries are text-only or Unicode text files where source and target entries (and optional comments) are separated with tabulators;
*you glossary has been reorganised using the relevant WFC/Terminology/Glossary/Reorganise button;
*the relevant Wordfast/Terminology/Glossary/"This glossary is active" checkbox is checked.

== ''Slow performance or frequent "out of memory messages":'' ==
Most systems are overloaded with fonts. Many applications add unwanted fonts to your system without telling you. In Windows, see the \Windows\Fonts (or \Winnt\Fonts) folder. If you have more than 50 fonts, consider the following. Create a \Windows\Font2 folder and drag-drop into this new folder all the fonts that are found in \Windows\Fonts and that are not vital. If these fonts are later required, you can drag them back into the \Windows\Fonts (or \WinNt\Fonts) folder. Note that any font that is located in the \Windows\Font folder burdens your system, gobbling RAM and resources. There are many other ways to make sure your system is streamlined for optimal professional use, but this is beyond the scope of this manual. In any case, if your system is used for games, or intensive multimedia activities, or other purposes, especially by other people, expect trouble. You cannot use a workstation for gaming, or heavy graphical/multimedia applications, and expect it to be utterly stable with the full Microsoft Office environment.

On slower computers (less than 200 MHz and/or less than 32 Mb RAM, and/or very slow video cards), I recommend using some or all of the following methods:

#Turn off spell/grammar check ''during'' the translation session (make spell-check an after-translation task).
#Decrease the colour depth of your display to 16 or 256 colours, at least during translation sessions.
#Using Tools/Options, uncheck the "Paginate" option to prevent Ms-Word from constantly re-paginating your document. Work in Normal view mode, not Page or Print view.
#Turn off the "Autosave" function in Tools/Options or Preferences. ''During translation, press Ctrl+S once in a while to save your document.''
#In extreme cases, use the Draft font option in the View tab of the ''Tools/Options'' menu in Ms-Word; in the ''View'' menu, select ''Normal'' rather than ''Page''.
#With large TMs (over 50,000 TUs), reorganise the TM at least once a week with the Reorganise button in Wordfast/Translation memories/TM. Do some [https://www.wordfast.net/w/index.php/Wordfast_Classic_User_Manual#TM_and_glossary_management TM maintenance].
#Uncheck "Allow fast save" in Tools/Options/Save (or "Preferences" in a Mac). "Allow fast save" is known to drain resources and may cause Word to crash.
#Desperate cases: pre-translate (Wordfast/Tools/Tools/Translate) the document before working on it.

== ''Bugs and Crashes'' ==
Windows 9.xx, Millenium (and 2000 to some extent), as well as Mac OS 7, 8, 9, are not "mission-critical", or bullet-proof OSs like Unix or Linux, for example. They're variations of earlier OSs that were running with late-XXth-century limited resources, over a rather primitive architecture.

All applications, but especially Ms-Word, keep robbing more RAM resources to display fonts, graphics, temporary text editing, undo information, etc as you open documents, scroll, type, edit etc. Furthermore, Ms-Word does many tasks in the background, while those OSs are not really multi-tasking.

If Ms-Word crashes while Wordfast is active: re-start your system and try the same task again with a "fresh" system. Temporarily turn off fancy system add-ons that are supposed to miraculously guard your system from crashes, boost power, enhance the desktop, defragment in the background etc. Just keep the antivirus, but temporarily turn it off for testing purposes.

In Ms-Word, turn off any '''template or add-in''' other than Wordfast (go to Tools/Templates & Add-Ins, uncheck templates and add-ins). If you can duplicate the same crash (or freezing) on a bare system, Wordfast may be the cause of the crash. In case of freezing, try pressing Ctrl+Pause (or Ctrl+Break on some keyboards), then click End if a dialog box appears. If you have the chance, try executing the same job or task with Wordfast on another computer before concluding that Wordfast is responsible for the crash.

In such a case, make sure you have the latest version of Wordfast (compare your version with the one in [https://www.wordfast.net www.wordfast.net]). If the crash persists with the latest version of Wordfast, use the hotline on [https://www.wordfast.net www.wordfast.net] to let us know. We will process the report as quickly as possible.

''The Windows 2000+Ms-Word 2000 (or higher versions) combination is known to be significantly more stable.''

== ''Wordfast refuses to start'' ==
This could be due to one of the following reasons:

#'''Invalid Normal.Dot.''' Close Ms-Word. Search for all files named "Normal.dot" and rename them all "Normal.old", or delete them all. If no file named "Normal.dot" comes up, see the point on [https://www.wordfast.net/w/index.php/Removing_Wordfast_Classic#Manual_removal hidden folders], then search for Normal.dot files again. Start Ms-Word and Wordfast again.
#'''Ms-Word installation problem.''' Your Ms-Word installation is not complete, although Ms-Word works fine. VBA modules could be outdated or missing. Refer to your Ms-Word manual for a proper and full installation of Ms-Word. You can also press Alt+F11 in Ms-Word to open the Visual Basic window. In the Tools menu, click the first sub-menu and make sure that the following 4 references are checked:
- Visual Basic for Applications
- Ms-Word X Object library (''where X can be 7 or greater'')
- Microsoft Forms 2.0 Object library
- Microsoft Office X Object library (''where X can be 7 or greater'')

== ''MacIntosh'' ==
Use simple folder and file names for TMs and glossaries, without accented letters, spaces, punctuation, or symbols, less than 32 characters in length. This point does not concern documents, only TMs and glossaries.
Back to [[Wordfast Classic User Manual]]

Tags in a WFC TM Wordfast Classic

2017-11-06T05:39:52Z

Samar:

When dealing with so-called tagged documents, a WFC TM records placeholders for tags. Those placeholders have a &tX; format, where X is the order of appearance of tags in the source segment. The X order is noted A (ANSI decimal 65), B, C, etc., up to ANSI decimal code 165. Thus, there can be no more than 100 tags in a WFC segment.

For example, the following "tagged" source segment:

<div style="text-align: center;font-family: Courier New"> <FONT FACE="Helvetica"> This is some text.</div>

would appear, in a Wordfast TM as:

<div style="text-align: center;font-family: Courier New"> &tA;This is some text.&tB; </div>

At translation time, when WFC pulls a TU from the TM and is about to propose the TU's target segment as a translation candidate, WFC uses a substitution algorithm to dress the proposed target segment with the full "real" tags, taken from the document's (not the TM's) source segment, using a triangulation method:

Document's source segment <—> TM's source segment <—> TM's target segment

The triangulation can be successful only if all target tags have a "parent" tag in the source segment. In the rare cases when the TM's target segment has tags that do not appear in the TM's source segment (orphaned tags), WFC records the full syntax of these orphaned tags at TU creation time, so that they can be restored properly at translation time, when the target segment must be proposed with the correct format. If we have, at TU creation time:

{|
|-
|In source segment: || <FONT FACE="Arial">This is some text: 
|-
|In target segment: || <FONT FACE="Arial">Voici du texte&nbsp;: 
|}
then the target segment would be recorded in the TM as:

&tA;Voici du texte&t=;&nbsp;&t=;:

where &t= opens the original tag syntax (&nbsp; in our example) and ; (colon) closes the sequence.

Other examples of segments:

{|
|-
|In source segment: ||<FT>This is some text<AR> here<FT>.
|-
|In target segment: ||<AR>Voici du texte<FT> ici.
|-
|In TM TU source: ||&tA;This is some text&tB; here&tA;.
|-
|In TM TU target: ||&tB;Voici du texte&tA; ici.
|-
|
|-
|
|-
|
|-
|
|-
|In source segment: ||<FT>This is some text<AR> here.
|-
|In target segment: ||<AR>Voici du<AR> texte<X;X> ici<FT>.
|-
|In TM TU source: ||&tA;This is some text&tB; here.
|-
|In TM TU target: ||&tB;Voici du&tB; texte&t=;<X;X>&t=; ici&tA;.
|}

In most translation memory systems, TMs are overloaded with tags that do not belong there. A TM takes significance when its content is put to (re-) use, meaning, when its past translations are leveraged for a new transation project. Re-using TM content is only done in the presence of a new document to be translated. In other words, at use time, the software operates a triangulation between a new document's new source segment which contains the new formatting, and an existing TM source/target pair which contains formatting placeholders.
Back to [[Wordfast Classic User Manual]]

The WFC Translation memory format Wordfast Classic

2017-11-06T05:30:51Z

Samar:

A Wordfast translation memory is a tab-delimited text file. It's the simplest of all formats - it can be opened with text editors, like Notepad, or unicode-compliant word processors, as well as with Excel. Wordfast TMs can be regular ANSI (8-bit) text, or Unicode UTF-16 (both little-endian and big-endian).

A Translation Memory (TM) is a set of lines (paragraphs) of text. In a pure text file where the display does not wrap, lines are paragraphs. The very first line is a header, and all other lines are TUs (Translation Units), sometimes called "entries". Lines/Entries/TUs are sets of fields, a field being any text (even lack of text, which denotes an empty field) followed by a tabulator. In other words, the Wordfast TM format is Tab-delimited Text, which is arguably one of the oldest, most robust, open, easy to manipulate data format ever. In the header (the very first line in a TM), each field begins with a % (per cent) mark.

=== Fields making up a TU: ===
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
|Field
|Example
|Format
|Remark
|-
|Date
|20041231~165410
|yyyymmdd~hhmmss - the example here means 31 December 2004, at 16:54:10, local time. See note on the tilde ~ character further below.
|Optional field: can be empty
|-
|User ID
(Attribute #1)
|YAC
|Initials of the TU's creator.
|Optional field: can be empty
|-
|Counter
|5
|A number between 0 and 9999 that records how many times this TU was proposed as a 100% match and accepted, meaning, re-used, as it is.
|Optional field: can be empty
|-
|Source language
|EN-US
|TMX-compliant language code (but case-insensitive with WFC). It is made of a two-letter ISO language code, and optinally, a dash followed by a two-letter local variant.
|Optional field: can be empty.
Rule: field cannot be longer than 5 characters.
|-
|Source segment
|Red Riding Hood was walking in the woods.
|The source segment. Maximum size: 8000 Unicode characters.
|Should contain at least one character.
|-
|Target language
|FR-FR
|Language code, TMX-compliant
|Optional field: can be empty.
Rule: field cannot be longer than 5 characters.
|-
|Target segment
|Le Petit Chaperon Rouge se promenait dans les bois.
|The target segment. Maximum size: 8000 Unicode characters.
|Optional field: can be empty
|-
|Attribute #2 (optional)
|EL
|rowspan=4 | A mnemonic (maximum length=64 characters; no space allowed) for user-defined attribute #1. See Wordfast's "Sample" attributes.
|Optional field: can be empty+tabulator omitted
|-
|Attribute #3 (optional)
|PS
|Optional field: can be empty+tabulator omitted
|-
|Attribute #4 (optional)
|
|Optional field: can be empty+tabulator omitted
|-
|Attribute #5 (optional)
|
|Optional field: can be empty+tabulator omitted
|}
Here are the first two paragraphs (the TM's header and first Translation Unit) of a TM where the TU is defined as in the table above. Paragraphs are long, so they may wrap in your display - but there are only two paragraphs:
{|style="font-family: Arial Narrow; font-size: 10"
|-
|%20041231~160445
|%YAC, Yves A. Champollion
|%TU=00000000
|%EN-US %Wordfast TM v5.0
|%FR-FR
|%87412764
|-
|20041231~165410 YAC
|5
|EN-US
|Red Riding Hood was walking in the woods.
|FR-FR
|Le Chaperon Rouge se promenait dans les bois.
|EL
|PS
|}

The header (first line in the TU) in the example above defines two attributes named Domain and Client. The first TU contains two attribute values: EL and PS. Either attribute names (unique per TM) or attribute values (multiple: one per TU) can be made of up to 64 characters (acronyms are used in the example above: EL for Electronics and PS for a client, however, longer descriptors can be used). Question/exclamation marks ( ! ¡ ? ¿ ) are forbidden in attributes names and values.

When reading a TU, Wordfast defaults on the side of optimism in case the TU does not look correct or canonical. When in a TU:

*the date is missing or wrong: if WFC is executing a loop that parses TUs, then it will take the previous TU's date and increment it with one second, otherwise, WFC takes the local machine's current date and time;
*the user ID is empty, WFC will assume the TM header's user ID. If it is missing, WFC will use the user's identity as defined in Ms-Word. If it is missing, WFC will use XX;
*• a language code is missing or incorrec: WFC assumes the TM's header language code.

== Files ==

A translation memory (e.g. WfMemory) generates the following files:

{| border="1" style="border-collapse: collapse;"
|-
|WfMemory.Txt
|This is the translation memory. Do not delete it unless you want to discard it.
|-
|WfMemoryXXX.Itx
|This is the TM's index. Deletion not a problem, since WFC re-creates it automatically when needed.
|-
|WfMemory.Bak
|This is a copy of the TM before any Reorganisation, Merge or Sort operation. Deletion not a problem.
|-
|WfMemory.Old
|When a new BAK file is created and replaces an existing BAK file, WFC renames the existing WfMemory.Bak file WfMemory.Old if the existing BAK file appears larger than the new BAK file that overwrites it. Deletion not a problem.
|}

If you need to archive a TM, or send it to a colleague, the only necessary file is the .TXT file. It is recommended to reorganise a TM before sending it to someone (using the WFC/Translation memory/TM/Reorganise button).

If a translation memory is lost, remember that (if you keep copies of your translated, segmented files) cleaning up the segmented files that produced the TM will recreate the corresponding TM with its translation units.

== Fault detection (ignoring malformed TUs) ==

WFC considers that a TU is a bad one based on counting how many tabulators are in a line of text. A line of text with less than 6 tabulators cannot form a valid TU. Another fault-detection method used by WFC is that language codes should not be no longer than 5 characters. When language codes of more than 5 characters are encountered during a TM reorganisation, it is an indicator that something is amiss with that particular TU, and it is assumed to be faulty. WFC does not halt on faulty TUs, it ignores them.

Remarks:

The date does not necessarily have a tilde (~) separating date and time. Any printable character can be used there, except a number. WFC uses the tilde (~), the equal (=) sign, and the star sign(*). The equal sign means the TU was "marked" (flagged) by WFC's data editor. This has no consequence on the TU's status: it remains fully valid. Although WFC always records the date and time when writing a TU, the date and time are optional and could be empty (or even made of an invalid date) in which case WFC would simply assume the current computer's date and time, or previous TU incremented by one second, if in a sequential loop. Dates and times are "local", taken from the local computer's clock.

If any optional field is left empty, its trailing tabulator should be present. For a TU to be valid, there must be at least six tabulators, with the fifth field (the source segment, located between the fourth and the fifth tabulator) made of at least one printable character.

The date's first character (a number from 0 to 9, usually, a number 2 if the TU was created in the current millenium) can be "x". It means that this TU is not valid anymore - WFC marked it for future deletion. The first full reorganisation of the TM by WFC will erase this TU. Do not remove the "x", or replace it with a number, unless you know what you are doing.

Back to [[Wordfast Classic User Manual]]

Placeholders Wordfast Classic

2017-11-06T05:29:39Z

Samar:

Placeholders are used to encapsulate a few special characters, or tags. A WFC placeholder always has the following format: &tX; where X can take various values: &t=; &tA; &t1; &t#; , etc.
{| border="1" style="border-collapse: collapse;"
|-
|&t1;
|a placeholder for a Word graphic;
|-
|&t2;
|a placeholder for a Word footnote/endnote;
|-
|&t9;
|a tabulator mark;
|-
|&t#;
|a manual line feed;
|-
|&tA; &tB; &tC; ... &t¥;
|constitute 100 placeholders for tags;
|-
|&t=<some tag="here">;
|records an "unknown" tag. Unknown tags are found only in a target segment, but not in the matching source segment. Colons in the tag are escaped with a backward slash \.
|}

'''Note to engineers'''

The ampersand, quotes, as well as < and > characters are not considered escaping character. The ampersand is not escaped. The WFC TM format is not a member of the SGML/HTML/XML family. The WFC TM format is simple text, tab-delimited.

'''Limitation:''' A WFC TM would create a slightly fuzzy match with text containing the &tX; placeholder, as in this very paragraph. That is a known and accepted minor limitation that has not happened yet in decades.

Back to [[Wordfast Classic User Manual]]

The WFC Translation memory format Wordfast Classic

2017-11-06T05:23:31Z

Samar:

A Wordfast translation memory is a tab-delimited text file. It's the simplest of all formats - it can be opened with text editors, like Notepad, or unicode-compliant word processors, as well as with Excel. Wordfast TMs can be regular ANSI (8-bit) text, or Unicode UTF-16 (both little-endian and big-endian).

A Translation Memory (TM) is a set of lines (paragraphs) of text. In a pure text file where the display does not wrap, lines are paragraphs. The very first line is a header, and all other lines are TUs (Translation Units), sometimes called "entries". Lines/Entries/TUs are sets of fields, a field being any text (even lack of text, which denotes an empty field) followed by a tabulator. In other words, the Wordfast TM format is Tab-delimited Text, which is arguably one of the oldest, most robust, open, easy to manipulate data format ever. In the header (the very first line in a TM), each field begins with a % (per cent) mark.

=== Fields making up a TU: ===
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
|Field
|Example
|Format
|Remark
|-
|Date
|20041231~165410
|yyyymmdd~hhmmss - the example here means 31 December 2004, at 16:54:10, local time. See note on the tilde ~ character further below.
|Optional field: can be empty
|-
|User ID
(Attribute #1)
|YAC
|Initials of the TU's creator.
|Optional field: can be empty
|-
|Counter
|5
|A number between 0 and 9999 that records how many times this TU was proposed as a 100% match and accepted, meaning, re-used, as it is.
|Optional field: can be empty
|-
|Source language
|EN-US
|TMX-compliant language code (but case-insensitive with WFC). It is made of a two-letter ISO language code, and optinally, a dash followed by a two-letter local variant.
|Optional field: can be empty.
Rule: field cannot be longer than 5 characters.
|-
|Source segment
|Red Riding Hood was walking in the woods.
|The source segment. Maximum size: 8000 Unicode characters.
|Should contain at least one character.
|-
|Target language
|FR-FR
|Language code, TMX-compliant
|Optional field: can be empty.
Rule: field cannot be longer than 5 characters.
|-
|Target segment
|Le Petit Chaperon Rouge se promenait dans les bois.
|The target segment. Maximum size: 8000 Unicode characters.
|Optional field: can be empty
|-
|Attribute #2 (optional)
|EL
|rowspan=4 | A mnemonic (maximum length=64 characters; no space allowed) for user-defined attribute #1. See Wordfast's "Sample" attributes.
|Optional field: can be empty+tabulator omitted
|-
|Attribute #3 (optional)
|PS
|Optional field: can be empty+tabulator omitted
|-
|Attribute #4 (optional)
|
|Optional field: can be empty+tabulator omitted
|-
|Attribute #5 (optional)
|
|Optional field: can be empty+tabulator omitted
|}
Here are the first two paragraphs (the TM's header and first Translation Unit) of a TM where the TU is defined as in the table above. Paragraphs are long, so they may wrap in your display - but there are only two paragraphs:
{|style="font-family: Arial Narrow; font-size: 10"
|-
|%20041231~160445
|%YAC, Yves A. Champollion
|%TU=00000000
|%EN-US %Wordfast TM v5.0
|%FR-FR
|%87412764
|-
|20041231~165410 YAC
|5
|EN-US
|Red Riding Hood was walking in the woods.
|FR-FR
|Le Chaperon Rouge se promenait dans les bois.
|EL
|PS
|}

The header (first line in the TU) in the example above defines two attributes named Domain and Client. The first TU contains two attribute values: EL and PS. Either attribute names (unique per TM) or attribute values (multiple: one per TU) can be made of up to 64 characters (acronyms are used in the example above: EL for Electronics and PS for a client, however, longer descriptors can be used). Question/exclamation marks ( ! ¡ ? ¿ ) are forbidden in attributes names and values.

When reading a TU, Wordfast defaults on the side of optimism in case the TU does not look correct or canonical. When in a TU:

*the date is missing or wrong: if WFC is executing a loop that parses TUs, then it will take the previous TU's date and increment it with one second, otherwise, WFC takes the local machine's current date and time;
*the user ID is empty, WFC will assume the TM header's user ID. If it is missing, WFC will use the user's identity as defined in Ms-Word. If it is missing, WFC will use XX;
*• a language code is missing or incorrec: WFC assumes the TM's header language code.

'''Files'''

A translation memory (e.g. WfMemory) generates the following files:

{| border="1" style="border-collapse: collapse;"
|-
|WfMemory.Txt
|This is the translation memory. Do not delete it unless you want to discard it.
|-
|WfMemoryXXX.Itx
|This is the TM's index. Deletion not a problem, since WFC re-creates it automatically when needed.
|-
|WfMemory.Bak
|This is a copy of the TM before any Reorganisation, Merge or Sort operation. Deletion not a problem.
|-
|WfMemory.Old
|When a new BAK file is created and replaces an existing BAK file, WFC renames the existing WfMemory.Bak file WfMemory.Old if the existing BAK file appears larger than the new BAK file that overwrites it. Deletion not a problem.
|}

If you need to archive a TM, or send it to a colleague, the only necessary file is the .TXT file. It is recommended to reorganise a TM before sending it to someone (using the WFC/Translation memory/TM/Reorganise button).

If a translation memory is lost, remember that (if you keep copies of your translated, segmented files) cleaning up the segmented files that produced the TM will recreate the corresponding TM with its translation units.

'''Fault detection (ignoring malformed TUs)'''

WFC considers that a TU is a bad one based on counting how many tabulators are in a line of text. A line of text with less than 6 tabulators cannot form a valid TU. Another fault-detection method used by WFC is that language codes should not be no longer than 5 characters. When language codes of more than 5 characters are encountered during a TM reorganisation, it is an indicator that something is amiss with that particular TU, and it is assumed to be faulty. WFC does not halt on faulty TUs, it ignores them.

Remarks:

The date does not necessarily have a tilde (~) separating date and time. Any printable character can be used there, except a number. WFC uses the tilde (~), the equal (=) sign, and the star sign(*). The equal sign means the TU was "marked" (flagged) by WFC's data editor. This has no consequence on the TU's status: it remains fully valid. Although WFC always records the date and time when writing a TU, the date and time are optional and could be empty (or even made of an invalid date) in which case WFC would simply assume the current computer's date and time, or previous TU incremented by one second, if in a sequential loop. Dates and times are "local", taken from the local computer's clock.

If any optional field is left empty, its trailing tabulator should be present. For a TU to be valid, there must be at least six tabulators, with the fifth field (the source segment, located between the fourth and the fifth tabulator) made of at least one printable character.

The date's first character (a number from 0 to 9, usually, a number 2 if the TU was created in the current millenium) can be "x". It means that this TU is not valid anymore - WFC marked it for future deletion. The first full reorganisation of the TM by WFC will erase this TU. Do not remove the "x", or replace it with a number, unless you know what you are doing.

Back to [[Wordfast Classic User Manual]]

The WFC Translation memory format Wordfast Classic

2017-11-05T19:09:43Z

Samar:

A Wordfast translation memory is a tab-delimited text file. It's the simplest of all formats - it can be opened with text editors, like Notepad, or unicode-compliant word processors, as well as with Excel. Wordfast TMs can be regular ANSI (8-bit) text, or Unicode UTF-16 (both little-endian and big-endian).

A Translation Memory (TM) is a set of lines (paragraphs) of text. In a pure text file where the display does not wrap, lines are paragraphs. The very first line is a header, and all other lines are TUs (Translation Units), sometimes called "entries". Lines/Entries/TUs are sets of fields, a field being any text (even lack of text, which denotes an empty field) followed by a tabulator. In other words, the Wordfast TM format is Tab-delimited Text, which is arguably one of the oldest, most robust, open, easy to manipulate data format ever. In the header (the very first line in a TM), each field begins with a % (per cent) mark.

=== Fields making up a TU: ===
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
|Field
|Example
|Format
|Remark
|-
|Date
|20041231~165410
|yyyymmdd~hhmmss - the example here means 31 December 2004, at 16:54:10, local time. See note on the tilde ~ character further below.
|Optional field: can be empty
|-
|User ID
(Attribute #1)
|YAC
|Initials of the TU's creator.
|Optional field: can be empty
|-
|Counter
|5
|A number between 0 and 9999 that records how many times this TU was proposed as a 100% match and accepted, meaning, re-used, as it is.
|Optional field: can be empty
|-
|Source language
|EN-US
|TMX-compliant language code (but case-insensitive with WFC). It is made of a two-letter ISO language code, and optinally, a dash followed by a two-letter local variant.
|Optional field: can be empty.
Rule: field cannot be longer than 5 characters.
|-
|Source segment
|Red Riding Hood was walking in the woods.
|The source segment. Maximum size: 8000 Unicode characters.
|Should contain at least one character.
|-
|Target language
|FR-FR
|Language code, TMX-compliant
|Optional field: can be empty.
Rule: field cannot be longer than 5 characters.
|-
|Target segment
|Le Petit Chaperon Rouge se promenait dans les bois.
|The target segment. Maximum size: 8000 Unicode characters.
|Optional field: can be empty
|-
|Attribute #2 (optional)
|EL
|rowspan=4 | A mnemonic (maximum length=64 characters; no space allowed) for user-defined attribute #1. See Wordfast's "Sample" attributes.
|Optional field: can be empty+tabulator omitted
|-
|Attribute #3 (optional)
|PS
|Optional field: can be empty+tabulator omitted
|-
|Attribute #4 (optional)
|
|Optional field: can be empty+tabulator omitted
|-
|Attribute #5 (optional)
|
|Optional field: can be empty+tabulator omitted
|}
Here are the first two paragraphs (the TM's header and first Translation Unit) of a TM where the TU is defined as in the table above. Paragraphs are long, so they may wrap in your display - but there are only two paragraphs:
{|style="font-family: Arial Narrow; font-size: 10"
|-
|%20041231~160445
|%YAC, Yves A. Champollion
|%TU=00000000
|%EN-US %Wordfast TM v5.0
|%FR-FR
|%87412764
|-
|20041231~165410 YAC
|5
|EN-US
|Red Riding Hood was walking in the woods.
|FR-FR
|Le Chaperon Rouge se promenait dans les bois.
|EL
|PS
|}

The header (first line in the TU) in the example above defines two attributes named Domain and Client. The first TU contains two attribute values: EL and PS. Either attribute names (unique per TM) or attribute values (multiple: one per TU) can be made of up to 64 characters (acronyms are used in the example above: EL for Electronics and PS for a client, however, longer descriptors can be used). Question/exclamation marks ( ! ¡ ? ¿ ) are forbidden in attributes names and values.

When reading a TU, Wordfast defaults on the side of optimism in case the TU does not look correct or canonical. When in a TU:

*''the date is missing'': if Wordfast is executing a loop that parses TUs, then it will take the previous TU's date and increment it with one second, otherwise, it will take the local machine's current date and time;
*''the user ID is empty'', Wordfast will assume the TM header's user ID. If it is missing, Wordfast will use the user's identity as defined in Ms-Word. If it is missing, Wordfast will use XX;
*''a language code is missing or incorrect - but less than 6 characters:'' Wordfast will use the current TM's header language code (the code in the first line of the TM).

'''Fault detection''' (Wordfast considering that a TU is a bad one) is based on counting how many tabulators are in a line of text. A line of text with less than 6 tabulators cannot form a valid TU. Another fault-detection method used by Wordfast is that language codes should not be no longer than 5 characters. When language codes of more than 5 characters are encountered during a TM reorganisation, it is an indicator that something is amiss with that particular TU, and it is assumed to be faulty.

Remarks:
#The date does not necessarily have a tilde (~) separating date and time. Any printable character can be used there, except a number. Wordfast uses the tilde (~), and the equal (=) sign. The equal sign, in the Wordfast editor, means the TU was "marked" (flagged). This has no consequence at all on the TU's status: it remains fully valid. Although Wordfast always records the date and time when writing a TU, the date and time are optional and could be empty (or even made of an invalid date) in which case Wordfast would simply assume the current date and time. All dates and times are "local", taken from the local computer's clock.
#If any optional field is left empty, its trailing tabulator should be present. For a TU to be valid, there must be at least six tabulators, with the fifth field (the source segment, located between the fourth and the fifth tabulator) made of at least one printable character.
#The date's first character (a number from 0 to 9, usually, a number 2 if the TU was created in the current millenium) can appear to be "x". This means that this TU is not valid anymore. The first full reorganisation of the TM by Wordfast will erase this TU. Do not remove the "x", or replace it with a number, unless you know what you are doing.
Back to [[Wordfast Classic User Manual]]

The WFC Translation memory format Wordfast Classic

2017-11-05T19:08:26Z

Samar:

A Wordfast translation memory is a tab-delimited text file. It's the simplest of all formats - it can be opened with text editors, like Notepad, or unicode-compliant word processors, as well as with Excel. Wordfast TMs can be regular ANSI (8-bit) text, or Unicode UTF-16 (both little-endian and big-endian).

A Translation Memory (TM) is a set of lines (paragraphs) of text. In a pure text file where the display does not wrap, lines are paragraphs. The very first line is a header, and all other lines are TUs (Translation Units), sometimes called "entries". Lines/Entries/TUs are sets of fields, a field being any text (even lack of text, which denotes an empty field) followed by a tabulator. In other words, the Wordfast TM format is Tab-delimited Text, which is arguably one of the oldest, most robust, open, easy to manipulate data format ever. In the header (the very first line in a TM), each field begins with a % (per cent) mark.

=== Fields making up a TU: ===
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
|Field
|Example
|Format
|Remark
|-
|Date
|20041231~165410
|yyyymmdd~hhmmss - the example here means 31 December 2004, at 16:54:10, local time. See note on the tilde ~ character further below.
|Optional field: can be empty
|-
|User ID
(Attribute #1)
|YAC
|Initials of the TU's creator.
|Optional field: can be empty
|-
|Counter
|5
|A number between 0 and 9999 that records how many times this TU was proposed as a 100% match and accepted, meaning, re-used, as it is.
|Optional field: can be empty
|-
|Source language
|EN-US
|TMX-compliant language code (but case-insensitive with WFC). It is made of a two-letter ISO language code, and optinally, a dash followed by a two-letter local variant.
|Optional field: can be empty.
Rule: field cannot be longer than 5 characters.
|-
|Source segment
|Red Riding Hood was walking in the woods.
|The source segment. Maximum size: 8000 Unicode characters.
|Should contain at least one character.
|-
|Target language
|FR-FR
|Language code, TMX-compliant
|Optional field: can be empty.
Rule: field cannot be longer than 5 characters.
|-
|Target segment
|Le Petit Chaperon Rouge se promenait dans les bois.
|The target segment. Maximum size: 8000 Unicode characters.
|Optional field: can be empty
|-
|Attribute #2 (optional)
|EL
|rowspan=4 | A mnemonic (maximum length=64 characters; no space allowed) for user-defined attribute #1. See Wordfast's "Sample" attributes.
|Optional field: can be empty+tabulator omitted
|-
|Attribute #3 (optional)
|PS
|Optional field: can be empty+tabulator omitted
|-
|Attribute #4 (optional)
|
|Optional field: can be empty+tabulator omitted
|-
|Attribute #5 (optional)
|
|Optional field: can be empty+tabulator omitted
|}
Here are the first two paragraphs (the TM's header and first Translation Unit) of a TM where the TU is defined as in the table above. Paragraphs are long, so they may wrap in your display - but there are only two paragraphs:
{|style="font-family: Arial Narrow; font-size: 10"
|-
|%20041231~160445
|%YAC, Yves A. Champollion
|%TU=00000000
|%EN-US %Wordfast TM v5.0
|%FR-FR
|%87412764
|-
|20041231~165410 YAC
|5
|EN-US
|Red Riding Hood was walking in the woods.
|FR-FR
|Le Chaperon Rouge se promenait dans les bois.
|EL
|PS
|}
When reading a TU, Wordfast defaults on the side of optimism in case the TU does not look correct or canonical. When in a TU:

*''the date is missing'': if Wordfast is executing a loop that parses TUs, then it will take the previous TU's date and increment it with one second, otherwise, it will take the local machine's current date and time;
*''the user ID is empty'', Wordfast will assume the TM header's user ID. If it is missing, Wordfast will use the user's identity as defined in Ms-Word. If it is missing, Wordfast will use XX;
*''a language code is missing or incorrect - but less than 6 characters:'' Wordfast will use the current TM's header language code (the code in the first line of the TM).

'''Fault detection''' (Wordfast considering that a TU is a bad one) is based on counting how many tabulators are in a line of text. A line of text with less than 6 tabulators cannot form a valid TU. Another fault-detection method used by Wordfast is that language codes should not be no longer than 5 characters. When language codes of more than 5 characters are encountered during a TM reorganisation, it is an indicator that something is amiss with that particular TU, and it is assumed to be faulty.

Remarks:
#The date does not necessarily have a tilde (~) separating date and time. Any printable character can be used there, except a number. Wordfast uses the tilde (~), and the equal (=) sign. The equal sign, in the Wordfast editor, means the TU was "marked" (flagged). This has no consequence at all on the TU's status: it remains fully valid. Although Wordfast always records the date and time when writing a TU, the date and time are optional and could be empty (or even made of an invalid date) in which case Wordfast would simply assume the current date and time. All dates and times are "local", taken from the local computer's clock.
#If any optional field is left empty, its trailing tabulator should be present. For a TU to be valid, there must be at least six tabulators, with the fifth field (the source segment, located between the fourth and the fifth tabulator) made of at least one printable character.
#The date's first character (a number from 0 to 9, usually, a number 2 if the TU was created in the current millenium) can appear to be "x". This means that this TU is not valid anymore. The first full reorganisation of the TM by Wordfast will erase this TU. Do not remove the "x", or replace it with a number, unless you know what you are doing.
Back to [[Wordfast Classic User Manual]]

WFC segmentation rules Wordfast Classic

2017-11-04T02:41:26Z

Samar:

The largest possible unit of segmentation with Wordfast, as with most translation tools, is the paragraph. Paragraphs end with a paragraph mark (ANSI 13 with or without page feed ANSI 10), page feed (ANSI 12), end of cell (ANSI 7). Not that the manual line feed (ANSI 11) does not end a paragraph. Nevertheless, Wordfast can be set up to consider the manual line feed as ending a segment: see the section on [[customizing ESPs]], or the note further below.

Wordfast attempts to recognize individual segments within a paragraph by parsing the paragraph and looking for End of Segment Punctuations (ESPs). The default ESPs used by Wordfast are . : ! ? as well as the tabulator mark, noted ^t by Wordfast, and the manual line feed, noted ^l . Users can edit the list of ESPs to fine-tune segmentation, although that is not recommended, as it breaks their TM compatibility with most other TMs.

If ''all'' ESPs are deleted, Wordfast segments at the whole paragraph level. This is not recommended, as some paragraphs may exceed the acceptable segment limit of 8,000 characters (nearly two large pages!) imposed by Wordfast, although segments of that size are very rare. If a segment is larger than 8,000 characters, Wordfast ignores the extra characters, which can be segmented with the "ForceSegment" shortcut.

To remain compatible with most other tools, Wordfast does not consider the manual line feed (noted ^l ) as ending a segment. Users can add ^l to the user-defined list of ESPs in Wordfast to break segments when a manual line feed (ANSI code 11, decimal) is encountered, which is generally considered more logical. However, by default, Wordfast does not end a segment at a manual line feed.

Within a paragraph, Wordfast will consider that it has reached the end of a segment if:

#the said segment ends with an ESP, AND
#a space is immediately after the ESP,AND
#the letter following that space is a capital letter, AND
#the character immediately before the ESP is not a number.

Rules 2, 3, 4 can be disabled by the user in the Wordfast > Setup > Segments pane. With CJK languages, rule 2 is always disabled, and the "wide-character" equivalent punctuations are also used.
{| border="1" style="border-collapse: collapse;"
|-style="background:# #c8ccd1"
|the following sequence
|example
|produces
|-
|full stop, space, uppercase.
|Hello world. Hello world.
|2 segments
|-
|full stop, space, lowercase.
|Hello world. hello world.
|1 segment
|-
|full stop, space, number.
|Hello world. 10 Hello world.
|1 segment
|-
|full stop, no space, upper/lowercase.
|Hello world.Hello world.
|1 segment
|}
'''Rule concerning the beginning of a segment'''
If a segment begins with a series of numbers (or combination of numbers and full stops) followed by a full stop, Wordfast assumes that it's a numbering scheme, and skips the apparent numbering scheme. With the following text:

10. This is text

the segment will begin with "This is text", skipping the initial "10.". If the initial number is actually part of the segment, translators can press Alt+Delete (Unsegment), then select the entire sentence and press Shift+Alt+Down (ForceSegment). Translators can also set Wordfast to always override the number-skipping behaviour with the "[[SegmentAll]]" command in Pandora's Box.

== Parts of text not considered as segments. ==
Isolated series/combinations of numbers, spaces, punctuation do not consitute a segment. For example,

100

100.89.67.90

100 (9078) // 67-56

will be skipped by Wordfast as being "numbers". But

100a

100.89.67ö90

100 (9078) // 67-56 é

will all be segmented, because at least one letter is present in each series of numbers/punctuations. The "[[SegmentAll]]" command in Pandora's Box will force Wordfast to segment isolated series of numbers/spaces/punctuation at all times.

== Abbreviation ==

Users can specify a list of abbreviations in WFC > Setup > Segments. WFC will not end a segment if its last series of characters matches any of the abbreviations, case-sensitive. For example, if "Pr." is listed in the user-specified abbreviations, which is the case by default, the following sentence will be considered as making up a whole segment...

 Here is Pr. Johnson.

... although "Pr." is followed by a full stop, a space, and a capital letter.

There are many translation-time shortcuts and options that let the translator fine-tune segments to expand them, shrink them, or force a selection of text to be considred a whole segment, regardless of rules. However, translators should remember to prefer default segmentation whenever possible, to remain compatible with other TMs.

back to [[ Wordfast Classic User Manual]]

WFC segmentation rules Wordfast Classic

2017-11-03T22:46:22Z

Samar:

The largest possible unit of segmentation with Wordfast, as with most translation tools, is the paragraph. Paragraphs end with a paragraph mark (ANSI 13 with or without page feed ANSI 10), page feed (ANSI 12), end of cell (ANSI 7). Not that the manual line feed (ANSI 11) does not end a paragraph. Nevertheless, Wordfast can be set up to consider the manual line feed as ending a segment: see the section on [[customizing ESPs]], or the note further below.

Wordfast attempts to recognize individual segments within a paragraph by parsing the paragraph and looking for End of Segment Punctuations (ESPs). The default ESPs used by Wordfast are . : ! ? as well as the tabulator mark, noted ^t by Wordfast, and the manual line feed, noted ^l . Users can edit the list of ESPs to fine-tune segmentation, although that is not recommended, as it breaks their TM compatibility with most other TMs.

If ''all'' ESPs are deleted, Wordfast segments at the whole paragraph level. This is not recommended, as some paragraphs may exceed the acceptable segment limit of 8,000 characters (nearly two large pages!) imposed by Wordfast, although segments of that size are very rare. If a segment is larger than 8,000 characters, Wordfast ignores the extra characters, which can be segmented with the "ForceSegment" shortcut.

To remain compatible with most other tools, Wordfast does not consider the manual line feed (noted ^l ) as ending a segment. Users can add ^l to the user-defined list of ESPs in Wordfast to break segments when a manual line feed (ANSI code 11, decimal) is encountered, which is generally considered more logical. However, by default, Wordfast does not end a segment at a manual line feed.

Within a paragraph, Wordfast will consider that it has reached the end of a segment if:

#the said segment ends with an ESP, AND
#a space is immediately after the ESP,AND
#the letter following that space is a capital letter, AND
#the character immediately before the ESP is not a number.

Rules 2, 3, 4 can be disabled by the user in the Wordfast > Setup > Segments pane. With CJK languages, rule 2 is always disabled, and the "wide-character" equivalent punctuations are also used.
{| border="1" style="border-collapse: collapse;"
|-style="background:# #c8ccd1"
|the following sequence
|example
|produces
|-
|full stop, space, uppercase.
|Hello world. Hello world.
|2 segments
|-
|full stop, space, lowercase.
|Hello world. hello world.
|1 segment
|-
|full stop, space, number.
|Hello world. 10 Hello world.
|1 segment
|-
|full stop, no space, upper/lowercase.
|Hello world.Hello world.
|1 segment
|}
'''Rule concerning the beginning of a segment'''
If a segment begins with a series of numbers (or combination of numbers and full stops) followed by a full stop, Wordfast assumes that it's a numbering scheme, and skips the apparent numbering scheme. With the following text:

10. This is text

the segment will begin with "This is text", skipping the initial "10.". If the initial number is actually part of the segment, translators can press Alt+Delete (Unsegment), then select the entire sentence and press Shift+Alt+Down (ForceSegment). Translators can also set Wordfast to always override the number-skipping behaviour with the "[[SegmentAll]]" command in Pandora's Box.

'''Parts of text not considered as segments.'''
Isolated series/combinations of numbers, spaces, punctuation do not consitute a segment. For example,

100

100.89.67.90

100 (9078) // 67-56

will be skipped by Wordfast as being "numbers". But

100a

100.89.67ö90

100 (9078) // 67-56 é

will all be segmented, because at least one letter is present in each series of numbers/punctuations. The "[[SegmentAll]]" command in Pandora's Box will force Wordfast to segment isolated series of numbers/spaces/punctuation at all times.

'''Abbreviations'''

Users can specify a list of abbreviations in WFC > Setup > Segments. WFC will not end a segment if its last series of characters matches any of the abbreviations, case-sensitive. For example, if "Pr." is listed in the user-specified abbreviations, which is the case by default, the following sentence will be considered as making up a whole segment...

 Here is Pr. Johnson.

... although "Pr." is followed by a full stop, a space, and a capital letter.

There are many translation-time shortcuts and options that let the translator fine-tune segments to expand them, shrink them, or force a selection of text to be considred a whole segment, regardless of rules. However, translators should remember to prefer default segmentation whenever possible, to remain compatible with other TMs.

back to [[ Wordfast Classic User Manual]]

The TM/Glossary editor Wordfast Classic

2017-11-03T01:39:16Z

Samar:

Click the "TM/Glossary editor" [[File:TM Glossary editor icon.png]] icon in Wordfast's main toolbar, or the last icon in any of the glossary toolbars to start the TM/Glossary editor. Outside a translation session, glossary toolbars can be opened using the Ctrl+Alt+Right shortcut (and closed using the Ctrl+Alt+Left shortcut). During a translation session, the Ctrl+Alt+G shortcut pressed on a word or selection will open the glossary toolbar(s) of the glossary(ies) where the term was found. Glossary toolbars open only on glossaries that were specified in Wordfast/Terminology.

Wordfast's TM/Glossary editor is intended to make maintenance easy and intuitive, and offers practically identical methods for TMs and glossaries. Once the editor is opened, you can scroll up/down the data, edit/delete/add entries.
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
!Shortcut
!Effect
|-
|Space bar
|mark/unmark entries
|-
|Ctrl+A
|mark/unmark all entries
|-
|Shift+Ctrl+A
|reverse the current marking
|-
|Ctrl+X
|cut all marked entries
|-
|Ctrl+Y
|undo the previous cut operation
|-
|Ctrl+C
|copy all marked entries to Wordfast's own clipboard
|-
|Ctrl+V
|paste Wordfast's clipboard's contents to the end of the file
|-
|Ctrl+D
(right-click)
|Toggle the display of all, or only marked, TUs.
|-
|Ctrl+O
|Open another file (another glossary or antoher TM).
|}
Note: cutting (deleting) a single line (or entry, or TU) is a soft operation, meaning it can be reversed or undone (press Delete twice on an entry to see the toggling effect). When an entry is cut (or soft-deleted), it appears as a blank line, but when it is selected, the source and target data appears in the editor's bottom blue/green display. Ctrl+Delete will permanently erase cut entries by "packing", i.e. rewriting, the entire TM or glossary.

The editor's Filter or Sort dialog box (Press F7 or click the column header are) gives access to three types of operation on data: Filter, Sort and Special filters.

== Filter ==

Filtering means you define a condition with a Field Condition Argument format.

For example:

{| border="1" style="border-collapse: collapse;"
|-
|SourceText & "MyText
|}
where & means "contains", or
{| border="1" style="border-collapse: collapse;"
|-
|Counter = 0

|}
See more examples in the Filter or Sort dialog box' Help.

When Argument is made of text, it must be enclosed in straight quotes like this: "MyText".

The effect of a filter is that only the entries that conform to the filter's condition(s) will be made visible in the glossary editor. When a filter has been set, using the Mark methods (mark, unmark, copy, paste, cut) will operate only on visible entries.

In the Data Editor, use the F8 shortcut to cancel a filter.

== Sort ==

Sort files only if you need. Sorting can take some time, because the entire file is actually (physically) sorted, not just the display of the file. Sort when necessary. WFC adds the convenience of being able to sort source or target text on the number of words or characters in segments. This can be useful for terminology extraction.

== Replace ==

This is a standard Find-replace operation. The operation is done on one specific field at a time.

With this feature, you can replace a word like "Smith" into "Jones" in the TM's target segments. Be careful that find-replace operations do not produce unwanted results.

Example: Changing language codes in your TM

Suppose your source language code is EN and you want to change it into EN-US: Select "SourceLanguageCode" in the list of fields, enter EN as search, enter EN-US as replacement. Click OK.

== TM Tools (Special Filters) ==

TM Tools contains special filters are meant to perform operations that would be difficult or impossible to perform with just filtering and sorting. These operations are:

'''Mark redundant entries'''

(there are various types of definition for a redundant entry, depending on whether you use a TM or a glossary). This feature marks entries that are considered duplicates. Once the marking is done, you can review them, then delete them all by using the Cut shortcut (Ctrl+X) followed by a hard-delete command (Ctrl+Delete). Of course, with a TM, such entries are grouped if the TM is sorted on the source segment.

'''Reverse source and target'''

This will rewrite the current file and reverse source and target fields.

'''Export to Unicode'''

Exports the current file to a unicode format.

'''Export to TMX (TM only)'''

Exports the current file to the TMX format. The TM is not overwritten - a new file is created, and it has a .tmx extension.

'''Remove tags'''

This special filter removes tags from a TM. This is recommended after finishing a project with tagged files. The leverage of TUs with tags is precious within the scope of a particular project. Tagged leveraged outside a project is an extreme rarity. This is why it is recommended to remove tags from a TM that will be used on different translation projects. Tags bloat TMs to a ridiculous extent.

'''Export as segment document'''

This filter will create a segmented document in Ms-Word that contains all Translation Units (TUs) in the TM.

'''Repair and compact TM'''

This maintenance will rewrite the entire TM, removing lines marked for deletion, removing empty lines. It will re-create the index. This filter can be run if the TM does not perform well, or before storing or archiving a TM.

'''Mark suspicious TUs'''

This powerful feature can clean up a TM by marking TUs that look suspicious for various reasons. After the filter was executed, TUs that loo, suspicious are simply marked (checked, or selected). You can review and delete them as needed.

'''Rewrite Entries with a Mask'''

This powerful feature is used to replace a particular field, or many fields, with some given value, or erase the content of the fields, in all visible entries. Visible entries are those that are displayed in the editor. If a filter is set, only some entries are visible.

You are first presented with an empty entry (a mask). You can:

*enter an equal sign (=) followed by some text in any field, in which case, the text after the equal sign will replace whatever is found is the corresponding fields in all visible entries in the file (TM or glossary);
*enter "=null" in a field to erase the content of that field.

All fields that are left blank (or which do not begin with = followed by at least one character) in the mask will remain untouched in the file.

The following mask would replace all User fields with "FOO", and erase Attribute fields 1, 2, 3, 4 in the entire TM:

'''Practical example:''' "I have that older, bulky TM that combines TUs from various translators. I want these entries grouped by user (translator) name. I want to delete all entries that have a usage counter of less than 2, and that are older than August 31, 2004. Then I want to review them one by one and perhaps have some entries not marked for deletion if I think they're useful after all. Only then will I erase all marked entries that remain".

*Start the TM/Glossary editor, click the Tools button.
*Sort on "User".
*Set the following filter: Counter < 2 AND Date < 20040831 .
*Press Ctrl+D to view only marked entries.
*Review marked entries, un-mark the ones you wish to keep.
*Press Ctrl+X to cut all marked entries.
*Press Ctrl+Delete to permanently erase all marked entries.
*Sort on Date to revert to a "natural" order in the TM.

Note that all operations except #7 can be undone.

TMs and glossaries must be created for one language pair only. I also advise keeping separate TMs for different subject (domain) and client, and having them in dedicated folders so that keeping track of them, and especially backing them up, remains easy.

TMs keep growing all the time. Most of TUs are very unkikely to be re-used, while a minority of them will. Since WFC keeps track of how many times a TU is re-used in the usage counter field, it is advised, when a TM reaches a large size (over 100,000 TUs), or when finishing a large translation project, to perform a compression by eliminating all TUs that have never been re-used. As a result, the TM's size will be considerably reduced, while its overall efficiency will be preserved. To do so:

*Start the TM/glossary editor on the required TM.
*Press F7, and set the following filter: Counter = 0 . Click OK.
*Mark all (Ctrl+A). Cut marked (Ctrl+X). Hard-delete (Ctrl+Delete).

'''Creating a startup TM.''' Create one single, large TM by combining all the TMs you have. Delete all TUs that have a usage counter of less than 3. To compress further, you can visually review the TM and delete TUs that are unlikely to pop up again. To do so, sort the TM on "SourceWords", go to the end of it and review the TUs that are the longest, where there are likely "ghost" candidates, longish TUs that are unikely to show up again. Delete them. This TM can then be used as a primer - if you need to create a new, empty TM, better use a copy of that TM instead, because it contains a "Top 50" or perhaps a "Top 1000" of your previous work. It's like priming a pump with a cup of water.

A Wordfast TM may contain TUs where the first figure of the date (normally "2", but it can be "1" for TMs created in the previous millenium) is replaced with "x", and which, as a consequence, appear to be "cut" in the editor. This is because, in the course of a translation session, the TU was proposed as 100% match on a green background, but the target segment was edited, so WFC has deleted the original version of the TU in the TM and has re-written the TU's edited version at the end of the TM. This is normal. Do not "resurrect" or un-delete such TUs: their correct version appears further down in the TM. During translation sessions, WFC is blind to TUs that are marked "x". As a rule of thumb, perform a "Reorganisation" of the TM before working on it. This is done with the WFC > Translation memory > TM "Reorganise" button and it erases all TUs that were marked as "Deleted" with an "x" mark in the course of previous translation sessions.

Sharing TMs with other WFC users, or with other CAT tools.

Sharing TMs with other CAT tools: open the TM with the TM/Glossary editor, click Tools, apply the "Export TM as TMX" special filter. The TM will be re-written as TMX and the file's extension will be changed to .tmx.

Back to [[Wordfast Classic User Manual]]

The TM/Glossary editor Wordfast Classic

2017-11-03T01:25:04Z

Samar:

Click the "TM/Glossary editor" [[File:TM Glossary editor icon.png]] icon in Wordfast's main toolbar, or the last icon in any of the glossary toolbars to start the TM/Glossary editor. Outside a translation session, glossary toolbars can be opened using the Ctrl+Alt+Right shortcut (and closed using the Ctrl+Alt+Left shortcut). During a translation session, the Ctrl+Alt+G shortcut pressed on a word or selection will open the glossary toolbar(s) of the glossary(ies) where the term was found. Glossary toolbars open only on glossaries that were specified in Wordfast/Terminology.

Wordfast's TM/Glossary editor is intended to make maintenance easy and intuitive, and offers practically identical methods for TMs and glossaries. Once the editor is opened, you can scroll up/down the data, edit/delete/add entries.
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
!Shortcut
!Effect
|-
|Space bar
|mark/unmark entries
|-
|Ctrl+A
|mark/unmark all entries
|-
|Shift+Ctrl+A
|reverse the current marking
|-
|Ctrl+X
|cut all marked entries
|-
|Ctrl+Y
|undo the previous cut operation
|-
|Ctrl+C
|copy all marked entries to Wordfast's own clipboard
|-
|Ctrl+V
|paste Wordfast's clipboard's contents to the end of the file
|-
|Ctrl+D
(right-click)
|Toggle the display of all, or only marked, TUs.
|-
|Ctrl+O
|Open another file (another glossary or antoher TM).
|}
Note: cutting (deleting) a single line (or entry, or TU) is a soft operation, meaning it can be reversed or undone (press Delete twice on an entry to see the toggling effect). When an entry is cut (or soft-deleted), it appears as a blank line, but when it is selected, the source and target data appears in the editor's bottom blue/green display. Ctrl+Delete will permanently erase cut entries by "packing", i.e. rewriting, the entire TM or glossary.

The editor's ''Filter'' or ''Sort'' dialog box (Press F7 or click the column header are) gives access to three types of operation on data: ''Filter, Sort and Special filters.''
== Filtering ==
Filtering means you define a condition with a Field Condition Argument format.
For example:
{| border="1" style="border-collapse: collapse;"
|-
|SourceText & "MyText
|}
where & means "contains", or
{| border="1" style="border-collapse: collapse;"
|-
|Counter = 0

|}
See more examples in the ''Filter or Sort'' dialog box' Help.

When Argument is made of text, it must be enclosed in straight quotes like this: "MyText".

The effect of a filter is that only the entries that conform to the filter's condition(s) will be made visible in the glossary editor. When a filter has been set, using the ''Mark'' methods (mark, unmark, copy, paste, cut) will operate only on visible entries.
Use the F8 shortcut to cancel a filter.

== Sorting ==
Sorting can take some time, because the entire file is actually (''physically'') sorted, not just the display of the file. Sort when necessary. Wordfast adds the convenience of being able to sort source or target text on ''word or character'' number. This can be useful for terminology extraction.

== Special filters ==

Special filters are meant to perform operations that would be difficult or impossible to perform with just filtering and sorting. These operations are:

'''Mark redundant entries''' (there are various types of definition for a redundant entry, depending on whether you use a TM or a glossary). This feature marks entries that are considered duplicates. Once the marking is done, you can review them, then delete them all by using the Cut shortcut (Ctrl+X) followed by a hard-delete command (Ctrl+Delete). Of course, with a TM, such entries are grouped if the TM is sorted on the source segment.

'''Reverse source and target''' This will rewrite the current file and reverse source and target fields.

'''Export to Unicode''' Exports the current file to a unicode format.

'''Export to TMX (TM only)''' Exports the current file to the TMX format. The TM is not overwritten - a new file is created, and it has a .tmx extension.

'''Remove tags''' This special filter removes tags from a TM. This is recommended after finishing a project with tagged files. The leverage of TUs with tags is precious within the scope of a particular project. Tagged leveraged outside a project is an extreme rarity. This is why it is recommended to remove tags from a TM that will be used on different translation projects. Tags bloat TMs to a ridiculous extent.

'''Rewrite Entries with a Mask'''
This powerful feature is used to replace a particular field, or many fields, with some given value, or erase the content of the fields, in all visible entries. Visible entries are those that are displayed in the editor. If a filter is set, only some entries are visible.

You are first presented with an empty entry (a mask). You can:

*enter an equal sign (=) followed by some text in any field, in which case, the text after the equal sign will replace whatever is found is the corresponding fields in all visible entries in the file (TM or glossary);
*enter "=null" in a field to erase the content of that field.

All fields that are left blank in the mask will remain untouched in the file.

The following mask would replace all User fields with "FOO", and erase Attribute fields 2, 3, 4 in the entire TM:

'''Practical example:''' ''"I have that older, bulky TM that combines TUs from various translators. I want these entries grouped by user (translator) name. I want to delete all entries that have a usage counter of less than 2, and that are older than August 31, 2004. Then I want to review them one by one and perhaps have some entries not marked for deletion if I think they're useful after all. Only then will I erase all marked entries that remain".''

#Start the TM/Glossary editor, click the Tools button.
#Sort on "User".
#Set the following filter: Counter < 2 AND Date < 20040831 .
#Press Ctrl+D to view only marked entries.
#Review marked entries, un-mark the ones you wish to keep.
#Press Ctrl+X to cut all marked entries.
#Press Ctrl+Delete to permanently erase all marked entries.
#Sort on Date to revert to a "natural" order in the TM.

Note that all operations except #7 can be undone.

TMs and glossaries must be created for one language pair only. I also advise keeping separate TMs for different subject (domain) and client, and having them in dedicated folders so that keeping track of them, and especially backing them up, remains easy.

TMs keep growing all the time. Simple statistics show that a majority of TUs will never be re-used (or are very unkikely to be re-used), while a minority of them will. Since Wordfast keeps track of how many times a TU is re-used in the usage counter field, it is advised, when a TM reaches a large size (over 100,000 TUs), or when finishing a large translation project, to perform a compression by eliminating all TUs that have never been re-used. As a result, the TM's size will be considerably reduced, while its overall efficiency will be preserved. To do so:

#Start the TM/glossary editor on the required TM.
#Press F7, and set the following filter: Counter = 0 . Click OK.
#Mark all (Ctrl+A). Cut marked (Ctrl+X). Hard-delete (Ctrl+Delete).

'''Creating a startup TM.''' Create one single, large TM by combining all the TMs you have. Delete all TUs that have a usage counter of less than 3. To compress further, you can visually review the TM and delete TUs that are unlikely to pop up again. To do so, sort the TM on "SourceWords", go to the end of it and review the TUs that are the longest, where there are likely "ghost" candidates, longish TUs that are unikely to show up again. Delete them. This TM can then be used as a primer - if you need to create a new, empty TM, better use a ''copy'' of that TM instead, because it contains a "''Top 50''" or perhaps a "''Top 1000''" of your previous work. It's like priming a pump with a cup of water.

A Wordfast TM may contain TUs where the first figure of the date (normally "2", but it can be "1" for TMs created in the previous millenium) is replaced with "x", and which, as a consequence, appear to be "cut" in the editor. This is because, in the course of a translation session, the TU was proposed as 100% match on a green background, but the target segment was edited, so Wordfast has deleted the original version of the TU in the TM and has re-written the TU's edited version at the end of the TM. This is normal. Do not "resurrect" or un-delete such TUs: their correct version appears further down in the TM. During translation sessions, Wordfast is blind to TUs that are marked "x". As a rule of thumb, perform a "Reorganisation" of the TM before working on it. This is done with the Wordfast > Translation memory > TM ''"Reorganise''" button and it erases all TUs that were marked as "Deleted" with an "x" mark in the course of previous translation sessions.

'''Sharing TMs with other Wordfast users, or with other CAT tools.'''
Sharing TMs with other Wordfast users: always reorganise (use the Translation memory/TM/Reorganise button in Wordfast) before sharing a TM with another Wordfast user.
Sharing TMs with other CAT tools: open the TM with the TM/Glossary editor, click Tools, apply the "Export TM as TMX" special filter. The TM will be re-written as TMX and the file's extension will be changed to .tmx.
Back to [[Wordfast Classic User Manual]]

The TM/Glossary editor Wordfast Classic

2017-11-03T01:23:24Z

Samar:

Click the "TM/Glossary editor" [[File:TM Glossary editor icon.png]] icon in Wordfast's main toolbar, or the last icon in any of the glossary toolbars to start the TM/Glossary editor. Outside a translation session, glossary toolbars can be opened using the Ctrl+Alt+Right shortcut (and closed using the Ctrl+Alt+Left shortcut). During a translation session, the Ctrl+Alt+G shortcut pressed on a word or selection will open the glossary toolbar(s) of the glossary(ies) where the term was found. Glossary toolbars open only on glossaries that were specified in Wordfast/Terminology.

Wordfast's TM/Glossary editor is intended to make maintenance easy and intuitive, and offers practically identical methods for TMs and glossaries. Once the editor is opened, you can scroll up/down the data, edit/delete/add entries.
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
!Shortcut
!Effect
|-
|Space bar
|mark/unmark entries
|-
|Ctrl+A
|mark/unmark all entries
|-
|Shift+Ctrl+A
|reverse the current marking
|-
|Ctrl+X
|cut all marked entries
|-
|Ctrl+Y
|undo the previous cut operation
|-
|Ctrl+C
|copy all marked entries to Wordfast's own clipboard
|-
|Ctrl+V
|paste Wordfast's clipboard's contents to the end of the file
|-
|Ctrl+D
(right-click)
|Toggle the display of all, or only marked, TUs.
|-
|F7 or Click the
column header area
|Open the "Filter or sort" dialog box.
|-
|Ctrl+O
|Open another file (another glossary or antoher TM).
|}
Note: cutting (deleting) a single line (or entry, or TU) is a soft operation, meaning it can be reversed or undone (press Delete twice on an entry to see the toggling effect). When an entry is cut (or soft-deleted), it appears as a blank line, but when it is selected, the source and target data appears in the editor's bottom blue/green display. Ctrl+Delete will permanently erase cut entries by "packing", i.e. rewriting, the entire TM or glossary.

The editor's ''Filter'' or ''Sort'' dialog box (Press F7 or click the column header are) gives access to three types of operation on data: ''Filter, Sort and Special filters.''
== Filtering ==
Filtering means you define a condition with a Field Condition Argument format.
For example:
{| border="1" style="border-collapse: collapse;"
|-
|SourceText & "MyText
|}
where & means "contains", or
{| border="1" style="border-collapse: collapse;"
|-
|Counter = 0

|}
See more examples in the ''Filter or Sort'' dialog box' Help.

When Argument is made of text, it must be enclosed in straight quotes like this: "MyText".

The effect of a filter is that only the entries that conform to the filter's condition(s) will be made visible in the glossary editor. When a filter has been set, using the ''Mark'' methods (mark, unmark, copy, paste, cut) will operate only on visible entries.
Use the F8 shortcut to cancel a filter.

== Sorting ==
Sorting can take some time, because the entire file is actually (''physically'') sorted, not just the display of the file. Sort when necessary. Wordfast adds the convenience of being able to sort source or target text on ''word or character'' number. This can be useful for terminology extraction.

== Special filters ==

Special filters are meant to perform operations that would be difficult or impossible to perform with just filtering and sorting. These operations are:

'''Mark redundant entries''' (there are various types of definition for a redundant entry, depending on whether you use a TM or a glossary). This feature marks entries that are considered duplicates. Once the marking is done, you can review them, then delete them all by using the Cut shortcut (Ctrl+X) followed by a hard-delete command (Ctrl+Delete). Of course, with a TM, such entries are grouped if the TM is sorted on the source segment.

'''Reverse source and target''' This will rewrite the current file and reverse source and target fields.

'''Export to Unicode''' Exports the current file to a unicode format.

'''Export to TMX (TM only)''' Exports the current file to the TMX format. The TM is not overwritten - a new file is created, and it has a .tmx extension.

'''Remove tags''' This special filter removes tags from a TM. This is recommended after finishing a project with tagged files. The leverage of TUs with tags is precious within the scope of a particular project. Tagged leveraged outside a project is an extreme rarity. This is why it is recommended to remove tags from a TM that will be used on different translation projects. Tags bloat TMs to a ridiculous extent.

'''Rewrite Entries with a Mask'''
This powerful feature is used to replace a particular field, or many fields, with some given value, or erase the content of the fields, in all visible entries. Visible entries are those that are displayed in the editor. If a filter is set, only some entries are visible.

You are first presented with an empty entry (a mask). You can:

*enter an equal sign (=) followed by some text in any field, in which case, the text after the equal sign will replace whatever is found is the corresponding fields in all visible entries in the file (TM or glossary);
*enter "=null" in a field to erase the content of that field.

All fields that are left blank in the mask will remain untouched in the file.

The following mask would replace all User fields with "FOO", and erase Attribute fields 2, 3, 4 in the entire TM:

'''Practical example:''' ''"I have that older, bulky TM that combines TUs from various translators. I want these entries grouped by user (translator) name. I want to delete all entries that have a usage counter of less than 2, and that are older than August 31, 2004. Then I want to review them one by one and perhaps have some entries not marked for deletion if I think they're useful after all. Only then will I erase all marked entries that remain".''

#Start the TM/Glossary editor, click the Tools button.
#Sort on "User".
#Set the following filter: Counter < 2 AND Date < 20040831 .
#Press Ctrl+D to view only marked entries.
#Review marked entries, un-mark the ones you wish to keep.
#Press Ctrl+X to cut all marked entries.
#Press Ctrl+Delete to permanently erase all marked entries.
#Sort on Date to revert to a "natural" order in the TM.

Note that all operations except #7 can be undone.

TMs and glossaries must be created for one language pair only. I also advise keeping separate TMs for different subject (domain) and client, and having them in dedicated folders so that keeping track of them, and especially backing them up, remains easy.

TMs keep growing all the time. Simple statistics show that a majority of TUs will never be re-used (or are very unkikely to be re-used), while a minority of them will. Since Wordfast keeps track of how many times a TU is re-used in the usage counter field, it is advised, when a TM reaches a large size (over 100,000 TUs), or when finishing a large translation project, to perform a compression by eliminating all TUs that have never been re-used. As a result, the TM's size will be considerably reduced, while its overall efficiency will be preserved. To do so:

#Start the TM/glossary editor on the required TM.
#Press F7, and set the following filter: Counter = 0 . Click OK.
#Mark all (Ctrl+A). Cut marked (Ctrl+X). Hard-delete (Ctrl+Delete).

'''Creating a startup TM.''' Create one single, large TM by combining all the TMs you have. Delete all TUs that have a usage counter of less than 3. To compress further, you can visually review the TM and delete TUs that are unlikely to pop up again. To do so, sort the TM on "SourceWords", go to the end of it and review the TUs that are the longest, where there are likely "ghost" candidates, longish TUs that are unikely to show up again. Delete them. This TM can then be used as a primer - if you need to create a new, empty TM, better use a ''copy'' of that TM instead, because it contains a "''Top 50''" or perhaps a "''Top 1000''" of your previous work. It's like priming a pump with a cup of water.

A Wordfast TM may contain TUs where the first figure of the date (normally "2", but it can be "1" for TMs created in the previous millenium) is replaced with "x", and which, as a consequence, appear to be "cut" in the editor. This is because, in the course of a translation session, the TU was proposed as 100% match on a green background, but the target segment was edited, so Wordfast has deleted the original version of the TU in the TM and has re-written the TU's edited version at the end of the TM. This is normal. Do not "resurrect" or un-delete such TUs: their correct version appears further down in the TM. During translation sessions, Wordfast is blind to TUs that are marked "x". As a rule of thumb, perform a "Reorganisation" of the TM before working on it. This is done with the Wordfast > Translation memory > TM ''"Reorganise''" button and it erases all TUs that were marked as "Deleted" with an "x" mark in the course of previous translation sessions.

'''Sharing TMs with other Wordfast users, or with other CAT tools.'''
Sharing TMs with other Wordfast users: always reorganise (use the Translation memory/TM/Reorganise button in Wordfast) before sharing a TM with another Wordfast user.
Sharing TMs with other CAT tools: open the TM with the TM/Glossary editor, click Tools, apply the "Export TM as TMX" special filter. The TM will be re-written as TMX and the file's extension will be changed to .tmx.
Back to [[Wordfast Classic User Manual]]

Concordance search Wordfast Classic

2017-11-03T01:20:22Z

Samar:

The search for concordance will be done first in the background translation memory (if applicable), then in the regular translation memory. The purpose of Concordance search is to find Translation Units (TUs) that contain a given word or a set of words.

The Ctrl+Alt+C shortcut or the Concordance icon launches the search. The search will bring results on words that begin like the searched-for item, case-insensitive. Searching for cat will bring TUs that contain cat, or catering or caterpillar, etc, but not bobcat or supercat.

Searching for *cat will bring TUs that contain words like bobcat, or supercat, etc.

The AND operator can be used. Searching for cat+dog will bring TUs where the two words cat AND dog are found. If words are simply separated with spaces, the OR operator is assumed, so searching for cat dog will bring TUs where either cat OR dog are found. To search for an exact phrase, have it contained within straight quotes, so searching for "The cat chases the dog" will bring results where the phrase "The cat chases the dog" is literally found, regardless of case.

Note that to open the dialog box that lets you specify such extended search options, you must start concordance search when no selection is made; if a selection is made (for example, one word is selected in the source segment), then WFC assumes that the selected word has to be searched and will directly search for it, without offering the extended search dialog box. This allows fast searches with minimal clicks or shortcuts.

The same rules apply for Reference searches as well.

If you check the "Search concordances in all sibling translation memories" option in WFC/Terminology/Other, the concordance search will be extended to other TMs present in the same folder as the currently active TM.

It is possible to cancel a Concordance search with the Escape key, or with the same shortcut that started the search (i.e., Ctrl+Alt+C).

Back to [[Wordfast Classic User Manual]]

Concordance search Wordfast Classic

2017-11-03T01:19:29Z

Samar:

The search for concordance will be done first in the background translation memory (if applicable), then in the regular translation memory. The purpose of Concordance search is to find Translation Units (TUs) that contain a given word or a set of words.

The Ctrl+Alt+C shortcut or the Concordance icon launches the search. The search will bring results on words that begin like the searched-for item, case-insensitive. Searching for cat will bring TUs that contain cat, or catering or caterpillar, etc, but not bobcat or supercat.

Searching for *cat will bring TUs that contain words like bobcat, or supercat, etc.

The AND operator can be used. Searching for cat+dog will bring TUs where the two words cat AND dog are found. If words are simply separated with spaces, the OR operator is assumed, so searching for cat dog will bring TUs where either cat OR dog are found. To search for an exact phrase, have it contained within straight quotes, so searching for "The cat chases the dog" will bring results where the phrase "The cat chases the dog" is literally found, regardless of case.

Note that to open the dialog box that lets you specify such extended search options, you must start concordance search when no selection is made; if a selection is made (for example, one word is selected in the source segment), then WFC assumes that the selected word has to be searched and will directly search for it, without offering the extended search dialog box. This allows fast searches with minimal clicks or shortcuts.

The same rules apply for Reference searches as well.

If you check the "Search concordances in all sibling translation memories" option in WFC/Terminology/Other, the concordance search will be extended to other TMs present in the same folder as the currently active TM.
It is possible to cancel a Concordance search with the Escape key, or with the same shortcut that started the search (i.e., Ctrl+Alt+C).

Back to [[Wordfast Classic User Manual]]

Dictionary Wordfast Classic

2017-11-03T01:18:02Z

Samar:

(PC only) Wordfast can be linked to virtually any external dictionary application, such as the Collins ™ On-line, Harrap's™ Shorter, Merriam Webster's ™, Microsoft Encarta ™, any web-based dictionary or database, Trados Multiterm ™ etc, using the Select dictionary button of the Terminology/Reference tab.

The access keystroke (Keys button) defines the keystrokes used for accessing an external dictionary, where some fields are replaced with values as in the following table:
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
|Field
|will be replaced by Wordfast with
|Example
|-
|{SearchWord}
|the word you are searching for
|house
|-
|{SourceSegment}
|the text of the source segment (without tags, if any)
|
|-
|{TargetSegment}
|the text of the target segment (without tags, if any)
|
|-
|{SL-CD}
|The source language code with local variant
|EN-US
|-
|{SL}
|The source language code, in 2 characters
|EN
|-
|{TL-CD}
|The target language code with local variant
|FR-FR
|-
|{TL}
|2-character target language code
|FR
|-
|{pause}
|Pauses the execution for 200 milliseconds
|
|-
|{PAUSE}
|Pauses the execution for 4 seconds
|
|-
|{pause=Harraps}
|Pauses until the application's window caption contains the string "Harraps". Case-insensitive. 10-second timeout.
|
|-
|{Ms-Word}
|Returns the focus to the Ms-Word application
|
|}
To set up the "Keys" parameter, start your dictionary application, then note the sequence of keystrokes necessary to perform a word search. Once this is done, click the Keys button and enter the caption of the dictionary application window, followed by a semi-colon, followed by the keys you noted. For example,
{| border="1" style="border-collapse: collapse;" align="center"
|-
|Harraps;{pause}{F3}{Escape}%e{SearchWord}{Enter}
|}
will instruct Wordfast to look for an application whose window name begins with Harraps, activate it, pause for 200 milliseconds, then type an F3 key, followed by an Escape Key, then Alt+E, then the searched-for word, then an Enter key.

All typable keys are simply entered as they are, in lowercase. Function keys and other special keys are entered as follows:
{| border="1" style="border-collapse: collapse;"
|-
|A, B, C etc
|a, b, c etc
|
|F1 etc
|{F1} etc
|-
|Enter
|{Enter}
|
|End
|{End}
|-
|Escape
|{Escape}
|
|Tabulator
|{Tab}
|-
|Alt
|%
|
|Shift
| +
|-
|Ctrl
|^
|
|Up
|{Up}
|-
|Down
|{Down}
|
|PageUp
|{PgUp}
|-
|PageDown
|{PgDn]
|
|Home
|{Home}
|}
Once the dictionary has been setup, close WFC. Position the cursor on a word, or select an expression, and click the Dictionary icon (or press Ctrl+Alt+D. For the dictionary #2, use the Ctrl+Alt+F shortcut). WFC will launch the dictionary application (or activate the relevant window if the application is already running) and execute the sequence of keystrokes you defined.

Back to [[Wordfast Classic User Manual]]

Dictionary Wordfast Classic

2017-11-03T01:16:39Z

Samar:

(PC only) Wordfast can be linked to virtually any external dictionary application, such as the Collins ™ On-line, Harrap's™ Shorter, Merriam Webster's ™, Microsoft Encarta ™, any web-based dictionary or database, Trados Multiterm ™ etc, using the Select dictionary button of the Terminology/Reference tab.

The access keystroke (Keys button) defines the keystrokes used for accessing an external dictionary, where some fields are replaced with values as in the following table:
{| border="1" style="border-collapse: collapse;"
|-style="background:#a2a9b1"
|Field
|will be replaced by Wordfast with
|Example
|-
|{SearchWord}
|the word you are searching for
|house
|-
|{SourceSegment}
|the text of the source segment (without tags, if any)
|
|-
|{TargetSegment}
|the text of the target segment (without tags, if any)
|
|-
|{SL-CD}
|The source language code with local variant
|EN-US
|-
|{SL}
|The source language code, in 2 characters
|EN
|-
|{TL-CD}
|The target language code with local variant
|FR-FR
|-
|{TL}
|2-character target language code
|FR
|-
|{pause}
|Pauses the execution for 200 milliseconds
|
|-
|{PAUSE}
|Pauses the execution for 4 seconds
|
|-
|{pause=Harraps}
|Pauses until the application's window caption contains the string "Harraps". Case-insensitive. 10-second timeout.
|
|-
|{Ms-Word}
|Returns the focus to the Ms-Word application
|
|}
To set up the "Keys" parameter, start your dictionary application, then note the sequence of keystrokes necessary to perform a word search. Once this is done, click the Keys button and enter the caption of the dictionary application window, followed by a semi-colon, followed by the keys you noted. For example,
{| border="1" style="border-collapse: collapse;" align="center"
|-
|Harraps;{pause}{F3}{Escape}%e{SearchWord}{Enter}
|}
will instruct Wordfast to look for an application whose window name begins with Harraps, activate it, pause for 200 milliseconds, then type an F3 key, followed by an Escape Key, then Alt+E, then the searched-for word, then an Enter key.

All typable keys are simply entered as they are, in lowercase. Function keys and other special keys are entered as follows:
{| border="1" style="border-collapse: collapse;"
|-
|A, B, C etc
|a, b, c etc
|
|F1 etc
|{F1} etc
|-
|Enter
|{Enter}
|
|End
|{End}
|-
|Escape
|{Escape}
|
|Tabulator
|{Tab}
|-
|Alt
|%
|
|Shift
| +
|-
|Ctrl
|^
|
|Up
|{Up}
|-
|Down
|{Down}
|
|PageUp
|{PgUp}
|-
|PageDown
|{PgDn]
|
|Home
|{Home}
|}
Once the dictionary has been setup, close Wordfast. Position the cursor on a word, or select an expression, and click the Dictionary icon [[File:Dictionary icon.png]] (or press Ctrl+Alt+D. For the dictionary #2, use the Ctrl+Alt+F shortcut). Wordfast will launch the dictionary application (or activate the relevant window if the application is already running) and execute the sequence of keystrokes you defined.
Back to [[Wordfast Classic User Manual]]

Bookmarks Wordfast Classic

2017-11-03T01:12:55Z

Samar:

See the [https://www.wordfast.net/w/index.php/Glossary_of_terms_used_in_this_manual_Wordfast_Classic#Bookmarks glossary of terms] if you are not sure what a bookmark is.

Handling bookmarks, or not handling bookmarks, is a question to be discussed with the client. In many projects, the author or the client may not need bookmarks to be positioned in the translated text. This is simply due to the fact that in many cases, bookmarks are part of a complex, carefully engineered scenario, and the document's owner may rather wish an engineer, or a technician, to re-position bookmarks on the translated document, then test the entire document again. In this situation (the translator not being required to position bookmarks in the translated document), simply click "No" if WFC prompts you to have bookmarks prepared for translation.

Your client should inform you of the presence of bookmarks and give you instructions (transfer them or ignore them), since it is the client, or the author, who has introduced the bookmarks in the first place. However, your client may not be the author of the document(s), and the client may not even know what a bookmark is. In this last case, use tact and wisdom to make sure what should be done. The bottom line is: do not transfer bookmarks - a complex task at times - unless your client asks you to do so; but if you have to handle bookmarks, carefully weigh and estimate the extra workload. A bookmark, at the very least, should be billed as two words, although it usually takes longer to correctly position the two ends of a bookmark than to translate two words.

Normally, bookmarks found in the source text should be transferred into the target text, over the corresponding span of translated text.

One important point is, since two bookmarks cannot have the same name in the same document, bookmarks must be transferred (moved), not copied, into the target text. In other words, you cannot duplicate or copy bookmarks as you would, for example, duplicate or copy fields.

Before starting a translation session over a document that contains bookmarks, WFC will warn of the presence of bookmarks and propose to mark them using conspicuous red markers positioned at the beginning and end of the bookmark, like this: [ and ]. If a bookmark has a null length, you would see []. Answer "Yes" to have bookmarks thus marked.

WFC will prompt you only once (per document) for marking bookmarks. If you answer "No", then WFC will not prompt you anymore for marking bookmarks on the current dcoument unless you open a translation session with the cursor at the very top of the document. If you answered "No" by mistake, or if you want to mark bookmarks at a later stage, use the WFC menu, select the Miscellaneous submenu and run "Unlink". Once the document has been "unlinked", WFC will prompt you again for marking bookmarks if you start a translation session.

During translation, if a source segment contains red markers, all you need to do is use the Next/Previous/Copy Placeable icons or shortcuts (Ctrl+Alt+Left/right/down) to select or box the red bookmark markers (they always come in pairs, opening and closing), then transfer the red marker(s) at the appropriate location in the target segment using Ctrl+Alt+down.

When cleaning up a document, WFC will remove the source segments as usual then replace the red markers in the target segments with the appropriate bookmarks.

WFC's Quick-clean function will propose an option for processing (restoring) bookmarks without cleaning up the document. This is useful for translators who are required by the client to send back "uncleaned" or "bilingual" documents (for example, because the client wants to clean up the documents with a different tool, not with WFC). In this case, the document is not cleaned up, but all bookmark markers are removed, bookmarks are correctly assigned to the target text.

Pay attention to the bookmark question before beginning a project, because handling bookmarks takes time; if the problem is overlooked, reconstructing bookmarks manually on a translated document can take a long time.

The WFC Translate tool's default behaviour is to mark bookmarks. If you want to prevent this, add "TranslateIgnoreBookmarks" in Pandora's box.

The WFC Clean up tool's default behaviour is to clean up documents and process bookmark markers (remove bookmark markers and move actual bookmarks to the target segments). If you just want to have bookmarks processed without cleaning up documents, add "CleanUpOnlyBookmarks" in Pandora's box.

Bookmarks can be found in many different types of documents, and they are put to many different uses. Documents that contain hyperlinks, indexes, or Tables of Contents usually make considerable use of bookmarks.

Back to [[Wordfast Classic User Manual]]

Translatable fields Wordfast Classic

2017-11-03T01:11:05Z

Samar:

''Read the general introduction to fields (above), if this is not yet done.
''
=== Fields where the result (not the code) must be translated. ===
Hyperlinks are a good example. These fields should be manually copied from source to target, then manually translated - toggle the field's view with Alt+F9 as necessary, so you can edit the translatable element (the result). Another approach is to right-click the hyperlink, then select "Edit" and translate the field's displayed text.

''With Ms-Word 2000 or higher, right-click the field, click "Hyperlink", then "Edit hyperlink". The translatable item is at the very top of the "Edit hyperlink" dialog box.''

=== Fields where part of the code must be translated. ===
The code for most fields cannot, and should not, be translated. There are a few exceptions to this rule, like index fields ("EX", "XE"). Such fields have a translatable item, contained between quotes as in the following example:

{XE "Translatable text:Page 4 Figure 5" \b \r }

Make sure Ms-Word's View options (Tools/Options/View or the Alt+F9 shortcut) are set to display field codes and hidden text.

When you open a segment with translatable fields (and the TM does not bring any match), you can use the Previous/Next Placeable utility (Ctrl+Alt+Left/Right shortcuts or the corresponding icons with arrows) to select the field in the source segment, then copy it down (Ctrl+Alt+Down) at the proper position in the target segment. At that moment, WFC will display a text input dialog box containing the translatable part of the field and will wait for the translation (if a match is found in the TM, it will be proposed).

Another way is to use the CopySource icon or shortcut. When WFC copies a source segment with translatable fields, it will take you to each translatable field and prompt you for translation.

It is also possible to directly edit the editable part of the field in the document, if the field codes are made visible (Alt+F9). This is recommended if the above method fails for some reason.

Back to [[Wordfast Classic User Manual]]

Fields and objects Wordfast Classic

2017-11-03T01:08:27Z

Samar:

An Ms-Word document can contain fields or objects like hypertext links, buttons, graphics etc. Normally, fields (to the exception of hyperlinks) 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" or "Draft" 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 WFC'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.

Back to [[Wordfast Classic User Manual]]

Footnotes Wordfast Classic

2017-11-03T01:06:33Z

Samar:

When a source segment contains a footnote reference (a number that looks like this: 1 and which, if double-clicked, opens the corresponding footnote), start translating the target segment as usual. At the point where the footnote reference should appear in the translated text, use Ctrl+Alt+left/right to select the footnote reference (it should be boxed in red), then transfer it into the target segment using Ctrl+Alt+Down. If these shortcuts are not available, you can use the corresponding icons (Next/Previous/Copy Placeable) in the WFC toolbar.

You can also manually select the footnote reference, cut it (not copy it) and paste it into the target segment. The important point is to actually cut (not copy) then paste the footnote reference (move the footnote reference), otherwise you would duplicate notes.

When the document's translation is over, double-click any footnote reference to open the footnote pane (the current window will split and the bottom half will show footnotes) to translate the actual footnotes. Simply put your cursor in a footnote and start translating as usual with WFC. You can translate foonotes immediately after a segment, by closing the segment then opening the footnote pane and translating the footnote. But I recommend translating all footnotes in a separate translation session when the document's translation is over.

After you transfer a footnote reference, WFC will replace the source segment's original footnote reference with a "dummy" footnote reference number, so the revisor can know where the original footnote reference position was.

Note that when there are multiple footnotes references in the same segment, they will appear wrongly numbered after you transfer the first footnote reference. The correct numbering will be restored when you transfer the segment's last footnote reference.

In case of mistake, use Ms-Word's undo function immediately after pasting a footnote..

Back to [[Wordfast Classic User Manual]]

PDF Wordfast Classic

2017-11-02T23:56:13Z

Samar:

'''''Important note:''' Wordfast Anywhere (http://anywhere.wordfast.net) can convert a PDF document into a Word document, for free as of Spring 2011. This even concerns "dead PDFs", i.e., PDF documents that contain screenshots of text, or scanned text.'' Wordfast, as a brand, was the first translation tool maker to offer really free (no usage restriction, no advertizing, no platinum upgrades) PDF-to-RTF conversions.

The PDF (Portable Document File) format was designed at an age when fonts were scarce and expensive. Many systems lacked fonts, or were equipped with very different fonts. The PDF format contained the fonts it used, making it very portable.

Unfortunately for us translators, the success of PDF is found in another feature: the difficulty (or the near impossibility for most people) to alter PDF content. As a consequence, one cannot directly edit, therefore, translate a PDF file: text has to be extracted from it. To make things even more complicated, many PDF documents (so-called "Dead PDFs") either lock their content, or worse, only contain graphics (screenshots) of text, not actual, selectable text.

The bottom line is that there is no tool that will let you translate a PDF "from within", and deliver a translated PDF at the push of a button. PDFs must be converted to another format, and even that process is hazardous.

WFC can convert most "live" PDF documents into Word documents, in the Windows environment, provided:

*You have Adobe (PDF) Reader version 7, 8, 9, or above, installed (note: Adobe Reader is free, and found on most systems).
*The PDF document is not password-protected again copy/pasting (to verify: in Adobe Reader, use the Edit menu: if ''Copy'' and ''Paste'' are greyed out, the document is locked).
*The PDF document actually contains text, not pictures of text, or screenshots.

There are two methods to import PDF into a Word document with Wordfast:

*'''Drag-drop the PDF file straight into Ms-Word''' (drop it in Ms-Word's window title bar, not inside the Ms-Word window). Wordfast should detect the '''.pdf''' extension and start the import process.
*'''Open the PDF file with Abobe Reader''' (double-click the PDF file). In Adobe Reader's Preferences / Display (View) options, set the mode to the "One page" view, '''not''' the "One page continuous" view. In the PDF document, make sure that text (like individual words) can be selected with the mouse.

Get back to Ms-Word, create a new, blank document, press Alt+Down (this is the same process as with Excel and PowerPoint files).
Back to [[Wordfast Classic User Manual]]

Tagged files Wordfast Classic

2017-11-01T21:30:50Z

Samar:

Wordfast Classic is designed to translate the Word native "DOC" format. Tagged files are better translated with programs that were designed from the ground up to handle tagged files, like Wordfast PRO.

Wordfast Classic retains the capability to translate "tagged" files, but it should be noted that an Ms-Word tool cannot efficiently handle or protect tags. Translating tagged files with Ms-Word requires expertise, should things go wrong at any stage.

Some translation agencies, which are equipped with tagging software to prepare documents, may ask free-lance translators to work on tagged files. Agencies and free-lance translators should know that Wordfast is '''compatible with the most current tag formats, such as Trados and RWS Rainbow.''' Here is some advice for translating tagged documents. Please pay attention to the following advice, because tagged files that are not properly handled can cause serious problems.

''Agencies that entrust tagged files to a translator for the first time should review the first translated file immediately after the translator has completed it, to make sure tags have been properly handled. If necessary, adjustments should be made before going any further into the project.''

== Internal tags ==
The red tags (usually with the style tw4winInternal) are internal and are mostly found within the text to be translated, and in the translation.
{|
|-
|Example:|| The final document.
|-
|translates into || Le document final.
|}
In this example, and are tags that command the bold type in HTML. The translator has positioned the red tags at the right position in the translated sentence. The translated text does not have a tw4winInternal (neither a tw4winExternal) style (with a "Normal" or "Translatable" style). Only tags have a tag (tw4winInternal) style, red or grey. Styles are important, because tagging/untagging software relies on style, not font colour, to differentiate tags from translated text.

! Be careful when typing. If you type regular text (for example, right after right after a <tag>), and notice that the text appears red, stop! Only tags must have the tw4winInternal style. Regular text should have another style, usually named "Normal", or "Translatable", whatever that is. In fact, the style of the regular text does not matter, as long as it is neither tw4winInternal nor tw4winExternal.
Note that to revert text from a tw4winInternal style (or any other style) to the default style, select the text and press Ctrl+Spacebar. A slower method involves the Style listbox, the mouse, etc. If you are not familiar with Ctrl+Spacebar, learn it right now: select some styled text, apply it and see how it works.

! '''Internal tags must normally not be modified, edited or translated'''. Some tags can be added or omitted if the translation requires it. Otherwise, the golden rule is that '''all internal tags''' (usually enclosed between < and >) present in the source segment must be '''duplicated in the target segment''', and positioned correctly.

To duplicate these internal tags, Wordfast provides a set of shortcuts. '''Ctrl+Alt+left/right''' will select the next/previous internal tag (in the source segment); '''Ctrl+Alt+down''' will duplicate ("bring down") the selected tag at the insertion point, in the target segment. You should get used to these shortcuts. For better speed, you can type < or / and AutoSuggest will pop up a list of available tags for quicker placement.

If you copy the source text into the target segment and translate by overwriting it, or if you edit an existing target segment, make sure the translated text does not have a tag (red or grey) style. If the cursor is immediately after a red (or grey) tag, whatever you type will also be red (or grey), and this causes problems later on. To avoid this, remember that if your cursor is immediately after a red tag, pressing Ctrl+Spacebar will restore the normal style at that point, and the text you type will not have a tag style. Ctrl+Spacebar is an Ms-Word shortcut.

In a regular tagged style, the only two important styles are tw4winInternal and tw4winExternal. Text outside tags can have any other style (styles named Normal, Translatable, etc.) or font attributes (bold, blue, whatever).

Here are examples of correct and uncorrect translation units:
{| border="1" style="border-collapse: collapse" width= "700px"
|-style="background:#eaecf0"
|Examples of translation units
|Notes
|-
|align= "center" | The <B> final document is here.

Le document <B> final est ici.
|align= "center" | This TU is OK.
|-
|align= "center" | The <B> final document is here.

Le document <B> final est ici.
|align= "center" |Problem: the target word "final" has an internal tag style
|-
|align= "center" | The <B> final document is here.

 Le document <B> final est ici.
|align= "center" |Problem: the target segment's first tag has lost its internal (red) tag style.
|-
|align= "center" | The <B> final document is here.

Le document <B> final est ici.
|align= "center" | Problem: the target segment's second tag is missing (it should be ).
|}
Wordfast has a Quality Assurance option called "Identical tags in source/target segments". I recommend turning this QA option on. To avoid having false alerts for tags that are actually optional, use Pandora Box' "OptionalTags" command in Wordfast/Setup/PB.

Most optional tags are tagged items (like the unbreakable space, quotes, ampersand etc) that look like &amp; or <<:hs> or &nbsp; etc. You may have them in the source segment but not in the target segment, or the reverse, according to the translation's needs. Thus, the following segment:

The R &amp; D department is <B> ready .

Le Département "Recherche et Développement" est <B> prêt .

is valid, even if there are three internal tags in the source segment and two in the target. The source segment's ampersand has not been re-used. There may be other exceptions where even non-optional tags must be added or omitted.

'''Long tags.''' WFC considers any contiguous text with an Internal style as a one tag. So for example

<palign="left" font="Times New Roman" size"12"><strong><table align="center">

is considered one tag.

If this contiguous stretch of text actually contains more than one tag, and if these tags have to be handled separately, use the Ctrl+Alt+Up shortcut to make WFC treat this tag as separate placeables. The pairs of characters < and > as well as & and ; will be considered as tag beginning and tag ending.

== External tags ==

External tags (tw4winExternal style) are kept out of the translation. Like internal tags, they must not be edited, deleted, translated etc.

! In case of doubt, stop and ask the client or the agency. Do not proceed if you are not sure you handle tags correctly. If you start working on a project with tags for the first time, submit your first translated file for review and approval before going any further.

Back to [[Wordfast Classic User Manual]]

Tagged files Wordfast Classic

2017-11-01T21:15:03Z

Samar:

Wordfast Classic is designed to translate the Word native "DOC" format. Tagged files are better translated with programs that were designed from the ground up to handle tagged files, like Wordfast PRO.

Wordfast Classic retains the capability to translate "tagged" files, but it should be noted that an Ms-Word tool cannot efficiently handle or protect tags. Translating tagged files with Ms-Word requires expertise, should things go wrong at any stage.

Some translation agencies, which are equipped with tagging software to prepare documents, may ask free-lance translators to work on tagged files. Agencies and free-lance translators should know that Wordfast is '''compatible with the most current tag formats, such as Trados and RWS Rainbow.''' Here is some advice for translating tagged documents. Please pay attention to the following advice, because tagged files that are not properly handled can cause serious problems.

''Agencies that entrust tagged files to a translator for the first time should review the first translated file immediately after the translator has completed it, to make sure tags have been properly handled. If necessary, adjustments should be made before going any further into the project.''

== Internal tags ==
The red tags (usually with the style tw4winInternal) are internal and are mostly found within the text to be translated, and in the translation.
{|
|-
|Example:|| The final document.
|-
|translates into || Le document final.
|}
In this example, and are tags that command the bold type in HTML. The translator has positioned the red tags at the right position in the translated sentence. The translated text does not have a tw4winInternal (neither a tw4winExternal) style (with a "Normal" or "Translatable" style). Only tags have a tag (tw4winInternal) style, red or grey. Styles are important, because tagging/untagging software relies on style, not font colour, to differentiate tags from translated text.

! Be careful when typing. If you type regular text (for example, right after right after a <tag>), and notice that the text appears red, stop! Only tags must have the tw4winInternal style. Regular text should have another style, usually named "Normal", or "Translatable", whatever that is. In fact, the style of the regular text does not matter, as long as it is neither tw4winInternal nor tw4winExternal.
Note that to revert text from a tw4winInternal style (or any other style) to the default style, select the text and press Ctrl+Spacebar. A slower method involves the Style listbox, the mouse, etc. If you are not familiar with Ctrl+Spacebar, learn it right now: select some styled text, apply it and see how it works.

! '''Internal tags must normally not be modified, edited or translated'''. Some tags can be added or omitted if the translation requires it. Otherwise, the golden rule is that '''all internal tags''' (usually enclosed between < and >) present in the source segment must be '''duplicated in the target segment''', and positioned correctly.

To duplicate these internal tags, Wordfast provides a set of shortcuts. '''Ctrl+Alt+left/right''' will select the next/previous internal tag (in the source segment); '''Ctrl+Alt+down''' will duplicate ("bring down") the selected tag at the insertion point, in the target segment. You should get used to these shortcuts. For better speed, you can type < or / and AutoSuggest will pop up a list of available tags for quicker placement.

If you copy the source text into the target segment and translate by overwriting it, or if you edit an existing target segment, make sure the translated text does not have a tag (red or grey) style. If the cursor is immediately after a red (or grey) tag, whatever you type will also be red (or grey), and this causes problems later on. To avoid this, remember that if your cursor is immediately after a red tag, pressing Ctrl+Spacebar will restore the normal style at that point, and the text you type will not have a tag style. Ctrl+Spacebar is an Ms-Word shortcut.

In a regular tagged style, the only two important styles are tw4winInternal and tw4winExternal. Text outside tags can have any other style (styles named Normal, Translatable, etc.) or font attributes (bold, blue, whatever).

Here are examples of correct and uncorrect translation units:
{| border="1" style="border-collapse: collapse" width= "700px"
|-style="background:#eaecf0"
|Examples of translation units
|Notes
|-
|align= "center" | The <B> final document is here.

Le document <B> final est ici.
|align= "center" | This TU is OK.
|-
|align= "center" | The <B> final document is here.

Le document <B> final est ici.
|align= "center" |Problem: the target word "final" has an internal tag style
|-
|align= "center" | The <B> final document is here.

 Le document <B> final est ici.
|align= "center" |Problem: the target segment's first tag has lost its internal (red) tag style.
|-
|align= "center" | The <B> final document is here.

Le document <B> final est ici.
|align= "center" | Problem: the target segment's second tag is missing (it should be ).
|}
Wordfast has a Quality Assurance option called "Identical tags in source/target segments". I recommend turning this QA option on. To avoid having false alerts for tags that are actually optional, use Pandora Box' "OptionalTags" command in Wordfast/Setup/PB.

Most optional tags are tagged items (like the unbreakable space, quotes, ampersand etc) that look like &amp; or <:hs> or &nbsp; etc. You may have them in the source segment but not in the target segment, or the reverse, according to the translation's needs. Thus, the following segment:

The R &amp; D department is ready .

Le Département "Recherche et Développement" est prêt .

is valid, even if there are three internal tags in the source segment and two in the target. The source segment's ampersand has not been re-used. There may be other exceptions where even non-optional tags must be added or omitted.

'''Long tags'''. Wordfast considers any contiguous text with an Internal style as a one tag. So for example

 align= "left" font= "Times New Roman" size= "12" > > <sp

Tagged files Wordfast Classic

2017-11-01T17:17:33Z

Samar:

Wordfast Classic is designed to translate the Word native "DOC" format. Tagged files are better translated with programs that were designed from the ground up to handle tagged files, like Wordfast PRO.

Wordfast Classic retains the capability to translate "tagged" files, but it should be noted that an Ms-Word tool cannot efficiently handle or protect tags. Translating tagged files with Ms-Word requires expertise, should things go wrong at any stage.

Some translation agencies, which are equipped with tagging software to prepare documents, may ask free-lance translators to work on tagged files. Agencies and free-lance translators should know that Wordfast is '''compatible with the most current tag formats, such as Trados and RWS Rainbow.''' Here is some advice for translating tagged documents. Please pay attention to the following advice, because tagged files that are not properly handled can cause serious problems.

''Agencies that entrust tagged files to a translator for the first time should review the first translated file immediately after the translator has completed it, to make sure tags have been properly handled. If necessary, adjustments should be made before going any further into the project.''

'''Internal tags'''
The red tags (usually with the style tw4winInternal) are internal and are mostly found within the text to be translated, and in the translation.
{|
|-
|Example:|| The final document.
|-
|translates into || Le document final.
|}
In this example, and are tags that command the bold type in HTML. The translator has positioned the red tags at the right position in the translated sentence. The translated text does not have a tw4winInternal (neither a tw4winExternal) style (with a "Normal" or "Translatable" style). Only tags have a tag (tw4winInternal) style, red or grey. Styles are important, because tagging/untagging software relies on style, not font colour, to differentiate tags from translated text.

! Be careful when typing. If you type regular text (for example, right after right after a <tag>), and notice that the text appears red, stop! Only tags must have the tw4winInternal style. Regular text should have another style, usually named "Normal", or "Translatable", whatever that is. In fact, the style of the regular text does not matter, as long as it is neither tw4winInternal nor tw4winExternal.
Note that to revert text from a tw4winInternal style (or any other style) to the default style, select the text and press Ctrl+Spacebar. A slower method involves the Style listbox, the mouse, etc. If you are not familiar with Ctrl+Spacebar, learn it right now: select some styled text, apply it and see how it works.

! '''Internal tags must normally not be modified, edited or translated'''. Some tags can be added or omitted if the translation requires it. Otherwise, the golden rule is that '''all internal tags''' (usually enclosed between < and >) present in the source segment must be '''duplicated in the target segment''', and positioned correctly.

To duplicate these internal tags, Wordfast provides a set of shortcuts. '''Ctrl+Alt+left/right''' will select the next/previous internal tag (in the source segment); '''Ctrl+Alt+down''' will duplicate ("bring down") the selected tag at the insertion point, in the target segment. You should get used to these shortcuts. For better speed, you can type < or / and AutoSuggest will pop up a list of available tags for quicker placement.

If you copy the source text into the target segment and translate by overwriting it, or if you edit an existing target segment, make sure the translated text does not have a tag (red or grey) style. If the cursor is immediately after a red (or grey) tag, whatever you type will also be red (or grey), and this causes problems later on. To avoid this, remember that if your cursor is immediately after a red tag, pressing Ctrl+Spacebar will restore the normal style at that point, and the text you type will not have a tag style. Ctrl+Spacebar is an Ms-Word shortcut.

In a regular tagged style, the only two important styles are tw4winInternal and tw4winExternal. Text outside tags can have any other style (styles named Normal, Translatable, etc.) or font attributes (bold, blue, whatever).

Here are examples of correct and uncorrect translation units:
{| border="1" style="border-collapse: collapse" width= "700px"
|-style="background:#eaecf0"
|Examples of translation units
|Notes
|-
|align= "center" | The <B> final document is here.

Le documentThe <B> final est ici.
|align= "center" | This TU is OK.
|-
|align= "center" | The The <B> final document is here.

Le documentThe <B> final est ici.
|align= "center" |Problem: the target word "final" has an internal tag style
|-
|align= "center" | The <B> final document is here.

 Le document <B> final est ici.
|align= "center" |Problem: the target segment's first tag has lost its internal (red) tag style.
|-
|align= "center" | The <B> final document is here.

Le document <B> final est ici.
|align= "center" | Problem: the target segment's second tag is missing (it should be ).
|}
Wordfast has a Quality Assurance option called "Identical tags in source/target segments". I recommend turning this QA option on. To avoid having false alerts for tags that are actually optional, use Pandora Box' "OptionalTags" command in Wordfast/Setup/PB.

Most optional tags are tagged items (like the unbreakable space, quotes, ampersand etc) that look like &amp; or <:hs> or &nbsp; etc. You may have them in the source segment but not in the target segment, or the reverse, according to the translation's needs. Thus, the following segment:

The R &amp; D department is ready .

Le Département "Recherche et Développement" est prêt .

is valid, even if there are three internal tags in the source segment and two in the target. The source segment's ampersand has not been re-used. There may be other exceptions where even non-optional tags must be added or omitted.

'''Long tags'''. Wordfast considers any contiguous text with an Internal style as a one tag. So for example

 align= "left" font= "Times New Roman" size= "12" > > < table align="center"> 

is considered one tag.

If this contiguous stretch of text actually contains more than one tag, and if these tags have to be handled separately, use the Ctrl+Alt+Up shortcut to make Wordfast treat this tag as separate placeables. The pairs of characters < and > as well as & and ; will be considered as tag beginning and tag ending.

Note that the PB option "BreakDownTags" will translate tags into symbolic, short entities such as <1> , <2> , etc. in any opened segment. When validating the segment, tags will be restored to their original syntax. This allows you to have shorter and more readable segments when long tags are present. When such a tag is selected as a placeable, the tag's full syntax appears in the status bar.

External tags
External tags ( tw4winExternal style) are kept out of the translation. Like internal tags, they must not be edited, deleted, translated etc.

! '''In case of doubt, stop and ask the client or the agency.''' Do not proceed if you are not sure you handle tags correctly. If you start working on a project with tags for the first time, submit your first translated file for review and approval before going any further.
Back to [[Wordfast Classic User Manual]]

Tagged files Wordfast Classic

2017-11-01T17:14:51Z

Samar:

Wordfast Classic is designed to translate the Word native "DOC" format. Tagged files are better translated with programs that were designed from the ground up to handle tagged files, like Wordfast PRO.

Wordfast Classic retains the capability to translate "tagged" files, but it should be noted that an Ms-Word tool cannot efficiently handle or protect tags. Translating tagged files with Ms-Word requires expertise, should things go wrong at any stage.

Some translation agencies, which are equipped with tagging software to prepare documents, may ask free-lance translators to work on tagged files. Agencies and free-lance translators should know that Wordfast is '''compatible with the most current tag formats, such as Trados and RWS Rainbow.''' Here is some advice for translating tagged documents. Please pay attention to the following advice, because tagged files that are not properly handled can cause serious problems.

''Agencies that entrust tagged files to a translator for the first time should review the first translated file immediately after the translator has completed it, to make sure tags have been properly handled. If necessary, adjustments should be made before going any further into the project.''

'''Internal tags'''
The red tags (usually with the style tw4winInternal) are internal and are mostly found within the text to be translated, and in the translation.
{|
|-
|Example:|| The final document.
|-
|translates into || Le document final.
|}
In this example, and are tags that command the bold type in HTML. The translator has positioned the red tags at the right position in the translated sentence. The translated text does not have a tw4winInternal (neither a tw4winExternal) style (with a "Normal" or "Translatable" style). Only tags have a tag (tw4winInternal) style, red or grey. Styles are important, because tagging/untagging software relies on style, not font colour, to differentiate tags from translated text.

! Be careful when typing. If you type regular text (for example, right after right after a <tag>), and notice that the text appears red, stop! Only tags must have the tw4winInternal style. Regular text should have another style, usually named "Normal", or "Translatable", whatever that is. In fact, the style of the regular text does not matter, as long as it is neither tw4winInternal nor tw4winExternal.
Note that to revert text from a tw4winInternal style (or any other style) to the default style, select the text and press Ctrl+Spacebar. A slower method involves the Style listbox, the mouse, etc. If you are not familiar with Ctrl+Spacebar, learn it right now: select some styled text, apply it and see how it works.

! '''Internal tags must normally not be modified, edited or translated'''. Some tags can be added or omitted if the translation requires it. Otherwise, the golden rule is that '''all internal tags''' (usually enclosed between < and >) present in the source segment must be '''duplicated in the target segment''', and positioned correctly.

To duplicate these internal tags, Wordfast provides a set of shortcuts. '''Ctrl+Alt+left/right''' will select the next/previous internal tag (in the source segment); '''Ctrl+Alt+down''' will duplicate ("bring down") the selected tag at the insertion point, in the target segment. You should get used to these shortcuts. For better speed, you can type < or / and AutoSuggest will pop up a list of available tags for quicker placement.

If you copy the source text into the target segment and translate by overwriting it, or if you edit an existing target segment, make sure the translated text does not have a tag (red or grey) style. If the cursor is immediately after a red (or grey) tag, whatever you type will also be red (or grey), and this causes problems later on. To avoid this, remember that if your cursor is immediately after a red tag, pressing Ctrl+Spacebar will restore the normal style at that point, and the text you type will not have a tag style. Ctrl+Spacebar is an Ms-Word shortcut.

In a regular tagged style, the only two important styles are tw4winInternal and tw4winExternal. Text outside tags can have any other style (styles named Normal, Translatable, etc.) or font attributes (bold, blue, whatever).

Here are examples of correct and uncorrect translation units:
{| border="1" style="border-collapse: collapse" width= "700px"
|-style="background:#eaecf0"
|Examples of translation units
|Notes
|-
|align= "center" | The <B> final document is here.

Le documentThe <B> final est ici.
|align= "center" | This TU is OK.
|-
|align= "center" | The The <B> final document is here.

Le documentThe <B> final est ici.
|align= "center" |Problem: the target word "final" has an internal tag style
|-
|align= "center" | The <B> final document is here.

<B> final est ici.
|align= "center" |Problem: the target segment's first tag has lost its internal (red) tag style.
|-
|align= "center" | The <B> final document is here.

Le document <B> final est ici.
|align= "center" | Problem: the target segment's second tag is missing (it should be ).
|}
Wordfast has a Quality Assurance option called "Identical tags in source/target segments". I recommend turning this QA option on. To avoid having false alerts for tags that are actually optional, use Pandora Box' "OptionalTags" command in Wordfast/Setup/PB.

Most optional tags are tagged items (like the unbreakable space, quotes, ampersand etc) that look like &amp; or <:hs> or &nbsp; etc. You may have them in the source segment but not in the target segment, or the reverse, according to the translation's needs. Thus, the following segment:

The R &amp; D department is ready .

Le Département "Recherche et Développement" est prêt .

is valid, even if there are three internal tags in the source segment and two in the target. The source segment's ampersand has not been re-used. There may be other exceptions where even non-optional tags must be added or omitted.

'''Long tags'''. Wordfast considers any contiguous text with an Internal style as a one tag. So for example

 align= "left" font= "Times New Roman" size= "12" > > < table align="center"> 

is considered one tag.

If this contiguous stretch of text actually contains more than one tag, and if these tags have to be handled separately, use the Ctrl+Alt+Up shortcut to make Wordfast treat this tag as separate placeables. The pairs of characters < and > as well as & and ; will be considered as tag beginning and tag ending.

Note that the PB option "BreakDownTags" will translate tags into symbolic, short entities such as <1> , <2> , etc. in any opened segment. When validating the segment, tags will be restored to their original syntax. This allows you to have shorter and more readable segments when long tags are present. When such a tag is selected as a placeable, the tag's full syntax appears in the status bar.

External tags
External tags ( tw4winExternal style) are kept out of the translation. Like internal tags, they must not be edited, deleted, translated etc.

! '''In case of doubt, stop and ask the client or the agency.''' Do not proceed if you are not sure you handle tags correctly. If you start working on a project with tags for the first time, submit your first translated file for review and approval before going any further.
Back to [[Wordfast Classic User Manual]]

Tagged files Wordfast Classic

2017-11-01T17:10:36Z

Samar:

Wordfast Classic is designed to translate the Word native "DOC" format. Tagged files are better translated with programs that were designed from the ground up to handle tagged files, like Wordfast PRO.

Wordfast Classic retains the capability to translate "tagged" files, but it should be noted that an Ms-Word tool cannot efficiently handle or protect tags. Translating tagged files with Ms-Word requires expertise, should things go wrong at any stage.

Some translation agencies, which are equipped with tagging software to prepare documents, may ask free-lance translators to work on tagged files. Agencies and free-lance translators should know that Wordfast is '''compatible with the most current tag formats, such as Trados and RWS Rainbow.''' Here is some advice for translating tagged documents. Please pay attention to the following advice, because tagged files that are not properly handled can cause serious problems.

''Agencies that entrust tagged files to a translator for the first time should review the first translated file immediately after the translator has completed it, to make sure tags have been properly handled. If necessary, adjustments should be made before going any further into the project.''

'''Internal tags'''
The red tags (usually with the style tw4winInternal) are internal and are mostly found within the text to be translated, and in the translation.
{|
|-
|Example:|| The final document.
|-
|translates into || Le document final.
|}
In this example, and are tags that command the bold type in HTML. The translator has positioned the red tags at the right position in the translated sentence. The translated text does not have a tw4winInternal (neither a tw4winExternal) style (with a "Normal" or "Translatable" style). Only tags have a tag (tw4winInternal) style, red or grey. Styles are important, because tagging/untagging software relies on style, not font colour, to differentiate tags from translated text.

! Be careful when typing. If you type regular text (for example, right after right after a <tag>), and notice that the text appears red, stop! Only tags must have the tw4winInternal style. Regular text should have another style, usually named "Normal", or "Translatable", whatever that is. In fact, the style of the regular text does not matter, as long as it is neither tw4winInternal nor tw4winExternal.
Note that to revert text from a tw4winInternal style (or any other style) to the default style, select the text and press Ctrl+Spacebar. A slower method involves the Style listbox, the mouse, etc. If you are not familiar with Ctrl+Spacebar, learn it right now: select some styled text, apply it and see how it works.

! '''Internal tags must normally not be modified, edited or translated'''. Some tags can be added or omitted if the translation requires it. Otherwise, the golden rule is that '''all internal tags''' (usually enclosed between < and >) present in the source segment must be '''duplicated in the target segment''', and positioned correctly.

To duplicate these internal tags, Wordfast provides a set of shortcuts. '''Ctrl+Alt+left/right''' will select the next/previous internal tag (in the source segment); '''Ctrl+Alt+down''' will duplicate ("bring down") the selected tag at the insertion point, in the target segment. You should get used to these shortcuts. For better speed, you can type < or / and AutoSuggest will pop up a list of available tags for quicker placement.

If you copy the source text into the target segment and translate by overwriting it, or if you edit an existing target segment, make sure the translated text does not have a tag (red or grey) style. If the cursor is immediately after a red (or grey) tag, whatever you type will also be red (or grey), and this causes problems later on. To avoid this, remember that if your cursor is immediately after a red tag, pressing Ctrl+Spacebar will restore the normal style at that point, and the text you type will not have a tag style. Ctrl+Spacebar is an Ms-Word shortcut.

In a regular tagged style, the only two important styles are tw4winInternal and tw4winExternal. Text outside tags can have any other style (styles named Normal, Translatable, etc.) or font attributes (bold, blue, whatever).

Here are examples of correct and uncorrect translation units:
{| border="1" style="border-collapse: collapse" width= "700px"
|-style="background:#eaecf0"
|Examples of translation units
|Notes
|-
|align= "center" | The <B> final document is here.

Le documentfinal est ici.
|align= "center" | This TU is OK.
|-
|align= "center" | The final document is here.

Le documentfinal est ici.
|align= "center" |Problem: the target word "final" has an internal tag style
|-
|align= "center" | The final document is here.

Le document final est ici.
|align= "center" |Problem: the target segment's first tag has lost its internal (red) tag style.
|-
|align= "center" | The final document is here.

Le documentfinal est ici.
|align= "center" | Problem: the target segment's second tag is missing (it should be ).
|}
Wordfast has a Quality Assurance option called "Identical tags in source/target segments". I recommend turning this QA option on. To avoid having false alerts for tags that are actually optional, use Pandora Box' "OptionalTags" command in Wordfast/Setup/PB.

Most optional tags are tagged items (like the unbreakable space, quotes, ampersand etc) that look like &amp; or <:hs> or &nbsp; etc. You may have them in the source segment but not in the target segment, or the reverse, according to the translation's needs. Thus, the following segment:

The R &amp; D department is ready .

Le Département "Recherche et Développement" est prêt .

is valid, even if there are three internal tags in the source segment and two in the target. The source segment's ampersand has not been re-used. There may be other exceptions where even non-optional tags must be added or omitted.

'''Long tags'''. Wordfast considers any contiguous text with an Internal style as a one tag. So for example

 align= "left" font= "Times New Roman" size= "12" > > < table align="center"> 

is considered one tag.

If this contiguous stretch of text actually contains more than one tag, and if these tags have to be handled separately, use the Ctrl+Alt+Up shortcut to make Wordfast treat this tag as separate placeables. The pairs of characters < and > as well as & and ; will be considered as tag beginning and tag ending.

Note that the PB option "BreakDownTags" will translate tags into symbolic, short entities such as <1> , <2> , etc. in any opened segment. When validating the segment, tags will be restored to their original syntax. This allows you to have shorter and more readable segments when long tags are present. When such a tag is selected as a placeable, the tag's full syntax appears in the status bar.

External tags
External tags ( tw4winExternal style) are kept out of the translation. Like internal tags, they must not be edited, deleted, translated etc.

! '''In case of doubt, stop and ask the client or the agency.''' Do not proceed if you are not sure you handle tags correctly. If you start working on a project with tags for the first time, submit your first translated file for review and approval before going any further.
Back to [[Wordfast Classic User Manual]]