[ http://jira.codehaus.org/browse/MSITE-19?page=comments#action_72875 ] 
            
Marian Flor commented on MSITE-19:
----------------------------------

This is a follow-up to Michael Schnake's explanation:

Here's how I got the most german umlauts (may be in general applied to other 
languages):
Running Maven 2.0.4 (bin), with maven-project-info-reports-plugin-2.0.1.jar and 
maven-site-plugin-2.0-beta-5.jar.

- Default Eclipse-IDE/OS Encoding is UTF-8.
- Edited the _de.properties according to Michaels instructions (this is the 
ugly part since it will break the umlauts whenever a new version of the plugin 
is propagated) and repacked (ISO-8859-1 encoded Prop-Files) the jars in the 
local repository.
- Plugin-Configuration (pom.xml):
      ...
       <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-site-plugin</artifactId>
        <configuration>
          <locales>de</locales>
          <outputEncoding>UTF-8</outputEncoding>
        </configuration>
       ...
- set MAVEN_OPTS=-Dfile.encoding=UTF-8
- pom.xml, site.xml are UTF-8 encoded.
- *.apt-Files are ISO-8859-1 encoded.
- faq.fml (UTF-8 or ISO-8859-1 does not matter)

Results:
Navigation (site.xml): ok, Copyright and team-list (pom.xml): ok, Content 
(*.apt): ok, FAQ (*.fml): broken umlauts. Thus I get 3 from 4 :-).

The FAQ Umlauts are broken with either encoding. My workaround is to use ASCII 
in *.fml-Documents. :-/
The "FAQ-Umlauts" does not bother me that much, but if someone has an 
explanation/fix for this it will be greatly appreciated.

regards,
Marian




> Various encoding problems with InputStream and XML
> --------------------------------------------------
>
>                 Key: MSITE-19
>                 URL: http://jira.codehaus.org/browse/MSITE-19
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>            Reporter: Naoki Nose
>             Fix For: 2.0
>
>         Attachments: plexus-i18n.diff, plexus-site-renderer.diff, 
> plexus-utils.diff, plexus-utils_2.diff, project-info-report_ja.properties, 
> project-info-report_zh_CN.properties, project-info-report_zh_CN.properties, 
> site-plugin_ja.properties, site-plugin_zh_CN.properties
>
>
> There is various encoding problems with InputStream and XML in different 
> components.
> - Property resource file is encoded with UTF-8 , but Java reads bundle with 
> UTF-8.
> - In different components Reader is constructed with default system encoding.
> - MXParser ignores encoding attribute in xml declaration.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to