You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "paul bolger (JIRA)" <ji...@apache.org> on 2006/03/10 10:50:38 UTC

[jira] Created: (FOR-828) Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.

Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.
----------------------------------------------------------------------------------------------------------------

         Key: FOR-828
         URL: http://issues.apache.org/jira/browse/FOR-828
     Project: Forrest
        Type: Bug
  Components: Dispatcher (aka views)  
    Versions: 0.8-dev    
    Reporter: paul bolger


First four lines of Dispatcher rendered page:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns:forrest="http://apache.org/forrest/templates/1.0" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
<head>

IE (win, version 6.0 - haven't tried others) misses the character encoding and defaults to western 88 or whatever, messing up some characters. 
Putting a XHTML namespace declaration in the html tag seems to fix this, but skipping the XML tag and adding a standard HTML metatag encoding would also do the trick. I'm not sure on the relative merits of either approach but suspect neolithic browsers such as NS4.79 aren't going to be impressed by namespaces...Might be better to go for the legacy option.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (FOR-828) Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.

Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-828?page=all ]
     
Thorsten Scherler closed FOR-828:
---------------------------------


> Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.
> ----------------------------------------------------------------------------------------------------------------
>
>          Key: FOR-828
>          URL: http://issues.apache.org/jira/browse/FOR-828
>      Project: Forrest
>         Type: Bug

>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: paul bolger
>  Attachments: FOR-828.patch, ie.patch.v1.diff, ie.patch.v2.diff
>
> First four lines of Dispatcher rendered page:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html xmlns:forrest="http://apache.org/forrest/templates/1.0" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
> <head>
> IE (win, version 6.0 - haven't tried others) misses the character encoding and defaults to western 88 or whatever, messing up some characters. 
> Putting a XHTML namespace declaration in the html tag seems to fix this, but skipping the XML tag and adding a standard HTML metatag encoding would also do the trick. I'm not sure on the relative merits of either approach but suspect neolithic browsers such as NS4.79 aren't going to be impressed by namespaces...Might be better to go for the legacy option.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (FOR-828) Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.

Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-828?page=all ]
     
Thorsten Scherler resolved FOR-828:
-----------------------------------

    Resolution: Fixed

I fixed the meta tag in all supported themes to 
<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>.

Further I changed the transformation that the formating the final xhtml output the way IE really likes it.

> Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.
> ----------------------------------------------------------------------------------------------------------------
>
>          Key: FOR-828
>          URL: http://issues.apache.org/jira/browse/FOR-828
>      Project: Forrest
>         Type: Bug

