Since AutoCAD adopted the .NET technology, it has been always a wonder which .NET culture corresponds to which AutoCAD language and how to name .NET resource (.RESX) files accordingly. In this article, we are going to address it.
Things are clear if a table like the following is presented:
Language Culture Resource
English en *.en.resx
Japanese ja *.ja.resx
Korean ko *.ko.resx
Simplified Chinese zh-Hans *. zh-Hans.resx
Traditional Chinese zh-Hant *. zh-Hant.resx
French fr *.fr.resx
German de *.de.resx
Italian it *.it.resx
Spanish es *.es.resx
Russian ru *.ru.resx
Czech cs *.cs.resx
Polish pl *.pl.resx
Hungarian hu *.hu.resx
Portuguese pt *.pt.resx
The left column is the languages that AutoCAD supports; the middle is the neutral culture that each language corresponds; the right one indicates the naming patterns for the resource files.
In terms of culture dialects such as British English vs. American English, France French vs. Canada French, and Portugal Portuguese vs. Brazil Portuguese, it may be a good idea to put all those aside as far as AutoCAD .NET development is concerned and just use the neutral languages since there are not really so big differences especially written in engineering fields. Even AutoCAD itself does not really care about that. For some really big, broadly used and very culture sensitive systems maybe they will. Windows may be a good example.
So no need to name the cultures as the pattern of languages+country/region and create resource files accordingly like *.fr-FR.resx, *.de-DE.resx, *.en-GB.resx, or something like that. It is not really necessary and will just make things complicated and coding bug prone, as far as AutoCAD .NET is concerned.
The leading edge AutoCAD .NET Addin Wizard (AcadNetAddinWizard) follows the simple and functional strategy and takes care of all these automatically when applicable, such as during command creations in its Local Commands wizard/creator.
Recent Comments