Some placeables in IDML appear as translatable text in the XLIFF+RTF layer

Create issue
Issue #175 resolved
Former user created an issue

Original issue 175 created by benjamin.t.m... on 2011-06-02T21:37:45.000Z:

What steps will reproduce the problem?
1. Open Rainbow, add IDML file to input list
2. Utilities > Translation Kit Creation
3. Package Format > XLIFF with RTF
4. Execute

What is the expected output? What do you see instead?
Should see an RTF file with translatable content in "normal" style and placeables represented as untranslatable tags. Instead, we see some placeables as translatable text.

What version of the product are you using? On what operating system?
Rainbow 6.0.12 on Windows 7
IDML generated from InDesign CS4 for PC. Identical results with InDesign CS5.

Please provide any additional information below.
Description (translatable text)
em space ( )
en space ( )
Straight double quote (")
Straight single quote (apostrophe)(')
Non-joiner mark (‌)

Comments (9)

  1. Former user Account Deleted
    • changed status to open

    Comment [1.](https://code.google.com/p/okapi/issues/detail?id=175#c1) originally posted by @ysavourel on 2011-06-03T12:00:23.000Z:

    Thanks for the sample file Ben.

    For ' and ": I'll try to not escape those.

    Using an inline code for some of those special markers is fine (like index marker, some very rare spaces, etc.) But for some other, I think they should stay as raw characters if possible. For example the non-joiner mark is possibly used by Word to display the character sequence properly. En and Em spaces could also be display properly. The escaping is coming from the RTF layer. Currently we tend to force backward compatibility for RTf reader that can't deal with Unicode, but nowadays we should just write out the RTF as Unicode with possibly an option for backward compatibility. This should make those spacial marker displayed as themselves in Word.

  2. Jim Hargrave (OLD)
    • edited description
    • changed milestone to 1.42.0
    • removed responsible
    • changed version to M38

    I added a new unit test “issue175“. The roundtrip fails. This may longer be an issue but please test and “resolve“ if no longer an issue.

  3. Denis Konovalyenko

    @Jim Hargrave , the roundtrip is OK on the latest dev (1.44.0 snapshot).

    Below is a list of characters which considered as codes for extraction:

            ALIGNMENT("0"),
            END_NESTED_STYLE("3"),
            FOOTNOTE_MARKER("4"),
            INDENT_HERE_TAB("7"),
            RIGHT_INDENT_TAB("8"),
            AUTO_PAGE_NUMBER("18"),
            SECTION_MARKER("19"),
    
            FIXED_WIDTH_NON_BREAKING_SPACE("\u202F"),
    
            HAIR_SPACE("\u200A"),
            THIN_SPACE("\u2009"),
            PUNCTUATION_SPACE("\u2008"),
            FIGURE_SPACE("\u2007"),
            SIXTH_SPACE("\u2006"),
            QUARTER_SPACE("\u2005"),
            THIRD_SPACE("\u2004"),
            FLUSH_SPACE("\u2001"),
    
            FORCED_LINE_BREAK("\u2028"),
            DISCRETIONARY_LINE_BRAKE("\u200B"),
            ZERO_WIDTH_NON_JOINER("\u200C"),
    
            DISCRETIONARY_HYPHEN("\u00AD"),
            NON_BREAKING_HYPHEN("\u2011"),
    
            ZERO_WIDTH_NO_BREAK_SPACE("\uFEFF"),
    

  4. Log in to comment