|
| |
  
Some strings should not be translated. For example, if a
hard coded registry path was in a localization string table then it would be
natural for a localizer to translate it, resulting in a non-obvious failure for
that particular language. It is to the developer’s advantage to make it easier
for the localizer to not make the mistake in the first place. This can be
accomplished by:
- Define the non-localizable values as string defines in
an H file that the localizers never possess and so couldn’t possibly make a
mistake with them.
- Define the non-localizable values in a resource file
not sent to the localizers so that, again, the localizers are never given
the opportunity to translate them.
- Define a character sequence that all non-localizable
resources share and inform the localizers of the convention. They might
still mistakenly translate the values but we would have a really good excuse
to verbally abuse the localizers without having to suffer those nasty old
guilt pangs afterwards.
|
.
