[I've dropped the case number from the subject and set Reply-To.] On Mon, Jul 07, 2008 at 01:48:24PM +0200, Roland Mainz wrote: > > we will gather more > > information/feedback to see if we have future plans for legacy locales. > > Ok... my main concern is "interoperabilty", e.g. what happens if I am > running something like the "ms_MY.UTF-8" or "vi_VN.UTF-8" locale and > then do a slogin into a Linux machine ?
You know the answer: without codeset conversion somewhere you'll get garbage, or worse depending on the degree of [in]compatibility between the two codesets. I suppose we could add codeset conversion features to things like ssh(1), but that's not this case. Nor do I see how adding UTF-8 locales binds the i-team to add non-UTF-8 locales as well. I might hesitate to call non-Unicode codesets "legacy" for precisely the reason that you gave, but as long as that's not used in the documentation I don't care. Nico --
