ASP.NET Multilingual Strategy Guidelines

Question

Hi brothers and sisters

I am wondering if anyone can share their experience with what they consider to be the best strategy for enabling a dynamic multilingual system using .NET.

I have a client who wants to have a semi-MRP system that stores all the materials and product specifications. This data will later be used for other modules, such as invoices, purchasing, marketing (extracting information for printing purposes) and much more.

The fact is that he wants everything to be stored in several languages. It also cannot capture the number of languages. Consequently, the number of languages ​​will grow over time.

So, I assume that I am asking what is the best strategy for setting up a site with support for a dynamic language that includes field names (e.g. name) as well as data (e.g. Lasker).

Thanks a lot in advance, Lasker

Answer 1

Several options are available.

---

Firstly, for shortcuts and interface elements .

Here, as a rule, two options are possible: you either use resources (* .resx) or deploy your own multilingual support at the database level. They both have their advantages and disadvantages.

Resoures:

[+] , . Orders.en.resx, Orders.fr.resx .. Resources.Orders.Title. , .

[+] - XML-, , .

[-] - , . , (VS), , . . .

[-] , .

:

[-]

[-] ,

[+] / . .

[+] . , . - , , .

---

( ).

, - , .

:

:

[Language]
-----------------
ID    Description

[Translation]
------------------
ID    FallbackText

[TranslationText]
--------------------------------
ID    TRID    LanguageID    Text

[Order]
------------------------------------------------
ID    TitleTRID    DescriptionTRID    RemarkTRID

, , TranslationID. , , , , ( ).

:

, . XML .

<translation>
  <en>Order</en>
  <de>Bestellung</de>
  <fr>Commande</fr>
</translation>

, , .

---

. , .

, .:)

Answer 2

, New in Town .

resx, , , -, , , , .. , . VS, , resx. " " "". , ( ), resx. .

, web.config.

<globalization enableClientBasedCulture="true" culture="ar-EG" uiCulture="ar-EG"/> 

,