Maven Doxia

AptParser ignores UTF-8 BOMs

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.2
  • Fix Version/s: None
  • Component/s: Module - Apt
  • Labels:
    None
  • Number of attachments :
    1

Description

If an input apt doc is in UTF-8 with a BOM, the BOM passes through as noise characters inside the HTML result.

Issue Links

relates to

Improvement - An improvement or enhancement to an existing feature or task. MSITE-130 Site generation fails for site.xml in UTF8 with BOM

  • Critical - Crashes, loss of data, severe memory leak.
  • 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
Hide
Permalink
Lukas Theussl added a comment -

How did you test this? If with the site plugin: did you set the input- and outputEncoding in the site plugin configuration? Can you provide a test case?

Show
Lukas Theussl added a comment - How did you test this? If with the site plugin: did you set the input- and outputEncoding in the site plugin configuration? Can you provide a test case?
Hide
Permalink
Benson Margulies added a comment -

I dropped an APT file into a Maven project and ran the site plugin. The site plugin config is:

 <plugin>
          <artifactId>maven-site-plugin</artifactId>
          <version>3.0</version>
          <configuration>
            <chmod>true</chmod>
            <dependencyDetailsEnabled>false</dependencyDetailsEnabled>
            <dependencyLocationsEnabled>false</dependencyLocationsEnabled>
          </configuration>
        </plugin>

I thought that project.build.sourceEncoding was UTF-8, but I just checked and I was wrong, it's not set. So I'll either make a test case or close this today after I add that and try again.

Show
Benson Margulies added a comment - I dropped an APT file into a Maven project and ran the site plugin. The site plugin config is: <plugin> <artifactId>maven-site-plugin</artifactId> <version>3.0</version> <configuration> <chmod> true </chmod> <dependencyDetailsEnabled> false </dependencyDetailsEnabled> <dependencyLocationsEnabled> false </dependencyLocationsEnabled> </configuration> </plugin> I thought that project.build.sourceEncoding was UTF-8, but I just checked and I was wrong, it's not set. So I'll either make a test case or close this today after I add that and try again.
Hide
Permalink
Benson Margulies added a comment - - edited

I made the test. There is a problem. if the first line of the file is:

<BOM>     --------

then the minus signs are not interpreted as format. I'll make a little project and paste it together for you later.

Show
Benson Margulies added a comment - - edited I made the test. There is a problem. if the first line of the file is: <BOM> -------- then the minus signs are not interpreted as format. I'll make a little project and paste it together for you later.
Hide
Permalink
Lukas Theussl added a comment -

Confirmed.

Show
Lukas Theussl added a comment - Confirmed.

People

  • Assignee:
    Unassigned
    Reporter:
    Benson Margulies
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: