Most recent edit on 2009-10-15 02:51:55 by AlexTaylor [Added reference to GPS files under SOURCE\COMMON]
Additions:
Some of the more high-penetration NLVs (in particular, German and Dutch) have almost everything translated. However, these NLVs have generally had multiple translators working on them over a long period of time. NLVs with only one or two translators, working on a short time-frame, can generally get away with leaving various non-essential items in English.
Deletions:
Some of the more high-penetration NLVs (in particular, German and Dutch) do have almost everything translated. However, these NLVs have generally had multiple translators working on them over a long period of time. NLVs with only one or two translators, working on a short time-frame, can generally get away with leaving various non-essential items in English.
Installer GUI text (*.GPS under COMMON\ECS\INSTALL\NLS\xx)
SmartGuide wizard text (*.TPL under COMMON\ECS\INSTALL\NLS\xx
GPMESSGS.
Edited on 2009-08-03 02:59:47 by AlexTaylor [Formatting improvements & minor corrections]
Additions:
The translators for a particular NLV (that is: you, and your teammates if you're lucky enough to have any) are responsible for determining which components must be translated, and which may acceptably be left untranslated.
Some of the more high-penetration NLVs (in particular, German and Dutch) do have almost everything translated. However, these NLVs have generally had multiple translators working on them over a long period of time. NLVs with only one or two translators, working on a short time-frame, can generally get away with leaving various non-essential items in English.
Be aware, however, that the installer and desktop tend to get modified quite often during pre-release development. So you'll have to keep an eye on any changes that get made to the EN_US (English) tree by checking the CVS log from time to time. (Changes that need to be implemented in other NLVs should be marked with the @@nls tag.)
There are a great many utilities and applications, which you may or may not want to translate (resources permitting). If you are able to do this, I suggest giving the highest priority to:
Deletions:
The translators for a particular NLV (i.e. you, and your teammates if you're lucky enough to have any) are responsible for determining which components must be translated, and which may acceptably be left untranslated.
Some of the more high-penetration NLVs (in particular, German and Dutch) do have almost everything translated. However, these NLVs have generally had multiple translators working on them over a long period of time. NLVs with only one or two translators, working on a short time-frame, can generally get away with leaving various non-essential items in English.
Be aware, however, that the installer and desktop tend to get modified quite often during pre-release development. So you'll have to keep an eye on any changes that get made to the EN_US (English) tree by checking the CVS log from time to time. (Changes that need to be implemented in other NLVs should be marked with the
nls tag.)
There are a great many utilities and applications, which you may or may not want to translate (resources permitting). If you are able to do this, I suggest giving the highest priority to AE (text editor), ArcView, the Internet connection wizard, Theme Manager, and Icon Themes.
Edited on 2009-07-31 14:58:36 by AlexTaylor
Additions:
The translators for a particular NLV (i.e. you, and your teammates if you're lucky enough to have any) are responsible for determining which components must be translated, and which may acceptably be left untranslated.
Other components of the installer include:
It is good to have these translated as well. Together with the items previously listed (above), that would result in a CD installation which is completely translated from start to finish.
The following should be the most high-priority items, as they are the most visible to the user.
There are a great many utilities and applications, which you may or may not want to translate (resources permitting). If you are able to do this, I suggest giving the highest priority to AE (text editor), ArcView, the Internet connection wizard, Theme Manager, and Icon Themes.
- nlsdocen - translation guidelines and techniques
Deletions:
The translators for a particular NLV (you, and your teammates if you're lucky enough to have any) are responsible for determining which components "must" be translated, and which may acceptably be left untranslated.
Other components of the installer include: MINILVM (the volume manager), PMFORMAT, RESIZEFS, and GPMESSGS. It is good to have these translated as well. Together with items just listed (above), that would result in a CD installation which is completely translated from start to finish.
The most high-priority items should be eWorkplace, eStyler, NewView, and the multimedia classes, as these are the most visible to the user.
There are a great many utilities and applications, which you may or may not want to translate (resources permitting). If you are able to do this, I suggest giving the highest priority to AE (text editor), ArcView, the Internet connection wizard, and Icon Themes.
- nlsdocen - general guidelines for translation
Oldest known version of this page was edited on 2009-07-31 04:03:42 by AlexTaylor [Initial version]
Page view:
Getting Started With NLV Translation
So you've volunteered to help translate eComStation into a new National Language Version (NLV). Figuring out where to start and how to proceed can be a little confusing. This is a brief introduction designed to help you get started.
eComStation uses language-specific text in a large number of components. However, not everything really needs to be translated.
The translators for a particular NLV (you, and your teammates if you're lucky enough to have any) are responsible for determining which components "must" be translated, and which may acceptably be left untranslated.
Some of the more high-penetration NLVs (in particular, German and Dutch) do have almost everything translated. However, these NLVs have generally had multiple translators working on them over a long period of time. NLVs with only one or two translators, working on a short time-frame, can generally get away with leaving various non-essential items in English.
Things to consider when deciding how much needs to be translated:
- How much time is available?
- How many translators are working on the project?
- Will customers be willing to accept having some components in English instead of in their native language?
Translation instructions for the various components, including links to the necessary files, are collected here on the eComStation wiki under
NLSeCSComponentStatus.
While there is a large number of items listed, many of them are very small and/or low-profile. Once again, it is up you to decide what actually needs to be translated. That said, some basic guidelines are outlined here.
What to Translate First?
Installer & Desktop
In general, the highest-priority items are the installer and the desktop. Basically, the minimum set of translated files should be:
You may also want to have the CD boot messages (
MEMDISK) and configuration menu (
OS2CSM) translated, although these require somewhat more effort to do. (It should be noted that neither MEMDISK or OS2CSM supports DBCS text at the present time.)
Other components of the installer include:
MINILVM (the volume manager),
PMFORMAT,
RESIZEFS, and
GPMESSGS. It is good to have these translated as well. Together with items just listed (above), that would result in a CD installation which is completely translated from start to finish.
Be aware, however, that the installer and desktop tend to get modified quite often during pre-release development. So you'll have to keep an eye on any changes that get made to the EN_US (English) tree by checking the CVS log from time to time. (Changes that need to be implemented in other NLVs should be marked with the
nls tag.)
Other Components
Once the installer and desktop are taken care of, that leaves the installed system components. Fortunately, if the NLV is based on an existing IBM OS/2 NLV, then the basic operating system and most of the core IBM components should be translated already. That leaves all the extra eComStation stuff.
This is all completely optional. Again, it depends on your resources and on how necessary you think it is.
The most high-priority items should be
eWorkplace,
eStyler,
NewView, and the
multimedia classes, as these are the most visible to the user.
There are a great many utilities and applications, which you may or may not want to translate (resources permitting). If you are able to do this, I suggest giving the highest priority to
AE (text editor),
ArcView, the Internet connection wizard, and Icon Themes.
Additional Information
This wiki contains a number of resources for translators. In particular, you are encouraged to look at:
This page has been accessed 1272 times ::
Valid XHTML 1.0 Transitional∞ ::
Valid CSS∞ ::
Powered by Wikka Wakka Wiki 1.1.6.0∞