Maven 2.x Changes Plugin

page encoding ISO-8859-1 not definable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: 2.1
  • Fix Version/s: None
  • Component/s: changes.xml
  • Labels:
    None
  • Environment:
    Windows XP, Maven 2.09
  • Number of attachments :
    2

Description

Neither property <project.reporting.outputEncoding>ISO-8859-1</project.reporting.outputEncoding>
nor <maven.docs.outputencoding>ISO-8859-1</maven.docs.outputencoding> is accepted for report generation (changes:changes-report).

German characters like 'äöü' are misinterpreted.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Bentmann added a comment -

A demo poject would be nice. There are various components involved in site generation and from the few bits you gave it's hard to tell whether the problem is really the Changes Plugin, the Site Plugin or just a misconfiguration in your POM.

Show
Benjamin Bentmann added a comment - A demo poject would be nice. There are various components involved in site generation and from the few bits you gave it's hard to tell whether the problem is really the Changes Plugin, the Site Plugin or just a misconfiguration in your POM.
Hide
Permalink
Bruno Marti added a comment -

see entry in Release 1.0.0 comment. Characters should be 'äöü ÄÖÜ'

Show
Bruno Marti added a comment - see entry in Release 1.0.0 comment. Characters should be 'äöü ÄÖÜ'
Hide
Permalink
Bruno Marti added a comment -

a littler demo project to regenerate the bug.
useage:
mvn changes:changes-report

Show
Bruno Marti added a comment - a littler demo project to regenerate the bug. useage: mvn changes:changes-report
Hide
Permalink
Dennis Lundberg added a comment -

I can confirm this bug. We ran into it the other day.

Show
Dennis Lundberg added a comment - I can confirm this bug. We ran into it the other day.
Hide
Permalink
Dennis Lundberg added a comment -

The problem here is actually the charset speciied in the generated html file. It looks like this:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

This is a hint to the browser that the contents of this file is encoded in UTF-8, which it is not. If you manually change the view encoding in your browser to "ISO-8859-1" the characters are displayed correctly.

So you'd need to use a skin that specifies the same encoding that your changes.xml file uses.

Show
Dennis Lundberg added a comment - The problem here is actually the charset speciied in the generated html file. It looks like this: <meta http-equiv= "Content-Type" content= "text/html; charset=UTF-8" /> This is a hint to the browser that the contents of this file is encoded in UTF-8, which it is not. If you manually change the view encoding in your browser to "ISO-8859-1" the characters are displayed correctly. So you'd need to use a skin that specifies the same encoding that your changes.xml file uses.
Hide
Permalink
Bruno Marti added a comment -

I changed site.xml and changes.xml to
<?xml version="1.0" encoding="ISO-8859-1"?>

Problem has gone away.
This issue can be closed

Show
Bruno Marti added a comment - I changed site.xml and changes.xml to <?xml version="1.0" encoding="ISO-8859-1"?> Problem has gone away. This issue can be closed

People

  • Assignee:
    Unassigned
    Reporter:
    Bruno Marti
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: