[Bug libc/11635] setlocale() doesn't support path based locale specification

[Bug libc/11635] setlocale() doesn't support path based locale specification

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=11635

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/11635] setlocale() doesn't support path based locale specification

[yann at droneaud dot fr]

------- Additional Comments From yann at droneaud dot fr  2010-05-26 08:50 -------
(In reply to comment #4)
> It's not a conformance issue.  There is nothing that can be done for
> LC_ALL=/some/path.  The standard only requires that  if the envvar points to a
> file it is used. 

Not necessarily a file, it could be a directory.

> With LC_ALL there is no single file and pointing to a
> directory does not fulfill the requirements of the standard.  

The path to be given to LC_* is the same as the path given to localedef.
Whether it's a single file or a directory, it's up to the implementation.

example:

  localedef -f UTF-8 -i fr_FR /home/foo/locales/fr_FR.UTF-8

  LC_ALL=/home/foo/locales/fr_FR.UTF-8 locale
  LC_CTYPE=/home/foo/locales/fr_FR.UTF-8 locale


> And I have no
> interest whatsoever to add a bogus extension which would allow doing this. 

The kind of bogus extension would be to use the path given in LC_* variables
instead of the hard-coded ones.

> Nobody should ever use this.  

Yes, probably.

I think the purpose of this extension is to allow user of a proprietary/closed
system to be able to use specific locales.

Having the glibc sources, I can rebuild it with any locale I want, so I'm not
stuck for my tests, but it would be easier to use the facility given by the
standard.

> The specification for localedef doesn't describe
> the format of the output files and therefore this whole portion of the spec is
> utterly bogus useless crap.

The specification of this feature doesn't rely on the underlying format of the
localedef output (hopefully).


If you don't want to implement this part of the POSIX specification, it's not a
problem for me, but please don't say it doesn't exists (in the specification).
The resolution for this bug isn't INVALID, but WONTFIX instead.

Regards.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11635

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11635] setlocale() doesn't support path based locale specification

[drepper at redhat dot com]

------- Additional Comments From drepper at redhat dot com  2010-05-25 20:26 -------
It's not a conformance issue.  There is nothing that can be done for
LC_ALL=/some/path.  The standard only requires that  if the envvar points to a
file it is used.  With LC_ALL there is no single file and pointing to a
directory does not fulfill the requirements of the standard.  And I have no
interest whatsoever to add a bogus extension which would allow doing this. 
Nobody should ever use this.  The specification for localedef doesn't describe
the format of the output files and therefore this whole portion of the spec is
utterly bogus useless crap.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID


http://sourceware.org/bugzilla/show_bug.cgi?id=11635

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11635] setlocale() doesn't support path based locale specification

[pasky at suse dot cz]

------- Additional Comments From pasky at suse dot cz  2010-05-25 20:10 -------
This is a conformance issue; either glibc should implement POSIX properly, or if
you think the spec is not sane, a defect against POSIX should be filed as the
bug is closed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |


http://sourceware.org/bugzilla/show_bug.cgi?id=11635

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11635] setlocale() doesn't support path based locale specification

[yann at droneaud dot fr]

------- Additional Comments From yann at droneaud dot fr  2010-05-25 15:25 -------
(In reply to comment #1)
> The LC_* variables don't contain paths.  Why should they? 

So, you, as a member of the Austin group, should ask for the removal of this
feature from the Open Group specifications.

Regards.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11635

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11635] setlocale() doesn't support path based locale specification

[drepper at redhat dot com]

------- Additional Comments From drepper at redhat dot com  2010-05-25 15:11 -------
The LC_* variables don't contain paths.  Why should they?  Paths are specified
in LOCPATH.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


http://sourceware.org/bugzilla/show_bug.cgi?id=11635

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11635] setlocale() doesn't support path based locale specification

[yann at droneaud dot fr]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement


http://sourceware.org/bugzilla/show_bug.cgi?id=11635

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.