forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [issues] Created: (FOR-143) Encoding of HTML files should be configurable
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-143


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-143
    Summary: Encoding of HTML files should be configurable
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
  Component: None

   Assignee: 
   Reporter: Juan Jose Pablos

    Created: Tue, 4 May 2004 7:04 PM
    Updated: Tue, 4 May 2004 7:04 PM

Description:
From: Fabrice Bacchella <bacchell@club-internet.fr>


By default, HTML files are encoded in ISO-8859-1 because of the way the Cocoon's HTML serialiser
is declared in sitemap.xmap :

<map:serializer name=3D"html" mime-type=3D"text/html"
src=3D"org.apache.cocoon.serialization.HTMLSerializer">
	<doctype-public>-//W3C//DTD HTML 4.01 =
Transitional//EN</doctype-public>

<doctype-system>http://www.w3.org/TR/html4/loose.dtd</doctype-system>
</map:serializer>

The default one is such a case is ISO-8859-1. And it even add a META inthe HTML result. But
here in French, ISO-8859-15 is better because of=20
the  =AB e dans l'o =BB character : =9C. In Russian or Asia, the =
situation is even worse.

Is that possible to add a properties in forrest.properties saying for example :
project.encoding=UTF-8

and adding a <encoding>@project.encoding@</encoding> element in the
HTML serializer ?

And in a more general way, where can I find a document about the way=20
properties are used by forrest ? Which files use them ? How to add a=20
new one ?


---------------------------------------------------------------------
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