search

computerline1z / okapi

Automatically exported from code.google.com/p/okapi
0 stars 0 forks source link

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

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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 (‌)

Original issue reported on code.google.com by benjamin...@gmail.com on 2 Jun 2011 at 9:37

Attachments:

GoogleCodeExporter commented 9 years ago 
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.

Original comment by yves.sav...@gmail.com on 3 Jun 2011 at 12:00

GoogleCodeExporter commented 9 years ago 
The ' and " case has been fixed in the latest snapshot.
Still thinking about the best way to resolve the other Unicode characters.

Original comment by yves.sav...@gmail.com on 7 Jun 2011 at 5:36

GoogleCodeExporter commented 9 years ago 
Hi Yves, I forgot to add ampersand & to the previous list.

Original comment by benjamin...@gmail.com on 19 Jun 2012 at 11:41