Re: Bug#176661: locale.1 does not mention LOCPATH
On Sun, Mar 09, 2003 at 01:27:18AM +0900, GOTO Masanori wrote: [...] > > > I disagree. I've needed to use LOCPATH a couple of times. For > > > instance GCC's testsuite wants to use it to make sure some locales are > > > generated before running the libstdc++ tests. > > > > Is there a similar environment variable for /usr/share/locale? > > No, there isn't. > > > I would need it to generate translated man pages of coreutils programs. > > bindtextdomain(3) is not your friend? Thus, LOCALEDIR option in make > is useful for your purpose. Right, but it means that one must: * generate and install .mo files into $foo/locale * set LOCALEDIR=$foo and compile programs in order to generate translated man pages, so programs must be compiled twice :( > BTW, why does coreutils contain /usr/share/locale/*/LC_TIME/*.mo? Excerpt from po/Changelog: 2002-11-09 Jim Meyering <[EMAIL PROTECTED]> * Makevars (EXTRA_LOCALE_CATEGORIES): Add LC_TIME. Patch by Tim Waugh for Red Hat bug #73669. More informations are also available under RH#73672. This trick gives correct date format when LC_TIME and LC_MESSAGES are different. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#176661: locale.1 does not mention LOCPATH
At Sat, 8 Mar 2003 13:35:59 +0100, Denis Barbier wrote: > > On Fri, Mar 07, 2003 at 02:43:17PM -0500, Daniel Jacobowitz wrote: > [...] > > > > It is not obvious how to use a different directory than > > > > /usr/lib/locale for the locale data from reading the manual pages. > > > > > > Well, it's not worth while describing. > > > > I disagree. I've needed to use LOCPATH a couple of times. For > > instance GCC's testsuite wants to use it to make sure some locales are > > generated before running the libstdc++ tests. > > Is there a similar environment variable for /usr/share/locale? No, there isn't. > I would need it to generate translated man pages of coreutils programs. bindtextdomain(3) is not your friend? Thus, LOCALEDIR option in make is useful for your purpose. BTW, why does coreutils contain /usr/share/locale/*/LC_TIME/*.mo? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#176661: locale.1 does not mention LOCPATH
On Fri, Mar 07, 2003 at 02:43:17PM -0500, Daniel Jacobowitz wrote: [...] > > > It is not obvious how to use a different directory than > > > /usr/lib/locale for the locale data from reading the manual pages. > > > > Well, it's not worth while describing. > > I disagree. I've needed to use LOCPATH a couple of times. For > instance GCC's testsuite wants to use it to make sure some locales are > generated before running the libstdc++ tests. Is there a similar environment variable for /usr/share/locale? I would need it to generate translated man pages of coreutils programs. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#176661: locale.1 does not mention LOCPATH
At Fri, 7 Mar 2003 14:43:17 -0500, Daniel Jacobowitz wrote: > > On Sat, Mar 08, 2003 at 01:20:29AM +0900, GOTO Masanori wrote: > > At Fri, 07 Mar 2003 23:51:21 +0900, > > Junichi Uekawa wrote: > > > > > > > > --- locale.1.orig 2003-01-14 21:30:42.0 +0900 > > > > > +++ locale.12003-01-14 21:31:13.0 +0900 > > > > > @@ -233,6 +233,11 @@ > > > > > .Vb 1 > > > > > \&Metadata about the locale information. > > > > > .Ve > > > > > +\&\s-1LOCPATH\s0 > > > > > +.PP > > > > > +.Vb 1 > > > > > +\&The directory where locale data is stored > > > > > +.Ve > > > > > .SH "AUTHOR" > > > > > .IX Header "AUTHOR" > > > > > \&\fIlocale\fR was written by Ulrich Drepper for the \s-1GNU\s0 C Library. > > > > > > > > It's easy to add this description, but why is this needed? Who do use > > > > it? Please explain to me. > > > > > > I've been looking for a way to specify the directory. > > > And this information is available elsewhere also. > > > > And, still my question is: why? > > No reason, no accept. > > > > Locale data should be the same exactly. Or are you hacking locale > > system or locale data? BTW do you know glibc-2.3.1 uses only > > /usr/lib/locale/locale-archive ? > > > > > If there is an alternative POSIX defined locale environment to do a > > > similar thing instead, then please document that. > > > > OK. > > > > > It is not obvious how to use a different directory than > > > /usr/lib/locale for the locale data from reading the manual pages. > > > > Well, it's not worth while describing. > > I disagree. I've needed to use LOCPATH a couple of times. For > instance GCC's testsuite wants to use it to make sure some locales are > generated before running the libstdc++ tests. That makes sense. Thanks for your explanation. I add it. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#176661: locale.1 does not mention LOCPATH
On Sat, Mar 08, 2003 at 01:20:29AM +0900, GOTO Masanori wrote: > At Fri, 07 Mar 2003 23:51:21 +0900, > Junichi Uekawa wrote: > > > > > > --- locale.1.orig 2003-01-14 21:30:42.0 +0900 > > > > +++ locale.12003-01-14 21:31:13.0 +0900 > > > > @@ -233,6 +233,11 @@ > > > > .Vb 1 > > > > \&Metadata about the locale information. > > > > .Ve > > > > +\&\s-1LOCPATH\s0 > > > > +.PP > > > > +.Vb 1 > > > > +\&The directory where locale data is stored > > > > +.Ve > > > > .SH "AUTHOR" > > > > .IX Header "AUTHOR" > > > > \&\fIlocale\fR was written by Ulrich Drepper for the \s-1GNU\s0 C Library. > > > > > > It's easy to add this description, but why is this needed? Who do use > > > it? Please explain to me. > > > > I've been looking for a way to specify the directory. > > And this information is available elsewhere also. > > And, still my question is: why? > No reason, no accept. > > Locale data should be the same exactly. Or are you hacking locale > system or locale data? BTW do you know glibc-2.3.1 uses only > /usr/lib/locale/locale-archive ? > > > If there is an alternative POSIX defined locale environment to do a > > similar thing instead, then please document that. > > OK. > > > It is not obvious how to use a different directory than > > /usr/lib/locale for the locale data from reading the manual pages. > > Well, it's not worth while describing. I disagree. I've needed to use LOCPATH a couple of times. For instance GCC's testsuite wants to use it to make sure some locales are generated before running the libstdc++ tests. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#176661: locale.1 does not mention LOCPATH
At Fri, 07 Mar 2003 23:51:21 +0900, Junichi Uekawa wrote: > > > > --- locale.1.orig 2003-01-14 21:30:42.0 +0900 > > > +++ locale.12003-01-14 21:31:13.0 +0900 > > > @@ -233,6 +233,11 @@ > > > .Vb 1 > > > \&Metadata about the locale information. > > > .Ve > > > +\&\s-1LOCPATH\s0 > > > +.PP > > > +.Vb 1 > > > +\&The directory where locale data is stored > > > +.Ve > > > .SH "AUTHOR" > > > .IX Header "AUTHOR" > > > \&\fIlocale\fR was written by Ulrich Drepper for the \s-1GNU\s0 C Library. > > > > It's easy to add this description, but why is this needed? Who do use > > it? Please explain to me. > > I've been looking for a way to specify the directory. > And this information is available elsewhere also. And, still my question is: why? No reason, no accept. Locale data should be the same exactly. Or are you hacking locale system or locale data? BTW do you know glibc-2.3.1 uses only /usr/lib/locale/locale-archive ? > If there is an alternative POSIX defined locale environment to do a > similar thing instead, then please document that. OK. > It is not obvious how to use a different directory than > /usr/lib/locale for the locale data from reading the manual pages. Well, it's not worth while describing. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#176661: locale.1 does not mention LOCPATH
> > --- locale.1.orig 2003-01-14 21:30:42.0 +0900 > > +++ locale.12003-01-14 21:31:13.0 +0900 > > @@ -233,6 +233,11 @@ > > .Vb 1 > > \&Metadata about the locale information. > > .Ve > > +\&\s-1LOCPATH\s0 > > +.PP > > +.Vb 1 > > +\&The directory where locale data is stored > > +.Ve > > .SH "AUTHOR" > > .IX Header "AUTHOR" > > \&\fIlocale\fR was written by Ulrich Drepper for the \s-1GNU\s0 C Library. > > It's easy to add this description, but why is this needed? Who do use > it? Please explain to me. I've been looking for a way to specify the directory. And this information is available elsewhere also. If there is an alternative POSIX defined locale environment to do a similar thing instead, then please document that. It is not obvious how to use a different directory than /usr/lib/locale for the locale data from reading the manual pages. regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#176661: locale.1 does not mention LOCPATH
> setlocale is affected by LOCPATH, and it probably is worth mentioning in locale.1 > manual page. > > --- locale.1.orig 2003-01-14 21:30:42.0 +0900 > +++ locale.12003-01-14 21:31:13.0 +0900 > @@ -233,6 +233,11 @@ > .Vb 1 > \&Metadata about the locale information. > .Ve > +\&\s-1LOCPATH\s0 > +.PP > +.Vb 1 > +\&The directory where locale data is stored > +.Ve > .SH "AUTHOR" > .IX Header "AUTHOR" > \&\fIlocale\fR was written by Ulrich Drepper for the \s-1GNU\s0 C Library. It's easy to add this description, but why is this needed? Who do use it? Please explain to me. BTW, other environment variables are not the same to LOCPATH; they are POSIX-defined locale behavior specific environment variables, not setlocale() specific variable. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
