JIRA-Browser: Invalid encoding name "Cp1252"

Error message: Original exception:
org.xml.sax.SAXParseException: Invalid encoding name "Cp1252".

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at org.jdom.input.SAXBuilder.build(SAXBuilder.java:370)

at org.jdom.input.SAXBuilder.build(SAXBuilder.java:694)

at
com.talios.jira.feeds.AbstractFeedBuilder.buildFeed(AbstractFeedBuilder.java:52)

at
com.talios.jira.feeds.AbstractFeedBuilder.buildFeedData(AbstractFeedBuilder.java:65)

at
com.talios.jira.browser.JiraIssuesTableModel$2.run(JiraIssuesTableModel.java:53)

5 comments

On Thu, 05 Feb 2004 18:06:36 +0100, Thomas Singer wrote:

Error message: Original exception:
org.xml.sax.SAXParseException: Invalid encoding name "Cp1252".


Hi Thomas,

What version of Jira are you using? 2.5.3 which I'm currently using sends
out RSS in UTF-8 ( atlassians install, my personal install, and works
install all does UTF-8 ).

Mark

0

I'm using 2.3#53, the latest version that runs for us. But in order to
handle German umlauts we needed to switch JIRA's encoding to Cp1252.

Tom

0

On Fri, 06 Feb 2004 09:56:19 +0100, Thomas Singer wrote:

I'm using 2.3#53, the latest version that runs for us. But in order to
handle German umlauts we needed to switch JIRA's encoding to Cp1252.


Ah ok, I've noticed Jira doesn't encode alot of things properly in the XML
file it sends out, which is causing alot of issues when I validate the XML
( entity refs used without being declared etc. etc. ).

I'm about to enter issues in for the main Jira product for these, and link
them all back to the issues i've created against the plugin, I think maybe
for now if I disable validation (ik) things should work.

0

On Fri, 06 Feb 2004 09:56:19 +0100, Thomas Singer wrote:

I'm using 2.3#53, the latest version that runs for us. But in order to
handle German umlauts we needed to switch JIRA's encoding to Cp1252.


Hmm, I entered this issue in my jira and someone just commented:

http://jira.atlassian.com/secure/ViewIssue.jspa?key=INTPLUG-35&page=comments#action_19333

Author: Matt BishopDate: Mon, 9 Feb 2004 5:39 PM
Comment:This encoding is not a standard XML encoding value, but rather the
Windows US encoding. Change it to UTF-8 in your XML editor and resave.

Mmmm

0

Change it to UTF-8 in your XML editor and resave.


No, I will not do it, because me and my coworkers want to be able to
read and write German umlauts correctly. BTW, I don't care, whether it
is a "standard" encoding. It is an encoding supported by Java (and
SAX), only dumb xerces seems to not understand it.

Tom

PS: This answer does not point to you directly, Mark.

0

Please sign in to leave a comment.