Forum: SDL Trados support
Topic: Studio 2014 incorrectly localizes currency symbol
Poster: hieuthao
Post title: Oh dear, there's been a misunderstanding
And it was very nice of you to record a video complete with family photos ;). But I don't need to replace the $ symbol with the đ symbol. You are right, that would be a simple fix using search and replace. I don't need the đ symbol at all, because the amounts in the target file are all in dollars, they are not being converted to Vietnamese dong. What I need to do is to move the $ symbol from after the number (where Trados places it) back to before the number (as in English). I need to change 50 $ to $50 or 0.33 $ to $0.33 and so on. Can that be done with regex?
I don't see this as being a problem with Windows. The Windows stylesheet is correct, the đ symbol goes after the number (although I wouldn't put in the space). The problem is that Trados assumes that a language uses the same convention for all currency symbols and Vietnamese does not. When using the dollar sign, Vietnamese either places it before the number as in English (most common) or after the number but with no space.
Also, I have a large client that requires I use the English convention for numbers (1,000.00 rather than 1.000,00) in my translations due to their software requirements. This is acceptable linguistically since the translations are for use in the US Vietnamese community who are used to seeing that numbering convention. But it seems I will not be able to use Trados for such translations, as the only way to turn off the localization feature also disables two of the most useful functions, the autotranslate and verify functions.
I understand that you may not be able to allow the translator to configure the conversion settings. I will grant you that Trados has a lot of flexibility and one can only do so much. But at the very least the translator should be able to completely turn off the conversion/localization feature (including AT) without sacrificing other much more important features. There are a lot of real world situations (at least in my world) where I don't localize certain things in my translation. Maybe this happens more with languages of limited diffusion?
Topic: Studio 2014 incorrectly localizes currency symbol
Poster: hieuthao
Post title: Oh dear, there's been a misunderstanding
And it was very nice of you to record a video complete with family photos ;). But I don't need to replace the $ symbol with the đ symbol. You are right, that would be a simple fix using search and replace. I don't need the đ symbol at all, because the amounts in the target file are all in dollars, they are not being converted to Vietnamese dong. What I need to do is to move the $ symbol from after the number (where Trados places it) back to before the number (as in English). I need to change 50 $ to $50 or 0.33 $ to $0.33 and so on. Can that be done with regex?
I don't see this as being a problem with Windows. The Windows stylesheet is correct, the đ symbol goes after the number (although I wouldn't put in the space). The problem is that Trados assumes that a language uses the same convention for all currency symbols and Vietnamese does not. When using the dollar sign, Vietnamese either places it before the number as in English (most common) or after the number but with no space.
Also, I have a large client that requires I use the English convention for numbers (1,000.00 rather than 1.000,00) in my translations due to their software requirements. This is acceptable linguistically since the translations are for use in the US Vietnamese community who are used to seeing that numbering convention. But it seems I will not be able to use Trados for such translations, as the only way to turn off the localization feature also disables two of the most useful functions, the autotranslate and verify functions.
I understand that you may not be able to allow the translator to configure the conversion settings. I will grant you that Trados has a lot of flexibility and one can only do so much. But at the very least the translator should be able to completely turn off the conversion/localization feature (including AT) without sacrificing other much more important features. There are a lot of real world situations (at least in my world) where I don't localize certain things in my translation. Maybe this happens more with languages of limited diffusion?