Bug 135193 - FILEOPEN DOCX SAXException: [word/footnotes.xml line 2]: Namespace prefix r for id on hyperlink is not defined for file written by 3.5.0.3
Summary: FILEOPEN DOCX SAXException: [word/footnotes.xml line 2]: Namespace prefix r f...
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-27 12:07 UTC by Telesto
Modified: 2020-07-27 12:32 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
ODT source file (101.63 KB, application/vnd.oasis.opendocument.text)
2020-07-27 12:07 UTC, Telesto 		Details
DOCX created with 3.5.0.3 (36.12 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-07-27 12:09 UTC, Telesto 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-07-27 12:07:32 UTC 
Description:
FILEOPEN DOCX SAXException: [word/footnotes.xml line 2]: Namespace prefix r for id on hyperlink is not defined

Steps to Reproduce:
1. open the attached file
2. Save with 3.5.0.3 to docx
3. open with 7.1

Actual Results:
SAXException

Expected Results:
No clue, it's more FYI


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: <buildversion>
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2020-07-27 12:07:56 UTC 
Created attachment 163620 [details]
ODT source file
Comment 2 Telesto 2020-07-27 12:09:20 UTC 
Created attachment 163621 [details]
DOCX created with 3.5.0.3
Comment 3 Telesto 2020-07-27 12:13:36 UTC 
@Mike
Is this worth having .. else please close again..

It's in DOCX export of 3.3.0 - 3.5.0.3. Surely fixed in 3.5.7.2
Comment 4 Mike Kaganski 2020-07-27 12:32:26 UTC 
Opening a corrupt document should show the error. Any bug about SAXException must seek to either fix *generation* of corrupt document (normally), or try to fix *wrong* error - if our import code would ever happen to treat a valid XML as corrupt (never seen yet). No use to file bugs like "when I use some ancient version, it generates a bad file (and doesn't in current versions) - let's do something with those bad files".