FM9 and Russian Translation Problems

[Jeremy H. Griffith]

On Mon, 21 Jun 2010 11:21:37 -0700, Alison Craig <Alison.Craig at ultrasonix.com> 
wrote:

>FM 9 Version: 9.0p250
>Unstructured
>OS: XP Pro with SP3
>FM Experience: 12 months
>Translation/Localization Management Experience: 11 years
>Writing Team: 1 (me)
>
>I have just received my Russian User Manual translation back from 
>the LSP and am encountering problems I haven't seen with any other 
>language in FM. (I've handled Russian, Greek and Bulgarian in Word 
>so I'm experienced with Cyrillic languages in general, but not 
>specifically in FM.)
>
>I may have to make the LSP fix these issues, but in the meantime, 
>if anyone has any insight I would appreciate it. At the very least 
>I would like to understand the issue.
>
>PROBLEM 1
>-------------------
>Although the auto-numbering of my Heading Para Tags appears to be 
>correct - ie, identical to the English version - they are not 
>showing up properly.
>
>              ENGLISH                 RUSSIAN
>Heading 1     A:Chapter <n+>:         ?:????? <n+>:
>Heading 2     A:<n>.<n+>\t            A:<n>.<n+>\t
>Heading 3     A:<n>.<n>.<n+>\t        A:<n>.<n>.<n+>\t
>Heading 4     A:<n>.<n>.<n>.<n+>\t    A:<n>.<n>.<n>.<n+>\t
>
>
>All Heading 1 Para Tags shows up correctly (with the word Chapter 
>translated to Russian and the correct Chapter number) but Headings 
>2 to 4 are wrong. They all begin with 0.

That (and the other two problems related to this) are all because the
Russian Heading 1 does not have the same series letter, "A", as the
others.  Series letters should **not** be translated.

>Interestingly, Tables and Figures are handled correctly, although 
>they actually specify the use of <$chapnum>
>
>F:Figure <$chapnum>\+<n=1>:
>F:??????? <$chapnum>\+<n=1>:

Here, they did *not* translate the series letter.


>PROBLEM 2
>-------------------
>Is there any way to do a wholesale change to language settings? 
>Instead of being set to Russian (or ??????), all the Para and 
>Char Tags seem to be set to None.
>
>If I can't automate a fix to this (and I don't have FrameScript), 
>I will definitely have to make the LSP fix it.

I'm pretty sure you can do that by opening the para designer,
setting it to As Is, changing the one language setting, and
applying it globally.  But I don't have 9 handy to check on.

>---------------------------------------------------------
>
>Any help is appreciated, Alison

HTH!

-- Jeremy H. Griffith, at Omni Systems Inc.
  <jeremy at omsys.com>  http://www.omsys.com/