Re: [Scrollkeeper-devel] Locale fallback

[Malcolm T. <ma...@co...>]

On Sat, 2003-08-23 at 13:48, Malcolm Tredinnick wrote:
> Hi Laszlo,
> 
> On Fri, 2003-08-22 at 22:12, Laszlo Kovacs - Sun Ireland wrote:
> > Here is another one. Scrollkeeper is designed to fall back to translated 
> > locales if docs are not translated to the current locale.
> > 
> > setlocale() (in libs/i18n.c) is used to identify the desired fallback 
> > path with the C locale sticked to the end (so that we fall back to 
> > English if all else fails).
> > 
> > But if we are in a locale like ja_JP.UTF-8, the Sun i180n team is 
> > telling me that we should be able to fall back to a ja or ja_JP if 
> > ja_JP.UTF-8 is not available (before falling to English). This should be 
> > the case even if setlocale() only returns ja_JP.UTF-8 (as opposed to 
> > ja_JP.UTF-8:ja_JP:ja). I know this is not implemented right now. Is this 
> > how people think it should work? Or some other way?
> 
> This should already be happening. I added some code back in September of
> last year (9/9/2002) to do this sort of stuff and it has been tested
> fairly thoroughly (since it affects the GNOME help system, for example).
> The code in question is in libs/i18n.c and should work exactly as you
> describe. This should have been in the 0.3.12 release.

Aah ... light dawns on marble head! They (your docs and build guys) may
well not be using this release, since that particular bunch of code used
strndup(), which I had not realised at the time was a GNU extension and
hence not in libc on Solaris (or *BSD amongst others). That bug has
probably been reported a dozen times since then. :-(

[Although I seem to remember that two of the bug reports came from
@sun.com, so somebody is testing things.]

I removed the strndup() usage a while ago, and have had some reports
that it now builds on those boxes. So if the case it just that Sun are
still using the 0.3.11 release, please either test the CVS version or
wait a few days until 0.3.12 comes out and try that.

Cheers,
Malcolm