 | |
Visual Studio - Set text of a label, pointing to a resource
Dotnet Internationalization microsoft.public.dotnet.internationalization
 |
| | Thread Tools | Search this Thread | Display Modes |
#11
 
| |||
| |||
|
Re: Visual Studio - Set text of a label, pointing to a resource -
07-31-2008
, 02:02 AM
|
2. Sometimes you have some text repeated more times, like "New item", "Delete item". It's better to have only one resource for one of them. |
The same English word is transalated in different ways depending on context.
For instance "Print" is translated onto French as "Imprimer" or "Impression",
depending if it is a commanding element (ie button) vs describing stuff
(label, title).
Same element type can also require different translations.
Examples: "Scan" can mean "scan a page of paper" or "scan the disk" and
have different translations.
"New" can be translated as "Nuovo" "Nuova" "Nuovi" "Nuove"
(masculin singular, feminin singular, masculin plural, feminin plural)
Uless you don't speak all target languages, you have no way to judge if
two elements require a different translation or not.
So you better leave that "saving" alone.
--
Mihai Nita [Microsoft MVP, Visual C++]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email
#12
| |||
| |||
|
|
On Jul 30, 5:10*pm, Ondrej Medek <xmed... (AT) gmail (DOT) com> wrote: Hi all, the Visualk Studio built-in localization has some limitation. It is suitable for small projects only. Becasue: 1. It is difficult for the traslator to go throuh all forms and do not miss anything. It's better to have averything only in a few resx 1. *Translations often depend on the context. *Just because the same word is used in English in two different forms doesn't mean the same word should be used in another Language. * You can overcome this by defining a separate resource entry in these cases, however you don't know upfront (before localizing in every possible language) when this may occur. * So the only way to avoid code changes during the localization phase is to define a separate resource for each form - which brings you back to the standard .NET localization solution. 2. *Strings are not the only things that need localization. *The standard .NET localization approach allows you to change the size and layout of forms as required for specific languages. * This means that you can allow extra room as required for languages like German which can be verbose without leaving large ugly spaces in other languages. In addition right to left languages like Hebrew will require a completely different layout. * You can do all this in the Visual Studio forms editor and check your layout at design time. |
english speaker. My proposed solution is flexible enough. It does not
prevent from using VS 2005 the old way. I think it might be also
simple to implement.
#13
| |||
| |||
|
|
On Jul 30, 5:10*pm, Ondrej Medek <xmed... (AT) gmail (DOT) com> wrote: Hi all, the Visualk Studio built-in localization has some limitation. It is suitable for small projects only. Becasue: 1. It is difficult for the traslator to go throuh all forms and do not miss anything. It's better to have averything only in a few resx 1. *Translations often depend on the context. *Just because the same word is used in English in two different forms doesn't mean the same word should be used in another Language. * You can overcome this by defining a separate resource entry in these cases, however you don't know upfront (before localizing in every possible language) when this may occur. * So the only way to avoid code changes during the localization phase is to define a separate resource for each form - which brings you back to the standard .NET localization solution. 2. *Strings are not the only things that need localization. *The standard .NET localization approach allows you to change the size and layout of forms as required for specific languages. * This means that you can allow extra room as required for languages like German which can be verbose without leaving large ugly spaces in other languages. In addition right to left languages like Hebrew will require a completely different layout. * You can do all this in the Visual Studio forms editor and check your layout at design time. |
english speaker. My proposed solution is flexible enough. It does not
prevent from using VS 2005 the old way. I think it might be also
simple to implement.
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.