|
|
|
Leveraging behaviour for strings with inline tags |
|
|
|
|
Leveraging behaviour for strings with inline tags |
|
|
This article is to reference the behavior of Alchemy Catalyst's Leverage Expert when treating strings with inline tags. Users may find it surprising to get Fuzzy match statuses while not using the option in the Leverage Expert. This page will explain why. Inline tags are present in HTML and XML files. From version to version, a translatable file's inline tags can change position, count or even attributes. Below we review the different changes and their impact on results of the Leverage Expert.
The translation memoryLet's take a sample HTML file which we have translated into French in Alchemy Catalyst. This is what the TM (Translation Memory) looks like:
Note: In the last 3 strings, the Span inline tags include an attribute.
The new source fileA new source file is inserted in Alchemy Catalyst creating a new .ttk project. The image below shows the string lists viewed in the TM and new .ttk project.
LeveragingHaving performed the leverage on the New .ttk project in Alchemy Catalyst, we get the following results.
The results in reviewFollowing is the description of the leverage results with a comparison review of the original string (O) from the Translation Memory and new string (N) in the source files, with changes highlighted in yellow. No text change The first 2 strings do not contain any inline tags. They have not changed and thus the Locked and Signed Off statuses are simply maintained.
O= Leveraging behaviour with tags in localisable strings. O= They were all Signed off in the Translation Memory
Tags change but not position The string text is identical but the <b> (bold) tags have changed to <i> tags (italic). The tags' positions are unchanged (and the text also) thus Alchemy Catalyst leverages the translation and updates the tags. The Signed Off status is not retained as the tags update will need to be reviewed to insure appropriately placed.
O= The tags <b>changed</b> but are still in the exact same position
Tags changed position While the string text is unchanged, one or more tags in the new string have changed position. Alchemy Catalyst cannot predict accurately how the change in tag position should be reflected in the translated string, so they are moved to the beginning of the string. The status is set to Fuzzy match to inform the translator to review the position of the tags.
O= One tag has <Span>moved within</span> the string!
Tags added or removed Some of the tags have been removed in the new string. Alchemy Catalyst needs to reflect this change in the translated string but cannot know where to position the tags within the translated string. The tags are thus positioned at the beginning the of translated string and the status is set to fuzzy match to inform the translator to review the position of the tags. The same process will be applied if new tags are added in the new string.
O= We had multiple tags within this <Span>string</Span>, and only one in the new <Span>string</Span>, tags are placed at the front.
Tags added at end or beginning of string A tag was added to the end of the new string. As the tag is at the end of the string, Alchemy Catalyst can leverage the translation as normal. As this is a changed string, the status is set For Review. Tags positioned at the Beginning or End of strings do not affect the text itself as it's "outside" of it.
O= This string had one tag at the end.
Unlike the previous example, the new tag added is not on the extremities of the string. Alchemy Catalyst cannot tell the position of the new tag in the new string and thus positions them to the beginning of the translatable string and sets the status to Fuzzy match to inform the translator to review the position of the tags.
O= This string had one tag here in the middle of the string.
Tags with attribute This string contains a tag with an attribute. The Span tag has an "inline" attribute with value "stringw". This can be viewed in Alchemy Catalyst by right clicking on the Span tag which has a little plus symbol
O= The Span tag includes attribute <Span inline="stringw">stringw</span> within.
The string itself has not changed, however the value of the "inline" attribute has changed. As a result, Alchemy Catalyst can leverage the translation but cannot retain the Signed Off status as some changes were made, even if in an attribute which is not localisable.
O= The Span tag includes attribute <Span inline="stringx">stringx</span> within.
The situation is the same but the attribute itself has changed. Alchemy Catalyst can leverage the translation but cannot keep the Signed Off status to reflect the change made, even if not in the localisable part.
O= The Span tag includes attribute <Span inline="stringz">stringz</span> within.
Sample filesThe files used in this article are available to download. HTMLsamples.zip contains the following files: Lev_tags.html = Original file inserted in the Translation Memory TTK (lev_tags_translated.ttk). \new version\Lev_tags.html = New source file. Insert this file in a new TTK and leverage from the Translation Memory TTK (lev_tags_translated.ttk). lev_tags_translated.ttk = Translation Memory. Pseudo translations were applied to mimic translations using the Pseudo Translation Expert.
Products or Versions Affected
Article last updated with Catalyst 9.0
|
 |
 |
|
|
in the translator Toolbar, then select "Edit Attributes". In this first example, the string is unchanged and Alchemy Catalyst can leverage and retain the Signed Off status.
