Just out of curiousity, why are you running ><htmlserver side? Is it just
to Internationaliz e?
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
or just read it:
*************** *************** **************
| Think outside the box! |
*************** *************** **************
"Lee C." <nomail@spam.co mwrote in message
news:O%23KsAQA2 IHA.4572@TK2MSF TNGP03.phx.gbl. ..
to Internationaliz e?
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
or just read it:
*************** *************** **************
| Think outside the box! |
*************** *************** **************
"Lee C." <nomail@spam.co mwrote in message
news:O%23KsAQA2 IHA.4572@TK2MSF TNGP03.phx.gbl. ..
>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
>
>
>
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
>
>
Comment