Created attachment 84867 [details] RTF document with formatting issues Although the RTF import is getting better, the attached document still has several problems: - The "Jellyfish Shark Limited" heading at the top of all pages is not centered - A number of table cell entries are not aligned on the decimal tabs, e.g. on page 6, in the row containing "Total assets less current liabilities" the 2012 and 2011 accounts are not aligned on the decimal tab (the tab seems to be missing completely) and in the row above the same is true for *only* the 2011 amount. The same thing happens to both amounts in the "Administration" row on page 10, while all other amounts in that table *are* correct.
Thank you for your bug report, I can reproduce this bug running LibreOffice. Version: 4.1.1.2 Build ID: 7e4286b58adc75a14f6d83f53a03b6c11fa2903 on Mac osx 10.8.4.
> - The "Jellyfish Shark Limited" heading at the top of all pages is not centered Reproducible with LibreOffice 4.2.5 and 4.3.0 on Debian. > - A number of table cell entries are not aligned on the decimal tabs, e.g. on > page 6, in the row containing "Total assets less current liabilities" the 2012 > and 2011 accounts are not aligned on the decimal tab (the tab seems to be > missing completely) and in the row above the same is true for *only* the 2011 > amount. The same thing happens to both amounts in the "Administration" row on > page 10, while all other amounts in that table *are* correct. I can not reproduce. These lines seems to be aligned on the decimal tabs. Some other lines are not. Unfortunately, in MS Word Viewer more lines are not aligned on the decimal tabs. Is LibreOffice representation correct now? If not, could you provide a reference representation? Maybe comparative screenshot?
Square brakets appear on page 10 in the text ducument in LibreOffice 4.3.0.3. I report it as bug 81502.
Current (4.3.0.4) issues: 1) Square brackets appear in lots of places 2) Page headings are not centred 3) Formulas in tables still don't work
> 1) Square brackets appear in lots of places Michael Stahl has already fixed the issue with brackets (bug 81502). The patch will be available in LibreOffice 4.3.1 and 4.4.0.
** 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
Decimal tabs are still wrong! Version: 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: en-GB (en_GB) W7-64, fully patched.
Migrating Whiteboard tags to Keywords: (filter:rtf)
Decimal tabs look ok in Version: 5.3.0.0.alpha0+ Build ID: ae3ec79354f7b4967e736c6a4cd7c08fc52e2b7d CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; Locale: ca-ES (ca_ES.UTF-8); Calc: group thus, closing this as RESOLVED WORKSFORME
Problems with decimal tabs and formulae still occur with Version: 6.2.3.2 (x64) Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac CPU threads: 8; OS: Windows 6.1; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-US Calc: threaded
Created attachment 151448 [details] comparison MSO 2010 and LibreOffice 6.3 Master
(In reply to robert from comment #10) > Problems with decimal tabs and formulae still occur with > > Version: 6.2.3.2 (x64) > Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac > CPU threads: 8; OS: Windows 6.1; UI render: default; VCL: win; > Locale: en-GB (en_GB); UI-Language: en-US > Calc: threaded See attached image. I don't see any difference between LibreOffice and MSO 2010. Please, add a screenshot of the problem you have with decimal tabs...
Created attachment 151541 [details] Every amount with a comma is aligned wrongly! Every amount containing a comma is aligned wrongly!
Dear Robert, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping
On 2019-05-20T22:01 a side-by-side screenprint of the same document opened in Word and LO wasattached. It VERY CLEARLY SHOWS THE PROBLEM. And for what it's worth, formula's in tables still do not work either! Version: 6.3.3.2 (x64) Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU threads: 8; OS: Windows 6.1; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-US Calc: threaded
Robert, I can see difference in attachment from comment 13, but when I open the document from bug description in MS Word 2013, it looks the same as in LO 6.4.0.0.beta 1. What version of MS Word do you use?
Word 2002 (10.2627.2625), the freebie that came with my PC.
(In reply to robert from comment #17) > Word 2002 (10.2627.2625), the freebie that came with my PC. See results from LO an d Word 2016 in the following attachments. Do you see any difference? If not, can we close this bug?
Created attachment 155907 [details] Result form MS Word 2016
Created attachment 155908 [details] Result from LO 6.4.0.0
There are no differences, and that means both Word and LO fail to properly process the decimal tabs, and this means that BOTH are buggy. Look at the flipping pages, the amounts are not, not, not properly aligned, and I don't really give a flying whatever that LO displays them the same way as some M$ product that isn't even compatible with itself, amounts that should be aligned on decimal tabs should be aligned on decimal tabs! THIS IS A BUG, SO DO NOT CLOSE THIS REPORT!
I don't think, that it is a problem of decimal tabs, because it I replace comma with a dot, the numbers are in line. you can save it as rtf and reopen and it still looks fine. I think this is independent from localization (tested with German and UK Localization). I've tried with number recognition enabled and different setting in Table => Number Format but wasn't successful. Version: 7.0.0.0.alpha1+ (x64) Build ID: 99c337d1d3831ce9d2c7dc1cbff713f4ac49d6ac CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI: en-GB Calc: CL So I change status to new but change also bug summary, bacause Word shows the same wrong result.
(In reply to Dieter from comment #22) > I don't think, that it is a problem of decimal tabs, because it I replace > comma with a dot, the numbers are in line. you can save it as rtf and reopen > and it still looks fine. I think this is independent from localization > (tested with German and UK Localization). That is exactly the problem. The UK uses a 9,999.99 format, Germany uses 9.999,99 format, and from the whole thread it should be obvious that something somewhere mixes up the locales vs decimal tabs!
(In reply to robert from comment #23) > That is exactly the problem. The UK uses a 9,999.99 format, Germany uses > 9.999,99 format, and from the whole thread it should be obvious that > something somewhere mixes up the locales vs decimal tabs! Do you know, if it works outside tables (I haven't tested).
Same results outside tables, which doesn't surprise me as the issue has nothing to do with tables. See the attached six files, a RTF, two ODTs and three PNGs of the screen. Pasted the LO data to the ODT, and displayed the setting dialog. FWIW, in "one.6.4.3.2.odt" "content.xml" the styles contain <style:style style:name="P1" style:family="paragraph" style:parent-style-name="Standard"> <style:paragraph-properties> <style:tab-stops> <style:tab-stop style:position="4.001cm" style:type="char" style:char=","/> </style:tab-stops> </style:paragraph-properties> </style:style> Manually unzipping the ODT and replacing the "," with a "." still screws up the output - see the "one(dot).6.4.3.2.odt/png"
Created attachment 160899 [details] Word 2002 with decimal tabs
Created attachment 160900 [details] Word 2002 with decimal tabs - screenprint
Created attachment 160901 [details] Saved one.word2002.rtf to .odt
Created attachment 160902 [details] Saved one.word2002.rtf to .odt - screenprint
Created attachment 160903 [details] Saved one.word2002.rtf to .odt manual change of style
Created attachment 160904 [details] Saved one.word2002.rtf to .odt manual change of style - screenprint
Still reproducible in Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 8043fe3e45c8999c8eaf475ba46d50b125e38b93 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear Robert, 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
Bug seems to have been replace by something far worse! Alignment is OK, but clicking on any, like for example the "0" in the "Turnover" row, of the 12 grey-background amounts on the fifth page of the document sets all amounts to 0, which is bad, bad, bad! And there is no UNDO, which is even worse! Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: CL threaded
This bug has now been going on for over TEN years? WTEE is going on?