Hello everyone,
I was reading an article on MSDN about localizing objects on Windows forms,
however it didn't cover localization of programmed strings. For example, how
would I go about localizing an error message for a message box if the
message box is created from my own code rather than from an actual form?
In Cocoa under OS X, you would create a very simple XML-style file with
translations of different strings in it, and then call a system-defined
method with the text to be translated and the default if no translation was
found. The OS would then do the rest for you, returning the correct form of
the string based on the operating system's lingual settings. Is there any
equivilent to this in .NET? I looked through the System.Globaliz ation
namespace docs, but they didn't provide any clues of ways to localize
programmed string literals.
TIA,
Marc W.
I was reading an article on MSDN about localizing objects on Windows forms,
however it didn't cover localization of programmed strings. For example, how
would I go about localizing an error message for a message box if the
message box is created from my own code rather than from an actual form?
In Cocoa under OS X, you would create a very simple XML-style file with
translations of different strings in it, and then call a system-defined
method with the text to be translated and the default if no translation was
found. The OS would then do the rest for you, returning the correct form of
the string based on the operating system's lingual settings. Is there any
equivilent to this in .NET? I looked through the System.Globaliz ation
namespace docs, but they didn't provide any clues of ways to localize
programmed string literals.
TIA,
Marc W.