You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2003/08/22 12:42:15 UTC
[jira] Closed: (MAVEN-559) generated docs don't have charset=xxx set.
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Fri, 22 Aug 2003 5:41 AM
the meta tag is already in generated html head.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-559
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-559
Summary: generated docs don't have charset=xxx set.
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin-xdoc
Fix Fors:
1.0-rc1
Versions:
1.0-beta-9
Assignee:
Reporter: Ramon Casha
Created: Thu, 10 Jul 2003 6:02 AM
Updated: Fri, 22 Aug 2003 5:41 AM
Description:
With maven.docs.outputencoding=UTF-8 (or anything else), the documentation is correctly generated in the right encoding, but the HTML file headers don't say so, so the browser has no indication which encoding should be used. Suggest adding <meta http-equiv="content-type" content="text/html;charset=XXX"/> to the headers.
Current workaround is to hardwire the above in site.jsl
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org