You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2004/07/28 07:11:47 UTC

DO NOT REPLY [Bug 30355] New: - Character encodings in html tags

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30355>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30355

Character encodings in html tags

           Summary: Character encodings in html tags
           Product: Struts
           Version: 1.1 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Custom Tags
        AssignedTo: dev@struts.apache.org
        ReportedBy: ephemeris.lappis@tiscali.fr


HTML tags sometimes seem to encode characters before they write them into the 
page output. In these cases, characters like '<' are translated into '&lt;', 
that is right. But in other cases, the characters are not correctly encoded, 
and the resulting pages can't be processed by the receiving UA. Here some 
cases :

- It seems that strings from resources in attributes like 'altKey' 
or 'titleKey' are never encoded and characters like '"' lead the browser to 
fail.

- Attribute values set in the tag body seems to be written as is and produce 
the same problem.

The tags documentation doesn't specify clearly when characters are encoded and 
when they are not, and, if they are, what kind of encoding is performed : from 
what i can see, encodings seem to take into account characters that could break 
the tagged structure, like '<', '\'', '"' and '>', but latin characters 
like 'é' or 'ñ' are left as is when the page charset is set to UTF-8, for 
example. Is it right ? In other cases, other thags like in the 'bean' family, 
seem to encode some characters when the content type is not "text/html" 
but "plain/text" !

Is there a more precise documentation about content and character encodings ? 
Is this process deterministic ?

Thanks for your help.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org