OK. I withdraw my proposal. 2009/6/16 Corinna Vinschen <corinna-cyg...@cygwin.com>: > On Jun 15 23:35, IWAMURO Motonori wrote: >> 2009/6/15 Corinna Vinschen: >> > If everybody agrees to this suggestion, here's the patch. >> >> Is the name of modifier prefix "cjk-" good? It influences not CJK >> characters but a part of symbols and European characters. >> Please refer to Andy's opinion: >> http://cygwin.com/ml/cygwin/2009-06/msg00240.html >> >> It personally proposes "ambinarrow" because the switch of Vim is "ambiwidth". > > I think "cjk" in the name is the right choice. There are no ambiguous > characters in western languages (well, probably there are, but the > ambiguity is not on the level of character widths). This is a problem > which only has a meaning in these so called CJK languages. It makes > sense to me to use this in the modifier name. > >> And, I don't think that it is symmetrical. How about the following >> patch? (I have not changed the name of modifier prefix) > > I'm not convinced that we need symmetry. It looks like a nice idea for > Cygwin or newlib, given that the setlocale language string is checked > and picked to pieces hardcoded in the loadlocale function. > > However, besides of being unnecessary, other systems like Linux or BSD > use the language string as directory name relative to the > /usr/share/locale directory. If this gets ever used on non-Cygwin > systems, the symmetry (which has no precedent in the locale arena) would > require these systems to create yet another subdirectory or symlink for > the same purpose. Even worse, if you propose that @cjkwide is a valid > modifier for *any* language, you would make the whole mechanism on > non-newlib based systems more complicated for no apparent reason. > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Project Co-Leader cygwin AT cygwin DOT com > Red Hat >
-- 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/
