> If you believe this must be a mono bug then there should be such a test > case that tests encoding conversion against > your default encoding (I don't know what it is) and corresponding binary > file (non-utf8-test file) that contains such a > problematic bytes. If it is supplied, then I'll take a look.
What should i do? I can send you result of VS project publishing. But i made my tests under Windows + XSP2. On windows i selected "Language for non-Unicode programs" as Russian (Windows-1251 encoding). (it is in "Regional and Language Options" -> "Advanced"). Also i've made test and run it on same mono version: Console.WriteLine(System.Text.Encoding.Default.WindowsCodePage.ToString()) and it showed me 1251 So what else can i do? > BTW you wrote "too many bugs" but have mentioned only one. I wonder if > one is too much number for you to count. Because i made simple (like "Hello world!") application and immediately found 3 problems: encoding, parsing of '<' inside aspx, problem with ObjectDataSource. When it will be fixed i'll find next bugs, but now problem with ObjectDataSource is a blocker bug for me... _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
