Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#39 Install documentation should be multilingual

open
nobody
None
3
2008-03-09
2008-03-09
Eric Auer
No

Moved from Bugzilla bug 609 (Feb/Jun 2001)

*Jim Hall* 2001-02-25

I had this email discussion about the install program and
internationalization. I am including this as a 'bug' so that I can
include this in a future release:
> > 1.-) It is a pity that the descriptions of disks are not
translated!
>
> I'm going to put some thought into how to best provide
> translations for
> the different disk sets. Right now, the Install program just
> reads from
> a file (BASE.TXT, EDIT.TXT, ...). I suppose Install could try to
read
> BASE.%lang%, and failing that, read BASE.TXT. What do you think?

*Jeremy Davis* 2001-06-29

Install 3.7.2 and higher will first try %lang%\<file> and
<file>.%lang%

Install 3.7.2 and higher will 1st try to display localized
versions (see src\cat.c for implementation), so if translations are
created then it should use them.
Note: actual search path is as follows:
First try the current directory (where INSTALL.EXE is started from)
%LANG%\filename.TXT
%LANG%\filename
filename.%LANG%
if %LANG% in format "aa-BB", such as "en-UK" then try
{
aa\filename.TXT (ie .\en\filename.TXT)
aa\filename
filename.aa (ie .\filename.en )
}
filename.TXT
filename
Then repeat above search, except instead of current directory,
use each path listed in %NLSPATH%
The catch is the current files (BASE.TXT, etc) will be found
before any files in NLSPATH unless localized files are placed in
the current directory, or the current english files are moved
into an EN\ subdirectory (even if %LANG% is not set, install
will default to 'EN').
So anyone who can read/write other languages need only
supply translated versions of COPYR.TXT, OEM.TXT, BASE.TXT,
LANG.TXT, ... and INSTALL can use them.

Discussion