forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [issues] Created: (FOR-213) Forrest doesnt render foreing charactercodes correctly to UTF-8
Date Thu, 01 Jan 1970 00:00:00 GMT
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-213


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-213
    Summary: Forrest doesnt render foreing charactercodes correctly to UTF-8
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: Forrest
  Component: None
   Versions:
             0.5.1

   Assignee: 
   Reporter: Lukas Zapletal

    Created: Sat, 10 Jul 2004 3:45 PM
    Updated: Sat, 10 Jul 2004 3:45 PM
Environment: Java 1.4.1, Windows XP

Description:
When I create all XML pages in the right encoding (e.g. windows-1250) and set this encoding
at the top of each XML document, the result static HTML pages are NOT converted to UTP-8 (but
the header says it should be this encoding).

Forrest leaves all characters as is plus it converts SOME of them to HTML entities. Thats
totally bad. It should convert all characters to the UTF8 codes.

Same with CWIKI pages - in the CWIKI page I am not able to set the source file encoding, but
I suppose Forrest will use the default platform encoding (in my case windows-1250). The result
is same: characters are NOT converted and some of them are converted only to HTML entities.

This needs to be fixed, it blocks all non-english users. Thanks.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org/jira//Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message