>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: paul bolger
>  Attachments: FOR-828.patch, ie.patch.v1.diff, ie.patch.v2.diff
>
> First four lines of Dispatcher rendered page:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html xmlns:forrest="http://apache.org/forrest/templates/1.0" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
> <head>
> IE (win, version 6.0 - haven't tried others) misses the character encoding and defaults to western 88 or whatever, messing up some characters. 
> Putting a XHTML namespace declaration in the html tag seems to fix this, but skipping the XML tag and adding a standard HTML metatag encoding would also do the trick. I'm not sure on the relative merits of either approach but suspect neolithic browsers such as NS4.79 aren't going to be impressed by namespaces...Might be better to go for the legacy option.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (FOR-828) Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.

Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/FOR-828?page=comments#action_12370582 ] 

Thorsten Scherler commented on FOR-828:
---------------------------------------

I added the meta tags you provided. 
Can you try whether this works for you?

Commit de la revisiĆ³n 386160.


> Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.
> ----------------------------------------------------------------------------------------------------------------
>
>          Key: FOR-828
>          URL: http://issues.apache.org/jira/browse/FOR-828
>      Project: Forrest
>         Type: Bug
>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: paul bolger
>  Attachments: ie.patch.v1.diff, ie.patch.v2.diff
>
> First four lines of Dispatcher rendered page:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html xmlns:forrest="http://apache.org/forrest/templates/1.0" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
> <head>
> IE (win, version 6.0 - haven't tried others) misses the character encoding and defaults to western 88 or whatever, messing up some characters. 
> Putting a XHTML namespace declaration in the html tag seems to fix this, but skipping the XML tag and adding a standard HTML metatag encoding would also do the trick. I'm not sure on the relative merits of either approach but suspect neolithic browsers such as NS4.79 aren't going to be impressed by namespaces...Might be better to go for the legacy option.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (FOR-828) Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.

Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-828?page=all ]

Thorsten Scherler updated FOR-828:
----------------------------------

    Attachment: ie.patch.v1.diff

First version of a fix. Will add the xmlns but strips it again later on. 
not my favorite.

> Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.
> ----------------------------------------------------------------------------------------------------------------
>
>          Key: FOR-828
>          URL: http://issues.apache.org/jira/browse/FOR-828
>      Project: Forrest
>         Type: Bug
>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: paul bolger
>  Attachments: ie.patch.v1.diff
>
> First four lines of Dispatcher rendered page:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html xmlns:forrest="http://apache.org/forrest/templates/1.0" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
> <head>
> IE (win, version 6.0 - haven't tried others) misses the character encoding and defaults to western 88 or whatever, messing up some characters. 
> Putting a XHTML namespace declaration in the html tag seems to fix this, but skipping the XML tag and adding a standard HTML metatag encoding would also do the trick. I'm not sure on the relative merits of either approach but suspect neolithic browsers such as NS4.79 aren't going to be impressed by namespaces...Might be better to go for the legacy option.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Updated: (FOR-828) Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.

Posted by Thorsten Scherler <th...@apache.org>.
Thorsten Scherler (JIRA) schrieb:
>      [ http://issues.apache.org/jira/browse/FOR-828?page=all ]
>
> Thorsten Scherler updated FOR-828:
> ----------------------------------
>
>     Attachment: FOR-828.patch
>
> This patch removes the xml declaration from the final output.
> Further it add a default namespace to the html element tag.
>   

Hi all,

I am away at a customer and cannot apply this patch.
Will do when I come back if no one beats me to it.

salu2

>   
>> Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.
>> ----------------------------------------------------------------------------------------------------------------
>>
>>          Key: FOR-828
>>          URL: http://issues.apache.org/jira/browse/FOR-828
>>      Project: Forrest
>>         Type: Bug
>>     
>
>   
>>   Components: Dispatcher (aka views)
>>     Versions: 0.8-dev
>>     Reporter: paul bolger
>>  Attachments: FOR-828.patch, ie.patch.v1.diff, ie.patch.v2.diff
>>
>> First four lines of Dispatcher rendered page:
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
>> <html xmlns:forrest="http://apache.org/forrest/templates/1.0" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
>> <head>
>> IE (win, version 6.0 - haven't tried others) misses the character encoding and defaults to western 88 or whatever, messing up some characters. 
>> Putting a XHTML namespace declaration in the html tag seems to fix this, but skipping the XML tag and adding a standard HTML metatag encoding would also do the trick. I'm not sure on the relative merits of either approach but suspect neolithic browsers such as NS4.79 aren't going to be impressed by namespaces...Might be better to go for the legacy option.
>>     
>
>   


[jira] Updated: (FOR-828) Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.

Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-828?page=all ]

Thorsten Scherler updated FOR-828:
----------------------------------

    Attachment: FOR-828.patch

This patch removes the xml declaration from the final output.
Further it add a default namespace to the html element tag.

> Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.
> ----------------------------------------------------------------------------------------------------------------
>
>          Key: FOR-828
>          URL: http://issues.apache.org/jira/browse/FOR-828
>      Project: Forrest
>         Type: Bug

>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: paul bolger
>  Attachments: FOR-828.patch, ie.patch.v1.diff, ie.patch.v2.diff
>
> First four lines of Dispatcher rendered page:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html xmlns:forrest="http://apache.org/forrest/templates/1.0" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
> <head>
> IE (win, version 6.0 - haven't tried others) misses the character encoding and defaults to western 88 or whatever, messing up some characters. 
> Putting a XHTML namespace declaration in the html tag seems to fix this, but skipping the XML tag and adding a standard HTML metatag encoding would also do the trick. I'm not sure on the relative merits of either approach but suspect neolithic browsers such as NS4.79 aren't going to be impressed by namespaces...Might be better to go for the legacy option.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (FOR-828) Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.

Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-828?page=all ]

Thorsten Scherler updated FOR-828:
----------------------------------

    Attachment: ie.patch.v2.diff

This one would be the cleanest solution IMO.

> Internet Explorer fails to read the UTF-8 character encoding in the XML statement, defaults to western encoding.
> ----------------------------------------------------------------------------------------------------------------
>
>          Key: FOR-828
>          URL: http://issues.apache.org/jira/browse/FOR-828
>      Project: Forrest
>         Type: Bug
>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: paul bolger
>  Attachments: ie.patch.v1.diff, ie.patch.v2.diff
>
> First four lines of Dispatcher rendered page:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html xmlns:forrest="http://apache.org/forrest/templates/1.0" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
> <head>
> IE (win, version 6.0 - haven't tried others) misses the character encoding and defaults to western 88 or whatever, messing up some characters. 
> Putting a XHTML namespace declaration in the html tag seems to fix this, but skipping the XML tag and adding a standard HTML metatag encoding would also do the trick. I'm not sure on the relative merits of either approach but suspect neolithic browsers such as NS4.79 aren't going to be impressed by namespaces...Might be better to go for the legacy option.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira