Created attachment 108195 [details] LibreOffice view of Figure 4.2.1-1 on Page 16 of 3GPP TS 23.401 V10.4.0 In this 3GPP document (3GPP TS 23.401 V10.4.0), Figures 4.2.1-1 and 4.2.1-2 on page 16 of the document show the text labels but are missing the boxes, ovals, and connecting lines. Official Microsoft Word version: http://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-a40.zip An unofficial PDF version: http://www.qtc.jp/3GPP/Specs/23401-a40.pdf I am attaching screenshots to illustrate the difference in the displays between LibreOffice and the PDF viewer (Mozilla Firefox). The 3rd Generation Partnership Project (3GPP) controls the standards around some mobile phone protocols. 3GPP documents are available as Microsoft Word documents. These documents are important to all implementors and testers of nodes within a mobile network (mobile phones, radio transceivers, switching network, packet core, etc). It is important that the fidelity of the documents is preserved when viewing them. LibreOffice does fairly well with the text of 3GPP documents. There are known problems with the cover page (bug 55946). However, many of the drawings/images are not handled so well.
Created attachment 108196 [details] PDF view of Figure 4.2.1-1 on Page 16 of 3GPP TS 23.401 V10.4.0
In addition to the network diagram issues, there are also problems with the message sequence charts. The lines and arrow heads critical to understanding the charts are missing. In this same 3GPP document (3GPP TS 23.401 V10.4.0), Figures 4.3.20.2-1 and 4.3.20.2-2 on Page 49 illustrate the issue.
Created attachment 108197 [details] LibreOffice view of Figure 4.3.20-1 on Page 49 of 3GPP TS 23.401 V10.4.0
Created attachment 108198 [details] PDF view of Figure 4.3.20-1 on Page 49 of 3GPP TS 23.401 V10.4.0
bug confirmed under Win7x64 using LibO 4.3.2.2 and 4.4.0.0.alpha1+ Build ID: 6ba8b7f5eacac969e4781d63718083a05491b1bc TinderBox: Win-x86@42, Branch:master, Time: 2014-10-24_02:23:51
** 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.4 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 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-12-20
As per request, this bug is still present in LibreOffice Version: 5.0.4.2 on Fedora 23. LibreOffice Build ID: 5.0.4.2-3.fc23. See attached new PNG images, which look much like the previous images.
Created attachment 121965 [details] LibreOffice-5.0.4.2 view of Figure 4.2.1-1
Created attachment 121966 [details] LibreOffice-5.0.4.2 view of Figure 4.3.20
** 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.2.5 or 5.3.0 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-20170306
Dear Morgan Garcia, 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
(In reply to QA Administrators from comment #11) Hi all, I tested with Libre office writer 6.3.3-1 , and confirmed this bug is fixed !