[Libreoffice-bugs] [Bug 94982] FILEOPEN XML Contents of a FastReport .xml not shown entirely (see comment 12)
https://bugs.documentfoundation.org/show_bug.cgi?id=94982 --- Comment #18 from Kevin Suo --- Sorry, typo ...file created by FastReport v4.0.58 opens correctly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145548] Form Controls Do Nothing in Draw or Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=145548 MarjaE changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from MarjaE --- Now they're doing something. I can create fields, but I still can't create usable ones. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145509] [META] Bugs Related to Liborcus
https://bugs.documentfoundation.org/show_bug.cgi?id=145509 Bug 145509 depends on bug 94982, which changed state. Bug 94982 Summary: FILEOPEN XML Contents of a FastReport .xml not shown entirely (see comment 12) https://bugs.documentfoundation.org/show_bug.cgi?id=94982 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94982] FILEOPEN XML Contents of a FastReport .xml not shown entirely (see comment 12)
https://bugs.documentfoundation.org/show_bug.cgi?id=94982 Kevin Suo changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #17 from Kevin Suo --- >From Kohei's comment in the Orcus issue ticket, the reason is that the XML contained in the test file is invalid. Specifically, the character references such as are missing the closing ";" to complete the encoded character. Without that, this XML file is invalid. While we can try to be too strict in following the standars and to to fix this, it take time. It is mentioned that this file is was generated by FastReport v3.20 preview, and you also mentioned that FastReport v4.0.58 opens correctly, thus FastReport must had realized the issue and fixed that in their code base. For this reason I close this as NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143511] Writer: Comment oversized and text missing when printed in margin in Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=143511 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145263] File size randomly increases Dramatically
https://bugs.documentfoundation.org/show_bug.cgi?id=145263 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145262] UI: Context menu for table content with Index / Bibliography entry is missing commands
https://bugs.documentfoundation.org/show_bug.cgi?id=145262 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145261] Libreoffice Writer: Can't type anymore after changing paragraph style, font or font size [KDE PLASMA]
https://bugs.documentfoundation.org/show_bug.cgi?id=145261 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145259] Printing on 'DL' paper (110 x 220mm)
https://bugs.documentfoundation.org/show_bug.cgi?id=145259 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145254] Language Tool 5.4-5.5--options--hangs--unusable, Writer v 7.1.6.2--manjaro 21.1.6
https://bugs.documentfoundation.org/show_bug.cgi?id=145254 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145251] Hunspell produces non-valid compounding results (for Dutch)
https://bugs.documentfoundation.org/show_bug.cgi?id=145251 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 --- Comment #15 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141532] Blurry characters under macOs Big Sur 11.2.3
https://bugs.documentfoundation.org/show_bug.cgi?id=141532 --- Comment #3 from QA Administrators --- Dear Edouard, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141532] Blurry characters under macOs Big Sur 11.2.3
https://bugs.documentfoundation.org/show_bug.cgi?id=141532 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141523] Problemas con la interfaz graphica
https://bugs.documentfoundation.org/show_bug.cgi?id=141523 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141523] Problemas con la interfaz graphica
https://bugs.documentfoundation.org/show_bug.cgi?id=141523 --- Comment #3 from QA Administrators --- Dear Edgar Castillo, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141521] "Fill Series" increments months instead of days on cells which are formatted as date
https://bugs.documentfoundation.org/show_bug.cgi?id=141521 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141521] "Fill Series" increments months instead of days on cells which are formatted as date
https://bugs.documentfoundation.org/show_bug.cgi?id=141521 --- Comment #3 from QA Administrators --- Dear Bob, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141494] LibreOffice 7.1.2 Fonts blurred (again) on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=141494 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141494] LibreOffice 7.1.2 Fonts blurred (again) on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=141494 --- Comment #5 from QA Administrators --- Dear war, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142168] libreoffice crashed on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=142168 --- Comment #2 from QA Administrators --- Dear luigino, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59257] UI: built-in elements (icons, labels) of a navigation bar control (for a data table) do not resize when zooming
https://bugs.documentfoundation.org/show_bug.cgi?id=59257 --- Comment #15 from QA Administrators --- Dear Biofjöd, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128435] Data crushed in another sheet when using 'search in all sheets'
https://bugs.documentfoundation.org/show_bug.cgi?id=128435 --- Comment #3 from QA Administrators --- Dear themightyloki, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145550] New: LibreOffice download site is full of pain/animation
https://bugs.documentfoundation.org/show_bug.cgi?id=145550 Bug ID: 145550 Summary: LibreOffice download site is full of pain/animation Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: erw...@alumni.beloit.edu The LibreOffice download site is full of pain/animation, which can trigger migraines and nausea. Migraine warning for the link: https://www.libreoffice.org/ If you click on the link, it fires an animated carousel. If you get that out of the way, and mouse over the seartch area, that fires more animation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119010] Page area hatch doesn't work correctly in a Writer document with mirrored pages.
https://bugs.documentfoundation.org/show_bug.cgi?id=119010 --- Comment #8 from QA Administrators --- Dear Robin Henderson, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112921] fancy quotation marks hide text and change font thereafter
https://bugs.documentfoundation.org/show_bug.cgi?id=112921 --- Comment #6 from QA Administrators --- Dear Terrence Enger, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38263] Zooming presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=38263 --- Comment #22 from MarjaE --- If people have post-concussion syndrome, among other issues, zooming can cause migraines, nausea, etc. Adding zooming to presentations may make them inaccessible, and may make audience members sick. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file (because of multiple trailers which is valid per PDF specification)
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 --- Comment #16 from Kevin Suo --- The cause may be, that the PDF file has two trailers while the first trailer is not terminated by a %%EOF, thus there is only one endTrailer called in "PDFGrammar", which means one m_aObjectStack is not pop_back(), which finally resulted in 2 m_aObjectStack. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file (because of multiple trailers which is valid per PDF specification)
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 Kevin Suo changed: What|Removed |Added Keywords||filter:pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file (because of multiple trailers which is valid per PDF specification)
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 Kevin Suo changed: What|Removed |Added Summary|General input/output error |General input/output error |loading pdf file|loading pdf file (because ||of multiple trailers which ||is valid per PDF ||specification) Keywords||implementationError -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 --- Comment #15 from Kevin Suo --- Below is the portion related to trailer in this pdf: endstream endobj xref 0 4644 04 65535 f 056752 0 n 004642 65535 f trailer <> xref 0 0 trailer <<64F67A6686A94D0B8F325336D36A35E8>]>> startxref 5043836 %%EOF So yes, there are two trailers in this pdf. The first xref and the first trailer should have been added before the file was once "incrementally updated". The 2nd one (i.e. the last one) is the one which should be used for pdf parsing. I note that there is a problem here - the first trailer is not terminated by its own end-of-file ( %%EOF ) marker, see citation below. --- Citing the Adobe PDF Reference (third edition): 3.4.5 Incremental Updates In an incremental update, any new or changed objects are appended to the file, a cross-reference section is added, and a new trailer is inserted. ... The cross-reference section added when a file is updated contains entries only for objects that have been changed, replaced, or deleted, plus the entry for object 0. Deleted objects are left unchanged in the file, but are marked as deleted via their cross-reference entries. The added trailer contains all the entries (perhaps modified) from the previous trailer, as well as a Prev entry giving the location of the previous cross-reference section (see Table 3.12 on page 68). As shown in Figure 3.3, a file that has been updated several times contains several trailers; note that each trailer is terminated by its own end-of-file ( %%EOF ) marker. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145549] New: Page Styles not saved with Calc document
https://bugs.documentfoundation.org/show_bug.cgi?id=145549 Bug ID: 145549 Summary: Page Styles not saved with Calc document Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kari.massar...@gmail.com Description: After upgrading to LibreOffice 7.2.2.2 (x64)/LibreOffice Community version on Windows 10 the Format-->Page Style dialog's Header on checkbox becomes unchecked after FILESAVE and subsequent FILEOPEN. This results in the worksheet name not being displayed on paper when the worksheet is printed unless the user checks the "Header on" box before PRINTING. This behavior has not been observed in previous versions of Calc. Steps to Reproduce: 1. Create a Calc worksheet. 2. Check "header on" checkbox under "Format->Page Style" dialog 3. Print the worksheet 4. Observe the worksheet's name at the top of the printed page 5. Save the document 6. Close the document 7. Open the document 8. Print the worksheet 9. Observe that the worksheet name is not printed on the paper page 10. Observe "header on" checkbox under "Format->Page Style" dialog is now unchecked Actual Results: In the above step 9, observe that the worksheet name is not printed on the paper page Expected Results: In the above step 9, the worksheet name should be printed at the top of the paper page. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 --- Comment #14 from Kevin Suo --- sdext/source/pdfimport/pdfiadaptor.cxx PDFIRawAdaptor::importer (in line 291): calls /source/pdfimport/pdfiadaptor.cxx PDFIRawAdaptor::parse (in line 217) which calls (in line 231): sdext/source/pdfimport/wrappter/wrapper.cxx xpdf_ImportFromStream (in line 1182) xpdf_ImportFromStream copied the pdf content to a temp file because the caller has passed in a file stream thus xInput.is() is true. I don't think it is necessary to make such temp file - why not pass the url of the original PDF file and then use the xpdf_ImportFromFile directly? Anyway,this is a separate issue. xpdf_ImportFromStream then calls: sdext/source/pdfimport/wrappter/wrapper.cxx xpdf_ImportFromFile (in line 998) which uses the temp file as the data source xpdf_ImportFromFile then calls (in line 1020): sdext/source/pdfimport/wrappter/wrapper.cxx checkEncryption (in line 891) (Poppler has the check encryption functionality, so why do we use our own encryption checking here? I think it is because we need to show a dialog to ask for password if it is encrypted. But how about we ask poppler to check encryption, and if poppler tells it is encrypted, then we provide the password through stdin?) checkEncryption then calls (in line 901): sdext/source/pdfimport/pdfparse/pdfparse.cxx pdfparse::PDFReader::read (there are two such function, one for win32 and another for the "else". I am confused by those #ifdef _WIN32 stuff, but for me on linux it is in line 608. Interestingly, there is another #ifdef _WIN32 in this block, and my program jumps to line 637 directly) Take note of the aGrammar: PDFGrammar< file_iterator<> > aGrammar( file_start ); pdfparse::PDFReader::read then calls boost::spirit::classic::parse, which took several seconds (maybe a performance issue here?) But there is no exception here yet: boost::spirit::classic::parse( file_start, file_end, aGrammar, boost::spirit::classic::space_p ); Then, finally, in line 672 we get the nEntries: unsigned int nEntries = aGrammar.m_aObjectStack.size(); And its value is 2 for this pdf, as a result a pRet is not set in line 679 block, thus in xpdf_ImportFromFile it returned False. I am not familiar with the boost::spirit::classic::parse staff, thus not sure why the aGrammar.m_aObjectStack.size() is 2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 --- Comment #13 from Kevin Suo --- Well, see below my observations (but without a solution at this moment): sdext/source/pdfimport/pdfiadaptor.cxx PDFIRawAdaptor::importer (in line 291): calls /source/pdfimport/pdfiadaptor.cxx PDFIRawAdaptor::parse (in line 217) which calls (in line 231): sdext/source/pdfimport/wrappter/wrapper.cxx xpdf_ImportFromStream (in line 1182) xpdf_ImportFromStream copied the pdf content to a temp file because the called has passed in a file stream thus xInput.is() is true. I don't think it is necessary to make such temp file - why not pass the url of the original PDF file and then use the xpdf_ImportFromFile directly? This is a separate issue. xpdf_ImportFromStream then calls: sdext/source/pdfimport/wrappter/wrapper.cxx xpdf_ImportFromFile (in line 998) which uses the temp file as the data source xpdf_ImportFromFile then calls (in line 1020): sdext/source/pdfimport/wrappter/wrapper.cxx checkEncryption (in line 891) (Poppler has the check encryption functionnality, so why do we use our own check encryption here? I think it is because we need to show a dialog to ask for password if it is encrypted. But how about we ask poppler to check encryption, and if poppler tells it is encrypted, then we provide the password through stdin?) checkEncryption then calls (in line 901): sdext/source/pdfimport/pdfparse/pdfparse.cxx pdfparse::PDFReader::read (there are two such function, one for win32 and another for the "else". I am confused by those ifdef _WIN32 stuff, but for me on linux it is in line 608. Interestingly, there is another #ifdef _WIN32 in this block, and my program jumps to line 637 directly) Take note for the aGrammar: PDFGrammar< file_iterator<> > aGrammar( file_start ); pdfparse::PDFReader::read calls boost::spirit::classic::parse, which took several seconds (maybe a performance issue here?) But there is no exception here: boost::spirit::classic::parse( file_start, file_end, aGrammar, boost::spirit::classic::space_p ); Then, finally, in line 672 we get the nEntries: unsigned int nEntries = aGrammar.m_aObjectStack.size(); And it is 2 for this pdf which in turn does not set a pRet in line 679 block, thus in xpdf_ImportFromFile it returned False. I am not familiar with the boost::spirit::classic::parse staff, thus not sure why the aGrammar.m_aObjectStack.size() is 2. I don't think I can fix this. I am providing this just FYI. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145539] Convert string literals defined as const char[] in header files to constexpr OUStringLiteral
https://bugs.documentfoundation.org/show_bug.cgi?id=145539 Po-Yen Huang changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |j...@mail.ossii.com.tw |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93070] Buttons in toolbar "Form Controls" fail to change state to "unpressed"
https://bugs.documentfoundation.org/show_bug.cgi?id=93070 --- Comment #11 from MarjaE --- Still unresolved in 7.1.5.2. As of now, the Form Controls buttons changing color, and not changing back when pressed again, are the only discernable effects of Form Controls. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145548] Form Controls Do Nothing in Draw or Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=145548 MarjaE changed: What|Removed |Added Summary|Form Controls Do Nothing in |Form Controls Do Nothing in |Draw|Draw or Writer --- Comment #2 from MarjaE --- Also tried Writer, in both apps. No luck. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 141335, which changed state. Bug 141335 Summary: Tabbed Notebookbar: Style preview should not move the selected style to the first one https://bugs.documentfoundation.org/show_bug.cgi?id=141335 What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141335] Tabbed Notebookbar: Style preview should not move the selected style to the first one
https://bugs.documentfoundation.org/show_bug.cgi?id=141335 stragu changed: What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- --- Comment #7 from stragu --- Actually, I am reopening it because the selected style does _not_ jump to the beginning of the row when using GTK3: Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: c7500945fc5d5bd2130a2d38be0bd4b15445cd90 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded ...but it _does_ jump to the beginning of the row when using the generic VCL pluging (i.e. with the option SAL_USE_VCLPLUGIN=gen): Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: c7500945fc5d5bd2130a2d38be0bd4b15445cd90 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: x11 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded So it looks like the issue is confirmed in the following VCL plugins: - gen - win - kf5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145548] Form Controls Do Nothing in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=145548 --- Comment #1 from MarjaE --- Exact same non-behavior in NeoOffice, btw. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145548] New: Form Controls Do Nothing in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=145548 Bug ID: 145548 Summary: Form Controls Do Nothing in Draw Product: LibreOffice Version: 7.1.5.2 release Hardware: x86 (IA32) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: erw...@alumni.beloit.edu Form Controls do nothing in Draw. 1. Create odg file. 2. Open in another *Office to create appropriate Custom Properties. Can't use Libreoffice for this to to bug 144075. 3. Open in LibreOffice to try to create forms. The Draw Guide says I can do this in text fields, and the detailed instructions are in thhe Writer Guide. 4. Create a rectangle, add text to the rectangle, open Form Controls turn on Design Mode, try frantically to get it to do anything. The Writer Guide p. 396 says that if you manage to activate something, the cursor will change. The only thing that changes is some buttons darken and can't be undarkened without closing and reopening the toolbar. The cursor never changes. 5. I can't create a text box without getting sick, so can't chack if that acts differently from text in a rectangle. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137121] UI: Make it possible to right click the style previews in NB Tabbed mode (to open settings; similar to Sidebar)
https://bugs.documentfoundation.org/show_bug.cgi?id=137121 stragu changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5547 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 stragu changed: What|Removed |Added Depends on||145547 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145547 [Bug 145547] [GTK3] can't right-click tabbed UI styles preview -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145547] [GTK3] can't right-click tabbed UI styles preview
https://bugs.documentfoundation.org/show_bug.cgi?id=145547 stragu changed: What|Removed |Added Blocks||107237 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7121 --- Comment #1 from stragu --- Adding meta bug, and related bug in "See also". Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 stragu changed: What|Removed |Added Depends on||137121 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137121 [Bug 137121] UI: Make it possible to right click the style previews in NB Tabbed mode (to open settings; similar to Sidebar) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137121] UI: Make it possible to right click the style previews in NB Tabbed mode (to open settings; similar to Sidebar)
https://bugs.documentfoundation.org/show_bug.cgi?id=137121 stragu changed: What|Removed |Added Status|RESOLVED|VERIFIED Blocks||107237 --- Comment #16 from stragu --- added meta bug as it didn't have any. Verified as fixed in: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 5b2848413883565c48d312c96daf8fbca25405d8 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: x11 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-11_23:38:53 Calc: threaded ... but opening another bug for the issue in GTK3. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145547] New: [GTK3] can't right-click tabbed UI styles preview
https://bugs.documentfoundation.org/show_bug.cgi?id=145547 Bug ID: 145547 Summary: [GTK3] can't right-click tabbed UI styles preview Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@member.fsf.org Description: Richt-clicking of style previews in the tabbed UI was implemented for Bug 137121. However, when using GTK3, right-clicking the first row of styles does not open a context menu, and right-clicking the following rows of headings result in what would happen if you right-clicked somewhere in the document. Steps to Reproduce: 1. Open Writer 2. Change "View > User Interface..." to "Tabbed" 3. Right-click on a style in the Home tab's style preview area Actual Results: Right-clicking the first row of styles does not open a context menu, and right-clicking the following rows of headings result in what would happen if you right-clicked somewhere in the document. Expected Results: Right-clicking a style preview should open a context menu. Reproducible: Always User Profile Reset: No Additional Info: Reproduced in: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 5b2848413883565c48d312c96daf8fbca25405d8 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-11_23:38:53 Calc: threaded and: Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Using SAL_USE_VCLPLUGIN=gen will allow right-clicking as expected. I am not sure if it ever worked with GTK3, or if it is a regression. Jim Raykowski seems to think it is a regression: https://bugs.documentfoundation.org/show_bug.cgi?id=137121#c14 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145546] New: Crash in: libc-2.31.so
https://bugs.documentfoundation.org/show_bug.cgi?id=145546 Bug ID: 145546 Summary: Crash in: libc-2.31.so Product: LibreOffice Version: 7.1.6.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: cjp...@gmail.com This bug was filed from the crash reporting server and is br-58ae3780-b204-4fec-96ff-e2e7abe86192. = While EDITING while using Zotero Add Citation Writer crashed and system froze. Zotero version 5.0.97-beta.51+6206209ed Upon reboot of system: Recovery was about to FINISH and Writer crashed again. The next Recovery completed successfully with no apparent loss of data. Hence there are two crash reports: https://crashreport.libreoffice.org/stats/crash_details/58ae3780-b204-4fec-96ff-e2e7abe86192 https://crashreport.libreoffice.org/stats/crash_details/7a0f4fc3-1697-4965-93d8-edefcf1af68a -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 141335, which changed state. Bug 141335 Summary: Tabbed Notebookbar: Style preview should not move the selected style to the first one https://bugs.documentfoundation.org/show_bug.cgi?id=141335 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141335] Tabbed Notebookbar: Style preview should not move the selected style to the first one
https://bugs.documentfoundation.org/show_bug.cgi?id=141335 stragu changed: What|Removed |Added Resolution|--- |WORKSFORME CC||stephane.guil...@member.fsf ||.org Status|NEW |RESOLVED --- Comment #6 from stragu --- This is fixed in: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 5b2848413883565c48d312c96daf8fbca25405d8 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-11_23:38:53 Calc: threaded Marking as "Works For Me". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 --- Comment #12 from Kevin Suo --- There can be many xref in a pdf file. Question is, why is the sdext.pdfimport.pdfparse code called? We use poppler to parse pdf which then resulted in the xpdfimprt executable which then generate the token to assemble an Flat ODF to be rendered. Poppler may parse the pdf very well. Why do we parse the pdf structure on our own? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143965] Irresponsive box of style preview under Home tab in tabbed view
https://bugs.documentfoundation.org/show_bug.cgi?id=143965 stragu changed: What|Removed |Added CC||stephane.guil...@member.fsf ||.org Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from stragu --- I can reproduce 7.2.2.2 (the view does not refresh when pressing the up arrow in the scrollbar): Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: x11 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But it seems fixed in: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 5b2848413883565c48d312c96daf8fbca25405d8 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: x11 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-11_23:38:53 Calc: threaded (the scrollbar arrows work as expected). Marking as WFM, but can someone else double-check? Not sure if the fix can be identified and backported to 7.2 at all. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 143965, which changed state. Bug 143965 Summary: Irresponsive box of style preview under Home tab in tabbed view https://bugs.documentfoundation.org/show_bug.cgi?id=143965 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129849] FILEOPEN DOCX: Math Formula size and color lost on import
https://bugs.documentfoundation.org/show_bug.cgi?id=129849 Luke changed: What|Removed |Added Summary|On LibreOffice, Mathemathic |FILEOPEN DOCX: Math Formula |expression are smaller than |size and color lost on |on Word and color in|import |formula is loss | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129849] On LibreOffice, Mathemathic expression are smaller than on Word and color in formula is loss
https://bugs.documentfoundation.org/show_bug.cgi?id=129849 Luke changed: What|Removed |Added Attachment #156980|0 |1 is obsolete|| --- Comment #5 from Luke --- Created attachment 176115 --> https://bugs.documentfoundation.org/attachment.cgi?id=176115=edit Extracted .docx to show problem with imported font color and size The colors are not imported. And the imported size is too small. The correct font size should be 16 pt. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129849] On LibreOffice, Mathemathic expression are smaller than on Word and color in formula is loss
https://bugs.documentfoundation.org/show_bug.cgi?id=129849 --- Comment #4 from Luke --- Created attachment 176114 --> https://bugs.documentfoundation.org/attachment.cgi?id=176114=edit Comparison of LibreOffice vs Word 2016 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138129] Add color picker to starmath
https://bugs.documentfoundation.org/show_bug.cgi?id=138129 Luke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||9849 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129849] On LibreOffice, Mathemathic expression are smaller than on Word and color in formula is loss
https://bugs.documentfoundation.org/show_bug.cgi?id=129849 Luke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||8129 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 --- Comment #11 from himajin100...@gmail.com --- can I have two trailers in a PDF? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106057] General input/output error loading pdf file
https://bugs.documentfoundation.org/show_bug.cgi?id=106057 --- Comment #10 from himajin100...@gmail.com --- Can this information be any of use ? Unlike other comments of my own on other bug reports, I don't have even a bit of clue. https://opengrok.libreoffice.org/xref/core/sdext/source/pdfimport/pdfparse/pdfparse.cxx?r=776a1b9b#575 == parseinfo: stop = xref 0 229 (snip) (buff=%PDF-1.6 %âãÏÓ 226 0 obj (snip) , offset = 138357), hit = true, full = false, length = 124498 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145545] Dragging window from title bar causes it to shrink to 1 pixel wide and a few pixels high.
https://bugs.documentfoundation.org/show_bug.cgi?id=145545 --- Comment #3 from Simon Dedman --- Created attachment 176113 --> https://bugs.documentfoundation.org/attachment.cgi?id=176113=edit appearance after unmaximising -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145545] Dragging window from title bar causes it to shrink to 1 pixel wide and a few pixels high.
https://bugs.documentfoundation.org/show_bug.cgi?id=145545 --- Comment #2 from Simon Dedman --- Created attachment 176112 --> https://bugs.documentfoundation.org/attachment.cgi?id=176112=edit appearance after moving, subsequent times -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145545] Dragging window from title bar causes it to shrink to 1 pixel wide and a few pixels high.
https://bugs.documentfoundation.org/show_bug.cgi?id=145545 --- Comment #1 from Simon Dedman --- Created attachment 176111 --> https://bugs.documentfoundation.org/attachment.cgi?id=176111=edit appearance after moving, first time -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145545] New: Dragging window from title bar causes it to shrink to 1 pixel wide and a few pixels high.
https://bugs.documentfoundation.org/show_bug.cgi?id=145545 Bug ID: 145545 Summary: Dragging window from title bar causes it to shrink to 1 pixel wide and a few pixels high. Product: LibreOffice Version: 7.1.6.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: simonded...@gmail.com Description: Dragging a Calc window from its title bar (typically when maximised) causes it to shrink to 1 pixel wide and a few pixels high. If you right click on its panel element and hit 'unmaximise', it widens by one or two pixels, and you can then try to resize it by successfully hitting the right resize pixel, or use alt+right-click-drag which gives you a bit more room for error. When I tried to reproduce this, initially I couldn't. This led to some extra information. I have 3 screens. If I have Thunar on the right screen, and open a spreadsheet, the spreadsheet opens in the right window and can be dragged to the middle window no problem. If I move thunar to the middle window and open a spreadsheet, it opens in the middle window. If I try to drag it, it collapses into the small box shape. If I repeat this with another sheet, it collapses into the thin line shape. I have another bug which might affect this, but it's more recent than this bug so I suspect not but for full disclosure: https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/525 My xfce4-panel doesn't span all 3 monitors, only the first. Earliest release this affects: unknown but it's been here at least 3 years. I've not customised much with my install. Currently on xubuntu 21.04, LO version 7.1.6.2. Attachments to be added once filed. Steps to Reproduce: 1. Open a spreadsheet in Calc. Maximise it. 2. Try to drag it using the title bar. Actual Results: Window size shrinks to a tiny box in the first instance, and a thin line in subsequent instances. Expected Results: Window moves normally, possibly is automatically shrunk to some reasonable size but probably doesn't need to. Reproducible: Sometimes User Profile Reset: No Additional Info: Version: 7.1.6.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 12; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: en-GB (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.1.6-0ubuntu0.21.04.1 Calc: threaded $ glxinfo | grep OpenGL OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.0.3 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.0.3 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145043] Footnotes & endnotes category in navigator causes exponential lag
https://bugs.documentfoundation.org/show_bug.cgi?id=145043 --- Comment #12 from Jim Raykowski --- Hi David, I put the in the patch mentioned in my previous post. It seems to improve UI response. Testing with gtk3 backend still shows lag for backspace and delete keys. x11 and qt backends don't exhibit this lag. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145525] Some Excel spreadsheet cell borders are not exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=145525 --- Comment #5 from Roman Kuznetsov <79045_79...@mail.ru> --- What PDF Viewer do you use? Could you attach your PDF result here? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145525] Some Excel spreadsheet cell borders are not exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=145525 --- Comment #4 from Rebecca Minghelli --- Created attachment 176110 --> https://bugs.documentfoundation.org/attachment.cgi?id=176110=edit Image of LibreOffice's Help->About dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145513] German-GUI 'Table of Contents, Index or Bibliography' (edit bibliography index) missing buttons 'Insert', 'Remove' and 'Tab Stop' in GUI-Langugage 'German'
https://bugs.documentfoundation.org/show_bug.cgi?id=145513 --- Comment #6 from whg.albre...@web.de --- I have tested the German GUI today in LO V6.4.7.2 in Linux (Ubuntu 20.04 LTS preinstalled). I had also no button problems in the 'Verzeichnis bearbeiten' dialog. The same LO version V6.4.7.2 as PortableApps for Windows show the button problem again. I agree with 'joomart', it might be a LO-PortableApps only. What to do? How is the connection to the LO-PortableApps team? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145525] Some Excel spreadsheet cell borders are not exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=145525 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- Please add info from LibreOffice's Help->About dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145525] Some Excel spreadsheet cell borders are not exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=145525 --- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> --- Created attachment 176109 --> https://bugs.documentfoundation.org/attachment.cgi?id=176109=edit PDF by LO 7.3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145525] Some Excel spreadsheet cell borders are not exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=145525 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- I don't see the problem in Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: c7500945fc5d5bd2130a2d38be0bd4b15445cd90 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144989] Exported PDF of master document with hidden sections in chapters loses pagination
https://bugs.documentfoundation.org/show_bug.cgi?id=144989 --- Comment #4 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/20ddabc88b6b45ea3efcc44ede5244ea526b09c4 tdf#144989 sw: disable idle jobs during printing or PDF export It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144989] Exported PDF of master document with hidden sections in chapters loses pagination
https://bugs.documentfoundation.org/show_bug.cgi?id=144989 Commit Notification changed: What|Removed |Added Whiteboard||target:7.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145544] Newly created lists should utilize "List 1" paragrapsh style
https://bugs.documentfoundation.org/show_bug.cgi?id=145544 --- Comment #2 from John --- OK, thanks, it seems I see your point. For example: You have a document where the main font is Liberation Serif, but the font that is used for the Table Contents style is Liberation Sans. You create a new table and then Writer apply the Table Contents style to its cells. And then you create a list in one of the cells of that table. In this case, the list will use Liberation Sans and this is exactly what you most probably want. Contrary, if newly created lists will utilize List 1 paragraph style, the newly created list in table cell will use Liberation Serif. And this is not what you probably want. Please correct me if I misunderstood you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91192] AutoCorrect: Writer not recognizing a URL's trailing carat, hash mark, question mark, backslash, or pipe
https://bugs.documentfoundation.org/show_bug.cgi?id=91192 himajin100...@gmail.com changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=69 ||599 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 69599] EDITING: No automatic detection of ANSI URL by AutoCorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=69599 himajin100...@gmail.com changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=91 ||192 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Writer table cells have address scheme that differs from Calc, "A-Z,a-z,AB-AZ,..." vs "A-Z,AA-AZ,BA-BZ,..."; lowercase cell refs are more error prone for cell formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval Summary|Lowercase cell references |Writer table cells have |not tolerated in formulas |address scheme that differs |for Writer table cells |from Calc, ||"A-Z,a-z,AB-AZ,..." vs ||"A-Z,AA-AZ,BA-BZ,..."; ||lowercase cell refs are ||more error prone for cell ||formulas CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145513] German-GUI 'Table of Contents, Index or Bibliography' (edit bibliography index) missing buttons 'Insert', 'Remove' and 'Tab Stop' in GUI-Langugage 'German'
https://bugs.documentfoundation.org/show_bug.cgi?id=145513 --- Comment #5 from joomart --- I have tested the german gui: 1. going onto menu point "Einfügen" "Verzeichnis" 2. and selected "Verzeichnis..." for creating new table of content It seems this dialog have changed in newer versions a little bit: on the left side there is a list of "Ebenen". I use 7.2.2 (Debian 11) and have no problems with german buttons. And I know from the older Version 7.1.6 there I had no button problems in this dialog, too. Perhaps it is a font style problem. Or there is a compiling problem while create package for PortableApps. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145544] Newly created lists should utilize "List 1" paragrapsh style
https://bugs.documentfoundation.org/show_bug.cgi?id=145544 --- Comment #1 from Mike Kaganski --- Please do not. Lists are not paragraph styles; they may be applied to many different paragraph styles. Linking lists to paragraph styles is just one possible way of using them; trying to enforce this workflow on everyone would be wrong. Using these two concepts (paragraph styles and list styles) separate provides greater flexibility. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Lowercase cell references not tolerated in formulas for Writer table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 --- Comment #26 from V Stuart Foote --- (In reply to V Stuart Foote from comment #25) > Created attachment 176108 [details] > sample Writer ODF with 60 column table, using cell formulas > but IMHO consistency would be better in the long run. For what it is worth, Word 2019 chokes on the ODF. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145544] New: Newly created lists should utilize "List 1" paragrapsh style
https://bugs.documentfoundation.org/show_bug.cgi?id=145544 Bug ID: 145544 Summary: Newly created lists should utilize "List 1" paragrapsh style Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: When I create a footnote or a table, Writer automatically applies "Footnote" and "Table Contents" paragraph styles to them. But when I create a list, Writer doesn't apply "List 1" style to it. This looks different (= inconsistent) with how it deals with footnotes and tables. So, when I create a list, Writer should use the "List 1" paragraph style it. That's it. Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Lowercase cell references not tolerated in formulas for Writer table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 --- Comment #25 from V Stuart Foote --- Created attachment 176108 --> https://bugs.documentfoundation.org/attachment.cgi?id=176108=edit sample Writer ODF with 60 column table, using cell formulas So in this attached Writer ODF with a 60 column table, it shows the column notation is -- A-Z,a-z,AA-AZ, etc. It probably would be better to make the cell labeling in Writer match the labeling in Calc, i.e A-Z,AA-AZ,BA-BZ, etc. That is, to eliminate the a-z labeling like calc by using the rtl::isAsciiAlpha() and rtl::toAsciiUpperCase() conversion as Eike suggested in comment 6 There would need to be a convert on edit/save for any existing documents, but IMHO consistency would be better in the long run. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 --- Comment #14 from giors...@yahoo.it --- (In reply to Michael Weghorn from comment #12) > > > Since you mention it works in GNOME: Does it also work in a Plasma session > when started with environment variable SAL_USE_VCPLUGIN=gtk3 set? (please > double-check that gtk3 actually shows up in "Help" -> "About LibreOffice") > Unable to double check (globalmenu and menu not working which should mean I'm using gtk3 skin). Works well. No crash. > Could you try collecting a backtrace and attach it here, as described at [1]? I don't know if I did it correctly. Please find attached the gdbtrace.log file (please confirm if it's ok). > Thanks a lot for your investigations, that's exactly what helps to narrow > down the issue! :) Thanks to you. Now (without languagetool) I can use plasma-wayland and libreoffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 --- Comment #13 from giors...@yahoo.it --- Created attachment 176107 --> https://bugs.documentfoundation.org/attachment.cgi?id=176107=edit gdbtrace Here's the gdbtrace.log file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145543] New: Font configuration dialog: fontsize with comma/point is displayed incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=145543 Bug ID: 145543 Summary: Font configuration dialog: fontsize with comma/point is displayed incorrectly Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: joode...@joonet.de Description: In the font configuration dialog: fontsize is displayed incorrectly if it is a number with comma/point. Steps to Reproduce: 1. Change the font size in Writer (directly or also in the template), e.g. to 10.5 pt, then the font size is actually changed. 2. Open the dialog for changing the font size again, always the rounded value, e.g. 11 pt, is displayed, although the correct value 10.5 pt is displayed in the icon bar (above the document). Actual Results: The font size configuration dialog displays the rounded value, e.g. 11 pt, although the correct value 10.5 pt is displayed in the icon bar (above the document), which would be right. Expected Results: Also in the change dialog the exact number should be displayed, with comma/dot. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: This bug is new, coming with 7.2. It does not exist in 7.1. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 --- Comment #12 from Michael Weghorn --- (In reply to giors_00 from comment #10) > So, since the problem seems to be related with java, I tried having > uninstalled languagetool (previously installed from aur repos) and I have to > tell you that now all seems fine (obviously need to test it deeply) no > metter which java version is selected. So apparently, it is a languagetool > issue (quite strange though, since with gnome it seems to work just > perfectly). Since you mention it works in GNOME: Does it also work in a Plasma session when started with environment variable SAL_USE_VCPLUGIN=gtk3 set? (please double-check that gtk3 actually shows up in "Help" -> "About LibreOffice") > Just to complete the test, I decided to try reinstalling languagetool but > manually (instead of from aur repository from libreoffice-extensions' page). > Download speed is quite annoying (never faster than 350kb/sec.). Crashing is > back. I quickly tried with current LO master and languagetool 5.5.1. I ran into an assertion here with my debug build that seems to be unrelated to the problem you're encountering (on both X11 and Wayland, but this only happens after clicking around in the menu a bit, and after silencing the assert, it seems to work OK so far, so that should not have hit you with a release build of LibreOffice). Could you try collecting a backtrace and attach it here, as described at [1]? That might give a clue on why you're running into this (from comment 8): [xcb] Unknown sequence number while processing reply [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. soffice.bin: xcb_io.c:725: _XReply: La declaración `!xcb_xlib_threads_sequence_lost' no se cumple. [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. soffice.bin: xcb_io.c:269: poll_for_event: La declaración `!xcb_xlib_threads_sequence_lost' no se cumple. > Finally: sorry for my inexperience (I am just a final user) but IMHO problem > seems to be related with languagetool extension's behaviour with kf5 skin. > Do you think it can be possible? Yes, that's what it looks like and is definitely possible. Thanks a lot for your investigations, that's exactly what helps to narrow down the issue! :) [1] https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145513] German-GUI 'Table of Contents, Index or Bibliography' (edit bibliography index) missing buttons 'Insert', 'Remove' and 'Tab Stop' in GUI-Langugage 'German'
https://bugs.documentfoundation.org/show_bug.cgi?id=145513 Julien Nabet changed: What|Removed |Added CC|serval2...@yahoo.fr | --- Comment #4 from Julien Nabet --- Thank you for your feedback. No more idea so can't help here=>uncc myself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99617] FILEOPEN pptx animation "rotate" is wrongly converted
https://bugs.documentfoundation.org/show_bug.cgi?id=99617 Xisco Faulí changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #10 from Xisco Faulí --- The fix is covered by the unittest for bug 112280 -> http://cgit.freedesktop.org/libreoffice/core/commit/?id=d921d4fd24b6416e00069678886f9692ffb4a008 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Lowercase cell references not tolerated in formulas for Writer table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 --- Comment #24 from Dave McKellar --- On unparsable formulas: If you enter a syntax error like: + The formula is retained but the value "** Expression is faulty **" is displayed. But if you enter something wrong inside angle brackets - eg it is changed into That's inconsistent. Perhaps the representation of a range could be expanded to hold things it can not parse as a string. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132499] Remove any remnants from ODBC < 3.0 + add missing functions + remove deprecated functions with ODBC > 3.0
https://bugs.documentfoundation.org/show_bug.cgi?id=132499 Julien Nabet changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132499] Remove any remnants from ODBC < 3.0 + add missing functions + remove deprecated functions with ODBC > 3.0
https://bugs.documentfoundation.org/show_bug.cgi?id=132499 Julien Nabet changed: What|Removed |Added Status|NEW |RESOLVED Whiteboard|target:7.3.0| CC||r...@debian.org Resolution|--- |WONTFIX --- Comment #10 from Julien Nabet --- Following comments in gerrit patches, it should be done upstream. Let's put this one as WONTFIX then. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132499] Remove any remnants from ODBC < 3.0 + add missing functions + remove deprecated functions with ODBC > 3.0
https://bugs.documentfoundation.org/show_bug.cgi?id=132499 --- Comment #9 from Commit Notification --- Julien Nabet committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a11425579127502f4ee0972cc9fef09894e64a0d Revert "tdf#132499: first stab to remove old stuff from ODBC ver < 3" It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132499] Remove any remnants from ODBC < 3.0 + add missing functions + remove deprecated functions with ODBC > 3.0
https://bugs.documentfoundation.org/show_bug.cgi?id=132499 --- Comment #8 from Commit Notification --- Julien Nabet committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/88982b04ae2c451a5af62f7fc6c9502414590f92 Revert "tdf#132499: consider ODBCVER >= 0x0300 and remove tests about it (unixODBC)" It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97327] Calc Compare Document (Spreadsheet Compare) doesn't works well when comparing documents with different number of Sheets.
https://bugs.documentfoundation.org/show_bug.cgi?id=97327 --- Comment #8 from Francisco José Cañizares Santofimia --- Still present in: Version: 7.2.1.2 (x86) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 (Windows) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Lowercase cell references not tolerated in formulas for Writer table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 --- Comment #23 from Mike Kaganski --- (In reply to Mike Kaganski from comment #22) > It *looks* reasonable, but dangerous. Personally I support this - but I'd > suggest you to post a message to the dev mailing list asking for opinions on > the proposal. OTOH, the formula is written into file format using this convention, so the change of this, however undocumented, convention would be incompatible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Lowercase cell references not tolerated in formulas for Writer table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 --- Comment #22 from Mike Kaganski --- (In reply to Dave McKellar from comment #20) > Since the difference between Writer and Calc doesn't appear to be > documented, perhaps Writer can be changed and then documented. To help > users transition if it sees lowercase call names it can display a message. > That would be best in the long run. It *looks* reasonable, but dangerous. Personally I support this - but I'd suggest you to post a message to the dev mailing list asking for opinions on the proposal. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Lowercase cell references not tolerated in formulas for Writer table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 --- Comment #21 from Mike Kaganski --- Fun detail is that it's even can't be justified "for compatibility with Word", since Word uses normal 26-base reference scheme. Wrt "unfriendly to delete something the user entered": IIUC, the formula text is never kept, it's parsed, tokenized, and the result is stored. Whatever can't be tokenized is not stored. Without much change that would highlight the problem, keeping the formula intact and only displaying "invalid reference" would make fixing formulas next to impossible, when user doesn't see which part is wrong. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Lowercase cell references not tolerated in formulas for Writer table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 --- Comment #20 from Dave McKellar --- It seems very unfriendly to delete something the user entered. Better to keep the formula and display "invalid reference" (or something) for the value. Since the difference between Writer and Calc doesn't appear to be documented, perhaps Writer can be changed and then documented. To help users transition if it sees lowercase call names it can display a message. That would be best in the long run. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145384] Lowercase cell references not tolerated in formulas for Writer table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=145384 --- Comment #19 from Mike Kaganski --- (In reply to Dave McKellar from comment #18) The same way as when you try to put '=' in a table with three columns. Unrelated to upper-vs-lowercase, and specific to the way Writer's tables validate formula references. Self-consistent in a sense... I am very disappointed to learn that Writer uses totally different column naming convention compared to Calc. But anyway, there is help missing on this topic. -- You are receiving this mail because: You are the assignee for the bug.
