Issue 27029 - XML import doesn't recognize ISO 8859-15 encoding
Summary: XML import doesn't recognize ISO 8859-15 encoding
Status: CONFIRMED
Alias: None
Product: xml
Classification: Code
Component: code (show other issues)
Version: OOo 1.1.1RC
Hardware: All All
: P4 Trivial with 1 vote (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-28 12:05 UTC by jvromans
Modified: 2013-02-07 22:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Demo document, as requested. (7.41 KB, application/vnd.sun.xml.writer)
2004-03-30 07:36 UTC, jvromans 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description jvromans 2004-03-28 12:05:15 UTC 
While developing a OOo document generator for one of my software products, I
noticed that OOo does not recognise ISO-8859-15 encoding for the XML files (in
particular, content.xml) that constitute the OOo documents.
OOo generates UTF-8 itself, but accepts ISO-8859-1 as well.
Is ISO-8859-15 deliberately left out, or just an oversight?
Comment 1 jogi 2004-03-29 05:01:50 UTC 
JSI->MIB: Do we support it or not?
Comment 2 michael.brauer 2004-03-30 05:21:30 UTC 
iso8869-15 should work. Can yopu please add an attachment containg a iso8859-15
encoded document that does not work.
Comment 3 jvromans 2004-03-30 07:36:57 UTC 
Created attachment 14170 [details]
Demo document, as requested.
Comment 4 jvromans 2004-04-07 17:24:53 UTC 
Please re-assign to mib.
Comment 5 thorsten.ziehm 2004-11-10 15:38:07 UTC 
reassign to MIB
Comment 6 michael.brauer 2004-11-11 08:36:43 UTC 
I don't know why the ISO 8859-15 encoding does not work. Anyway, I suggest to
set the priority of this issue to 4 and the target to "Office Later" for two
reasons:
1. ISO-8859-15 isn't an enoding that has to be supported by XML parsers
2. There is simple workaround: Rather than inserting the character code directly
one could inseret a character entity.
Comment 7 lo 2007-03-06 17:15:54 UTC 
I am not sure why I own this issue. Are we going to do anything about it? I
guess this could be set to wontfix and be closed. Michael, any opinions?
Comment 8 jvromans 2008-07-16 12:36:13 UTC 
Since ODF is ISO standard, I think full XML conformance is a mandatory requirement.
Comment 9 michael.brauer 2008-07-16 13:51:36 UTC 
Full conformance to what specification? XML requires support to UTF-8 and
UTF-16, and ODF does not add any additional requirements. So, there is no
requirement to support ISO-8859-15.
Comment 10 jvromans 2008-07-18 10:41:34 UTC 
If you're not going to support other encodings than UTF-8 and UTF-16, a slightly
more friendly error message would be appreciated.
You may close this bug as far as I'm concerned.