Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!uakari.primate.wisc.edu!caesar.cs.montana.edu!ogicse!decwrl!asente
From: asente@decwrl.dec.com (Paul Asente)
Newsgroups: comp.windows.x
Subject: Re: Language dependent application defaults
Keywords: Localization, Application Defaults
Message-ID: <2803@bacchus.dec.com>
Date: 16 Feb 90 23:58:42 GMT
References: <898@ztivax.UUCP> <3890@srava.sra.co.jp>
Organization: DEC Western Software Lab
Lines: 20

In article <3890@srava.sra.co.jp> erik@sra.co.jp (Erik M. van der Poel) writes:
<But let's get down to the point here. The X/Open catgets catalogues
<are only for multilingual text, while app-defaults files are for all
<sorts of resources including e.g. border width. So I suppose what you
<are trying to say is that we should keep language-dependent files in
<one place, specified by the environment variable NLSPATH. We could
<achieve this by keeping only language-independent files under
</usr/lib/X11/app-defaults. But I imagine that the Xt people decided to
<put language-dependent files under the app-defaults directory too
<because X/Open is not the only standard out there. In AT&T's MNLS, for
<example, the internationalized files are under /lib/locale. Somebody
<correct me if I'm wrong. What about POSIX? And others?

Close, but there's more to it.  You really need to customize more
resources than just strings (fonts, widget sizes, printing direction...)
The X/Open routines were adequate for simple applications, but more is
needed for window applications than just changing the text string.

	-paul asente
	    asente@decwrl.dec.com	decwrl!asente