[Bug 1108] New: jnlp files encoded in not-utf8 encoding with special characters are not loaded

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1108

          Priority: P3
            Bug ID: 1108
                CC: unassigned at icedtea.classpath.org
          Assignee: omajid at redhat.com
           Summary: jnlp files encoded in not-utf8 encoding with special
                    characters are not loaded
          Severity: minor
    Classification: Unclassified
                OS: All
          Reporter: jvanek at redhat.com
          Hardware: all
            Status: NEW
           Version: unspecified
         Component: NetX (javaws)
           Product: IcedTea-Web

When jnlp file is encoded in different then utf8 encoding, and special
characters are included (and used for loading of application) then application
will not start, but this can get worse on platforms with different default
encoding from utf8.

The cause is that all Readers in Netx are using default platform encoding
(means non-specified encoding:). Although some encoding detection is included,
it is not working very fine. This will probably be solved when "Get rid of the
custom parser in PluginAppletViewer and use a proper generic SGML/HTML parser"
goal will be accomplished.


As only minor number of jnlps is using special characters for resources, then
this is minor issue, however with bad luck also characters in description/title
(localised!) can cause troubles.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20120808/154bca2a/attachment.html