https://bz.apache.org/ooo/show_bug.cgi?id=117672
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Opening XLSX fails when the |Opening XLSX fails when the |Relationship "Target" |Relationship "Target" |attribute in _rels/.rels |attribute in _rels/.rels |has a leading slash |has superfluous slashes --- Comment #5 from [email protected] --- Testing against Excel and LO however shows they go even further than allowing one leading slash in the _rels/.rels Relationship "Target" attribute and the [Content Types].xml Override "PartName" attribute. <Relationship Target="///xl/workbook.xml" ...> <Override PartName="/xl/workbook.xml" ...> Excel and LO open successfully, no warnings. <Relationship Target="///xl///workbook.xml" ...> <Override PartName="/xl/workbook.xml" ...> Excel open successfully, no warnings. LO offers to repair the file. <Relationship Target="///xl///workbook.xml" ...> <Override PartName="//xl/workbook.xml" ...> Both Excel and LO offer to repair the file. So at least in Relationship "Target" we should allow multiple leading slashes, and multiple slashes anywhere else where one slash would be ok. The Override element's "PartName" attribute is apparently stricter and we can get away with doing less compatibility fixes there. -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue.
