jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 1.x XDoc Plugin
  • MPXDOC-11

Unicode entities from projext.xml are not shown in generated site in HTML or even in XML

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: 1.9.2
  • Labels:
    None
  • Environment:
    JDK 1.4.2, Linux 2.4.17, Debian Unstable

Description

Unicode entities from projext.xml are not shown in generated site in HTML or even in XML.
For example if there is a developer "name with letter ś",
in project.xml then in generated xml i html his named
"name with letter ?".

project.xml encoding does not matter here.

Setting any encoding e.g. ISO-8859-2, does not work either.

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    MPXDOC-11.patch
    03/Sep/05 6:36 PM
    0.7 kB
    Lukas Theussl

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MAVEN-847 Umlauts in project.xml become garbage in generated site

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MAVEN-382 POM encoding problem

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Norbert Pabis added a comment - 31/Jul/03 2:30 AM

After further investigation I found that it does not work
only in iso-8859-1 and utf-8 output encoding.

Show
Norbert Pabis added a comment - 31/Jul/03 2:30 AM After further investigation I found that it does not work only in iso-8859-1 and utf-8 output encoding.
Hide
Permalink
Norbert Pabis added a comment - 27/Sep/03 5:54 AM

I have resolved problem with entities.
When reading files SAX parser expands entities. Reading entities is not a problem. The problem is writing.
Reading a file in any encoding results in all strings in Unicode which is Java's internal encoding.
When writing files in maven.docs.outputencoding all these strings have to be encoded and here problems appear.
For example a copyright entity from site.jsl in xdocs plugin in is read correctly and expanded into specific Unicode character.
If output encoding is ISO-8859-1 copyright character can be written correctly,
but if it is not latin1 then there is no such character, and instead of copyright mark, "?" is written.
To avoid this, output encoding should be set to UTF-8 that can represent any character.

The problem is persistent, unless you use UTF-8 as output encoding or have
SAX parsers skip entities expanding.

IMHO this issue could be explained in FAQ, and this bug can be resolved as invalid as soon as http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-382 is fixed.

Show
Norbert Pabis added a comment - 27/Sep/03 5:54 AM I have resolved problem with entities. When reading files SAX parser expands entities. Reading entities is not a problem. The problem is writing. Reading a file in any encoding results in all strings in Unicode which is Java's internal encoding. When writing files in maven.docs.outputencoding all these strings have to be encoded and here problems appear. For example a copyright entity from site.jsl in xdocs plugin in is read correctly and expanded into specific Unicode character. If output encoding is ISO-8859-1 copyright character can be written correctly, but if it is not latin1 then there is no such character, and instead of copyright mark, "?" is written. To avoid this, output encoding should be set to UTF-8 that can represent any character. The problem is persistent, unless you use UTF-8 as output encoding or have SAX parsers skip entities expanding. IMHO this issue could be explained in FAQ, and this bug can be resolved as invalid as soon as http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-382 is fixed.
Hide
Permalink
Lukas Theussl added a comment - 31/Aug/05 12:13 PM

Problem gets fixed by changing system encoding, eg on FC3: export LANG=en_US.UTF-8
We'll document that in a FAQ.

Show
Lukas Theussl added a comment - 31/Aug/05 12:13 PM Problem gets fixed by changing system encoding, eg on FC3: export LANG=en_US.UTF-8 We'll document that in a FAQ.
Hide
Permalink
Lukas Theussl added a comment - 03/Sep/05 6:36 PM

A patch for the faq.

Show
Lukas Theussl added a comment - 03/Sep/05 6:36 PM A patch for the faq.
Hide
Permalink
Lukas Theussl added a comment - 06/Sep/05 3:49 PM

FAQ updatet in xdoc 1.9.2

Show
Lukas Theussl added a comment - 06/Sep/05 3:49 PM FAQ updatet in xdoc 1.9.2

People

  • Assignee:
    Lukas Theussl
    Reporter:
    Norbert Pabis
Vote (1)
Watch (2)

Dates

  • Created:
    25/Jul/03 2:42 AM
    Updated:
    06/Sep/05 3:49 PM
    Resolved:
    31/Aug/05 12:14 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.