Wordfast Wiki - User contributions [en]

Machine Translation in Wordfast Pro

2022-03-02T19:02:46Z

Jamie: Fixed a couple of typos, added some italics to options, added an image, added a couple of clarifications

[[Wordfast Pro]] (WFP) can send source segments to third-party, cloud-based '''Machine Translation''' (MT) sources, receive suggested MT translations, and make them available to the translator or use them to [[Pre-Translation in Wordfast Pro|pre-translate]] documents. It can speed up translation work. WFP only connects to MT sources if you activate this feature in WFP ''Preferences''.

To use Machine Translation in WFP, click the [[File:Sidebar_Preferences_Icon.png|20px]] '''''Preferences''''' icon on the sidebar, go to '''''Machine Translation''''' under '''''General Preferences''''', and enable the MT providers you prefer.

'''WorldLingo''' is the only out-of-the-box free provider. You need to subscribe and obtain an API key to use the other ones (see links when you click on “Enable…”).

The '''Microsoft Translator API''' is free for up to 2 million characters per month. Follow [https://docs.microsoft.com/en-us/azure/cognitive-services/translator/translator-how-to-signup these instructions] to get your own API key. '''IMPORTANT''': When creating your resource on Azure, make sure to choose “Central US” as your resource group region and “Global” as the resource region.

To use '''DeepL''' in Wordfast Pro, you need a paid [https://www.deepl.com/pro-tool_integration.html DeepL plan]. Note that DeepL offers two kinds of API keys – one is for web applications and the other one is for CAT tools such as Wordfast. Please make sure you are using the right key. If you are not sure about this, please consult the DeepL team.

Using ''Custom MT'' at the bottom of the options, you can also instruct Wordfast Pro to connect to MT sources that are not among the listed options. For example, you can [[Connecting_Wordfast_Pro_to_Modern_MT|connect to Modern MT]].

Tick the option ''Allow all unedited segments in active document to be leveraged with MT'' to use MT when there is no TM match. Your primary MT result will be automatically leveraged in the target segment.

[[File:2021-03-30_11-25-45.png|800px|WFP Preferences > Machine Translation]]

'''IMPORTANT''': Sometimes machine translated segments do not need to be edited, especially when they are very short. By default, Wordfast Pro will not commit unedited MT segments to your TM. If you want to commit these segments (recommended), make sure to update your [[New vs Current Project Preferences|new/current project preferences]] under the '''Translation Memory''' section. Tick the box next to ''Write 'unedited MT' to TM'' to commit these perfectly good segments.

[[File:2022-02-24_13-10-34.png|800px|WFP Preferences > Translation Memory]]

[[Category:Wordfast Pro]]

File:Sidebar Preferences Icon.png

2022-03-02T18:47:09Z

Jamie:

Working with Packages (or GLP files) in Wordfast Pro

2022-02-28T22:52:37Z

Jamie: Fixed a couple of typos, added some italics to options

Wordfast Pro 5.x and above is much more advanced and project centric in terms of project management than its predecessor, Wordfast Pro 3.x. The newer version allows you to create a project, export it as a package – roughly equivalent to a zip file which contains source files, reference files, bilingual files, linguistic assets and project settings – and send it to someone else so they can recreate the project on their instance of Wordfast Pro to perform the task they have been assigned. A user may also want to export a project in order to work on it on a different computer (laptop vs desktop).

== Exporting a project ==

Once you have created a project, there are two ways to export it:
* From the '''Project List''' view: select the project, then click on the '''''Export Package''''' icon.
* From the '''Current Project''' view: under the '''Project Files''' tab, click on the '''''Export Package''''' icon.

After clicking on the '''''Export Package''''' icon, you will see the following window:

[[File:Export_package.png]]

Under the ''Export'' section, you have two options:
# Export the entire project with all of the project’s resources and target languages into a single package.
# Export specific resources or separate packages if there is more than one target language.

You can then give the package the same name as the project (if multiple target languages, each package will have the target language’s codes appended at the end) or a custom name.

Finally, choose a location to save the package to. The saved package has the extension .''glp''.

Typically, if you are a project manager, you would first export a package, then later import a package. The opposite is true for the translator or revisor: you would first import a package and later export it to send back the completed task.

== Importing a package ==

There are generally two scenarios when importing a package:
# You are '''translator''' receiving a package from a project manager for a translation or revision task.
# You are a '''project manager''' receiving a package from a translator and containing the completed translation or revision task.

=== Scenario 1 – I’m a '''translator''' ===

From the '''Project List''' view, you can either drag and drop a .glp package into Wordfast Pro or click on the '''''Import Package''''' icon, then select the package.

In the '''Import Package''' window, you will then see two options:

[[File:Import package.png]]

# ''Update an existing project''
# ''Create a new project''

You need to choose the ''Create a new project'' option, then specify the name and location you want to create the project.

=== Scenario 2 – I’m a '''project manager''' ===

Open the project you had previously created, then drag and drop the package you received from the translator into the open project or click on the '''''Import Package''''' icon. Wordfast will pre-select the option to update the existing project. You should choose ''Only update the project’s existing TXLF files'' unless a file needed to be added to the project by the translator after the project was already underway.

Click on '''''Import''''' and you should see the ''Complete'' status bar move to 100% (if the translator marked all segments as ''translated'').

== Tips & Tricks ==
# '''Unzipping a package''': as mentioned earlier, a .glp package is simply a zip file with a different extension. If you are having problems importing the package, try changing the extension from .glp to .zip and then unzipping it. Inside you will find all the resources you need to “recreate” the project manually on your end.
# '''File organization''': be careful when organizing your incoming and outgoing packages. There is nothing worse than sending the wrong package to someone, then checking out for the day or weekend! You will have one frustrated translator or project manager to deal with…
# '''Project templates''': if you need to deploy project settings enterprise-wide, the most tech savvy person on your team can create a template project with your server TM and glossary settings, then export as a package and send it to everyone on the team. Team members import the package and reuse the project as a template when creating new projects moving forward.

Useful regular expressions (Regex)

2021-05-14T22:54:40Z

Jamie: Reorganized page and added major section regarding numbers in a specific format

A '''regular expression (regex or regexp)''' is a sequence of characters that define a search pattern.<ref>Check out [https://en.wikipedia.org/wiki/Regular_expression#Basic_concepts this article] for a more detailed explanation of the history of regular expressions and how they work.</ref> They can be very helpful in the Editor View for both the filter bar (used to show/hide specific segments) and the Find/Replace dialog. Below are a few examples of useful regexes. In order to use them in [[Wordfast Pro]], make sure any available '''regex''' option is enabled accordingly.

==Filter Bar: Showing/Hiding Certain Segments==

===Hide number-only segments===

Use the following regex in the segment filtering bar:

^(([0-9][^\n]*[^0-9])|([^0-9][^\n]*[0-9])|([^0-9]?[^\n]*[^0-9]))$

This regex will also hide numbers with punctuation (decimals, etc.)

===Show only number-only segments===

Use the following regex in the segment filtering bar:

^(?:(?:-|–|(?:(?:\$|€|£)(?:\h)?))?(?:\d{1,3})(?:\h|,|\.|(?:(?:\h)?(?:%|\$|€|£)))?)+$

If you have numbers like 8,675,309.00 that need to be replaced with 8.675.309,00, you can copy all sources to target with the filter applied, then apply a 3-step find and replace:
# Find '''.''' and replace with '''DUMMY'''
# Find ''',''' and replace with '''.'''
# Find '''DUMMY''' and replace with ''','''

===Show only thousands, ten thousands or hundred thousands surrounded by parentheses===

If you negative monetary figures in a financial report, they are generally surrounded by parentheses like this (1,234) or (10,123) or (100,123).

Use the following regex in the segment filtering bar to filter out these segments when the divider is a non-breaking space:

$\d{1,3}∘\d{3}$

And this one if the divider is a comma:

$\d{1,3},\d{3}$

With the filter in place, copy all sources, then find ∘ and replace with , or vice versa. (∘ represents a non-breaking space).

===Show only segments containing ''numbers in a specific format''===

Numbers that need to be converted to a different format can be found within any segment containing other text. Depending on the source number format you need to convert, use the corresponding regex from option A, B, or C in the table below to show only those segments for later conversion.

{| class="wikitable"
|-
! style="color:black" | Option
! style="color:black" | Thousands
! style="color:black" | Decimal
! style="color:black" | Example
! style="color:black" | Regex
|-
|A
|Space*
|Comma
| style="font-weight: bold" |1 000,00
|<nowiki>(?:\d{1,3})(?:(?:(?:(?<!,\d{3})( |\u00A0|\u2009|\u202F)(?=\d{3}[^\d])))|(?:(?<!\.\d{3}),(?=\d(?!\d+(,\d|\.\d)))))</nowiki>
|-
|B
|Dot
|Comma
| style="font-weight: bold" |1.000,00
|<nowiki>(?:\d{1,3})(?:(?:(?<!,\d{3})\.(?=\d{3}[^\d]))|(?:(?<!\d( |\u00A0|\u2009|\u202F)\d{3}),(?! |\d{3}(,[^ ]|\.[^ ]))))</nowiki>
|-
|C
|Comma
|Dot
| style="font-weight: bold" |1,000.00
|<nowiki>(?:\d{1,3})(?:(?:(?<!([\d]( |\u00A0|\u2009|\u202F)|(\.))\d{3}),(?=\d{3}[^\d]))|(?:(?<!\d( |\u00A0|\u2009|\u202F)\d{3})\.(?!$| |\d{3}(,[^ ]|\.[^ ]))))</nowiki>
|}
* Includes no-break space (U+00A0), thin space (U+2009), and narrow no-break space (U+202F)

==Filter Bar: Combine with Find/Replace==

===Replace ''numbers in a specific format''===

If you want to convert numbers between the formats in the table above, locate which options you want to convert between in the table below and follow the respective steps.

{| class="wikitable"
|-
! style="color:black" |(A) 1 000,00 
to 
(C) 1,000.00
! style="color:black" |(B) 1.000,00 
to 
(C) 1,000.00
! style="color:black" |(C) 1,000.00 
to 
(A) 1 000,00
! style="color:black" |(C) 1,000.00 
to 
(B) 1.000,00
|- style="vertical-align:top;"
|
# Copy option '''(A)''' regex from table above NOTE: Remaning steps are in WFP
# With a fresh file (target segments all empty) open in ''Editor View'', enable ''Regex'' option in segment filter bar
# Paste option '''(A)''' regex into filter field next to ''Regex'' option, press Enter
# After filter is applied, go to ''Translation'' tab and click ''Copy All Sources''
# Press Ctrl+H to show ''Find/Replace'' dialog
# Enable ''Use Regex'' and ''Search Target'' options, disable ''Search Source'' option
# Paste following expression into ''Find Next:'' field
#;<nowiki>(\d{1,3})(?: |\u00A0|\u2009|\u202F)(\d)</nowiki>
# Paste following expression into the ''Replace with:'' field
#;<nowiki>$1DUMMY$2</nowiki>
# Click ''Replace All''
# Paste following expression into ''Find Next:'' field
#;<nowiki>(\d),(\d)</nowiki>
# Paste following expression into ''Replace with:'' field
#;<nowiki>$1.$2</nowiki>
# Click ''Replace All''
# Paste following expression into ''Find Next:'' field
#;<nowiki>DUMMY(?=.*\d{3}\.)</nowiki>
# Paste following comma into ''Replace with:'' field
#;,
# Click ''Replace All'' NOTE: Stop here unless source numbers had thousand''th'' place spaces; otherwise, also do 16–18.
# Paste following expression into ''Find Next:'' field
#;DUMMY
# Clear ''Replace with:'' field and leave empty
# Click ''Replace All''
|
# Copy option '''(B)''' regex from table above NOTE: Remaning steps are in WFP
# With a fresh file (target segments all empty) open in ''Editor View'', enable ''Regex'' option in segment filter bar
# Paste option '''(B)''' regex into filter field next to ''Regex'' option, press Enter
# After filter is applied, go to ''Translation'' tab and click ''Copy All Sources''
# Press Ctrl+H to show ''Find/Replace'' dialog
# Enable ''Use Regex'' and ''Search Target'' options, disable ''Search Source'' option
# Paste following expression into ''Find Next:'' field
#;<nowiki>(\d{1,3})\.(\d)</nowiki>
# Paste following expression into the ''Replace with:'' field
#;<nowiki>$1DUMMY$2</nowiki>
# Click ''Replace All''
# Paste following expression into ''Find Next:'' field
#;<nowiki>(\d),(\d)</nowiki>
# Paste following expression into ''Replace with:'' field
#;<nowiki>$1.$2</nowiki>
# Click ''Replace All''
# Paste following expression into ''Find Next:'' field
#;DUMMY
# Paste following comma into ''Replace with:'' field
#;,
# Click ''Replace All''
|
# Copy option '''(C)''' regex from table above NOTE: Remaning steps are in WFP
# With a fresh file (target segments all empty) open in ''Editor View'', enable ''Regex'' option in segment filter bar
# Paste option '''(C)''' regex into filter field next to ''Regex'' option, press Enter
# After filter is applied, go to ''Translation'' tab and click ''Copy All Sources''
# Press Ctrl+H to show ''Find/Replace'' dialog
# Enable ''Use Regex'' and ''Search Target'' options, disable ''Search Source'' option
# Paste following expression into ''Find Next:'' field
#;<nowiki>(\d{1,3}),(\d)</nowiki>
# Paste following expression into the ''Replace with:'' field
#;<nowiki>$1DUMMY$2</nowiki>
# Click ''Replace All''
# Paste following expression into ''Find Next:'' field
#;<nowiki>(\d)\.(\d)</nowiki>
# Paste following expression into ''Replace with:'' field
#;<nowiki>$1,$2</nowiki>
# Click ''Replace All''
# Paste following expression into ''Find Next:'' field
#;DUMMY
# Paste following highlighted ''narrow no-break space'' character into ''Replace with:'' field
#; 
# Click ''Replace All''
|
# Copy option '''(C)''' regex from table above NOTE: Remaning steps are in WFP
# With a fresh file (target segments all empty) open in ''Editor View'', enable ''Regex'' option in segment filter bar
# Paste option '''(C)''' regex into filter field next to ''Regex'' option, press Enter
# After filter is applied, go to ''Translation'' tab and click ''Copy All Sources''
# Press Ctrl+H to show ''Find/Replace'' dialog
# Enable ''Use Regex'' and ''Search Target'' options, disable ''Search Source'' option
# Paste following expression into ''Find Next:'' field
#;<nowiki>(\d{1,3}),(\d)</nowiki>
# Paste following expression into the ''Replace with:'' field
#;<nowiki>$1DUMMY$2</nowiki>
# Click ''Replace All''
# Paste following expression into ''Find Next:'' field
#;<nowiki>(\d)\.(\d)</nowiki>
# Paste following expression into ''Replace with:'' field
#;<nowiki>$1,$2</nowiki>
# Click ''Replace All''
# Paste following expression into ''Find Next:'' field
#;DUMMY
# Paste following dot into ''Replace with:'' field
#;.
# Click ''Replace All''
|}

==Find/Replace==

===Find thousands separated by a non-breaking space and replace NBSP with a comma===

Find:

(\d{1,3})∘(\d{3})

Replace with:

$1,$2

Make sure to search target segments only, test on a few segments before replacing all, and run this operation twice to account for numbers in the millions.

===Invert currency symbols===

Say you have a lot of monetary values like 103,50€ in your document and you want to globally find/replace with €103.50, how would you do this?

Open the ''Find/Replace'' function and be sure to tick the '''Use Regex''' box.

Type the following regex in the ''Find what'' field:

(^[^,]+?)(,)([^€]+?)(€)

Type the following regex in the ''Replace with'' field:

\€$1\.$3

'''NOTE''': This only works for values up to 999. Values in the thousands will need another regex operation to replace comma/space/decimal with comma/space/decimal.

==References==

[[Category:Wordfast Pro]]

Building a Rules File for Tagged Text Translation in Wordfast Pro

2019-02-08T01:22:57Z

Jamie: Tagged text translation in Wordfast Pro: Learn the basics from creating a rules file (*.properties) to extracting specified translatable text into a WFP project.

The following instructions are for building a '''rules''' (*''.properties'') file for tagged text translation in [[Wordfast Pro 3|Wordfast Pro 3]] (WFP3) or [[Wordfast Pro 5|Wordfast Pro 5]] (WFP5). A rules file tells either Wordfast Pro (WFP) application where to look for translatable text in a tagged text file so it can extract the text as source segments.

==Create a new rules (*''.properties'') file using a text editor==

# Open a preferred text editor (e.g., Notepad in Windows)
# Add the following two extraction rules to a new blank text file:
#: ''paragraphPrefix.1=
#: ''paragraphSuffix.1=
# Name and save the text file to a simple location (e.g., the desktop), note that location for future reference, and close the file
# Go to that file's location now and change its file extension from ''.txt'' to ''.properties''
#: NOTE: If you don't see the file's ''.txt'' extension, go to [http://www.wikihow.com/Change-a-File-Extension this wikiHow tutorial] and follow ''Method 2'' or ''Method 3'' for Windows, or ''Method 4'' for Mac.
# Reopen the text file (now a rules, or .properties, file) in the preferred text editor in preparation for the next section below
#: NOTE: If the rules file is not recognized by the operating system, right-click the file, go to ''Open With'' and choose the preferred text editor.

==Determine tag patterns for translatable text==

# Open the desired source tagged text file in the preferred text editor
#: NOTE: If the source tagged text file is not recognized by the operating system, right-click the file, go to ''Open With'' and choose the preferred text editor.
# Within the opened source tagged text file, look for recurring tags (or other markup) at the beginning and ending of any translatable text and note these recurring tags/markup
#* EXAMPLE 1: Below, note that '''<string>''' opens translatable text and '''</string>''' closes translatable text.
#:: '''<string>'''Text to translate'''</string>'''
#:: '''<string>'''More text to translate'''</string>'''
#:: '''<string>'''Final text to translate'''</string>'''
#* EXAMPLE 2: Below, note that '''=·''' (equals symbol followed by a space) opens translatable text (everything before '''=·''' is not relevant) and '''¶''' (end of line) closes translatable text.
#:: String '''=·'''Text to translate¶
#:: String '''=·'''More text to translate¶
#:: String '''=·'''Final text to translate¶
#: NOTE: Both '''·''' (space formatting mark) and '''¶''' (end of line formatting mark) in all examples are used for visual convenience and will not necessarily be visible in your text editor.
#* EXAMPLE 3: Below, note that in some cases '''<string>''' opens translatable text and '''</string>''' closes translatable text, and in other cases '''=·''' (equals symbol followed by a space) opens translatable text (everything before '''=·''' is not relevant) and '''¶''' (end of line) closes translatable text.
#:: '''<string>'''Text to translate'''</string>'''
#:: String '''=·'''Text to translate¶
#:: '''<string>'''More text to translate'''</string>'''
#:: String '''=·'''More text to translate¶
# Leave the source tagged text file open in the preferred text editor in preparation for the next section below

==Add extraction rules to the new rules file==

# Switch to the open rules file (re-open it if it is not still open) and add each set of opening/closing tags (or other markup) as a prefix-suffix extraction rule pair
#* Using EXAMPLE 1 from above, '''<string>''' is prefix 1 and '''</string>''' is suffix 1
#:: ''paragraphPrefix.1='''<string>'''
#:: ''paragraphSuffix.1='''</string>'''
#* Using EXAMPLE 2 from above, '''=·''' (equals symbol followed by a space) is prefix 1 and '''¶''' (end of line) is suffix 1.
#: NOTE: '''(?m)$''' must be used to represent '''¶''' (end of line) in extraction rules.
#:: ''paragraphPrefix.1='''=·'''
#:: ''paragraphSuffix.1='''(?m)$'''
#* Using EXAMPLE 3 from above, '''<string>''' is prefix 1 and '''</string>''' is suffix 1, and '''=·''' (equals symbol followed by a space) is prefix 2 and '''¶''' (end of line) is suffix 2.
#: NOTE: '''(?m)$''' must be used to represent '''¶''' (end of line) in extraction rules.
#:: ''paragraphPrefix.1='''<string>'''
#:: ''paragraphSuffix.1='''</string>'''
#:: ''paragraphPrefix.2='''=·'''
#:: ''paragraphSuffix.2='''(?m)$'''
#: NOTE: In the case above where multiple prefix/suffix extraction rule pairs are required, each additional pair must use next highest number (e.g., a third pair would be ''paragraphPrefix.'''3'''='' │ ''paragraphSuffix.'''3'''=''), and rule pairs are processed in the order given.
#* OPTION: Some translatable text may include HTML tags within it. In this case, a prefix-suffix extraction rule pair can optionally include the extraction rule ''paragraphFormat.1=html-included'', which ensures HTML tags are converted to internal WFP tags and are thus not translatable nor included in word counts. If EXAMPLE 1 from directly above contained translatable text with HTML tags, the optional rule would be a third line added to the prefix-suffix pair and written as follows:
#:: ''paragraphPrefix.1=<string>
#:: ''paragraphSuffix.1=</string>
#:: '''''paragraphFormat.1=html-included
# Save the updated rules file, leave it open in the preferred text editor, and proceed to either the WFP5 or WFP3 section below according to the tool in use

==Add a file format filter to [[Wordfast Pro 5|Wordfast Pro 5]] and import source tagged text file==

: NOTE: Skip this section and go to the next if you are using WFP3.
# Switch to the opened source tagged text file (re-open it if it is not still open) and determine its encoding
#* METHOD 1: Check the first line of the file for an XML declaration, which states the encoding (see below in bold). If there is no XML declaration, proceed to METHOD 2.
#:: ''<?xml version="1.0" encoding="'''UTF-8'''"?>
#* METHOD 2: Check the text editor for the encoding of the open file (refer to the text editor's documentation for help). See below for how to do this in Windows Notepad.
#:: Go to {{menu|File}} > {{menu|Save As}} and locate the {{menu|Encoding}} drop-down at the bottom of the {{menu|Save As}} dialog box. Once the encoding has been determined, cancel the {{menu|Save As}} dialog.
# Open [[Wordfast Pro 5|Wordfast Pro 5]]
# Choose {{menu|Create Project}} and set up the project as usual, but DO NOT add the source tagged text file yet or complete the wizard
# Still in the wizard, choose {{menu|Create Filter}}
# From the {{menu|Choose file format}} drop-down, select {{menu|Text based filter (*.xml)}}
# In the {{menu|Filter Name}} field, type a simple, appropriate name for the new filter
# From the {{menu|Encoding}} drop-down, select the one that matches what you noted in step 1 of this section
# From the {{menu|Target Encoding}} drop-down, select the same encoding as the source tagged text file
# Next to {{menu|Extraction Rules}}, choose the {{menu|Browse...}} button, then locate and open your rules (''.properties'') file
# In the {{menu|Extension}} field, type the source file extension (without preceding period) and click {{menu|OK}}
# Choose {{menu|Add File}}, locate the folder containing the source tagged text file, select it, and choose {{menu|Open}} (or simply drag and drop the source tagged text file into the files pane)
# In the {{menu|Type}} column, choose the drop-down next to the source tagged text file and select your new filter's name
# Select {{menu|Create Project}} to complete the wizard as usual
: NOTE: Skip the next section and go to the "Make any rules file adjustments/corrections" section after it if you are using WFP5.

==Add a file format filter to [[Wordfast Pro 3|Wordfast Pro 3]] and import source tagged text file==

: NOTE: Skip this section and go to the next if you are using WFP5.
# Switch to the opened source tagged text file (re-open it if it is not still open) and determine its encoding
#* METHOD 1: Check the first line of the file for an XML declaration, which states the encoding (see below in bold). If there is no XML declaration, proceed to METHOD 2.
#:: ''<?xml version="1.0" encoding="'''UTF-8'''"?>
#* METHOD 2: Check the text editor for the encoding of the open file (refer to the text editor's documentation for help). See below for how to do this in Windows Notepad.
#:: Go to {{menu|File}} > {{menu|Save As}} and locate the {{menu|Encoding}} drop-down at the bottom of the {{menu|Save As}} dialog box. Once the encoding has been determined, cancel the {{menu|Save As}} dialog.
# Open [[Wordfast Pro 3|Wordfast Pro 3]]
# Choose {{menu|Edit}} then {{menu|Preferences}}
# In the {{menu|Preferences}} list on the left, go to {{menu|Translations}} > {{menu|Filters}} > {{menu|Formats}}
# To the right of {{menu|Available Formats}}, choose {{menu|New}}
# In the {{menu|New Format}} dialog, scroll down and choose {{menu|Text Based Filter}}
# In the {{menu|Filter Name}} field, type a simple, appropriate name for the new filter
# From {{menu|Source Encoding}} drop-down, select the one that matches what you noted in step 1 of this section
# Select {{menu|Target Encoding}} option, then select the same encoding as the source tagged text file from the drop-down
# Next to {{menu|Conversion rules}}, choose the {{menu|...}} button, then locate and open your rules (''.properties'') file
# In the {{menu|Extension}} field, type *. followed by the source file extension (e.g., *.txt) and click {{menu|OK}}
# If necessary, create a project from {{menu|File}} > {{menu|Create Project}}
# With the appropriate project active, choose {{menu|File}} > {{menu|Open File}}, locate the folder containing the source tagged text file, select it, and choose {{menu|Open}} (or simply drag and drop the source tagged text file into WFP3's ''Editor Perspective'')
# In the {{menu|Choose Format}} dialog that appears, select your new filter's name and then {{menu|OK}}

==Make any rules file adjustments/corrections==

: NOTE: If WFP extracted translatable segments from the source tagged text file as expected, skip this section and proceed to translation. Otherwise, continue below.
# ISSUE: ''File opens in WFP, but unintended text is included or some translatable text is missing.''
#* SOLUTION: This usually means that the prefix-suffix extraction rule pair is too general (unintended text is included) or too specific (translatable text is missing). Start by reopening the rules file AND the source tagged text file in the preferred text editor. Switch to the imported source tagged text file already open in WFP, note a segment with unintended text or a location where translatable text is missing, then return to the source tagged text file in the preferred text editor and locate that item. Once located, it should help to determine how to adjust the rules file. After each rules file adjustment, start a new project with the source tagged text file and updated rules file to see if the adjustment fixed the issue.
#* EXAMPLE: In the three lines below, '''<string>''' generally starts translatable text and '''</string>''' generally ends translatable text. However, the red text in the second and third lines is problematic.
## '''<string>'''Text to translate'''</string>''' │ EXTRACTION = ''Text to translate''
## '''<string "length=4">'''More text to translate'''</string>''' │ EXTRACTION = ''(nothing)''
##* The opening tag variation in red prevents text extraction. A regular expression (regex) needs to be used to capture any variation of the opening tag, such as the highlighted part of the example below. ''paragraphPrefix.1='''<string[^>]*>'''''
## '''<string>'''Final text to translate'''<reserved>'''DO NOT TRANSLATE'''</reserved></string>''' │ EXTRACTION = ''Final text to translate<reserved>DO NOT TRANSLATE</reserved>''
##* The '''<reserved>''' tag pair and the untranslatable text they encase fall between the prefix-suffix '''<string>''' tag pair, so are included in the translatable text. To completely exclude the '''<reserved>''' tag pair and any text between them, add an '''externalTag.N=''' line after the prefix and suffix lines, add the '''<reserved>''' tag pair, and use a regex between them to capture the text (see number one below; regex is highlighted). To include this content for context but make it untranslatable as WFP tags, add an '''internalTag.N=''' line after the prefix and suffix lines, add the '''<reserved>''' tag pair, and use a regex between them to capture the text (see number two below; regex is highlighted).
##:#''paragraphPrefix.1=<string>'' ''paragraphSuffix.1=</string>'' '''''externalTag.1=<reserved>.*?</reserved>'''''
##:#''paragraphPrefix.1=<string>'' ''paragraphSuffix.1=</string>'' '''''internalTag.1=<reserved>.*?</reserved>'''''
# ISSUE: ''Source tagged text file does not open and an error message is displayed indicating there is no translatable text.
#* SOLUTION: This usually means there is an issue with the prefix or suffix text due to a typo, misspelling, or prefix/suffix choice. Start by reopening the rules file AND the source tagged text file in the preferred text editor. Go to the rules file and check for typos or misspellings in the prefix and suffix text. Correct any issues that are found and save the rules file. If none are found, go to the source tagged text file in the preferred text editor and double-check that translatable text is indeed located between the prefix and suffix text that you specified in the rules file. Again, correct any issues that are found and save the rules file. After each rules file adjustment, start a new project with the source tagged text file and updated rules file to see if the adjustment fixed the issue. WFP3 NOTE: If the source tagged text file has an associated TXML file next to it, delete it before importing the source tagged text file again. Otherwise, WFP3 will simply reopen the previously created and problematic TXML instead of generating a new one from the updated rules file.
#* EXAMPLE: The two items below illustrate the issues described above if the sample source tagged text is '''<oops></oops><string>'''Text to translate'''</string>'''.
## ''paragraphPrefix.1='''<strin>''''' ''paragraphSuffix.1='''</string>'''''
##* The typo (i.e., the missing "g") in the prefix prevents any translatable text from being extracted.
## ''paragraphPrefix.1='''<oops>''''' ''paragraphSuffix.1='''</oops>'''''
##* Mistakenly choosing the '''<oops>''' tag, which does not encase any translatable text in this example, prevents anything from being extracted. Switching it to the correct '''<string>''' tag fixes the issue.
# ISSUE: ''Source tagged text file does not open, or project creation action appears to do nothing. An error message may or may not be displayed.
#* SOLUTION: This usually means there is an issue with a regular expression (regex) in the rules file. Regexes can be used, for example, to specify variations in prefixes, suffixes, external tags, and/or internal tags, or to capture chunks of general text (see ISSUE 1's second and third EXAMPLE items above for instances of how this is implemented). Go to the rules file and check any regexes for typos, incorrect syntax, or incomplete sets/groups (e.g., items that require parentheses or square brackets). Correct any issues that are found and save the rules file. After each rules file adjustment, start a new project with the source tagged text file and updated rules file to see if the adjustment fixed the issue. WFP3 NOTE: If the source tagged text file has an associated TXML file next to it, delete it before importing the source tagged text file again. Otherwise, WFP3 will simply reopen the previously created and problematic TXML instead of generating a new one from the updated rules file.
#* EXAMPLE: The two items below illustrate the issues described above if the sample source tagged text is '''<string "length=3">'''\"Text to\n translate\"'''</string>'''.
## ''paragraphPrefix.1='''<string[^>*>'''''
##* The stated prefix above includes a regex (to capture any variation of the opening tag) whose exclude character set '''[^]''' is missing its closing square bracket between the two red characters. The fix needed in order for WFP to understand the regex is then '''<string;[^>]*>'''''.
## ''internalTag.1='''\[^\s]'''''
##* The regex above is intended to locate within translatable text a literal backslash character followed by ''any'' single character that is NOT a white space ('''[^]''' = any character NOT specified within the square brackets; '''\s''' = any white space character, such as a space or tab). Anything the expression locates is then marked up as an untranslatable WFP tag, so '''\"''' from the sample source tagged text above would be marked up. However, regexes processed by Java, the programming language of WFP, must escape ''any'' backslashes by preceding them with a backslash. Thus, '''[^\s]''' from ''internalTag.1='' above becomes '''[^\\s]''' in a rules file. The second problem is that the engine that interprets regular expressions has its own requirement of escaping a literal backslash character by preceding it with a backslash, so the first '''\''' from ''internalTag.1='' above becomes '''\\'''. For Java to understand, both of those backslashes must be escaped with a backslash, thus yielding '''\\\\''' in a rules file. The final fix for WFP to understand the entire regex is then '''\\\\[^\\s]'''.

[[Category:Wordfast Pro 5]] [[Category:Wordfast Pro 3]]

Translating WordPress XLIFF files in Wordfast Pro

2017-04-05T19:16:23Z

Jamie: New article

The following instructions are for those who want to translate '''Wordpress (WP) XLIFF''' files in [[Wordfast Pro 4|Wordfast Pro 4]]. This process is required because WP XLIFF files differ from standard XLIFF files.

There are two steps to translate WP XLIFF files in [[Wordfast Pro 4|Wordfast Pro 4]]:
# Create a conversion rules (*''.properties'') file in a text editor
# Add a file format filter to [[Wordfast Pro 4|Wordfast Pro 4]]

==Create a conversion rules (*''.properties'') file in a text editor==

# Open your preferred text editor (e.g., Notepad in Windows)
# Add the following italicized text to a new blank text file:
#: ''paragraphPrefix.1=<target><!\\[CDATA\\[
#: ''paragraphSuffix.1=\\]\\]></target>
#: ''paragraphFormat.1=html-included
#: ''converter.regexp.collapsetags=true
# Name and save the text file to a safe location and note the location
# Go to the file and change the extension from ''.txt'' to ''.properties''
#: NOTE: If you don't see the ''.txt'' extension, go to [http://www.wikihow.com/Change-a-File-Extension this wikiHow tutorial] for more information, but ignore its Method 1.

==Add a file format filter to [[Wordfast Pro 4|Wordfast Pro 4]]==

# Open your WP XLIFF source file with your preferred text editor, note the encoding in the XML header, then close the file and return to [[Wordfast Pro 4|Wordfast Pro 4]]
# Under {{menu|Create Project}}, select {{menu|Use the advanced project wizard}}
# In wizard step 3 of 6 {{menu|Add Source Files}}, select {{menu|Create Filter Type}}
# From the {{menu|Choose file format}} drop-down, select {{menu|Text based filter (*.xml)}}
# Type an appropriate name for the new filter in the {{menu|Filter Name}} field
# From the {{menu|Encoding}} drop-down, select the one that matches what you noted in step 1 of this section
# Click the {{menu|Browse}} button next to {{menu|Extraction Rules}}, then locate and open your ''.properties'' file
# Type ''xliff'' in the {{menu|Extension}} field and click {{menu|OK}}
# Choose {{menu|Add File}}, locate the folder containing the WP XLIFF file(s), select the file(s), and click {{menu|Open}}
# Next to the folder name under {{menu|Type}}, click the drop-down and select your new WP XLIFF filter's name (this will select it for all files in the list)
# Complete the project wizard as usual to finish

[[Category:Wordfast Pro 4]]