Issue 65602 - Writer/Web should at least tolerate, better process <?xml > processing directive
Summary: Writer/Web should at least tolerate, better process <?xml > processing directive
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: jogi
QA Contact: issues@sw
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2006-05-19 21:45 UTC by superbiskit
Modified: 2006-08-14 11:00 UTC (History)
1 user (show)

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

Attachments
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 superbiskit 2006-05-19 21:45:46 UTC 
Especially because we are using xml internally, it seems absurd that openning an
XHTML document into writer/web causes the <?xml ...> processing directive to
appear as rendered text.  We must already have a full gamut of xml-parsing
routines and could easily parse all of it correctly.
Comment 1 michael.ruess 2006-05-22 08:46:13 UTC 
Reassigned to ES.
Comment 2 eric.savary 2006-05-22 08:51:17 UTC 
ES->JSI: Please have a look.
Comment 3 jogi 2006-05-26 09:01:46 UTC 
XHTML never will be opened into Writer/WEB. Writer/WEB only opens HTML pages
(3.2+++). Reporter: What you are doiung? Loading XML? Which XSLT do you then
use? Without bug document it is hard to reproduce.
Comment 4 jogi 2006-06-27 09:20:35 UTC 
If the external XSLT filters are not installed XHTML- files will be loaded as
text files. If the DTD statement is correct the transformation will put it into
a normal document.
No issue.
Comment 5 jogi 2006-08-14 11:00:07 UTC 
closing