Issue 56609 - Paths not parsed properly
Summary: Paths not parsed properly
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.4
Hardware: Mac Mac OS X, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-10-25 12:12 UTC by kaimikael
Modified: 2013-08-07 14:38 UTC (History)
1 user (show)

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

File with an image link that demonstrates the problem. (14.11 KB, application/vnd.sun.xml.writer)
2005-10-25 12:15 UTC, kaimikael
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description kaimikael 2005-10-25 12:12:27 UTC
Image links that look like xlink:href="#Pictures/./picture.png". cause read errors and a broken image. 

RFC 1808 (section 3.4) specifies that "./" is valid syntax and is to be removed by the parser.
Comment 1 kaimikael 2005-10-25 12:15:55 UTC
Created attachment 30817 [details]
File with an image link that demonstrates the problem.
Comment 2 michael.ruess 2005-10-25 12:39:19 UTC
Reassigned to ES.
Comment 3 eric.savary 2005-10-25 13:06:42 UTC
I don't understand your link.
1) "#" is reserved to point to a bookmark. So there can't be "directories" under
a bookmark.
2) "./" means "current directory", so why do you need to have "blabla/./blabla".
It doesn't appear to be a valide URl
3) you attach a document whitout any graphic attached and you don't prcize where
this graphic should be placed in the file system.

Comment 4 kaimikael 2005-10-25 13:20:40 UTC
The image file is actually included in the sxw file itself.  If you take the file test4.sxw and unzip it, it will 
expand into the following directories and files:   
META-INF/, META-INF/manifest.xml, Pictures/, Pictures/pics/, Pictures/pics/Tip.png, content.xml, 
meta.xml, settings.xml, styles.xml              

If you then go into the content.xml file and locate the xlink:href, it contains a "./".  You can delete that, 
save the file, rezip the kit and then read the sxw file into OOo, whereupon the image magically will turn 

The reason there is a "./" to begin with is because it is automatically generated by other software and 
since it is a syntactically valid path, I think the onus is on OOo to adjust its behaviour.
Comment 5 eric.savary 2005-10-26 03:56:11 UTC
ES->MBA: what do you think about this?
Comment 6 Mathias_Bauer 2005-10-26 08:50:33 UTC
I think it's more something for Michael.
Comment 7 kaimikael 2006-05-15 19:58:59 UTC
I just downloaded OOo 2.0 and the behaviour of this bug has worsened - OOo will now crash outright 
when running into a link such as this.  (Platform still Mac OS X.)
Comment 8 Mathias_Bauer 2006-05-16 17:12:08 UTC
Michael please give a comment about this problem. Though the target is "OOo
Later" I think we should raise it in case the crash is caused by a bug in OOo.