Summary: | Don't strip out "." from hyperlink file://./subdirectory/file.xyz when exporting to SVG | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | UbunLibOffImp <duder_temp> |
Component: | Impress | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | CC: | ilmari.lauhakangas, sberg.fun |
Priority: | medium | ||
Version: | 5.1.0.3 release | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 107733 | ||
Attachments: | Confirmed that in 6.0.1.1 LO makes a mess of hyperlinks when a *.ODP is exported to *.SVG. |
Description
UbunLibOffImp
2018-01-26 02:46:52 UTC
The issue a] is reported as bug 103454. Before I continue, could you please test the other bugs with 6.0? An easy way on Linux is appimage: https://www.libreoffice.org/download/appimage Created attachment 140168 [details]
Confirmed that in 6.0.1.1 LO makes a mess of hyperlinks when a *.ODP is exported to *.SVG.
See attached *.ODP created using AppImage Fresh 6.0.1.1
I could not reproduce b]. I do reproduce c], so let's change summary. Perhaps b] is specific to Ubuntu. Anyway, each issue should have its own report, so do open a new one for it. Same for this, using Documentation as the component: "Note: LibreOffice Documentation is not accurate. There are two checkboxes that are not referenced in the Help citation. The Help files do not address the reality of the UI." Arch Linux 64-bit Version: 6.0.1.1 Build ID: 6.0.1-1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: 0b49701fa5c22abba6b9b4a60ddd2720973dd858 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on February 27th 2018 ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug Dear UbunLibOffImp, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug Dear UbunLibOffImp, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug (In reply to UbunLibOffImp from comment #0) > c] Impress should never strip out "." character when used as the first > character in a relative link in a *.odp that is exported to type *.svg > (example [c] = Insert > Link type > DOCUMENT > DOCUMENT PATH: > "file://./subdirectory/file.xyz") > (result [c] = when the *.svg is opened in above listed web browser, > hyperlink becomes "file:///subdirectory/file.svg" and is dead since it is > not resolved correctly) (<file://./subdirectory/file.xyz> is not a relative URL. It is an absolute file URL whose authority component is a host denoting the registered name "."; whatever that is supposed to mean semantically.) I cannot reproduce this claim of LO stripping out ".": The resulting svg file contains the exact text "file://./subdirectory/file.xyz" eight times. It does not contain "subdirectory" in any other place (i.e., it does not also contain the text "file:///subdirectory/file.xyz" or something similar), which could indicate that LO does garble the specified <file://./subdirectory/file.xyz> URL when exporting to svg. (When I open that svg file in Firefox, following the link makes it indeed try to open <file:///subdirectory/file.xyz>, dropping the "." host. But that appears to be an issue of Firefox. In its inspector window, one still sees > <a xlink:href="file://./subdirectory/file.xyz">file://./subdirectory/file.x</a> as the source of the link.) |