i18n is basically a software development job; you need to deal with the code. The simplest concept is to move the hard code of the String from the source code to reduce the interaction between the translation of the string visible to the user and moving them back as resource files or database values ββor something, depending on your i18n sample. In i18n, you deal with logic, user interface, databases, scripts from left to right, etc., to get a code base that is pretty orthogonal to the specifics of the locale (language / countries). You may have strategies to combat the business logic specific to the country (i.e. Taxes). You are probably handling the formatting of simple elements such as date / time, currency, etc., and possibly complex (addresses, imperial calendar), which may require some design in terms of database, logic, user interface, etc. .d. Depending on your target locales.
L10n is due to appear later and is not the work of software engineers. For the most part, this is the "localization" of companies, with translators who do this part of the work.
i18n and L10n are essential components of the G11n strategy. Planning, QA, etc. Both sides must take into account, since there are issues of integration from one world to another.
Hope this helps.
Olivier Libouban Jan 03 '11 at 18:28 2011-01-03 18:28
source share