[Mono-bugs] [Bug 690675] New: Globalization still not working in Mono 2.10

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Apr 28 15:44:25 EDT 2011



           Summary: Globalization still not working in Mono 2.10
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.10.x
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: test051102 at hotmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101

I have created a simple ASP.NET application using MonoDevelop 2.6 Beta 2. I
added a test.htm file which contains the German text "für Flöhe älter als daß"
wich contains several special characters which are not displayed correctly in

I created the test.htm file with VS2008 in order to ensure that MonoDevelop
will not change it's format behind the scenes. I also copied the the text to
Default.aspx using VS2008.

Reproducible: Always

Steps to Reproduce:
1.Run the application
2.Look at the content of Default.aspx
3.Compare to the content of test.htm (enter into
the browser's address bar
Actual Results:  
Mono corrupts all special characters in Default.aspx. But it the text in
test.htm is displayed as expected!

Expected Results:  
Correct display of text including all special characters in Default.aspx.

MonoDevelop 2.6 Beta 2 creates the following section inside of web.config:

<globalization requestEncoding="utf-8" responseEncoding="utf-8" />

when changing "utf-8" against "iso-8859-1" things are changing as follows:

The text im Default.aspx is corrupted. But the displayed characters are
different compared to "utf-8" encoding. The text in test.htm is also totally

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list