And, I think that UTF-8 is best solution when the setting of LC_CTYPE category is C.
2009/6/4 IWAMURO Motonori <deenhe...@gmail.com>: > I think that this problem is caused by missing setting the locale > environment variable. > Therefore, I think that the problem can be solved by compelling the > setting with setup.exe. > > 2009/6/4 Corinna Vinschen <corinna-cyg...@cygwin.com>: >> >> http://cygwin.com/acronyms/#PCYMTNQREAIYR >> http://cygwin.com/acronyms/#TOFU >> >> On Jun 4 00:03, IWAMURO Motonori wrote: >>> 2009/6/3 Corinna Vinschen >>> > What's left as questionable is the LANG=C default case. Due to the >>> > discussion from the last month we now use UTF-8 as default encoding, >>> > because it's the only encoding which covers all (valid) characters. >>> > Sure, we could also convert the command line using the current ANSI >>> > codepage as Windows does it when calling CreateProcessA in this case. >>> > >>> > Maybe we should do that for testing? Anybody having a strong opinion >>> > here? >> >>> How about the addition of the setting of the locale environment >>> variable (like LANG) to the Cygwin installer? >> >> I'm sorry, but I don't understand how that's connected to the behaviour >> of the Cygwin DLL. Setup.exe is an entirely different beast. >> >> >> Corinna >> >> -- >> Corinna Vinschen Please, send mails regarding Cygwin to >> Cygwin Project Co-Leader cygwin AT cygwin DOT com >> Red Hat >> >> -- >> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >> Problem reports: http://cygwin.com/problems.html >> Documentation: http://cygwin.com/docs.html >> FAQ: http://cygwin.com/faq/ >> >> > > > > -- > IWAMURO Motnori <http://vmi.jp/> > -- IWAMURO Motnori <http://vmi.jp/> -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/