This is the mail archive of the libc-locales@sourceware.org mailing list for the GNU libc locales project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug localedata/14641] Deprecate name_fmt


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

--- Comment #18 from Philip Withnall <bugzilla at tecnocode dot co.uk> ---
(In reply to Florian Weimer from comment #15)
> (In reply to Philip Withnall from comment #14)
> > (In reply to Florian Weimer from comment #13)
> > > Closing per previous discussion.
> > 
> > As per comments #5 and #6, I think the proper solution is to deprecate
> > name_fmt, since it seems to be fundamentally incorrect to have it in libc,
> > and keeping it un-deprecated just encourages people to use it incorrectly or
> > unsuccessfully.
> 
> Fair enough.  That would extend to LC_NAME, LC_ADDRESS, LC_TELEPHONE, I
> suppose.  What about LC_MEASUREMENT and LC_IDENTIFICATION?

LC_MEASUREMENT and LC_IDENTIFICATION are in active use, and seem reasonably
well-defined and useful (for example, knowing which temperature units to use in
the current locale). LC_TELEPHONE also seems useful, giving international call
codes in and out of the current country.

I guess Iâd say the cutoff is whether the formatting depends on the origin of
the data. For phone numbers it doesnât (calling codes are internationally
defined), but for names and addresses.

> Related identifiers include _NL_NAME_*, _NL_ADDRESS_*, _NL_TELEPHONE_*, plus
> the _NL_NUM_* identifiers.  Anything else?

I canât find anything else.

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]