[Libreoffice-bugs] [Bug 33961] cross reference to a list number, dot bug
https://bugs.documentfoundation.org/show_bug.cgi?id=33961 Asley Patricia changed: What|Removed |Added URL|https://assignmentmasters.a |https://assignmentmaster.or |e/ |g.uk Alias|https://assignmentmasters.a | |e/ | --- Comment #12 from Asley Patricia --- This amazing topic, which is so reliable and authentic as well but there are also very beneficial https://assignmentmaster.org.uk/;>Assignment Help Leeds are always available in giving you their best results easily thesedays. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 73707] EDITING: Report-Builder - Conditional Print Expression isn't saved for Shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=73707 --- Comment #13 from Michael --- Still the same as in my comment #12 using actually Version: 7.3.6.2 / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Bug 10 depends on bug 153045, which changed state. Bug 153045 Summary: FILEOPEN: DOCX: incorrect height of row in table https://bugs.documentfoundation.org/show_bug.cgi?id=153045 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128907] Support for Hancom Office File Format (HWP)
https://bugs.documentfoundation.org/show_bug.cgi?id=128907 Michael Weghorn changed: What|Removed |Added CC||vihs...@gmail.com --- Comment #15 from Michael Weghorn --- *** Bug 108848 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111443] [META] Unsupported formats in LibreOffice Viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=111443 Bug 111443 depends on bug 108848, which changed state. Bug 108848 Summary: support for hancom hanword (.hwp) file https://bugs.documentfoundation.org/show_bug.cgi?id=108848 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108848] support for hancom hanword (.hwp) file
https://bugs.documentfoundation.org/show_bug.cgi?id=108848 Michael Weghorn changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Michael Weghorn --- (In reply to Ildar Muyukov from comment #4) > The sample file that the Reporter (@vihsa) provides cannot be opened even by > the Linux LO. > So I suggest this is > https://bugs.documentfoundation.org/show_bug.cgi?id=128907 > and not Android-relevant. Thanks, closing as duplicate. *** This bug has been marked as a duplicate of bug 128907 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149492] With nothing selected, properties sidebar shows an extra "Slide" or "Page" section
https://bugs.documentfoundation.org/show_bug.cgi?id=149492 Buovjaga changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #7 from Buovjaga --- Contrary to comment 2, the things that are solved with a profile reset we treat as WFM. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108848] support for hancom hanword (.hwp) file
https://bugs.documentfoundation.org/show_bug.cgi?id=108848 --- Comment #4 from Ildar Muyukov --- The sample file that the Reporter (@vihsa) provides cannot be opened even by the Linux LO. So I suggest this is https://bugs.documentfoundation.org/show_bug.cgi?id=128907 and not Android-relevant. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153043] Writer should not declare CJK (or RTL-CTL) fonts when if CJK (resp. RTL-CTL) support disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153043 --- Comment #8 from Mike Kaganski --- I mean: a document without CJK is sent to two CJK-using collaborators; and their results arrive like that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153043] Writer should not declare CJK (or RTL-CTL) fonts when if CJK (resp. RTL-CTL) support disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153043 --- Comment #7 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #6) > > Again: the results must be consistent not in your sense, but in absolute > > sense: the author can start something on a system configured for en-US, and > > then participants from all other places should not create a mess because of > > "unspecified behavior". > > They won't create a mess. Whenever some collaborator adds CJK content, they > will need to declare/specify fonts for that language group. While > collaborators don't use CJK either, that remains unnecessary. And - it is > not a problem if a collaborator declares the CJK fonts, and the author sees > the CJK fonts which the collaborator set, e.g. using their system's default, > rather than the original author's system default - because it's the > collaborator who introduced CJK. Two different collaborators would create two different formattings - each on their system with their settings; and then it is a mess. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153102] docx: instead of line showing triangle at left bottom
https://bugs.documentfoundation.org/show_bug.cgi?id=153102 --- Comment #2 from jindam, vani --- Created attachment 184769 --> https://bugs.documentfoundation.org/attachment.cgi?id=184769=edit screenshot showing rectangle instead of sloped line at bottom left of docx file on lo viewer 7.6 alpha android app -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153102] docx: instead of line showing triangle at left bottom
https://bugs.documentfoundation.org/show_bug.cgi?id=153102 jindam, vani changed: What|Removed |Added CC||jindam.v...@disroot.org --- Comment #1 from jindam, vani --- Created attachment 184768 --> https://bugs.documentfoundation.org/attachment.cgi?id=184768=edit screenshot showing sloped line at bottom left of docx file on word android app -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153102] New: docx: instead of line showing triangle at left bottom
https://bugs.documentfoundation.org/show_bug.cgi?id=153102 Bug ID: 153102 Summary: docx: instead of line showing triangle at left bottom Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Viewer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jindam.v...@disroot.org Description: it does not show line at left bottom, it shows rectangle Steps to Reproduce: 1. open attachment 130196 on bug 105143 Actual Results: it shows rectangle at bottom left Expected Results: it shows sloped line at bottom left Reproducible: Always User Profile Reset: No Additional Info: libreoffice viwer android [fdroid version]: Version: 7.6.0.0.alpha0+ Build ID: d6c54b3d4ee7 probably regression of bug 105143? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152864] FILEOPEN RTF Direct formatting on dropdown field not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=152864 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 148642] Embedded videos in Impress do not scale in presentation mode (4k display)
https://bugs.documentfoundation.org/show_bug.cgi?id=148642 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 152877] Dates are getting formatted as dollar amounts and can't change
https://bugs.documentfoundation.org/show_bug.cgi?id=152877 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 152881] Crash when installing new font on windows
https://bugs.documentfoundation.org/show_bug.cgi?id=152881 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 152874] FILEOPEN RTF Paragraph shading from style, overridden by DF is still visible in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152874 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 153047] PDF Export: default text in content control is gone
https://bugs.documentfoundation.org/show_bug.cgi?id=153047 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152870] Printing/exporting to PDF shows out-of-cell numbering that is invisible normally
https://bugs.documentfoundation.org/show_bug.cgi?id=152870 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 152873] Help Writer → Variables → Numbering by Chapter: Wrong description
https://bugs.documentfoundation.org/show_bug.cgi?id=152873 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 152875] Diagram legend is changed when saving
https://bugs.documentfoundation.org/show_bug.cgi?id=152875 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 153047] PDF Export: default text in content control is gone
https://bugs.documentfoundation.org/show_bug.cgi?id=153047 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148600] Wrong encoding in the GUI
https://bugs.documentfoundation.org/show_bug.cgi?id=148600 --- Comment #3 from QA Administrators --- Dear Maximilian, 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 149645] insert photo album does not rotate images
https://bugs.documentfoundation.org/show_bug.cgi?id=149645 --- Comment #4 from QA Administrators --- Dear Simo He, 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 149645] insert photo album does not rotate images
https://bugs.documentfoundation.org/show_bug.cgi?id=149645 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 148600] Wrong encoding in the GUI
https://bugs.documentfoundation.org/show_bug.cgi?id=148600 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 148205] A textbox occupies more space as size after saving the file as .pptx and open again
https://bugs.documentfoundation.org/show_bug.cgi?id=148205 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 122652] [META] Memory problems in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=122652 Bug 122652 depends on bug 114469, which changed state. Bug 114469 Summary: SfxItemSet::InitRanges_Impl(unsigned short const*) leaks memory with multiple invocations https://bugs.documentfoundation.org/show_bug.cgi?id=114469 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148205] A textbox occupies more space as size after saving the file as .pptx and open again
https://bugs.documentfoundation.org/show_bug.cgi?id=148205 --- Comment #4 from QA Administrators --- Dear tryingbefair, 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 114469] SfxItemSet::InitRanges_Impl(unsigned short const*) leaks memory with multiple invocations
https://bugs.documentfoundation.org/show_bug.cgi?id=114469 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 114469] SfxItemSet::InitRanges_Impl(unsigned short const*) leaks memory with multiple invocations
https://bugs.documentfoundation.org/show_bug.cgi?id=114469 --- Comment #10 from QA Administrators --- Dear Telesto, 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 95154] Table - Cells splitting vertically - cannot set sizes of the boxes individually/independent
https://bugs.documentfoundation.org/show_bug.cgi?id=95154 --- Comment #14 from QA Administrators --- Dear Michael, 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 92714] Deletion of an index/table as first element of a page resets page style to default
https://bugs.documentfoundation.org/show_bug.cgi?id=92714 --- Comment #6 from QA Administrators --- Dear Michael Fiedler, 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 89168] android: React on page size changes
https://bugs.documentfoundation.org/show_bug.cgi?id=89168 --- Comment #8 from QA Administrators --- Dear Jan Holesovsky, 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 137158] Notebookbar contextual groups: Alignment and text formatting status not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=137158 --- Comment #2 from QA Administrators --- Dear michaelklein27, 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 56161] VIEWING: Comment formatting change from 'Straight Line' to 'Angled Connector Line' not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=56161 --- Comment #10 from QA Administrators --- Dear Rainer Bielefeld Retired, 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 139744] AutoCorrect: faulty replacement of single Quotation Marks
https://bugs.documentfoundation.org/show_bug.cgi?id=139744 --- Comment #2 from QA Administrators --- Dear burbat, 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 139418] The layout is broken when opening a vertical writing manuscript paper(Genko yoshi) docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=139418 --- Comment #7 from QA Administrators --- Dear nogajun, 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 135378] FIELD TEXT reintroduced after undo
https://bugs.documentfoundation.org/show_bug.cgi?id=135378 --- Comment #9 from QA Administrators --- Dear Telesto, 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 123103] FILEOPEN PPTX Font size is smaller compared to MSO because LO doesn't recognize Autofit Text to Placeholder
https://bugs.documentfoundation.org/show_bug.cgi?id=123103 --- Comment #8 from QA Administrators --- Dear NISZ LibreOffice Team, 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 106777] Marchen text clipped in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=106777 --- Comment #15 from QA Administrators --- Dear Volga, 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 104833] Scroll panes in Check for Updates dialog do not expose names to assistive technologies
https://bugs.documentfoundation.org/show_bug.cgi?id=104833 --- Comment #5 from QA Administrators --- Dear am_dxer, 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 102046] Split and group buttons not exposed correctly on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=102046 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 153092] text is missing inside and right side of image on docx on page 2
https://bugs.documentfoundation.org/show_bug.cgi?id=153092 --- Comment #5 from jindam, vani --- @raal just now reckhecked, page 6 is also complete mess. attachment 118885 on Bug 94368 pg 13 has also text missing. however its a .doc file. should i open seperate issues or wait for fix. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153099] LibreOffice (Writer) shows a dot (.) to indicate a decimal point, when it should be a comma (, ) instead.
https://bugs.documentfoundation.org/show_bug.cgi?id=153099 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW --- Comment #1 from m.a.riosv --- Reproducible with Spanish Version: 7.4.1.0.0+ (x64) / LibreOffice Community Build ID: 7ef4ce12e52b699e31009e8bca8c57dd710de829 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f1830bff71847a9c17715cff52383956719847fe CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153100] Some buttons in dark mode are invisible.
https://bugs.documentfoundation.org/show_bug.cgi?id=153100 V Stuart Foote changed: What|Removed |Added Blocks||143344 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143344 [Bug 143344] [META] Linux Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=143344 V Stuart Foote changed: What|Removed |Added Depends on||153100 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153100 [Bug 153100] Some buttons in dark mode are invisible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153100] Some buttons in dark mode are invisible.
https://bugs.documentfoundation.org/show_bug.cgi?id=153100 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- Believe the foreground/background color "sense" for detected dark mode was corrected at 7.4, and certainly for the 7.5 release. 7.3.7 is EOL, please retest with a current 7.4.4 or upcoming 7.5.0 release. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130110] lang parameter of loleaflet.html
https://bugs.documentfoundation.org/show_bug.cgi?id=130110 Aron Budea changed: What|Removed |Added Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #3 from Aron Budea --- This can be considered moved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152850] bad scoping of sqrt after mathml import
https://bugs.documentfoundation.org/show_bug.cgi?id=152850 Joel Dowdy changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |joeldowd...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81720] After setting a cross-reference object from Fields dialog (or API calls), it can incorrectly receive edit cursor from document canvas during editing corrupting both refe
https://bugs.documentfoundation.org/show_bug.cgi?id=81720 V Stuart Foote changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |3085| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153085] Value of cross-references expand when setting cursor directly after inserted reference
https://bugs.documentfoundation.org/show_bug.cgi?id=153085 V Stuart Foote changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=81 | |720 | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153101] New: Disable Update Notifications for Technological Enthusiast Releases
https://bugs.documentfoundation.org/show_bug.cgi?id=153101 Bug ID: 153101 Summary: Disable Update Notifications for Technological Enthusiast Releases Product: LibreOffice Version: unspecified Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ataronchronon...@gmail.com Description: While I do like to be informed of new updates to the older stable version of LibreOffice, it is unnecessary and kind of annoying to receive the update notifications for the "technological enthusiast" version when I've no plans to install that one. Additionally, the update notification within the application does not specify what type of update it is, so you have to visit the download page to realize that it's the tech enthusiast version. Please add a setting to disable notifications for the tech enthusiast version and/or to disable update notifications altogether. Otherwise great software, thanks! Actual Results: Update notifications are inconsistent and too frequent, with little/no settings to modify their behavior (see Description for more info). Thanks! Expected Results: Allow disabling of update notifications or at least disabling of the "technological enthusiast" update notifications. Reproducible: Always User Profile Reset: No Additional Info: Please see Description, Actual Results, and Expected Results for more information. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91415] Improve design of comment indicators to block less of the cell's content
https://bugs.documentfoundation.org/show_bug.cgi?id=91415 --- Comment #8 from ady --- (In reply to Cor Nouws from comment #7) > (In reply to ady from comment #5) > Is it that there may never be any overlap in the content and the indicator? No, of course I'm not demanding that; just that the current workarounds be still available, especially the zoom, as it is the easiest to temporarily apply. The current change seems to prevent it. > Or..? > Can I see images/examples somewhere of what works and what not? First, apologies for the long text that follows, but this matter needs clear debate (as shown by the several bug tickets, many comments, and prior attempts of resolutions back and forth). I have encountered some case with the comment indicator blocking some text or number in a cell at some point or another in my life. Usually, I am able to overcome such situation by means of zoom. Using the zoom is something that I am used to use frequently, for other reasons, so it is natural for me to use such method. Other users might not even think about that, so they might think that they have a critical UI issue. There is very little mention of using zoom in the related bug reports (which might indicate that they don’t even try it or think about such alternative). Other workarounds, besides those I already mentioned, can be text alignment, indentation and border padding (all of which I also use for cases such as filter arrows blocking text, either within or around the boundaries of the filtering cell). When I saw the wording, "scale…", I went and asked Heiko Tietze in irc #libreoffice-design, and the screenshots and video provided show that, no matter the zoom, the resulting text is still covered by the indicator. This is not what happens as of LO 7.4.4, in which, most frequently than not, temporarily changing the zoom can resolve the relatively minor problem – I say "relatively minor", because it can be easily overcome by several currently-available methods. It is still in the hands of users. By changing the indicator to grow when we use higher values of zoom (i.e. part of scaling it), which is part of the change according to the screenshot that Heiko Tietze showed me, a relatively minor problem for some users in some cases can turn into a permanent inconvenience (especially to visually challenged users) that has no easy workaround (because no matter the zoom, if the indicator covers a text, it will cover it under any zoom value once the change is committed). There will be no longer an easy workaround in the hands of users (especially if the file is read-only, when other properties cannot be modified, but the zoom is yet available). Having some artifact covering some text is not an exclusive issue with the comment indicator. There is help text showing under the mouse pointer, and/or filter arrows, just as common examples. The user has sometimes some method to overcome or correct the situation (e.g. for filter arrows, and for comment indicators), but sometimes there is no workaround (e.g. mouse pointer over help text). The resolution proposed here seems to make useless the easy workaround currently available (as of LO 7.4.4.), and will not solve the issue really (as shown in the screenshots that Heiko Tietze provided in irc). For example (of what _not_ to do), making the indicator just one color (i.e. with no border of another contrasting color) would make it smaller, but such hypothetical change clearly clashes with using a similar background color for the cell or for the cell’s border, so you should _not_ make the indicator one_color_only and without its border (i.e. its border, with a different color, must remain). If you can make the indicator smaller but still visible (e.g. triangle, still with a border of a different color), then that’s an improvement (in UI) that shouldn't affect negatively other users. Perhaps if the indicator can be partly transparent (the alpha thing that was suggested before) then both objectives can be maintained(?): the text can be clearly seen, and the indicator can be clearly spotted. It is possible that just making it a triangle is enough, in which case no new bug enhancement requests would show up (and so, going step-by-step towards a resolution can be helpful, rather than applying several changes at one time, risking some unnecessary negative side-effects). Reading prior tickets (some of which I already linked to) on the same subject and prior attempts to improve the situation, demonstrates that there is some balance to consider, and that some changes that are centered on the comment indicator alone can negatively affect other aspects of UI and usage. Since I have to rely on using the zoom more often than not (and the comment indicator is not nearly the main reason for it, by far), I am perhaps more aware than others that using the zoom can be an easy workaround for the matter in question in many occasions, while scaling the comment indicator seems to have
[Libreoffice-bugs] [Bug 130453] [macOS] Convert from Carbon to Cocoa framework
https://bugs.documentfoundation.org/show_bug.cgi?id=130453 Caolán McNamara changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #13 from Caolán McNamara --- caolanm->ilmari: I think you have ended up as this years coordinator (de facto/jure?) of budget 2023 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130453] [macOS] Convert from Carbon to Cocoa framework
https://bugs.documentfoundation.org/show_bug.cgi?id=130453 Patrick Luby changed: What|Removed |Added CC||plub...@neooffice.org --- Comment #12 from Patrick Luby --- I saw this bug in a budgeting e-mail on the developer's mailing. This bug has been open for almost 3 years. Maybe we can narrow the scope of this bug to some concrete tasks. Here is some of the tasks that can think of: 1. Replace any remaining Carbon functions with non-Carbon functions. There aren't a lot of Carbon functions that I can see, but the following shared libraries are still linked to the Carbon framework: libAppleRemotelo.dylib libmacabdrv1.dylib libuno_sal.dylib.3 libvclplug_osxlo.dylib 2. Replace any deprecated macOS functions with supported functions. Apple routinely changes function names every few years, even in Cocoa and other frameworks. LibreOffice is still using some deprecated macOS functions and since Apple may remove deprecated functions from a future version of macOS, a second task for this bug could be replacing deprecated code within SAL_WNODEPRECATED_DECLARATIONS_PUSH/SAL_WNODEPRECATED_DECLARATIONS_POP #pragma blocks. I am planning on working on the second task for the native accessibility code in vcl/osx later this year. I am planning on replace the deprecated, heavyweight NSAccessibility informal protocol with the new, lightweight formal protocol. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153043] Writer should not declare CJK (or RTL-CTL) fonts when if CJK (resp. RTL-CTL) support disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153043 --- Comment #6 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #3) > This: "the document author doesn't care which CTL fonts the person opening > the document uses for adding content" is ... shocking ;) It may shock you, but it's true. > The author creates content *and styles*. Content and styles that don't involve CJK, because the author has configured their app to disable CJK support. Which happens when the author's work - including the author's collaboration work - does not involve CJK languages. > The work on a document can happen > collaboratively through sharing, and the end result *indeed* depends on > correct behavior of the program on all systems. The change of a styling > should be always an explicit action. That is only for _defined_ styling. > > > And even when a document is created in such an environment, it must have > > > defaults, so that when it later edited in different environments > > > (including > > > at the same place, using e.g. charmap), the results are consistent. The results will be consistent, since the document doesn't involve any CJK LG content. > Again: the results must be consistent not in your sense, but in absolute > sense: the author can start something on a system configured for en-US, and > then participants from all other places should not create a mess because of > "unspecified behavior". They won't create a mess. Whenever some collaborator adds CJK content, they will need to declare/specify fonts for that language group. While collaborators don't use CJK either, that remains unnecessary. And - it is not a problem if a collaborator declares the CJK fonts, and the author sees the CJK fonts which the collaborator set, e.g. using their system's default, rather than the original author's system default - because it's the collaborator who introduced CJK. > Any change from some *fixed default* must be explicit. We are arguing about whether there should be a fixed default. Even without a fixed default, of course any divergence from the absence of CJK should be explicit w.r.t. styling. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153100] Some buttons in dark mode are invisible.
https://bugs.documentfoundation.org/show_bug.cgi?id=153100 --- Comment #1 from jricar...@icloud.com --- Created attachment 184767 --> https://bugs.documentfoundation.org/attachment.cgi?id=184767=edit Some buttons in dark mode are invisible in toolbar. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153100] New: Some buttons in dark mode are invisible.
https://bugs.documentfoundation.org/show_bug.cgi?id=153100 Bug ID: 153100 Summary: Some buttons in dark mode are invisible. Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jricar...@icloud.com Description: Hello. In dark mode, some buttons like N (bold), I (italic) and alignment in the tool bar are invisible in Writer and Calc. Actual Results: Some buttons in dark mode are invisible. Expected Results: Visible buttons in tool bar. Reproducible: Always User Profile Reset: No Additional Info: Some buttons in dark mode are invisible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153019] LibreOffice calc recovery does not recover hours of unsaved work
https://bugs.documentfoundation.org/show_bug.cgi?id=153019 --- Comment #3 from m.a.riosv --- Just tested and it is enabled by default, at least on the last Windows versions. Don't know about distro Linux versions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152217] Black box in Basic IDE where the status bar should be (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=152217 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected Regression By||Jan-Marek Glogowski CC||glo...@fbihome.de --- Comment #2 from Stéphane Guillou (stragu) --- Bibisected with linux-64-7.5 repo to first bad commit 5c4a00e051f4d9366ae8a2e98a1f2ab4b016e9a7 which points to core commit: commit afc828b9833b7a612369e95606ba56d41ef2c369 author Jan-Marek Glogowski Sat May 28 23:47:21 2022 +0200 committer Jan-Marek Glogowski Tue Jun 21 17:26:06 2022 +0200 treeb60ec391ff6f93f85eb4f88d756c2f70b79b674c parent dbaf5f6fad2ec10f69cf46f9cb697b8760c2a01f VCL expect correct frame size for native menubars Change-Id: I7faeace61b456c2b0f42c7a826f58018b70d46ae Reviewed-on: https://gerrit.libreoffice.org/c/core/+/135082 Jan-Marek, can you please have a look? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153099] New: LibreOffice (Writer) shows a dot (.) to indicate a decimal point, when it should be a comma (, ) instead.
https://bugs.documentfoundation.org/show_bug.cgi?id=153099
Bug ID: 153099
Summary: LibreOffice (Writer) shows a dot (.) to indicate a
decimal point, when it should be a comma (,) instead.
Product: LibreOffice
Version: 7.4.4.2 release
Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
Severity: trivial
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: derussischefraudeerb...@proton.me
Description:
https://i.vgy.me/1rav2m.png
Image^^
When you press alt+p and go to "edges" ("randen" in Dutch), the program
sometimes shows a comma as decimal seprator and sometimes a dot. It should
always be a comma considering the fact I have my language set to Dutch, which
is a language that uses commas as decimal separators, unlike English.
Note: This issue might also appear in more places than just the alt+p menu.
Steps to Reproduce:
This only appears in the Dutch translation of LibreOffice!! Go to description
for an image.
1. Open Writer (this might also appear in different programs, like Impress, and
this might also appear in other sections of the UI. I haven't checked that.)
2. Press alt+p.
3. Go to "edges" ("randen" in Dutch)
Actual Results:
The decimal separator is a dot (.)
Expected Results:
The decimal separator should've been a comma (,)
Reproducible: Always
User Profile Reset: No
Additional Info:
Version: 7.4.4.2 (x64) / LibreOffice Community
Build ID: 85569322deea74ec9134968a29af2df5663baa21
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: nl-NL
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153098] LO skips the 1st column of 2nd section when sections have heading with Columb Break Before text flow, while loading the document
https://bugs.documentfoundation.org/show_bug.cgi?id=153098 --- Comment #1 from Pols12 --- Created attachment 184766 --> https://bugs.documentfoundation.org/attachment.cgi?id=184766=edit Sample issuing document: column breaks skipping first column -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153098] New: LO skips the 1st column of 2nd section when sections have heading with Columb Break Before text flow, while loading the document
https://bugs.documentfoundation.org/show_bug.cgi?id=153098 Bug ID: 153098 Summary: LO skips the 1st column of 2nd section when sections have heading with Columb Break Before text flow, while loading the document Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: poltro...@gmail.com Description: When you use “Column Break before” Text Flow for headings in two-columns layout sections, LibreOffice skip unexpectedly the first column for some sections while loading the document, whereas it did not skip it while creating the document. Steps to Reproduce: Short reproduction: open attached document. 1. Create the following document: ``` The first section starts after this paragraph == H1 == Paragraph of h1 == H2 == Paragraph of h2 Paragraph outside of section 1. The second section starts after this paragraph. == H3 == Paragraph of h3 == H4 == Paragraph of h4 The second section ends before this paragraph. ``` 2. Add a two-columns layout for first section (H1 and H2) and second section (H3 and H4). 3. For all headings, check Paragraph → Text Flow → Breaks → Insert: Column Before 4. Save the document. Close it. Reopen it. Actual Results: Heading3 displays in second column, the first column of its section is skipped. Expected Results: Closing and re-opening the document should not produce any change. Heading3 should display in 1st column, as Heading1 is. Reproducible: Always User Profile Reset: Yes Additional Info: Tested with: * LibreOffice 7.3.7 on Windows 10 * LibreOffice 7.0.4 on Debian -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149492] With nothing selected, properties sidebar shows an extra "Slide" or "Page" section
https://bugs.documentfoundation.org/show_bug.cgi?id=149492 Eyal Rozenberg changed: What|Removed |Added Summary|With nothing selected, |With nothing selected, |properties sidebar shows|properties sidebar shows an |"Slide" section |extra "Slide" or "Page" ||section -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149492] With nothing selected, properties sidebar shows "Slide" section
https://bugs.documentfoundation.org/show_bug.cgi?id=149492 Eyal Rozenberg changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #6 from Eyal Rozenberg --- I'm currently using: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ad387d5b984c906505d25685065f710ed55d CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Calc: threaded When clearing the profile, I don't see the bug. If I keep my profile - I see "page" twice. So, changing back to UNCONFIRMED. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153088] Dark Mode: Calc: Format Cells > Font + Font Effects sample text should be white
https://bugs.documentfoundation.org/show_bug.cgi?id=153088 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114537] Filesave: Export ConditionalText field to DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=114537 Justin L changed: What|Removed |Added Summary|FIlesave: Export|Filesave: Export |ConditionalText field to|ConditionalText field to |DOC |DOC Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114537] FIlesave: Export ConditionalText field to DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=114537 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112969] [META] DOCX (OOXML) field-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112969 Bug 112969 depends on bug 114537, which changed state. Bug 114537 Summary: FIlesave: Export ConditionalText field to DOC https://bugs.documentfoundation.org/show_bug.cgi?id=114537 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114537] FIlesave: Export ConditionalText field to DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=114537 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114537] FIlesave: Export ConditionalText field to DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=114537 --- Comment #7 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/c2bcaaeab0787c6658eeda0f570bb6aa59d4d64e tdf#114537 doc/rtf export: move DOCX impl so all formats use it It will be available in 7.6.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 110434] [META] Envelope bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=110434 Bug 110434 depends on bug 152770, which changed state. Bug 152770 Summary: Insert - Envelope in a new document: warnings in console with debug LO https://bugs.documentfoundation.org/show_bug.cgi?id=152770 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152770] Insert - Envelope in a new document: warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152770 Caolán McNamara changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #14 from Caolán McNamara --- Maybe that makes a difference, to defer until the resolution is needed the warning that the resolution is a guess because the ppd lists no resolutions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152770] Insert - Envelope in a new document: warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152770 --- Comment #13 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f93d4062c92e0508dc6a5272350ad98b9f0bfd72 tdf#152770 move warning about ppd with no resolution to use of resolution It will be available in 7.6.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 91415] Improve design of comment indicators to block less of the cell's content
https://bugs.documentfoundation.org/show_bug.cgi?id=91415 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #7 from Cor Nouws --- (In reply to ady from comment #5) > Reopening. Hi Ady, I understand and respect that you are not happy with the change. >From your comment, it is hard for me to understand what exactly _does_ work or _does not_ work for you, related to accessibility. Is it that there may never be any overlap in the content and the indicator? Or..? Can I see images/examples somewhere of what works and what not? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152864] FILEOPEN RTF Direct formatting on dropdown field not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=152864 raal changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||r...@post.cz Ever confirmed|0 |1 --- Comment #2 from raal --- Confirm with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f65d7fb18c5b850a381727a67c97fc94128082d2 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108018] [META] Writer UX bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108018 Bug 108018 depends on bug 56258, which changed state. Bug 56258 Summary: FORMATTING: Default TABs for numbered list inappropriate, 2-digits Numbers exceed first TAB position https://bugs.documentfoundation.org/show_bug.cgi?id=56258 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103369 Bug 103369 depends on bug 56258, which changed state. Bug 56258 Summary: FORMATTING: Default TABs for numbered list inappropriate, 2-digits Numbers exceed first TAB position https://bugs.documentfoundation.org/show_bug.cgi?id=56258 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119224] Crash scrolling formatted 2007 DOCX with revision, comments and images (SfxListener::~SfxListener() EXCEPTION_ACCESS_VIOLATION_WRITE) ( steps in comment 8 )
https://bugs.documentfoundation.org/show_bug.cgi?id=119224 Commit Notification changed: What|Removed |Added Whiteboard|target:6.2.0 target:6.1.1 |target:6.2.0 target:6.1.1 ||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153092] text is missing inside and right side of image on docx on page 2
https://bugs.documentfoundation.org/show_bug.cgi?id=153092 raal changed: What|Removed |Added Component|Android Viewer |Writer OS|Android |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153092] text is missing inside and right side of image on docx on page 2
https://bugs.documentfoundation.org/show_bug.cgi?id=153092 raal changed: What|Removed |Added CC||caol...@redhat.com Keywords||bibisected, bisected Regression By||Caolán McNamara --- Comment #4 from raal --- This seems to have begun at the below commit. Adding Cc: to Caolán McNamara ; Could you possibly take a look at this one? Thanks 5e9e431b4a9bc67357adaf635c34bdfd3ee61321 is the first bad commit commit 5e9e431b4a9bc67357adaf635c34bdfd3ee61321 Author: Jenkins Build User Date: Thu Aug 18 20:45:42 2022 +0200 source sha:1fa731d03ba0f22cb9392a578124ea977eaab2e9 https://gerrit.libreoffice.org/c/core/+/138448 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150305] A marked Fontwork shape is not in 'Current Selection' in Development tools
https://bugs.documentfoundation.org/show_bug.cgi?id=150305 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from Stéphane Guillou (stragu) --- Thank you, Regina. Confirming. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150819] CRASH: after a few paste and undo
https://bugs.documentfoundation.org/show_bug.cgi?id=150819 --- Comment #4 from Telesto --- STR in my case 1. Open attached document 2. CTRL+A 3. CTRL+C 4. CTRL+V (5x) -> So with the text at step 2 still selected 5. Press and hold CTRL+Z (or press it one by one, timing doesn't matter) If I press 6x CTRL+V in step 4 it won't crash. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 37e3455a13ab5741104bf41d05a80e60a4612682 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153072] LibreOffice calc Text import does not display imported data preview
https://bugs.documentfoundation.org/show_bug.cgi?id=153072 Robert Großkopf changed: What|Removed |Added CC||rob...@familiegrosskopf.de --- Comment #6 from Robert Großkopf --- Have tested this one with OpenSUSE 15.3 64bit rpm Linux. Version: 7.4.4.2 / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Couldn't confirm the buggy behavior. Preview of the input will be shown when inserting using "Text import dialog". Did you try it with Help → Restart in Safe Mode ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153092] text is missing inside and right side of image on docx on page 2
https://bugs.documentfoundation.org/show_bug.cgi?id=153092 raal changed: What|Removed |Added CC||r...@post.cz Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords||regression --- Comment #3 from raal --- Works in Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.1 Calc: threaded but not in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f65d7fb18c5b850a381727a67c97fc94128082d2 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 149296, which changed state. Bug 149296 Summary: Crash libswlo.dylib`SwNodeIndex::GetNode(this=0x) const at ndindex.hxx:119:39 https://bugs.documentfoundation.org/show_bug.cgi?id=149296 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149296] Crash libswlo.dylib`SwNodeIndex::GetNode(this=0x0000000000000000) const at ndindex.hxx:119:39
https://bugs.documentfoundation.org/show_bug.cgi?id=149296 Telesto changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #4 from Telesto --- No issue Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 37e3455a13ab5741104bf41d05a80e60a4612682 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153097] FILESAVE: DOCX: value of content control not displayed in MSO after RT
https://bugs.documentfoundation.org/show_bug.cgi?id=153097 Xisco Faulí changed: What|Removed |Added Ever confirmed|0 |1 Keywords||bibisected, bisected, ||regression Status|UNCONFIRMED |NEW CC||noelgran...@gmail.com, ||xiscofa...@libreoffice.org --- Comment #1 from Xisco Faulí --- Regression introduced by: author Noel Grandin 2022-08-20 10:57:19 +0200 committer Noel Grandin 2022-08-22 09:35:31 +0200 commit db04b3e154a1fb8f32ef969bb3617e051329 (patch) tree84195e6f47abd82024127ced37405585df7708bb parent b2b3b4e833484aa70cb73b296bb62cdb0304eac9 (diff) return 64-bit hash for O[U]String Bisected with: bibisect-linux64-7.5 Adding Cc: to Noel Grandin -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112037] please add support for crash reporting
https://bugs.documentfoundation.org/show_bug.cgi?id=112037 --- Comment #3 from BEEDELL ROKE JULIAN LOCKHART --- Michael, I'm no Android application developer. However, crash reporting appears to be managed by Android at the OS level, since a consistent dialog box appears when applications crash, and because crash reporting is manageable via the Developer Options of Settings. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104524] [META] DOCX (OOXML) Table of Contents (ToC) and Index related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104524 Bug 104524 depends on bug 153083, which changed state. Bug 153083 Summary: FILEOPEN DOCX Localized style name not merged in TOC settings, unlike in Navigator style list https://bugs.documentfoundation.org/show_bug.cgi?id=153083 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153083] FILEOPEN DOCX Localized style name not merged in TOC settings, unlike in Navigator style list
https://bugs.documentfoundation.org/show_bug.cgi?id=153083 Michael Stahl (allotropia) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Keywords||filter:docx Resolution|--- |FIXED Assignee|libreoffice-b...@lists.free |michael.st...@allotropia.de |desktop.org | Whiteboard||target:7.6.0 --- Comment #1 from Michael Stahl (allotropia) --- sorry didn't notice there was a separate bug for this, was fixed with: Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ecbad22fdf81c6f072b6c9f9c16dbba47fe4748c tdf#153082 writerfilter: import locale-dependent TOC \t style names It will be available in 7.6.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 153087] When opening files, the message "Write error. Unable to write file."
https://bugs.documentfoundation.org/show_bug.cgi?id=153087 Julien Nabet changed: What|Removed |Added Version|7.4.3.2 release |7.4.2.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153087] When opening files, the message "Write error. Unable to write file."
https://bugs.documentfoundation.org/show_bug.cgi?id=153087 Julien Nabet changed: What|Removed |Added Version|7.4.2.3 release |7.4.3.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149363] Inserted table defaults to alternating-gray-rows regardless of template
https://bugs.documentfoundation.org/show_bug.cgi?id=149363 Eyal Rozenberg changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #2 from Eyal Rozenberg --- Indeed, the default has changed. The new default seems to be no-background. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104524] [META] DOCX (OOXML) Table of Contents (ToC) and Index related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104524 Bug 104524 depends on bug 153082, which changed state. Bug 153082 Summary: FILEOPEN DOCX List separator not considered with TOC using custom styles https://bugs.documentfoundation.org/show_bug.cgi?id=153082 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153082] FILEOPEN DOCX List separator not considered with TOC using custom styles
https://bugs.documentfoundation.org/show_bug.cgi?id=153082 Michael Stahl (allotropia) changed: What|Removed |Added Resolution|--- |FIXED CC||michael.st...@allotropia.de Status|NEW |RESOLVED Assignee|libreoffice-b...@lists.free |michael.st...@allotropia.de |desktop.org | --- Comment #8 from Michael Stahl (allotropia) --- there was an additional complication because "Intense Quote" is actually a built-in style. fixed on master -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91415] Improve design of comment indicators to block less of the cell's content
https://bugs.documentfoundation.org/show_bug.cgi?id=91415 Heiko Tietze changed: What|Removed |Added Keywords||accessibility -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91415] Improve design of comment indicators to block less of the cell's content
https://bugs.documentfoundation.org/show_bug.cgi?id=91415 --- Comment #6 from Heiko Tietze --- Created attachment 184764 --> https://bugs.documentfoundation.org/attachment.cgi?id=184764=edit Comparison 7.4 vs. Master I disagree with the statement that the indicator covers too much content. Adjusting the size depending on the zoom factor makes it smaller than today (the left part, at 50% zoom and scaled back here to ~100%). Plus, the text is always drawn on top of the indicator. Making it even smaller is possible but makes the comments harder to spot. Opinions? -- You are receiving this mail because: You are the assignee for the bug.
