Encoding problem in Framemaker after translation in Trados
Thread poster: Pavel Lyakhovsky

Pavel Lyakhovsky  Identity Verified
Russian Federation
Local time: 04:51
Member (2006)
English to Russian
Apr 9, 2009

Hi all,

The client sent me .mif files created in FM 8. I'm using the latest Trados version (2007 Suite). I converted .mif to .ttx using S-Tagger (source and target languages set on Settings tab), translated .ttx, converted back to .mif. No errors.

However, when I (or the client) open the translated .mif in Framemaker, all translated Russian text appears as gibberish. It looks as if Framemaker thinks it's in codepage 1252 and not 1251.

I tried to change font from e.g. Times New Roman to Times New Roman CYR - no result.

I tried to specify Russian language in Paragraph Designer - no result.

Any ideas?

Thanks a lot in advance.

Best regards,
Pavel


 

Jerzy Czopik  Identity Verified
Germany
Local time: 03:51
Member (2003)
Polish to German
+ ...
Did you specify the language in S-Tagger? Apr 9, 2009

When you fail to specify Russian as target, it might fail.

Is it feasible to switch to Framemaker 8 and use FontMapper?


 

Pavel Lyakhovsky  Identity Verified
Russian Federation
Local time: 04:51
Member (2006)
English to Russian
TOPIC STARTER
Russian specified as target Apr 9, 2009

Yes, I specified Russian as target language on Settings tab of the S-Tagger tool.

I am afraid I can't really give any advise on feasibility of switching to FM 8 - just downloaded their trial version today after the client has reported this problem with Russian encoding.

[Edited at 2009-04-09 20:47 GMT]


 

Wojciech Froelich  Identity Verified
Poland
Local time: 03:51
English to Polish
What build? Apr 9, 2009

Pavel Lyakhovsky wrote:

The client sent me .mif files created in FM 8. I'm using the latest Trados version (2007 Suite). I converted .mif to .ttx using S-Tagger (source and target languages set on Settings tab), translated .ttx, converted back to .mif. No errors.

However, when I (or the client) open the translated .mif in Framemaker, all translated Russian text appears as gibberish. It looks as if Framemaker thinks it's in codepage 1252 and not 1251.


1. 2007 Suite, means SP3, correct? S-Tagger build should be 8.0.1.838. SP2 would work only when patched with specific hotfix.
2. Were files originally created in FM8? (.fm files, not .mif files) There is a huge technological gap between FM7 (non-Unicode) and FM8 (Unicode), not all conversions are as obvious as one may expect.
3. What are your S-Tagger settings for "Character Set"? Normal or Symbol?


 

Pavel Lyakhovsky  Identity Verified
Russian Federation
Local time: 04:51
Member (2006)
English to Russian
TOPIC STARTER
Build is correct Apr 10, 2009

I have S-Tagger build 8.0.1.838. Files were originally created in FM8. S-Tagger setting for "Character set" is Normal. According to the manual "Symbol" is only used for Japanese etc. However I tried switching to "Symbol" - then the text is totally corrupt, so the manual is right.

It looks as if S-Tagger doesn't take into account the language settings. It thinks the translation in in CP-1252 (Western) and converts it to the respective Unicode when performing .ttx to .mif conversion. But it must be CP-1251 (Cyrillic)...


 

Wojciech Froelich  Identity Verified
Poland
Local time: 03:51
English to Polish
Which means the documents might not be FM8 (Unicode) Apr 10, 2009

Pavel Lyakhovsky wrote:

It looks as if S-Tagger doesn't take into account the language settings. It thinks the translation in in CP-1252 (Western) and converts it to the respective Unicode when performing .ttx to .mif conversion. But it must be CP-1251 (Cyrillic)...


I would triple check the origins of the source .fm files. It's possible the non-Unicode > Unicode conversion for the documents failed. Create a small document from scratch (in FM8), save it as MIF, do some "dummy" translations into Russian and check the final MIF. That will eliminate your S-Tagger installation as the source of the problem (I bet you will see pretty Russian characters).


 

RieM  Identity Verified
United States
Local time: 21:51
English to Japanese
+ ...
And more... Apr 10, 2009

Wojciech Froelich wrote:

I would triple check the origins of the source .fm files. It's possible the non-Unicode > Unicode conversion for the documents failed. Create a small document from scratch (in FM8), save it as MIF, do some "dummy" translations into Russian and check the final MIF. That will eliminate your S-Tagger installation as the source of the problem (I bet you will see pretty Russian characters).


Hi,

I don't have FM8 and don't use s-tagger any longer for my own workicon_smile.gif , but have done (more than) enough troubleshooting with Asian fonts...

Testing the translation process with a small file is a must here, and at each step you can open files (mif/ttx) using a plain text editor. With mif, the text is all the way towards the end of the file, but you can verify how it is rendered. Also create small mif file with FM8 with Russian text, and use it for comparison. Somewhere along the way the unicode conversion is not happening.

Good luck!
Rie


 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Encoding problem in Framemaker after translation in Trados

Advanced search







WordFinder Unlimited
For clarity and excellence

WordFinder is the leading dictionary service that gives you the words you want anywhere, anytime. Access 260+ dictionaries from the world's leading dictionary publishers in virtually any device. Find the right word anywhere, anytime - online or offline.

More info »
SDL Trados Studio 2017 only €435 / $519
Get the cheapest prices for SDL Trados Studio 2017 on ProZ.com

Join this translator’s group buy brought to you by ProZ.com and buy SDL Trados Studio 2017 Freelance for only €435 / $519 / £345 / ¥63000 You will also receive FREE access to Studio 2019 when released.

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search