[Libreoffice-bugs] [Bug 49705] Alignment "Justify" ignored when opening PDF files
https://bugs.documentfoundation.org/show_bug.cgi?id=49705 --- Comment #27 from Eyal Rozenberg --- (In reply to خالد حسني from comment #25) > PDF does not have paragraphs or lines let alone justification options. Text > in PDF is just a stream of absolutely positioned glyphs, it can come in any > order and formation as long as it gives the desired visual output. While that is true in one sense, in another sense, it's false: When we look at a PDF, we see paragraphs and justification. So they are there, they're just not expressed explicitly. > I don’t see LibreOffice ever being able to exactly replicate the PDF > text spacing. This bug is not about replicating the positioning exactly. It is about deciding which alignment the text in a line (or a paragraph, if/when we reconstitute paragraphs) has. We currently just choose "Left". Not "Right", not "Justified", not "Centered". It is quite doable to make a much better, and usually-correct, choice. To do so we need to: 1. Guesstimate where the text boundaries are for the page or part-of-the-page. 2. Determine how much extra space the paragraph has to its left and to its right. 3. Estimate whether the line is a list line on its paragraph 4. Try to decide whether the spacing of the words on the line is the result of adding extra inter-word space (justification) or not. Also determine the inter-glyph spacing and perhaps the glyph stretch factor (which can immediately be set for the text in the paragraph/line, if it's uniform at least.) 5. Try to decide whether the paragraph in its entirety is indented and/or has a first-line indent 6. Based on our determinations and guesstimates, set the indentation, alignment, and inter-word spacing for the paragraph. ... and that would typically come after deciding what the paragraph boundaries are; although some of it may need to be combined (e.g. distinguishing paragraphs by indents when there is no inter-paragraph spacing.) And I'll emphasize again that this may not always result in the correct reconstitution of paragraph alignment - but it will certainly be correct for typical cases (think: the formal letter you exported as a PDF), and correct for the large majority of cases. - > Short of > using the exact font with the exact glyphs and positioning every glyph > individually to match the PDF positioning (which essentially means putting > each glyph in its own text box, which I don’t think people will be thrilled > about), That's outside the scope of this bug. However, that's not what it means. You can very well set the spacing and stretch factors of individual glyphs within the same text box or on the same paragraph. And - that should definitely be an option when editing a PDF: Sometimes, what the user would want is a document that's easy to read, unladen with a zillion formatting and positioning specifications; but sometimes, what the user wants is a perfect reproduction of what the PDF looks like, to the extent LO is capable of doing so. The second case is for when one wants to make an edit to a PDF in LO (e.g. adding some text or a signature), and save the result - passing through LO should cause minimal distortion to the rendering of existing PDF content. (Also, in the Writer filter, we typically don't want textboxes anyway, and the text should just go in the body.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145958] LibreOffice start menu opens, but won't open any document, new or existing
https://bugs.documentfoundation.org/show_bug.cgi?id=145958 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #4 from Buovjaga --- (In reply to Buovjaga from comment #2) > (In reply to kara.l.anderso...@gmail.com from comment #0) > > "Try excluding soffice.bin from any AV (especially Defender) scanning. > > EDIT: Also try turning off Skia." > > - no change > > So can you confirm in Help - About you are not seeing Skia/Vulkan and the > problem persists? Renewing this request. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 49705] Alignment "Justify" ignored when opening PDF files
https://bugs.documentfoundation.org/show_bug.cgi?id=49705 --- Comment #26 from Eugene Saenko --- > I don’t see LibreOffice ever being able to exactly replicate the PDF text > spacing. This does not mean that LibreOffice should distort the PDF document. There is an example of successful work with a formatted PDF document. Master PDF Editor does a great job with this task. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51779] support for SQL datatype INTERVAL
https://bugs.documentfoundation.org/show_bug.cgi?id=51779 Buovjaga changed: What|Removed |Added Assignee|pragat.pan...@gmail.com |libreoffice-b...@lists.free ||desktop.org Status|ASSIGNED|NEW --- Comment #26 from Buovjaga --- Seems like Pragat is not active, so let's reset the assignee. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152670] When editing PDF file Hebrew is displayed as LTR instead of RTL, which makes editing impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=152670 --- Comment #3 from Sergei Steshenko --- Created attachment 184338 --> https://bugs.documentfoundation.org/attachment.cgi?id=184338=edit Source file used to create the two earlier sent attachments Source file used to create earlier sent 'table_with_hebrew.png' and 'table_with_hebrew.pdf' files. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152670] When editing PDF file Hebrew is displayed as LTR instead of RTL, which makes editing impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=152670 --- Comment #2 from Sergei Steshenko --- Created attachment 184337 --> https://bugs.documentfoundation.org/attachment.cgi?id=184337=edit PDF file used to demonstrate the bug Lower part of earlier sent'table_with_hebrew.png' file was created using this PDF file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152670] When editing PDF file Hebrew is displayed as LTR instead of RTL, which makes editing impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=152670 Sergei Steshenko changed: What|Removed |Added CC||sergst...@yahoo.com --- Comment #1 from Sergei Steshenko --- Created attachment 184336 --> https://bugs.documentfoundation.org/attachment.cgi?id=184336=edit Screenshot showing the problem Upper part of the screenshot shows how the text should look, i.e. the correct RTL; lower part of the table shows how the text actually looks, i.e. wrong LTR. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152670] New: When editing PDF file Hebrew is displayed as LTR instead of RTL, which makes editing impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=152670 Bug ID: 152670 Summary: When editing PDF file Hebrew is displayed as LTR instead of RTL, which makes editing impossible Product: LibreOffice Version: 7.4.2.3 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sergst...@yahoo.com Description: If I try to edit a PDF file whose contents are in Hebrew, words are displayed as LTR (Left To Right) instead of the required RTL (Right To Left). I.e. order of Hebrew letters in words is reversed, and it makes editing the PDF file impossible. Steps to Reproduce: 1. Open the attached 'table_with_hebrew.pdf' file and see for yourselves. 2. 3. Actual Results: Hebrew words are displayed with letters in reverse order, i.e. Hebrew is displayed as LRT instead of RTL language. Expected Results: Hebrew words should be displayed as RTL, i.e. letters should be displayed from right to left. Reproducible: Always User Profile Reset: Yes Additional Info: Letters in Hebrew words should be displayed RTL. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121938] PDF import: Romanian special characters not shown
https://bugs.documentfoundation.org/show_bug.cgi?id=121938 --- Comment #19 from BogdanB --- I can NOT repro with Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: ad085990b8073a122ac5222e5220f8f1d6826dcf CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Also I can NOT repro with Version: 7.4.0.2 / LibreOffice Community Build ID: 1512ce97d7ed39dce3121f7e15651fd8895f950e CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded But I have to mention that I have ttf-mscorefonts-installer (Microsoft Fonts) installed on my Linux computer. (sudo add-apt-repository multiverse AND sudo apt update && sudo apt install ttf-mscorefonts-installer) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145138] Non breaking space not inserted from keyboard shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=145138 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de Ever confirmed|0 |1 --- Comment #3 from Dieter --- Rüssel, can you still reproduce the problem in an actual version of LO? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152649] Crash with activated SKIA Option
https://bugs.documentfoundation.org/show_bug.cgi?id=152649 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 152450] PostgreSQL JDBC: Creating query - table alias is always appended by GUI, special settings wont work here
https://bugs.documentfoundation.org/show_bug.cgi?id=152450 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 152649] Crash with activated SKIA Option
https://bugs.documentfoundation.org/show_bug.cgi?id=152649 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149720] Crash in: SwLayoutFrame::IsAnLower(SwFrame const *)
https://bugs.documentfoundation.org/show_bug.cgi?id=149720 --- Comment #2 from QA Administrators --- Dear Ainhoa, 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 149746] Crash in: SfxApplication::GetAppDispatcher_Impl()
https://bugs.documentfoundation.org/show_bug.cgi?id=149746 --- Comment #3 from QA Administrators --- Dear Ainhoa, 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 99982] FILE SAVE: formatting (and copy of formatting to new file) (from specific file) and save as XSLX give error by opening in excel
https://bugs.documentfoundation.org/show_bug.cgi?id=99982 --- Comment #18 from QA Administrators --- Dear VLB, 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 149504] incorrect import/insertion of datetime value into Calc using ctrl-shift-alt-v (Date (YMD) format is selected)
https://bugs.documentfoundation.org/show_bug.cgi?id=149504 --- Comment #5 from QA Administrators --- Dear kabilo, 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 99921] EDITING: file save as XLSX give error-by page formatting pagestyle
https://bugs.documentfoundation.org/show_bug.cgi?id=99921 --- Comment #14 from QA Administrators --- Dear VLB, 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 96616] FILESAVE: Generating a report as "Microsoft Word 2007-2013 XML" creates .odt with .docx extension
https://bugs.documentfoundation.org/show_bug.cgi?id=96616 --- Comment #11 from QA Administrators --- Dear Sparrowbe, 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 93391] Selected text disabled in Table Data View after left/right cursor movement
https://bugs.documentfoundation.org/show_bug.cgi?id=93391 --- Comment #12 from QA Administrators --- Dear Stang, 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 94720] After merging the cells in the table containing the last row and selecting as column you can not format the cell contents (as if read-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=94720 --- Comment #13 from QA Administrators --- Dear Roman Kuznetsov, 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 139114] FILEOPEN HTML: Content going off page in document view (instead of adjusting to page size)
https://bugs.documentfoundation.org/show_bug.cgi?id=139114 --- Comment #3 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 133536] Links to external files in a Calc table integrated in a Writer document can no longer be updated (steps in comment 11)
https://bugs.documentfoundation.org/show_bug.cgi?id=133536 --- Comment #16 from QA Administrators --- Dear Lothar Viel, 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 122044] Doesn't save merging of cells after copy/paste table from Calc to table in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=122044 --- Comment #6 from QA Administrators --- Dear Roman Kuznetsov, 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 108058] After renaming Primary Key AutoValue feature fails
https://bugs.documentfoundation.org/show_bug.cgi?id=108058 --- Comment #7 from QA Administrators --- Dear Howard Johnson, 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 106932] Impossible to select with mouse entire table rows when vertical Merges are present in the last column (Workaround: Ctrl+Shift+End)
https://bugs.documentfoundation.org/show_bug.cgi?id=106932 --- Comment #7 from QA Administrators --- Dear Jim Avera, 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 109529] FORMATTING - Column inserts even with information in A1 & AMJ1
https://bugs.documentfoundation.org/show_bug.cgi?id=109529 --- Comment #8 from QA Administrators --- Dear Stang, 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 109412] FORMATTING - Column Insert does not always insert a New column
https://bugs.documentfoundation.org/show_bug.cgi?id=109412 --- Comment #8 from QA Administrators --- Dear Stang, 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 151548] No access to FormField controls in StarBASIC/VBA
https://bugs.documentfoundation.org/show_bug.cgi?id=151548 --- Comment #29 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/24b969d10cd81e6f5eb438ded075dd330a1cde29 tdf#151548 DOCX formfield: export checkbox name 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-commits] core.git: include/xmloff sw/qa sw/source
include/xmloff/odffields.hxx |1
sw/qa/extras/ooxmlexport/data/tdf151548_activeContentDemo.docm |binary
sw/qa/extras/ooxmlexport/ooxmlexport8.cxx | 12
++
sw/source/filter/ww8/docxattributeoutput.cxx |4 ---
sw/source/filter/ww8/ww8par3.cxx |1
5 files changed, 13 insertions(+), 5 deletions(-)
New commits:
commit 24b969d10cd81e6f5eb438ded075dd330a1cde29
Author: Justin Luth
AuthorDate: Sat Dec 24 14:15:51 2022 -0500
Commit: Justin Luth
CommitDate: Sun Dec 25 02:58:56 2022 +
tdf#151548 DOCX formfield: export checkbox name
The two other fields are exporting the name,
(although it is getting somewhat lost in excess bookmarks),
because they are just using the Fieldmark name property.
See LO 7.5 8ad39b6f2aff3ca37aeff5373991e853c329
for tdf#151548 sw: use provided name for formfields
which saved the name for checkboxes and dropdowns.
ODF_FORMCHECKBOX_NAME was simply used as a grabbag
for ww8import. Since that is obsolete, get rid of it.
mostly introduced with ---
commit b547c0c2aa901667fef85233282ec84f34b7e5f4
Author: Noel Power on Thu Feb 10 16:18:40 2011 +
some form field import/export improvements
ODF_FORMDROPDOWN_NAME was dropped early on. ---
commit 79770ff55bd8c3bc5948c51373e8cb7867ce43d3
Author: Noel Power on Tue Mar 1 12:30:23 2011 +
partial revert of 803409125f4ed896b391acb99266d50691c6fd4a
remove currently unnecessary ( but possibly future )
odf attributes for form field controls to prevent those
attributes from being written to odf
Change-Id: I133028dce65361314e663bb5238f99c607f0ab14
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144792
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/include/xmloff/odffields.hxx b/include/xmloff/odffields.hxx
index 8dd75e038189..d5439d873a0f 100644
--- a/include/xmloff/odffields.hxx
+++ b/include/xmloff/odffields.hxx
@@ -27,7 +27,6 @@ inline constexpr OUStringLiteral ODF_FORMTEXT =
u"vnd.oasis.opendocument.field.F
inline constexpr OUStringLiteral ODF_FORMCHECKBOX =
u"vnd.oasis.opendocument.field.FORMCHECKBOX";
inline constexpr OUStringLiteral ODF_FORMCHECKBOX_HELPTEXT =
u"Checkbox_HelpText";
-inline constexpr OUStringLiteral ODF_FORMCHECKBOX_NAME = u"Checkbox_Name";
inline constexpr OUStringLiteral ODF_FORMCHECKBOX_RESULT = u"Checkbox_Checked";
inline constexpr OUStringLiteral ODF_FORMDROPDOWN =
u"vnd.oasis.opendocument.field.FORMDROPDOWN";
diff --git a/sw/qa/extras/ooxmlexport/data/tdf151548_activeContentDemo.docm
b/sw/qa/extras/ooxmlexport/data/tdf151548_activeContentDemo.docm
new file mode 100644
index ..80886d864a15
Binary files /dev/null and
b/sw/qa/extras/ooxmlexport/data/tdf151548_activeContentDemo.docm differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport8.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport8.cxx
index 4378f3b1a0c7..bccfbddb7eb0 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport8.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport8.cxx
@@ -1046,6 +1046,18 @@ DECLARE_OOXMLEXPORT_TEST(testN820509, "n820509.docx")
}
}
+DECLARE_OOXMLEXPORT_TEST(testTdf151548_activeContentDemo,
"tdf151548_activeContentDemo.docm")
+{
+SwXTextDocument* pTextDoc = dynamic_cast(mxComponent.get());
+SwDoc* pDoc = pTextDoc->GetDocShell()->GetDoc();
+IDocumentMarkAccess* pMarkAccess = pDoc->getIDocumentMarkAccess();
+for(auto aIter = pMarkAccess->getFieldmarksBegin(); aIter !=
pMarkAccess->getFieldmarksEnd(); ++aIter)
+{
+const OUString sName = (*aIter)->GetName();
+CPPUNIT_ASSERT(sName == "Check1" || sName == "Text1" || sName ==
"Dropdown1");
+}
+}
+
DECLARE_OOXMLEXPORT_TEST(testN830205, "n830205.docx")
{
// Previously import just crashed (due to infinite recursion).
diff --git a/sw/source/filter/ww8/docxattributeoutput.cxx
b/sw/source/filter/ww8/docxattributeoutput.cxx
index 0bc7e87f1469..a30cabad7ea7 100644
--- a/sw/source/filter/ww8/docxattributeoutput.cxx
+++ b/sw/source/filter/ww8/docxattributeoutput.cxx
@@ -2263,11 +2263,9 @@ void DocxAttributeOutput::WriteFFData( const
FieldInfos& rInfos )
}
else if ( rInfos.eType == ww::eFORMCHECKBOX )
{
-OUString sName;
+const OUString sName = params.getName();
bool bChecked = false;
-params.extractParam( ODF_FORMCHECKBOX_NAME, sName );
-
const sw::mark::ICheckboxFieldmark* pCheckboxFm = dynamic_cast();
if ( pCheckboxFm && pCheckboxFm->IsChecked() )
bChecked = true;
diff --git a/sw/source/filter/ww8/ww8par3.cxx b/sw/source/filter/ww8/ww8par3.cxx
index 445e5442a0fe..451cae7b2778 100644
--- a/sw/source/filter/ww8/ww8par3.cxx
+++ b/sw/source/filter/ww8/ww8par3.cxx
@@ -231,7 +231,6 @@ eF_ResT SwWW8ImplReader::Read_F_FormCheckBox( WW8FieldDesc*
pF, OUString&
[Libreoffice-bugs] [Bug 49705] Alignment "Justify" ignored when opening PDF files
https://bugs.documentfoundation.org/show_bug.cgi?id=49705 --- Comment #25 from خالد حسني --- PDF does not have paragraphs or lines let alone justification options. Text in PDF is just a stream of absolutely positioned glyphs, it can come in any order and formation as long as it gives the desired visual output. Short of using the exact font with the exact glyphs and positioning every glyph individually to match the PDF positioning (which essentially means putting each glyph in its own text box, which I don’t think people will be thrilled about), I don’t see LibreOffice ever being able to exactly replicate the PDF text spacing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82163] sdext.pdfimport: xpdfimport failed to detect certain characters in the attached PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=82163 خالد حسني changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|NEW |RESOLVED --- Comment #23 from خالد حسني --- The magazine title is not embedded as text, but as a logo split into 5 glyphs and the Unicode mapping for them gives: 34567, so there is nothing we can do here to get the actual text for the title since the PDF does not have it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 Bug 99746 depends on bug 82163, which changed state. Bug 82163 Summary: sdext.pdfimport: xpdfimport failed to detect certain characters in the attached PDF https://bugs.documentfoundation.org/show_bug.cgi?id=82163 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152669] Some ruled lines in the table are not set when writing vertically.
https://bugs.documentfoundation.org/show_bug.cgi?id=152669 --- Comment #1 from Saburo --- Created attachment 184335 --> https://bugs.documentfoundation.org/attachment.cgi?id=184335=edit image -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152669] New: Some ruled lines in the table are not set when writing vertically.
https://bugs.documentfoundation.org/show_bug.cgi?id=152669 Bug ID: 152669 Summary: Some ruled lines in the table are not set when writing vertically. Product: LibreOffice Version: 7.3.1.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: yosi3260+li...@gmail.com Description: The horizontal lines on both ends of the table are not set. Steps to Reproduce: 1.[Format]-[Page Style]-[Page]-[Text direction]:Right-to-Left(Vertical) 2.[Table]-[Insert Table] Columns:4 Rows:4 (Insert) 3.[Table Properties]dialog [Borders]-LineArrangement preset:"OuterBorder and inner all lines" Actual Results: The horizontal lines on both ends of the table are not set. Expected Results: I wanted you to draw a line on both ends of the column Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: cfc73f3373f49770b859bc68cbf6bd987342f9ad CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: ja-JP (ja_JP); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91666] PDF: Broken import of non-BMP characters
https://bugs.documentfoundation.org/show_bug.cgi?id=91666 خالد حسني changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #12 from خالد حسني --- The PDF is broken, there is no ToUnicode mapping the glyphs to input text and the textual content can’t be properly extracted. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 Bug 99746 depends on bug 91666, which changed state. Bug 91666 Summary: PDF: Broken import of non-BMP characters https://bugs.documentfoundation.org/show_bug.cgi?id=91666 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: include/editeng sw/CppunitTest_sw_core_theme.mk sw/Module_sw.mk sw/qa sw/source writerfilter/source xmloff/inc xmloff/source
include/editeng/unoprnms.hxx |2 sw/CppunitTest_sw_core_theme.mk | 62 ++ sw/Module_sw.mk |1 sw/qa/core/theme/ThemeTest.cxx| 35 ++ sw/qa/core/theme/data/ThemeColorInHeading.docx|binary sw/source/core/unocore/unomap.cxx |4 - sw/source/core/unocore/unomap1.cxx|6 + sw/source/core/unocore/unomapproperties.hxx |6 + sw/source/uibase/sidebar/ThemePanel.cxx | 29 ++-- sw/source/uibase/sidebar/WriterInspectorTextPanel.cxx | 14 ++-- writerfilter/source/dmapper/DomainMapper.cxx | 16 writerfilter/source/dmapper/PropertyIds.cxx |2 writerfilter/source/dmapper/PropertyIds.hxx |2 writerfilter/source/dmapper/TDefTableHandler.cxx | 44 writerfilter/source/dmapper/TDefTableHandler.hxx |1 xmloff/inc/XMLThemeColorHandler.hxx | 49 ++ xmloff/inc/enummaps.hxx |2 xmloff/source/draw/sdpropls.cxx |3 xmloff/source/text/txtprhdl.cxx |6 + 19 files changed, 254 insertions(+), 30 deletions(-) New commits: commit df9f3f3fd81d4f81ee2ff984d1e1abea2963 Author: Tomaž Vajngerl AuthorDate: Sun Sep 20 19:27:09 2015 +0200 Commit: Tomaž Vajngerl CommitDate: Sun Dec 25 02:06:58 2022 + sw: support for reading back theme color from OOXML OOXML supports theme colors and tint/shade value that additionally changed the theme color. Read back which theme color + tint/shade value was applied in the resulting color and add this attributes as properties to be used by writer. In sidebar theme panel the changing the theme colors now doesn't takes this into account and changes the colors correctly. Change-Id: I3a2d49d485fd37a1611483ee0bb5e6034ac5f88e Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143697 Tested-by: Jenkins Reviewed-by: Tomaž Vajngerl diff --git a/include/editeng/unoprnms.hxx b/include/editeng/unoprnms.hxx index 0df739ee5285..8569a3370464 100644 --- a/include/editeng/unoprnms.hxx +++ b/include/editeng/unoprnms.hxx @@ -21,6 +21,8 @@ #include inline constexpr OUStringLiteral UNO_NAME_CHAR_COLOR = u"CharColor"; +inline constexpr OUStringLiteral UNO_NAME_CHAR_COLOR_THEME = u"CharColorTheme"; +inline constexpr OUStringLiteral UNO_NAME_CHAR_COLOR_TINT_OR_SHADE = u"CharColorTintOrShade"; inline constexpr OUStringLiteral UNO_NAME_CHAR_HEIGHT = u"CharHeight"; inline constexpr OUStringLiteral UNO_NAME_CHAR_POSTURE = u"CharPosture"; inline constexpr OUStringLiteral UNO_NAME_CHAR_SHADOWED = u"CharShadowed"; diff --git a/sw/CppunitTest_sw_core_theme.mk b/sw/CppunitTest_sw_core_theme.mk new file mode 100644 index ..84b462ea8245 --- /dev/null +++ b/sw/CppunitTest_sw_core_theme.mk @@ -0,0 +1,62 @@ +# -*- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t -*- +#* +# +# This file is part of the LibreOffice project. +# +# This Source Code Form is subject to the terms of the Mozilla Public +# License, v. 2.0. If a copy of the MPL was not distributed with this +# file, You can obtain one at http://mozilla.org/MPL/2.0/. +# +#* + +$(eval $(call gb_CppunitTest_CppunitTest,sw_core_theme)) + +$(eval $(call gb_CppunitTest_use_common_precompiled_header,sw_core_theme)) + +$(eval $(call gb_CppunitTest_add_exception_objects,sw_core_theme, \ +sw/qa/core/theme/ThemeTest \ +)) + +$(eval $(call gb_CppunitTest_use_libraries,sw_core_theme, \ +comphelper \ +cppu \ +cppuhelper \ +sal \ +sfx \ +subsequenttest \ +sw \ +swqahelper \ +test \ +unotest \ +utl \ +vcl \ +svt \ +tl \ +svl \ +svxcore \ +)) + +$(eval $(call gb_CppunitTest_use_externals,sw_core_theme,\ +boost_headers \ +libxml2 \ +)) + +$(eval $(call gb_CppunitTest_set_include,sw_core_theme,\ +-I$(SRCDIR)/sw/inc \ +-I$(SRCDIR)/sw/source/core/inc \ +-I$(SRCDIR)/sw/source/uibase/inc \ +-I$(SRCDIR)/sw/qa/inc \ +$$(INCLUDE) \ +)) + +$(eval $(call gb_CppunitTest_use_api,sw_core_theme,\ +udkapi \ +offapi \ +)) + +$(eval $(call gb_CppunitTest_use_ure,sw_core_theme)) +$(eval $(call gb_CppunitTest_use_vcl,sw_core_theme)) +$(eval $(call gb_CppunitTest_use_rdb,sw_core_theme,services)) +$(eval $(call gb_CppunitTest_use_configuration,sw_core_theme)) + +# vim: set noet sw=4 ts=4: diff --git a/sw/Module_sw.mk b/sw/Module_sw.mk index 8a217a85fbf6..a15763330763 100644 --- a/sw/Module_sw.mk +++ b/sw/Module_sw.mk @@ -154,6 +154,7 @@ $(eval $(call gb_Module_add_slowcheck_targets,sw,\ CppunitTest_sw_filter_ww8 \ CppunitTest_sw_filter_html \
[Libreoffice-bugs] [Bug 121938] PDF import: Romanian special characters not shown
https://bugs.documentfoundation.org/show_bug.cgi?id=121938 --- Comment #18 from خالد حسني --- I can reproduce this issue with any of the attached PDFs, any one else can reproduce? Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 10; OS: Mac OS X 13.0.1; UI render: default; VCL: osx Locale: en-US (en_EG.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151788] Imported Arabic/Persian text from PDF should go through unshaping Algorithm
https://bugs.documentfoundation.org/show_bug.cgi?id=151788
خالد حسني changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #2 from خالد حسني ---
For the purpose of this, I think applying NFKC normalization to the text should
be enough:
>>> unicodedata.normalize("NFKC", "ﺿ ﻤ ﯿ ﻤ ﻪ")
'ض م ی م ه'
But NFKC normalization can change text meaning for other Unicode code points,
so it should be applied to Arabic Presentation Forms characters exclusively.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 خالد حسني changed: What|Removed |Added Depends on||149457 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149457 [Bug 149457] Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149457] Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=149457 خالد حسني changed: What|Removed |Added Blocks||99746 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99746 [Bug 99746] [META] PDF import filter in Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 خالد حسني changed: What|Removed |Added Depends on||131902 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=131902 [Bug 131902] Arabic language is messed up in imported PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131902] Arabic language is messed up in imported PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=131902 خالد حسني changed: What|Removed |Added Blocks||99746 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99746 [Bug 99746] [META] PDF import filter in Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL
https://bugs.documentfoundation.org/show_bug.cgi?id=151473 خالد حسني changed: What|Removed |Added Blocks||99746 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99746 [Bug 99746] [META] PDF import filter in Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 خالد حسني changed: What|Removed |Added Depends on||151473 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151473 [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL
https://bugs.documentfoundation.org/show_bug.cgi?id=151473 --- Comment #7 from خالد حسني --- (In reply to Kevin Suo from comment #5) > There seems to already be a fix on the Apache OpenOffice, see the > m_aMirrorMap in PDFIProcessor::prepareMirrorMap(): > http://opengrok.openoffice.org/xref/trunk/main/sdext/source/pdfimport/tree/ > pdfiprocessor.cxx?r=c142477c > > Not sure whether it is OK to "borrow" some of its code. Is there any license > issue? At what extent shall we use it? That is already what u_charMirror() does. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Bug 43808 depends on bug 151473, which changed state. Bug 151473 Summary: Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL https://bugs.documentfoundation.org/show_bug.cgi?id=151473 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL
https://bugs.documentfoundation.org/show_bug.cgi?id=151473 خالد حسني changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #6 from خالد حسني --- I don’t think there is a bug here. The Latin-script text in the ODT is: ABC) DEF) It looks differently because it is part of a RTL paragraph. When imported, parts of the text ends in different text boxes because they use different fonts, but if you select all the boxes in the line and right click -> Consolidate Text, you get the same rendering as in Writer since they are now in one text box. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143095] Draw and Writer PDF import: the fonts are shown in postscript names (PS names) rather than localized font family names
https://bugs.documentfoundation.org/show_bug.cgi?id=143095 --- Comment #19 from خالد حسني --- (In reply to خالد حسني from comment #17) > (In reply to V Stuart Foote from comment #16) > > (In reply to خالد حسني from comment #15) > > > If you have acess the the actual font data embedded in the PDF, most > > > likely > > > the full name is their as well, either in the “name” table of the TTF > > > fonts > > > or in the TopDICT of CFF/Type1 fonts. We probably have code to parse these > > > somewhere in vcl/source/fontsubset/. > > > > I've uncompressed a few PDFs and all pretty consistently have a /BaseFont > > that collapses the font name to the PS flavor. There is usually a single > > /Fontfamily stanza, but not clear that is granular enough for parsing the > > correct font details out of the CMAP or toUnicode entries we depend on. > > > > AFAICS Kevin's font equiv lookup seems necessary... > > The font data is stored in binary format inside the PDF file, you wont see > much in the uncompressed PDF. Try opening the PDF in FontForge, it might be > able to extract the embedded fonts, or use a tool like mutool to extract the > fonts if you want to manually examine them. The PDF font descriptor can also (optionally) include font family and font weight, so if present they should be used over the PostScript name that is currently used. Apparently not many tools write these to the PDF, including LibreOffice itself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Patrick Luby changed: What|Removed |Added Assignee|plub...@neooffice.org |libreoffice-b...@lists.free ||desktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 Bug 99746 depends on bug 151525, which changed state. Bug 151525 Summary: FILEOPEN: LibreOffice Draw renders emojis from some PDFs as the Unicode Replacement Character '�' https://bugs.documentfoundation.org/show_bug.cgi?id=151525 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151525] FILEOPEN: LibreOffice Draw renders emojis from some PDFs as the Unicode Replacement Character '�'
https://bugs.documentfoundation.org/show_bug.cgi?id=151525 خالد حسني changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|NEW |RESOLVED --- Comment #13 from خالد حسني --- The PDF is actually broken, the ToUnicode of the emoji font embedded in the PDF maps everything to U+FFFD (�), so the text representation is unrecoverable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 Bug 99746 depends on bug 148980, which changed state. Bug 148980 Summary: sdext xpdfimport (poppler): Garbage characters shown when open certain PDF in Draw https://bugs.documentfoundation.org/show_bug.cgi?id=148980 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148980] sdext xpdfimport (poppler): Garbage characters shown when open certain PDF in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=148980 خالد حسني changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|NEW |RESOLVED --- Comment #5 from خالد حسني --- The PDF contains mangled text; surrogate pairs are all missing the low surrogate part, making the original text unrecoverable. Garbage in, garbage out. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145988] macOS skia: colors not displayed correctly for all document previews e.g. start center or impress templates
https://bugs.documentfoundation.org/show_bug.cgi?id=145988 --- Comment #53 from Patrick Luby --- I think that I have narrowed down this bug to drawing 24 bit bitmaps that have an 8 bit alpha bitmap in SkiaSalGraphicsImpl::drawAlphaBitmap(). By default, that method calls SkiaSalGraphicsImpl::mergeCacheBitmaps() which combines the 24 bitand the alpha bitmaps into a single bitmap. My current theory is that SkiaSalGraphicsImpl::mergeCacheBitmaps() is doing something unexpected on some machines. I have posted the following patch that prints out some debugging data that I am hoping will narrow down the what is causing this bug: https://gerrit.libreoffice.org/c/core/+/144814/2 If anyone who is experiencing this bug and has a LibreOffice build is willing test out the above patch, can you apply the patch, make, and then do the following steps and post all of the "warn:vcl.skia.debug" messages that appear in the Terminal?: export SAL_DISABLE_SKIA_BITMAP_MERGE=1 ./instdir/LibreOfficeDev.app/Contents/MacOS/soffice 2>&1 | grep vcl.skia.debug When LibreOffice launches, open the About dialog, then quit. In addition to the Terminal messages, can you tell me if the large images in the About dialog are still colorshifted like in attachment 176623? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150582] Words with smart quotes/apostrophes get added to custom dictionaries via Writer but not Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=150582 xordevore...@gmail.com changed: What|Removed |Added CC||xordevore...@gmail.com Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152668] CALC sometimes hangs after selecting multiple cells to be copied
https://bugs.documentfoundation.org/show_bug.cgi?id=152668 --- Comment #1 from lee@gmail.com --- This problem may be similar to the one reported in Bug 99623 which was due to a 3rd-party clipboard manager. I am doing more analysis and will update with my findings. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152659] Lock up then crash
https://bugs.documentfoundation.org/show_bug.cgi?id=152659 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> --- Try disable Skia in Tools-Options-LibreOffice-View dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152668] New: CALC sometimes hangs after selecting multiple cells to be copied
https://bugs.documentfoundation.org/show_bug.cgi?id=152668 Bug ID: 152668 Summary: CALC sometimes hangs after selecting multiple cells to be copied Product: LibreOffice Version: 7.3.0.3 release Hardware: IA64 (Itanium) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lee@gmail.com Description: Sometimes when I select multiple cells (using the SHIFT key), calc goes into an infinite loop. This happens on many different spreadsheets. After restarting CALC, it fails to recover any of the changes made to the document prior to the hang. I encounter this about once a day, and has been a problem on multiple versions of LO. The problem is not reliably reproducible. Is there any information I can obtain to help diagnose this problem? Thank you! Steps to Reproduce: 1.Select two adjacent cells using SHIFT key (vertical or horizontal) 2.CALC goes into infinite loop (spinning color wheel) 3. Actual Results: See above. Expected Results: CALC should not hang. Reproducible: Sometimes User Profile Reset: Yes Additional Info: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Mac OS X 12.6.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded This problem also happens in Safe Mode. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152667] New: Wrong text encoding for file names and clip board under KDE x11
https://bugs.documentfoundation.org/show_bug.cgi?id=152667 Bug ID: 152667 Summary: Wrong text encoding for file names and clip board under KDE x11 Product: LibreOffice Version: 7.4.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tianer2...@outlook.com Description: When opening a file with Chinese characters in its name, the file name displayed on the title bar becomes some random codes. When pasting Chinese characters from the clipboard, it becomes random codes. Steps to Reproduce: 1. Open LibreOffice Write, save the file as "test 测试 123.odt" 2. The title bar displays "test æµè¯ 123.odt" 3. Now, copy the string "test 测试 123" to KWrite first so it becomes pure text without any html formatting 4. Copy the string again from KWrite to LibreOffice Write, it becomes some random codes. Actual Results: Strings with Chinese characters become random codes. Expected Results: The pasted string should be the same. Reproducible: Always User Profile Reset: Yes Additional Info: - This only happens under KDE X11. KDE Wayland works as expected. - Copy & paste from browsers or from LibreOffice itself works as expected, but any pure strings from text editor or file browser goes wrong. - Looks like LibreOffice is not using the correct encoding for pasting those strings. System Info: Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.14-300.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-9300HF CPU @ 2.40GHz Memory: 7.7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 Manufacturer: LENOVO Product Name: 81T0 System Version: Legion Y7000 2019 PG0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149731] Crash Report 5c0ae914-0d0e-42b1-bee0-2b611fff0b00
https://bugs.documentfoundation.org/show_bug.cgi?id=149731 Jim Robinson 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 152440] BOOK VIEW: Switching page view to book view or from book view results in a switch to a semi-random page
https://bugs.documentfoundation.org/show_bug.cgi?id=152440 V Stuart Foote changed: What|Removed |Added CC||rayk...@gmail.com, ||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- @Jim, any hints to make this easy-hackable? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145958] LibreOffice start menu opens, but won't open any document, new or existing
https://bugs.documentfoundation.org/show_bug.cgi?id=145958 --- Comment #3 from Tammy --- I am unable to reproduce the bug in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 780d55199e54fafc3784691d5cf716c1bb92b0aa CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 22621; 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 105263] FILEOPEN PDF Image placement incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=105263 Rajasekaran Karunanithi changed: What|Removed |Added CC||rajasekara...@gmail.com --- Comment #7 from Rajasekaran Karunanithi --- Still reproducable in L.O 7.6 Dev under Windows 10(x64). Images shown incorrectly in Draw. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ad387d5b984c906505d25685065f710ed55d CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102959] Formula not rotated in exported SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=102959 Rajasekaran Karunanithi changed: What|Removed |Added CC||rajasekara...@gmail.com --- Comment #14 from Rajasekaran Karunanithi --- Still reproducable in LO 7.6 Dev under Windows 10(x64). Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ad387d5b984c906505d25685065f710ed55d CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152663] The fonts in STIX MathJax Size1 for Libreoffice math, especially the integral signs, are not centered according to the line of the expression.
https://bugs.documentfoundation.org/show_bug.cgi?id=152663 خالد حسني changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152663] The fonts in STIX MathJax Size1 for Libreoffice math, especially the integral signs, are not centered according to the line of the expression.
https://bugs.documentfoundation.org/show_bug.cgi?id=152663 --- Comment #1 from خالد حسني --- Please attach document and screenshots demonstrating the issue. Please also note that these fonts are probably specifically build to be used with MathJax and may not be suitable for use in other environments. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90796] [META] HiDPI / Retina bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=90796 Bug 90796 depends on bug 150177, which changed state. Bug 150177 Summary: macOS Wildly blinking cursor and non-visible selection issues https://bugs.documentfoundation.org/show_bug.cgi?id=150177 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=42082 Bug 42082 depends on bug 150177, which changed state. Bug 150177 Summary: macOS Wildly blinking cursor and non-visible selection issues https://bugs.documentfoundation.org/show_bug.cgi?id=150177 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
Re: Subject : Help regarding Bug 90341 - Clean up excessive const_cast'ing
On 24.12.2022 13.42, Siddharth Khattar wrote: Hello, So I did all the recommended changes that were commented in the code in the file "impastpl.cxx" but Jenkins is still giving me a build error. Can someone please help me with it, the link to it on Gerrit is: https://gerrit.libreoffice.org/c/core/+/144537 I tried a further commit and investigated a few things by changing some static_cast back to const_cast but couldn't figure it out, unfortunately. For reference, The easy hack I'm referring to is: https://bugs.documentfoundation.org/show_bug.cgi?id=90341 Without commenting on the content of the changes, your problem is that you have created a series of patches. The expectation is that for a task like this, you keep updating the single patch. In your latest patch I also commented about this: https://gerrit.libreoffice.org/c/core/+/144790 You should look at 'git log', see how many of your own commits you have and then say git reset --soft HEAD~x where x is the number of your own commits minus one. Now you have all your modifications ready to commit with 'git commit --amend' and they will go toward your first patch which should be this: https://gerrit.libreoffice.org/c/core/+/144374 When editing the commit message, double-check that the Change-Id is Change-Id: I8a3d7c6695dea16536f1a0ed2c27fbedeb8d Finally './logerrit submit master' to submit the new patchset. Ilmari
[Libreoffice-bugs] [Bug 152666] New: Hiiding unwanted styles in the Toolbar Formatting - Paragraph Style select doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=152666 Bug ID: 152666 Summary: Hiiding unwanted styles in the Toolbar Formatting - Paragraph Style select doesn't work Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: th...@gmx.com Description: I have created my own styles which I use all the time, but I cannot remove some of the styles in the drop down list, which means every time I want to use my styles i have to select the "more styles". This is inhibiting my effectiveness. I have tried hiding all the styles I don't use but they still appear on the list. This is very frustrating. The best solution would be to make the paragraph styles fully customisable in what we want to appear in that drop down list. I don't use or ever want to see quotations, subtitle, preformatted text or Headings 1,2,3, or 4. It would also work much better if the list could also have a scroll bar so that we don't have to show more styles Steps to Reproduce: 1.In the formatting Tool bar have the "paragraph styles select box. 2.try hiding all the styles so you only see the custom styles you have created... I have 30 custom styles. I only want to use those styles. Actual Results: I have hidden all the styles in the sets of list Chapter, List,Index, Special. Default Paragraph style cant be hidden obviously, but in HTML style the following I have hidden are still appearing in that list.: Default Paragraph, Endnote, Footnote, Heading, Heading 1,2,3,4,5,6, Sender, Table Content, Table Heading and Text Body Text Styles continues to show Heading 4.Conditional Styles shows text body, Automatic shows Heading 4. The main drop down list from the box" paragraph styles" still shows: Default Paragraph style, Text Body,Title,Subtitle, Heading 1,2,3,4,Quotations, and preformatted text. Expected Results: After that I created a template and removed all instances of any paragraph style formatting in the document. I made sure I hid all the styles except my custom ones and I expected to see the drop down select list to reflect this. It did not. I expect styles I have hidden to not appear in any list or in the main drop down lsit Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.7.2 (x64) / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 16; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152636] FILESAVE DOCX: export loses section page break on table.
https://bugs.documentfoundation.org/show_bug.cgi?id=152636 Justin L changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108771] [META] DOCX (OOXML) page-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108771 Bug 108771 depends on bug 152636, which changed state. Bug 152636 Summary: FILESAVE DOCX: export loses section page break on table. https://bugs.documentfoundation.org/show_bug.cgi?id=152636 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138761] Writer table sum feature doesn't insert formula in empty cell at bottom of selected column range
https://bugs.documentfoundation.org/show_bug.cgi?id=138761 --- Comment #5 from Alan --- Checked again with current versions of LibreOffice, 7.4.3 and 7.3.7. Bug still exactly as described. Bug can be reproduced exactly as described. 7.3.7.2 Help About Version: 7.3.7.2 / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 1; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded 7.4.3.2 Help About Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 1; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152636] FILESAVE DOCX: export loses section page break on table.
https://bugs.documentfoundation.org/show_bug.cgi?id=152636 --- Comment #4 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/376152fbd110cdc0a2cde1fa9758f36c016d9352 tdf#152636 writerfilter: no w:br in DMLShapes 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-commits] core.git: sw/source
sw/source/filter/ww8/docxattributeoutput.cxx |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
New commits:
commit 376152fbd110cdc0a2cde1fa9758f36c016d9352
Author: Justin Luth
AuthorDate: Thu Dec 22 20:20:24 2022 -0500
Commit: Justin Luth
CommitDate: Sat Dec 24 13:51:37 2022 +
tdf#152636 writerfilter: no w:br in DMLShapes
Don't write postponed column and page breaks into DML shape
paragraphs.
No existing unit tests found that match this criteria.
The example file I have is not appropriate as a unit test,
and it too easily fails to match when any random change
is made to minimize/scrub it.
Change-Id: Iced1399f76caf97362a5ba47a325233b9f009fcf
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144779
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/sw/source/filter/ww8/docxattributeoutput.cxx
b/sw/source/filter/ww8/docxattributeoutput.cxx
index 3e4bca89472d..0bc7e87f1469 100644
--- a/sw/source/filter/ww8/docxattributeoutput.cxx
+++ b/sw/source/filter/ww8/docxattributeoutput.cxx
@@ -1545,7 +1545,8 @@ void DocxAttributeOutput::EndParagraphProperties(const
SfxItemSet& rParagraphMar
m_pSerializer->endElementNS(XML_w, XML_smartTag);
}
-if ( m_nColBreakStatus == COLBRK_WRITE || m_nColBreakStatus ==
COLBRK_WRITEANDPOSTPONE )
+if ((m_nColBreakStatus == COLBRK_WRITE || m_nColBreakStatus ==
COLBRK_WRITEANDPOSTPONE)
+&& !m_rExport.SdrExporter().IsDMLAndVMLDrawingOpen())
{
m_pSerializer->startElementNS(XML_w, XML_r);
m_pSerializer->singleElementNS(XML_w, XML_br, FSNS(XML_w, XML_type),
"column");
@@ -1557,7 +1558,8 @@ void DocxAttributeOutput::EndParagraphProperties(const
SfxItemSet& rParagraphMar
m_nColBreakStatus = COLBRK_NONE;
}
-if ( m_bPostponedPageBreak && !m_bWritingHeaderFooter )
+if (m_bPostponedPageBreak && !m_bWritingHeaderFooter
+&& !m_rExport.SdrExporter().IsDMLAndVMLDrawingOpen())
{
m_pSerializer->startElementNS(XML_w, XML_r);
m_pSerializer->singleElementNS(XML_w, XML_br, FSNS(XML_w, XML_type),
"page");
[Libreoffice-bugs] [Bug 121967] Can't select/pick multiples shapes or images in Writer/Calc/Impress/Draw with CTRL key
https://bugs.documentfoundation.org/show_bug.cgi?id=121967 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2437 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152437] Align & Distribute multiple inserted images within a Writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=152437 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||1967 Status|UNCONFIRMED |NEW Whiteboard| QA:needsComment| Version|7.4.3.2 release |5.4.7.2 release CC||dgp-m...@gmx.de OS|macOS (All) |All Blocks||112182, 103152 Ever confirmed|0 |1 --- Comment #1 from Dieter --- Pbatty, thank you for reporting the bug. I think you report two issues a) selecting multiple images b) Align multple images As there is one basic rule in bugzilla "One report, one issue" I would focus on the first problem. I was really suprised, that I couldn't find a way to select multiple images. So I confirm the problem Version: 7.5.0.0.beta1 (X86_64) / LibreOffice Community Build ID: 3aca23eec42e9d6fbe57071d7633ae1fc4bc5fcc CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded Version: 7.4.4.1 (x64) / LibreOffice Community Build ID: 988f4a351a6fa8cf4bdf2bdc873ca12cf8cbe625 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded and Version: 5.4.7.2 (x64) Build-ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU-Threads: 4; BS: Windows 6.19; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: CL Perhaps duplicate of bug 121967, although that report is much braoder. Additional information: Using shapes it's possible to select several with shift and aign them. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103152 [Bug 103152] [META] Writer image bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=112182 [Bug 112182] [META] Text and object selection issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112182] [META] Text and object selection issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112182 Dieter changed: What|Removed |Added Depends on||152437 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152437 [Bug 152437] Align & Distribute multiple inserted images within a Writer document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Dieter changed: What|Removed |Added Depends on||152437 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152437 [Bug 152437] Align & Distribute multiple inserted images within a Writer document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152440] BOOK VIEW: Switching page view to book view or from book view results in a switch to a semi-random page
https://bugs.documentfoundation.org/show_bug.cgi?id=152440 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7046 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137046] Unwanted scroll after changing from full screen view to non-full screen in multi page view
https://bugs.documentfoundation.org/show_bug.cgi?id=137046 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2440 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152441] An option to add to writing aids
https://bugs.documentfoundation.org/show_bug.cgi?id=152441 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Dieter --- Rferraro, thank you for the report, but I couldn't find Options -> Writing Aids -> Options, but only Tools -> Options -> LibreOffice Writer -> Formatting Aids. Perhaps you think of Tools -> Spelling -> Options -> Options. So could you please check this? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152440] BOOK VIEW: Switching page view to book view or from book view results in a switch to a semi-random page
https://bugs.documentfoundation.org/show_bug.cgi?id=152440 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Blocks||106773 Whiteboard| QA:needsComment| Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Summary|Switching between page |BOOK VIEW: Switching page |views switches to |view to book view or from |semi-random pages |book view results in a ||switch to a semi-random ||page --- Comment #1 from Dieter --- I confirm it with Version: 7.4.4.1 (x64) / LibreOffice Community Build ID: 988f4a351a6fa8cf4bdf2bdc873ca12cf8cbe625 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Single page -> multi-page: OK. Multi-page -> single-page: OK. Single-page -> Book View: view jumps to a total different page Book View -> single-page: view jumps to a total different page Book view -> multiple-page: view jumps to a total different page Multiple-page -> Book view: view jumps to total different page Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=106773 [Bug 106773] [META] Writer document canvas view / viewport jump issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106773] [META] Writer document canvas view / viewport jump issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106773 Dieter changed: What|Removed |Added Depends on||152440 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152440 [Bug 152440] BOOK VIEW: Switching page view to book view or from book view results in a switch to a semi-random page -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152649] Crash with activated SKIA Option
https://bugs.documentfoundation.org/show_bug.cgi?id=152649 --- Comment #4 from Viktor --- (In reply to Telesto from comment #2) > Sounds like bug 149527 looks like it is the same problem, but I can reproduce the failure with the provided ods in 149527. neither on the PC at home (Win11 22H2 with Nvidia) nor on the PC at work (AMD WX3200) I need skia because without it is horrible to work with larger spread sheets ☺ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - 2 commits - sw/inc sw/source
sw/inc/OnlineAccessibilityCheck.hxx |3 ++
sw/inc/node.hxx |3 ++
sw/source/core/access/AccessibilityCheck.cxx| 12 +++-
sw/source/core/docnode/node.cxx | 16 +++
sw/source/core/inc/AccessibilityCheck.hxx |1
sw/source/core/txtnode/OnlineAccessibilityCheck.cxx | 28 ++--
sw/source/core/txtnode/ndtxt.cxx|9 ++
7 files changed, 69 insertions(+), 3 deletions(-)
New commits:
commit fd56017db598ae7a9a955414cfed07e11014b56c
Author: Tomaž Vajngerl
AuthorDate: Sun Nov 13 22:21:29 2022 +0900
Commit: Tomaž Vajngerl
CommitDate: Sat Dec 24 12:16:57 2022 +
sw: handle joining and splitting nodes for online a11y check
Change-Id: I706bf56209beebbe2987bce436536c3d9ade51f1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142655
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
(cherry picked from commit 5e9ba2e6bc08493b10268abdec0c22c1d7c307f6)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144497
Tested-by: Jenkins CollaboraOffice
diff --git a/sw/inc/OnlineAccessibilityCheck.hxx
b/sw/inc/OnlineAccessibilityCheck.hxx
index 3d68a71f11db..5e1da9b77c99 100644
--- a/sw/inc/OnlineAccessibilityCheck.hxx
+++ b/sw/inc/OnlineAccessibilityCheck.hxx
@@ -66,6 +66,7 @@ private:
public:
OnlineAccessibilityCheck(SwDoc& rDocument);
void update(SwPosition const& rNewPos);
+void resetAndQueue(SwNode* pNode);
sal_Int32 getNumberOfAccessibilityIssues() { return
m_nAccessibilityIssues; }
};
diff --git a/sw/inc/node.hxx b/sw/inc/node.hxx
index 8099178c1eaf..a3b9e13ad52d 100644
--- a/sw/inc/node.hxx
+++ b/sw/inc/node.hxx
@@ -86,6 +86,7 @@ namespace sw
struct AccessibilityCheckStatus
{
std::unique_ptr pCollection;
+void reset();
};
}
@@ -324,6 +325,8 @@ public:
return m_aAccessibilityCheckStatus;
}
+void resetAndQueueAccessibilityCheck();
+
private:
SwNode( const SwNode & rNodes ) = delete;
SwNode & operator= ( const SwNode & rNodes ) = delete;
diff --git a/sw/source/core/docnode/node.cxx b/sw/source/core/docnode/node.cxx
index 8a319c03e7aa..a1a549d25069 100644
--- a/sw/source/core/docnode/node.cxx
+++ b/sw/source/core/docnode/node.cxx
@@ -69,12 +69,22 @@
#include
#include
#include
+#include
#ifdef DBG_UTIL
#include
#endif
using namespace ::com::sun::star::i18n;
+namespace sw
+{
+
+void AccessibilityCheckStatus::reset()
+{
+pCollection.reset();
+}
+
+}
/*
* Some local helper functions for the attribute set handle of a content node.
@@ -2142,4 +2152,10 @@ void SwNode::RemoveAnchoredFly(SwFrameFormat *const
pFlyFormat)
m_aAnchoredFlys.erase(it);
}
+void SwNode::resetAndQueueAccessibilityCheck()
+{
+GetDoc().getOnlineAccessibilityCheck()->resetAndQueue(this);
+}
+
+
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/core/txtnode/OnlineAccessibilityCheck.cxx
b/sw/source/core/txtnode/OnlineAccessibilityCheck.cxx
index 1188bc7d06c5..d162e1a661ba 100644
--- a/sw/source/core/txtnode/OnlineAccessibilityCheck.cxx
+++ b/sw/source/core/txtnode/OnlineAccessibilityCheck.cxx
@@ -263,8 +263,7 @@ void
OnlineAccessibilityCheck::clearAccessibilityIssuesFromAllNodes()
SwNode* pNode = pNodes[n];
if (pNode)
{
-auto& rStatus = pNode->getAccessibilityCheckStatus();
-rStatus.pCollection.reset();
+pNode->getAccessibilityCheckStatus().reset();
}
}
@@ -272,6 +271,20 @@ void
OnlineAccessibilityCheck::clearAccessibilityIssuesFromAllNodes()
updateStatusbar();
}
+void OnlineAccessibilityCheck::resetAndQueue(SwNode* pNode)
+{
+bool bOnlineCheckStatus
+=
officecfg::Office::Common::Accessibility::OnlineAccessibilityCheck::get();
+if (!bOnlineCheckStatus)
+return;
+
+pNode->getAccessibilityCheckStatus().reset();
+m_aNodes.erase(pNode);
+runAccessibilityCheck(pNode);
+updateNodeStatus(pNode);
+updateStatusbar();
+}
+
} // end sw
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/core/txtnode/ndtxt.cxx b/sw/source/core/txtnode/ndtxt.cxx
index 8eeb9b6cdf59..b3880c24fcc2 100644
--- a/sw/source/core/txtnode/ndtxt.cxx
+++ b/sw/source/core/txtnode/ndtxt.cxx
@@ -481,6 +481,9 @@ SwTextNode *SwTextNode::SplitContentNode(const SwPosition &
rPos,
}
SetSmartTagDirty( true );
+resetAndQueueAccessibilityCheck();
+pNode->resetAndQueueAccessibilityCheck();
+
if ( pNode->HasHints() )
{
if ( pNode->m_pSwpHints->CanBeDeleted() )
@@ -618,6 +621,9 @@ SwTextNode *SwTextNode::SplitContentNode(const SwPosition &
rPos,
SetSmartTags( std::move(pList2) );
}
+resetAndQueueAccessibilityCheck();
+pNode->resetAndQueueAccessibilityCheck();
+
if (pContentIndexRestore)
{ //
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - include/sfx2 officecfg/registry svx/sdi sw/inc sw/sdi sw/source sw/uiconfig
include/sfx2/sfxsids.hrc | 14 +-- officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu | 14 +++ svx/sdi/svx.sdi | 18 sw/inc/OnlineAccessibilityCheck.hxx |5 - sw/inc/node.hxx |1 sw/sdi/_viewsh.sdi | 11 ++ sw/source/core/txtnode/OnlineAccessibilityCheck.cxx | 42 +- sw/source/uibase/uiview/view0.cxx| 24 + sw/uiconfig/sglobal/menubar/menubar.xml |1 sw/uiconfig/swriter/menubar/menubar.xml |1 10 files changed, 119 insertions(+), 12 deletions(-) New commits: commit a71007c075e834cd5ac741cbbc9607ab8e1d877c Author: Tomaž Vajngerl AuthorDate: Fri Oct 28 22:11:59 2022 +0200 Commit: Tomaž Vajngerl CommitDate: Sat Dec 24 12:16:26 2022 + sw: add a menu option to enable/disable online a11y check Change-Id: I656037ef4e40e7c79daef5dd73f8f10c9818ac25 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142215 Tested-by: Tomaž Vajngerl Reviewed-by: Tomaž Vajngerl (cherry picked from commit 00128f14c400b661444676410b2088aca357291c) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144495 diff --git a/include/sfx2/sfxsids.hrc b/include/sfx2/sfxsids.hrc index 1937368ba2b9..d202087d95e5 100644 --- a/include/sfx2/sfxsids.hrc +++ b/include/sfx2/sfxsids.hrc @@ -443,15 +443,15 @@ class SvxSearchItem; #define SID_PASTE_ONLY_FORMULA (SID_SFX_START + 803) #define SID_PASTE_ONLY_VALUE(SID_SFX_START + 804) #define SID_PASTE_TEXTIMPORT_DIALOG (SID_SFX_START + 805) -#define SID_PASTE_TRANSPOSED(SID_SFX_START + 812) -#define SID_PASTE_AS_LINK (SID_SFX_START + 813) +#define SID_PASTE_TRANSPOSED(SID_SFX_START + 808) +#define SID_PASTE_AS_LINK (SID_SFX_START + 809) // Used for redaction -#define SID_SHAPE_NAME (SID_SFX_START + 808) -// FREE: SID_SFX_START + 809 -#define SID_GRAPHIC_SIZE_CHECK (SID_SFX_START + 809) -#define SID_ACCESSIBILITY_CHECK (SID_SFX_START + 810) -#define SID_ASYNCHRON (SID_SFX_START + 811) +#define SID_SHAPE_NAME (SID_SFX_START + 810) +#define SID_GRAPHIC_SIZE_CHECK (SID_SFX_START + 811) +#define SID_ACCESSIBILITY_CHECK (SID_SFX_START + 812) +#define SID_ASYNCHRON (SID_SFX_START + 813) +#define SID_ACCESSIBILITY_CHECK_ONLINE (SID_SFX_START + 814) // default-ids for configuration #define SID_CONFIG (SID_SFX_START + 904) diff --git a/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu b/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu index 0b1212292b13..f25abc61048e 100644 --- a/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu +++ b/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu @@ -4991,6 +4991,20 @@ bit 3 (0x8): #define UICOMMANDDESCRIPTION_PROPERTIES_TOGGLEBUTTON 8 9 + + + Automatic Accessibility Checking + + + Automatic A~ccessibility Checking + + + Toggle Automatic Accessibility Checking + + + 1 + + Do Not Mark Errors diff --git a/svx/sdi/svx.sdi b/svx/sdi/svx.sdi index ac886aaa0cd4..42a43e3fa1ea 100644 --- a/svx/sdi/svx.sdi +++ b/svx/sdi/svx.sdi @@ -12476,6 +12476,24 @@ SfxVoidItem AccessibilityCheck SID_ACCESSIBILITY_CHECK GroupId = SfxGroupId::Modify; ] +SfxBoolItem AccessibilityCheckOnline SID_ACCESSIBILITY_CHECK_ONLINE +(SfxBoolItem Enable FN_PARAM_1) +[ +AutoUpdate = TRUE, +FastCall = FALSE, +ReadOnlyDoc = TRUE, +Toggle = TRUE, +Container = FALSE, +RecordAbsolute = FALSE, +RecordPerSet; + + +AccelConfig = TRUE, +MenuConfig = TRUE, +ToolBoxConfig = TRUE, +GroupId = SfxGroupId::Options; +] + XColorItem GlowColor SID_ATTR_GLOW_COLOR [ diff --git a/sw/inc/OnlineAccessibilityCheck.hxx b/sw/inc/OnlineAccessibilityCheck.hxx index 7a37f05cc432..fe4652949d64 100644 --- a/sw/inc/OnlineAccessibilityCheck.hxx +++ b/sw/inc/OnlineAccessibilityCheck.hxx @@ -52,15 +52,18 @@ private: SwNodeOffset m_nPreviousNodeIndex; sal_Int32 m_nAccessibilityIssues; bool m_bInitialCheck; +bool m_bOnlineCheckStatus; void runAccessibilityCheck(SwNode* pNode); void updateStatusbar(); void updateNodeStatus(SwNode* pContentNode); void initialCheck(); +void lookForPreviousNodeAndUpdate(SwPosition const& rNewPos); +void
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - sw/inc sw/sdi sw/source sw/uiconfig
sw/inc/strings.hrc |1
sw/sdi/swriter.sdi |2
sw/source/uibase/inc/AccessibilityStatusBarControl.hxx |7 +-
sw/source/uibase/uiview/view2.cxx| 16 +
sw/source/uibase/utlui/AccessibilityStatusBarControl.cxx | 45 +--
sw/uiconfig/sglobal/statusbar/statusbar.xml |2
sw/uiconfig/swriter/statusbar/statusbar.xml |2
7 files changed, 53 insertions(+), 22 deletions(-)
New commits:
commit de9320f7fc86c1421ff59eb218a04c6c90049c39
Author: Tomaž Vajngerl
AuthorDate: Wed Oct 26 22:02:44 2022 +0200
Commit: Tomaž Vajngerl
CommitDate: Sat Dec 24 12:15:51 2022 +
sw: improve a11y check statusbar
Change-Id: I86f589d6618ae80f26542cf83b6b5e3695ca35f8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142193
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
(cherry picked from commit e96dd14288172187372b3a4f82de870b1d660020)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144494
Tested-by: Jenkins CollaboraOffice
diff --git a/sw/inc/strings.hrc b/sw/inc/strings.hrc
index 5748ba7122ff..b4b03968a1eb 100644
--- a/sw/inc/strings.hrc
+++ b/sw/inc/strings.hrc
@@ -1087,6 +1087,7 @@
#define STR_BOOKCTRL_HINT NC_("STR_BOOKCTRL_HINT", "Page
number in document. Click to open Go to Page dialog or right-click for bookmark
list.")
#define STR_BOOKCTRL_HINT_EXTENDED
NC_("STR_BOOKCTRL_HINT_EXTENDED", "Page number in document (Page number on
printed document). Click to open Go to Page dialog.")
#define STR_TMPLCTRL_HINT NC_("STR_TMPLCTRL_HINT", "Page
Style. Right-click to change style or click to open Style dialog.")
+#define STR_ACCESSIBILITY_CHECK_HINT
NC_("STR_ACCESSIBILITY_CHECK_HINT", "Status of the accessibility check.")
// Strings for textual attributes.
#define STR_DROP_OVER NC_("STR_DROP_OVER", "Drop
Caps over")
diff --git a/sw/sdi/swriter.sdi b/sw/sdi/swriter.sdi
index f001b70ebb90..bc58977788a4 100644
--- a/sw/sdi/swriter.sdi
+++ b/sw/sdi/swriter.sdi
@@ -5970,7 +5970,7 @@ SfxStringItem StateWordCount FN_STAT_WORDCOUNT
GroupId = SfxGroupId::View;
]
-SfxStringItem StateAccessibilityCheck FN_STAT_ACCESSIBILITY_CHECK
+SfxInt32Item StateAccessibilityCheck FN_STAT_ACCESSIBILITY_CHECK
[
AutoUpdate = FALSE,
diff --git a/sw/source/uibase/inc/AccessibilityStatusBarControl.hxx
b/sw/source/uibase/inc/AccessibilityStatusBarControl.hxx
index 52e64b99f5ac..63744499d083 100644
--- a/sw/source/uibase/inc/AccessibilityStatusBarControl.hxx
+++ b/sw/source/uibase/inc/AccessibilityStatusBarControl.hxx
@@ -15,14 +15,17 @@ namespace sw
{
class AccessibilityStatusBarControl final : public SfxStatusBarControl
{
+sal_Int32 mnIssues;
+
public:
SFX_DECL_STATUSBAR_CONTROL();
AccessibilityStatusBarControl(sal_uInt16 nSlotId, sal_uInt16 nId,
StatusBar& rStb);
virtual ~AccessibilityStatusBarControl() override;
-virtual void StateChangedAtStatusBarControl(sal_uInt16 nSID, SfxItemState
eState,
-const SfxPoolItem* pState)
override;
+void StateChangedAtStatusBarControl(sal_uInt16 nSID, SfxItemState eState,
+const SfxPoolItem* pState) override;
+void Paint(const UserDrawEvent& rEvent) override;
};
} // end sw
diff --git a/sw/source/uibase/uiview/view2.cxx
b/sw/source/uibase/uiview/view2.cxx
index 3472bf63ef0e..a5cdc27fd059 100644
--- a/sw/source/uibase/uiview/view2.cxx
+++ b/sw/source/uibase/uiview/view2.cxx
@@ -1614,19 +1614,11 @@ void SwView::StateStatusLine(SfxItemSet )
break;
case FN_STAT_ACCESSIBILITY_CHECK:
{
-if (rShell.GetDoc()->getOnlineAccessibilityCheck())
+std::unique_ptr const&
rOnlineAccessibilityCheck = rShell.GetDoc()->getOnlineAccessibilityCheck();
+if (rOnlineAccessibilityCheck)
{
-auto nIssues =
rShell.GetDoc()->getOnlineAccessibilityCheck()->getNumberOfAccessibilityIssues();
-OUString aString;
-if (nIssues > 0)
-{
-aString = u"Issues: " + OUString::number(nIssues);
-}
-else
-{
-aString = u"No Issues";
-}
-rSet.Put(SfxStringItem(FN_STAT_ACCESSIBILITY_CHECK,
aString));
+sal_Int32 nIssues =
rOnlineAccessibilityCheck->getNumberOfAccessibilityIssues();
+rSet.Put(SfxInt32Item(FN_STAT_ACCESSIBILITY_CHECK,
nIssues));
}
}
break;
diff --git a/sw/source/uibase/utlui/AccessibilityStatusBarControl.cxx
b/sw/source/uibase/utlui/AccessibilityStatusBarControl.cxx
index
[Libreoffice-bugs] [Bug 152649] Crash with activated SKIA Option
https://bugs.documentfoundation.org/show_bug.cgi?id=152649 --- Comment #3 from Viktor --- (In reply to m.a.riosv from comment #1) > Have you trying to update the graphics driver from the vendor, I guess it is > updated from win10. > > https://www.amd.com/en/support Yes, I have updated the the driver to latest version available from AMD. -- You are receiving this mail because: You are the assignee for the bug.
Subject : Help regarding Bug 90341 - Clean up excessive const_cast'ing
Hello, So I did all the recommended changes that were commented in the code in the file "impastpl.cxx" but Jenkins is still giving me a build error. Can someone please help me with it, the link to it on Gerrit is: https://gerrit.libreoffice.org/c/core/+/144537 I tried a further commit and investigated a few things by changing some static_cast back to const_cast but couldn't figure it out, unfortunately. For reference, The easy hack I'm referring to is: https://bugs.documentfoundation.org/show_bug.cgi?id=90341 Thanks for reading this, Siddharth
[Libreoffice-bugs] [Bug 147020] Default Printer not recognized
https://bugs.documentfoundation.org/show_bug.cgi?id=147020 --- Comment #4 from Steve Horn --- Thank you for fixing this issue and following up. Printing works as expected for me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152665] New: Fill cells (e.g. Fill down) not working on single-column/single-row selection discontinuous ranges of cells such as e.g. after applying autofilter (filtered cells)
https://bugs.documentfoundation.org/show_bug.cgi?id=152665 Bug ID: 152665 Summary: Fill cells (e.g. Fill down) not working on single-column/single-row selection discontinuous ranges of cells such as e.g. after applying autofilter (filtered cells) Product: LibreOffice Version: 7.3.5.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: temporary2...@homolog.de Description: There are multiple functions to fill cells, but all are disabled, when a discontinuous range of cells is selected. This makes it impossible to fill such a range with a value. At least simple cases should work: E.g. on discontinuous single-column selections, it is expected that "Fill down" or "Fill up" works by skipping the unselected/hidden/filtered out cells. Similar on discontinuous single-row selections. But the "Fill cells" functions should also work on multi-column / multi-row selections. And there is no workaround for this (e.g. pasting does not work either, but pastes the value from the clipboard to the first cell only instead of to all cells selected). I declared severity as "Enhancement request", but as this contradicts the expectations of the user on what Calc should do, this could also be considered a bug in terms of user experience. Steps to Reproduce: Variant 1 (Fill cells): 1. Start with a new Calc document 2. Write "A" into cell A1 3a. Select cells A1, A3 and A5. or 3b. Select cells A1, C1 and E1. Variant 2 (Paste): 1. Start with a new Calc document 2. Copy the text "A" to the clipboard 3. Mark a discontinuous range of cells (e.g. one of those given in steps 3a or 3b above) 4. Paste Actual Results: Variant 1: Nothing can be done to fill the range - all Fill cells functions are disabled Variant 2: Past only fills the top left cell. Expected Results: There should be any way to fill a discontinuous range of cells. Either using the "Fill cells" functions or by pasting a single-cell value from the clipboard. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.3.5.2 (x64) / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152664] New: Charts invisible on high contrst mode
https://bugs.documentfoundation.org/show_bug.cgi?id=152664 Bug ID: 152664 Summary: Charts invisible on high contrst mode Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ar...@outlook.com Description: Charty after insert on high contrast mode are invisible. Tested on 7.4 and 7.6 Steps to Reproduce: 1.Insert any chart 2. 3. Actual Results: chart is invisible Expected Results: show chart Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9b46020c262045aed0beace4708565235c2523cc CPU threads: 8; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: pl-PL (pl_PL); UI: pl-PL Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152503] Zotero plugin symbols added newly at the beginning of the icon list, not at the end
https://bugs.documentfoundation.org/show_bug.cgi?id=152503 g...@esbj.ch changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from g...@esbj.ch --- RESOLVED! got answer from Zotero: "Right-click and unlock the toolbar position, move it where you want it, and lock it again." important: right-click on the 6 symbols ... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108816] [META] Writer toolbar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108816 Bug 108816 depends on bug 152503, which changed state. Bug 152503 Summary: Zotero plugin symbols added newly at the beginning of the icon list, not at the end https://bugs.documentfoundation.org/show_bug.cgi?id=152503 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152663] New: The fonts in STIX MathJax Size1 for Libreoffice math, especially the integral signs, are not centered according to the line of the expression.
https://bugs.documentfoundation.org/show_bug.cgi?id=152663 Bug ID: 152663 Summary: The fonts in STIX MathJax Size1 for Libreoffice math, especially the integral signs, are not centered according to the line of the expression. Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Formula Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: h...@phys.ncku.edu.tw Description: The fonts in STIX MathJax Size1 for LibreOffice math/Impress, especially the integral signs, are not located at the center according to the line of the expression in the math mode. One can understand the problem easily by comparing the fonts' position with the positions of MathJax_Size2's fonts. Steps to Reproduce: 1. Activate LibreOffice's Math 2. Go to the Symbol window. 3. Pick any symbol and click 4. Choose any integral symbol in the STIX MathJax Size1 font set and assign it an arbitrary name, then do the same thing to an integral symbol in the MathJax_Size2 font set. 5. Write a test equation by using these two newly assigned symbols. Then their position difference in the equation will show obviously. Actual Results: The integral symbols of STIX MathJax Size1 don't align to the integral symbols of MathJax_Size2 which looks better to me. The misalignment of this two fonts makes it difficult to use both fonts at the same time. Expected Results: I hope that the fonts of STIX MathJax Size1 can be centered along a mathematical expression instead of being aligned at the bottom. Reproducible: Always User Profile Reset: No Additional Info: This font position problem should affect all version of LibreOffice since not too much people will use these fonts. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140061] Crash swlo!sw::WriterMultiListener::StartListening
https://bugs.documentfoundation.org/show_bug.cgi?id=140061 --- Comment #8 from Telesto --- No crash with macOS Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8635c9aa8c6f1078a9e220076d5a08daf30077e8 CPU threads: 8; OS: Mac OS X 12.3.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141852] Crash swlo!sw::Ring::unlink+0x2b79:
https://bugs.documentfoundation.org/show_bug.cgi?id=141852 Telesto changed: What|Removed |Added Keywords||wantBacktrace CC||serval2...@yahoo.fr --- Comment #4 from Telesto --- Repro Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8635c9aa8c6f1078a9e220076d5a08daf30077e8 CPU threads: 8; OS: Mac OS X 12.3.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
