You are viewing a plain text version of this content. The canonical link for it is here.
Posted to portalapps-dev@portals.apache.org by "Vladimir Figurov (JIRA)" <ji...@apache.org> on 2009/11/25 16:18:40 UTC
[jira] Created: (APA-25) Broken NLS chars in "as-portal" encoded
html documents
Broken NLS chars in "as-portal" encoded html documents
------------------------------------------------------
Key: APA-25
URL: https://issues.apache.org/jira/browse/APA-25
Project: Portals Apps
Issue Type: Bug
Components: apa-webcontent
Affects Versions: apa-webcontent-1.0
Environment: Windows XP pro 2002 SP2;
Apache Tomcat/6.0.20 (from EXE or ZIP distribution)
jdk1.5.0_12
jre1.6.0_17-b04
jetspeed2.2.0-demo.jar
Mozilla, MS IE
Reporter: Vladimir Figurov
Assignee: David Sean Taylor
Note: usage a Portal's CATALINA_HOME
1) Place to CATALINA_HOME\webapps\ROOT any UTF-8 HTML document with national chars.
2) Use a "Web Content Portlet" from "webcontent" PA.
3) Set SRC = http://localhost/<html_doc_name>
4) Place the WebContent Portlet on the any portal's page and look...on broken nls-chars
5) Navgate the browser to http://localhost/<html_doc_name> and view the correct nls-chars
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (APA-25) Broken NLS chars in "as-portal" encoded
html documents
Posted by "David Sean Taylor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Sean Taylor resolved APA-25.
----------------------------------
Resolution: Cannot Reproduce
Haven't heard back on Woonsan's question for over 4 months. Assuming Woonsan's recommendation worked
> Broken NLS chars in "as-portal" encoded html documents
> ------------------------------------------------------
>
> Key: APA-25
> URL: https://issues.apache.org/jira/browse/APA-25
> Project: Portals Apps
> Issue Type: Bug
> Components: apa-webcontent
> Affects Versions: apa-webcontent-1.0
> Environment: Windows XP pro 2002 SP2;
> Apache Tomcat/6.0.20 (from EXE or ZIP distribution)
> jdk1.5.0_12
> jre1.6.0_17-b04
> jetspeed2.2.0-demo.jar
> Mozilla, MS IE
> Reporter: Vladimir Figurov
> Assignee: David Sean Taylor
>
> Note: usage a Portal's CATALINA_HOME
> 1) Place to CATALINA_HOME\webapps\ROOT any UTF-8 HTML document with national chars.
> 2) Use a "Web Content Portlet" from "webcontent" PA.
> 3) Set SRC = http://localhost/<html_doc_name>
> 4) Place the WebContent Portlet on the any portal's page and look...on broken nls-chars
> 5) Navgate the browser to http://localhost/<html_doc_name> and view the correct nls-chars
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (APA-25) Broken NLS chars in "as-portal" encoded
html documents
Posted by "Woonsan Ko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782467#action_12782467 ]
Woonsan Ko commented on APA-25:
-------------------------------
WebContent portlet does not assume the target web content is in UTF-8 encoded.
HTML documents can be in any encoding, such as ISO-8859-1, the default web encoding.
So, WebContent portlet detects the encoding of the web content based on the response's character encoding or "content-type" meta tag of the content document itself.
So, I think you should check if the response of the target web content has UTF-8 encoding header or the target web content document contains "content-type" meta tag.
The current implementation assumes that it is in ISO-8859-1 encoding, the web default encoding, if the encoding is not detected by the ways mentioned above.
Could you check this in your target web contents?
> Broken NLS chars in "as-portal" encoded html documents
> ------------------------------------------------------
>
> Key: APA-25
> URL: https://issues.apache.org/jira/browse/APA-25
> Project: Portals Apps
> Issue Type: Bug
> Components: apa-webcontent
> Affects Versions: apa-webcontent-1.0
> Environment: Windows XP pro 2002 SP2;
> Apache Tomcat/6.0.20 (from EXE or ZIP distribution)
> jdk1.5.0_12
> jre1.6.0_17-b04
> jetspeed2.2.0-demo.jar
> Mozilla, MS IE
> Reporter: Vladimir Figurov
> Assignee: David Sean Taylor
>
> Note: usage a Portal's CATALINA_HOME
> 1) Place to CATALINA_HOME\webapps\ROOT any UTF-8 HTML document with national chars.
> 2) Use a "Web Content Portlet" from "webcontent" PA.
> 3) Set SRC = http://localhost/<html_doc_name>
> 4) Place the WebContent Portlet on the any portal's page and look...on broken nls-chars
> 5) Navgate the browser to http://localhost/<html_doc_name> and view the correct nls-chars
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.