Problem description: A relative link in the pdf produced by writer has the form file:///directory path/./filename which was not recognized by most readers Before versions had the form fille:///directory path/filename. Operating System: Windows 7 Version: 4.0.0.2 rc Last worked in: 3.6.4.3 release
"." path segments are perfectly valid in relative URIs according to the relevant IETF RFC (though i don't know what "URI" means in the PDF format). see RFC3986 section "5.2.4. Remove Dot Segments". which PDF consumers have problems with URIs containing "." path segments? however when trying this out on Linux i can't reproduce any difference between 4.0.0.2 and 3.6.4.3; please provide more detail how to reproduce such URIs, e.g. where exactly do the document and the link target need to be relative to each other.
>which PDF consumers have problems with URIs containing "." path segments? We are using Foxit Reader under windows and it could be a bug of the reader. >however when trying this out on Linux i can't reproduce any difference >between 4.0.0.2 and 3.6.4.3; please provide more detail how >to reproduce such URIs, e.g. where exactly do the document >and the link target need to be relative to each other. I reported a bug because we never had this problem with 3.6.4 under windows. This problem was introduced with version 4. Typical use is developping documentation on a drive and using it on an other. The LibreOffice links of type "file:///..." are not recognised by a lot of free pdf-reader under Windows. Foxit was an exception, until version 4.
dany, your comment does not contain a better description how to reproduce the problem. can you perhaps attach an ODF file, which will, when exported to PDF, contain such problematic URIs?
Created attachment 74165 [details] The link is in the first line This is a file with a relative link
Test document provided, so changing status: NEEDINFO -> UNCONFIRMED
Changing 'regression' -> 'PossibleRegression' until we can get independent confirmation of a regression.
Which link? The navigator doesn't say that there is a link in that odt, nor can I find any link in the exported (x)html nor in the exported PDF.
Yes, the link was suppressed by saving the document. Probably because the file was not found (tested with 4.0.5). For me, a relative link has the form: ./essai.pdf Such a link helps in moving a batch of files globally without having to change the links. It seems all the links that LO can produce are absolute links: file:///drive/repertory/file. Thanks for trying to help, but I think there are other and more problematic bugs waiting for your expertise, so I propose to close the bug.
Back to NEEDINFO - we need a functional document attached. Once attached mark as UNCONFIRMED. Thanks
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Message generated on: 10/01/2015
(In reply to Joel Madero from comment #9) > Back to NEEDINFO - we need a functional document attached. Once attached > mark as UNCONFIRMED. Thanks Yes, but: (In reply to dany franck from comment #8) > ... > Thanks for trying to help, but I think there are other and more problematic > bugs waiting for your expertise, so I propose to close the bug. That's fine. We have a number of open bugs that we're punting on anyhow, but without a demo document we can't repro, so: Status -> RESOLVED WORKSFORME (If anyone wants to provide a demo document showing the problem, we can open this bug again)
Migrating Whiteboard tags to Keywords: (possibleRegression) [NinjaEdit]