• State Verified Answer
  • Replies 17 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 5178 views
  • Users 0 members are here
Options
Related

Formatting doesn't apply on the output file (Persian target language)

Alireza Nadry

Hi,

Recently, we had a big issue with SDL Trados. When formatting a part of text in Trados, such as making the text bold, the output file won't take this format. In this case, in the word document you can see that the "bold" icon is activated, but the text isn't bold at all. I will send the .xliff file and its output for you to look at it. Please help me to solve the problem, cause we've assigned 19 projects to our translators, which each of them has around 140.000 words, and you know how much time it takes to manually make the output formatting right. (Segments 24 and 26 has formatting in the attached file; see Microsoft Word comments in the word file)

https://www.dropbox.com/sh/2wibx37ttx0vuvl/AADEM4_n8bGgMTOfOImpSar8a?dl=0

 

Regards,

Alireza
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    I have opened your Word file on my PC (German Windows 10, Office 2016, German GUI).
    I am NOT able to bold anything in this text, even if I enter some Latin characters and try to use Arial for those. The text does remain NOT bold.
    So I would suppose this could be a Word issue more than a Studio issue. Do you have the same problem with formatting which has already been in the source?

     

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik

    Unknown said:
    So I would suppose this could be a Word issue more than a Studio issue.

    It's a Studio issue Jerzy.  The same source into a non-script language works fine.  The problem is that we are nopt changing the formatting under the "Complex scripts".  We only set the font style for Latin text.  A bug is being logged and we'll fix it.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul

    Unknown said:
    It's a Studio issue Jerzy.  The same source into a non-script language works fine.  The problem is that we are nopt changing the formatting under the "Complex scripts".

    Can it be then somehow realted to the "Skip complex script..." and "Skip advanced font formatting..." options in Word filetype, which are ON by default?
  • 0 in reply to Evzen Polenka

    Unknown said:
    Can it be then somehow realted to the "Skip complex script..." and "Skip advanced font formatting..." options in Word filetype, which are ON by default?

    Maybe Evzen.,.. but when we looked at it the view was we should be making sure that complex scripts are catered for properly and set the appropriate switches in the target file.  The development team will look at this and we'll know soon enough.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul

    It just reminds me of maybe related issue we had recently with Small Caps - client sent us a Word file with text which contained some product name with the type number written partially in small caps... and because a) such thing is absolutely not possible to see in the middle of other text, and b) the default settings for Word filetype do NOT extract the formatting, the resulting translated file used normal small letters... and because of a) even QA did not find it... which led to a huuuuge client escalation :(

    So maybe also a revision of "complex script" and "advanced formatting" definitions and/or default settings would be a good idea...

    I found a screenshot - UNchecking the "Skip complex script..." option revealed the extra formatting... but having this set permanently (to catch other possible future cases) would cause too much other garbage to be present in the segments and polluting a TM (not mentioning lowering the leverage from existing non-polluted TM content... which would again cause BIG problems with the client)
Reply
  • 0 in reply to Paul

    It just reminds me of maybe related issue we had recently with Small Caps - client sent us a Word file with text which contained some product name with the type number written partially in small caps... and because a) such thing is absolutely not possible to see in the middle of other text, and b) the default settings for Word filetype do NOT extract the formatting, the resulting translated file used normal small letters... and because of a) even QA did not find it... which led to a huuuuge client escalation :(

    So maybe also a revision of "complex script" and "advanced formatting" definitions and/or default settings would be a good idea...

    I found a screenshot - UNchecking the "Skip complex script..." option revealed the extra formatting... but having this set permanently (to catch other possible future cases) would cause too much other garbage to be present in the segments and polluting a TM (not mentioning lowering the leverage from existing non-polluted TM content... which would again cause BIG problems with the client)
Children