After searching on website I post this question. I am aware of the fact that by default assemblies are "culture neutral" and one can create satellite assemblies with only resources (and no code) with culture specific information and place them inside the same folder as the culture name (i.e. en-us). But the question is, what is culture? Some specific real-life examples would help.
NET-based applications. An assembly is a collection of types and resources that are built to work together and form a logical unit of functionality. Assemblies take the form of executable (.exe) or dynamic link library (. dll) files, and are the building blocks of . NET applications.
CULTURES OF ASSEMBLY, a project by the Chair of the City of Esch, is currently developing a crossover format that consists of a digital platform alongside a pop-up neighbourhood agency in the centre of Esch-sur-Alzette.
Per MSDN, this includes such things as the names for the culture, the writing system, the calendar used, and formatting for dates and sort strings.
For translations, the most significant aspect is a combination of language and dialect. Here is a good list of examples.
For example, consider British English (en-GB) vs. American English (en-US) vs. Canadian English (en-CA) vs. Australian English (en-AU) vs. the at least ten other English dialects that exist (I kid you not / see the list I linked). Then, compare and contrast them to say Russian as spoken in Russia (ru-RU). Aside from differences in language, there are also different symbols used for the radix indicator, digit grouping, date (MDY vs DMY), etc...
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With