[Mono-dev] Possible Bug in Mono?

Atsushi Eno atsushieno at veritas-vos-liberabit.com
Mon Sep 6 11:29:18 EDT 2010


source code encoding can be specified when you save a source file on 
MonoDevelop (there is a combobox for encoding option).

On compilation, monodevelop takes compiler options from the project 
properties. I don't know which encoding MonoDevelop on Windows uses by 
default (I don't have Windows machine now), but adding "-codepage:utf8" 
to "additional options" line on the "Compiler" node on the "Build" menu 
tree would work.

(-codepage option is common to .NET csc.exe)

Atsushi Eno

(10/09/06 21:38), anidotnet wrote:
> Atsushi Eno-2 wrote:
>>    (In general, avoid using such ambiguous email subject; it makes
>> searching relevant messages difficult.)
> First of all sorry for the inconvenience caused due to short ambiguous
> subject of the email.
> Atsushi Eno-2 wrote:
>> You can avoid such a problem by avoiding non-ASCII characters in your
>> source code. In this case, use "¥u0083" instead of raw POUND SIGN.
> Secondly, I don't want to avoid Unicode char in the source code as the sole
> intention of the function I used is to get the Unicode representation of a
> string. That's why I want to specify the unicode char in the source code for
> unit testing.
> Atsushi Eno-2 wrote:
>> Make sure that you don't have your source
>> encoding and compiler -codepage argument or default encoding
>> mismatching. The default encoding is platform dependent.
> Can you please tell me how to do that? I am using Mono v2.6.7 with
> Monodevelop v2.4 on Windows XP. Any help would be highly appreciated.
> Thanks for your reply and time.
> --------------------
> Regards,
> Anindya Chatterjee
> http://abstractclass.org

More information about the Mono-devel-list mailing list