[Mono-dev] Fwd: [Mono-patches] r63710 - in trunk/mcs/class/System.Web: System.Web.UI.WebControls Test/System.Web.UI.WebControls
atsushi at ximian.com
Mon Aug 14 06:06:13 EDT 2006
Hi Kornél (am always copypasting your name ;-),
Kornél Pál wrote:
> What about using UTF-8 (without BOM) in ChangeLog? It may sound weird but I
> personally have no problem with using Kanji (or using other non-Latin
> scripts) when using UTF-8 altough using Latin characters are more likely to
> be readable by every people looking at the files (as we use English). So
> using Latin scripts seem to be more reasonable.:) But I personally see
> nothing wrong about optionally including names in alternative scripts in
> addition to Latin representations.
Is saving files in utf-8 without BOM possible in general western
editors land? If yes I like the idea. If not then maybe it is not
a good solution for us (yeah, not using non-ASCII letters is the
most pessimistic option).
(BTW I guess, with BOM you guys will get stuck, right?)
> Currently .cs files are compiled either as Latin 1 (default) or as UTF-8
> (when set in Makefile of the assembly, but anything else could be set) so I
> think the appropriate encoding can be used in source files.
(Note that what Kornél mentioned above was all about ChangeLogs.)
When it comes to mcs sources, we wouldn't want to change things.
It forces us to change all relevant sources to utf-8 because
with BOMless utf-8 explicit compiler option -codepage:65001 is
> Apart from the above things using \u#### and \U######## escape sequences for
> non-ASCII characters in string literals ensures that the code functions
> correctly. Compilers ignore comments so incorrectly encoded characters in
> comments can cause little harm if any.
Sadly it indeed caused problems when I tried to build a library
from the sources whose comments are written in Japanese (Shift_JIS).
So, in such cases, using UTF-8 is the only solution I think.
More information about the Mono-devel-list