Created attachment 98801 [details] odt file from LibO 4.2 I download the .docx file found at < http://download.microsoft.com/documents/uk/partner/publicsector/DraftMicrosoftResponsetoGovernment.docx >, opened it in LibO and then saved it as a .odt file. Then i opened the .odt file in ms word 2010 and on page 14, blue links have turned into black links. Tested on Linux Mint in the latest releases of 3.6 - 4.2, 4.2.5, and 4.3 alpha. Calligra Words shows black links like ms office.
Created attachment 98802 [details] links show in LibO 4.2, word 2010, and calligra
thanks for this new report. I have one questions for you: is this "link color change" issue happening just after .docx to .odt conversion in LibO or it's the same even on an .odt with link created from scratch in LibO? I think it's important to understand where the root of the problem is... as an additional info I can tell that Apache OpenOffice 4.1 correctly shows the blue links in the test .odt file so I'm wondering if this bug is really on LibO side or rather it's a problem of MS Word and Calligra failing to correctly render an .odt file.
Well the color change issue doesnt happen everywhere in the document, as the link on page 8 shows fine in blue in word and calligra, so i think it might be a style issue. Well as AOO and LibO originate from the same code base, using AOO to check ODF compatibility wouldnt be a suitable comparison when checking against 2 other completely different odf implementations. I brought up the same issue in the mailing list of where should i go to check if the ODF displayed by LibO is shown different in ms word. You can see Michael Meeks' and Inge Wallin's responses below. http://listarchives.documentliberation.org/www/discuss/msg00059.html http://listarchives.documentliberation.org/www/discuss/msg00063.html Presently, i only submit odf bugs when ms word and calligra show it one way and LibO shows it in a different way.
Reproducible, tested using Windows 8.1 with LibreOffice Version: 4.4.0.0.alpha0+ Build ID: eddd7646d672ea9b0561dacb09da224d098e531e TinderBox: Win-x86@39, Branch:master, Time: 2014-07-18_06:42:50 File opened using Word 2013. Kind regards, Joren
** 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 on a currently supported version of LibreOffice (5.0.0.5 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
So i checked WebODF and it shows it like LibreOffice, so i'll consider MSO and Calligra's rendering as incorrect. @Regina: please reopen if you disagree.