ASP.NET Internationalization bug?



I think I have discovered a bug in ASP.NET, related to I18N.

In ASP.NET 3.5 I have to set runat="server" on the html element to use
explicit expressions. It appears that ASP.NET eats the xml:lang attribute
on the html element when it is set to runat="server".

Of course I want to replace the hardcoded "en-US" values with (resource)
explicit expressions; but, for simplicity, try this:

<html runat="server" xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en-US"
lang="en-US" dir="ltr">

....And you will find that no xml:lang attribute is rendered to the browser!
Remove the runat="server", and, voila, the xml:lang attribute is rendered.
:[

....Any ideas?

Cordially,
Lee


.



Relevant Pages

  • Re: ASP.NET Internationalization bug?
    ... reason I presently have for wanting to use explicit expressions is ... internationalization. ... In ASP.NET 3.5 I have to set runat="server" on the html element to use ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP.NET Internationalization bug?
    ... that is a temporary workaround. ... no xml:lang attribute is rendered to the browser! ... In ASP.NET 3.5 I have to set runat="server" on the html element to use ... explicit expressions; but, for simplicity, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP.NET Internationalization bug?
    ... I have submitted this to Microsoft as a bug report. ... In ASP.NET 3.5 I have to set runat="server" on the html element to use ... explicit expressions; ...
    (microsoft.public.dotnet.framework.aspnet)