Finnish letters disappear after conversion from SDL Trados back into QuickSilver

Dear All,

We are working on a Finnish translation. Source files: QuickSilver. We noticed that translating in SDL Trados 2015/2017 and SDL 2007 works just fine. It only seems that after converting the TTX files back into QuickSilver files some letters disappear.

Trados: Asianmukainen käyttö

QuickSilver: Asianmukainen käytt

The last "ö" is missing.

Is there an explanation for this problem? How can we make sure the translation is Ok?

Hope to hear from anyone soon, since we need to deliver this translation urgently.

 

Best regards,

Denise Jacobs
DOCTEC

Parents
  • Hi Denise,

    How old is the version of QuickSilver that you are using? Anything up to10 years ago, the way Studio encoded Interleaf QuickSilver iascii files on conversion to stf changed. Some of the accented letters and other symbols were affected by this, they would be rendered as a blank or as a square (indicating that the character could not be displayed) depending on the QuickSilver display settings.

    My workaround was to create my ttx files using a very old version of Trados TagEditor, Trados 2006, which used the old encoding that then protected the accented letters/symbols and the resulting ttx could be translated in Studio and saved back to ttx with no problem so long as the ttx was then opened in the older version of TagEditor again to be taken back to the original format. This protected the old encoding from being updated by Studio.

    The translated file then opened successfully in QuickSilver with no loss of characters.

    I can't double-check this as I no long have Interleaf QuickSilver on my system.

    This may have nothing to do with your problem but it does sound similar.

    All the best,
    Ali
Reply
  • Hi Denise,

    How old is the version of QuickSilver that you are using? Anything up to10 years ago, the way Studio encoded Interleaf QuickSilver iascii files on conversion to stf changed. Some of the accented letters and other symbols were affected by this, they would be rendered as a blank or as a square (indicating that the character could not be displayed) depending on the QuickSilver display settings.

    My workaround was to create my ttx files using a very old version of Trados TagEditor, Trados 2006, which used the old encoding that then protected the accented letters/symbols and the resulting ttx could be translated in Studio and saved back to ttx with no problem so long as the ttx was then opened in the older version of TagEditor again to be taken back to the original format. This protected the old encoding from being updated by Studio.

    The translated file then opened successfully in QuickSilver with no loss of characters.

    I can't double-check this as I no long have Interleaf QuickSilver on my system.

    This may have nothing to do with your problem but it does sound similar.

    All the best,
    Ali
Children
No Data