So to clarify, you're not proposing removing any character set support, but propose to remove locale information for some character sets. (i.e. collation info, upper/lower, etc) correct?
Note that for the "OEM code pages" in SMB (8-bit char sets), you need the ability to convert upper/lower, lower/upper in any of those. (and case-insensitive match) I don't believe collation is required. Gordon On Thu, Jan 26, 2012 at 11:38 PM, Garrett D'Amore <[email protected]> wrote: > Iconv and protocol support is orthogonal to support for using the locale for > interactive logins. There is indeed value in removing those we don't need as > it takes real work to continue to support them under newer versions of cldr. > > Sent from my iPhone > > On Jan 26, 2012, at 6:58 PM, Gordon Ross <[email protected]> wrote: > >> A number of places in protocol code need support for various 8-bit >> character sets. >> For example, you can configure NFS to convert to/from some of these and utf-8 >> when serving NFS v2, v3. (NFSv4 does utf-8) >> >> It would take me a little time to get a complete list, but I remember >> seeing things >> like EUC-* SJIS-* and various ISO-8859-* sets in use in SMB for some "OEM" >> strings (legacy stuff). >> >> I'm not sure about the need for the locale data for any of those. >> Maybe that could go away, but is there much benefit in that? >> >> >> 2012/1/26 Garrett D'Amore <[email protected]>: >>>> I use koi8-r & windows-1251 in the PostgreSQL and nginx. In the new >>>> projects I use utf-8 only, but I have some old code which I can't rewrite >>>> now. >>> >>> Do you just need support for the encodings (via iconv or whatever) or do >>> you need the actual locales to be present on the system? >>> >>> I'm thinking UTF-8 ought to be sufficient, but I confess I'm not sure I >>> understand why the encoding would matter at all for the login locale -- >>> except perhaps you might be interfacing with systems via e.g. telnet or >>> ssh, which don't support UTF-8 but have a legacy locale. (Are such >>> concerns still relevant?) >>> >>> - Garrett >>> >>>> >>>> >>>> ------------------------------------------- >>>> illumos-discuss >>>> Archives: https://www.listbox.com/member/archive/182180/=now >>>> RSS Feed: >>>> https://www.listbox.com/member/archive/rss/182180/22003744-45f01c1f >>>> Modify Your Subscription: https://www.listbox.com/member/?&; >>>> Powered by Listbox: http://www.listbox.com >>> >>> >>> >>> ------------------------------------------- >>> illumos-discuss >>> Archives: https://www.listbox.com/member/archive/182180/=now >>> RSS Feed: >>> https://www.listbox.com/member/archive/rss/182180/21175550-b1877313 >>> Modify Your Subscription: https://www.listbox.com/member/?&; >>> Powered by Listbox: http://www.listbox.com >> >> >> ------------------------------------------- >> illumos-discuss >> Archives: https://www.listbox.com/member/archive/182180/=now >> RSS Feed: https://www.listbox.com/member/archive/rss/182180/22003744-45f01c1f >> Modify Your Subscription: https://www.listbox.com/member/?&; >> Powered by Listbox: http://www.listbox.com > > > ------------------------------------------- > illumos-discuss > Archives: https://www.listbox.com/member/archive/182180/=now > RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175550-b1877313 > Modify Your Subscription: https://www.listbox.com/member/?&; > Powered by Listbox: http://www.listbox.com ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
