[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 Bug 105948 depends on bug 118327, which changed state. Bug 118327 Summary: undo selects a list item https://bugs.documentfoundation.org/show_bug.cgi?id=118327 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126282] New: Enable Sri Lankan Currency in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=126282 Bug ID: 126282 Summary: Enable Sri Lankan Currency in LibreOffice Product: LibreOffice Version: 6.2.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: danis...@gmail.com Description: Rupee is the Sri Lankan currency which write as රුපියල් in Singala and ரூபாய் in Tamil. Currency symbol in Sinhala, Tamil and English is රු, ரூ, Rs respectively. Common abbreviation is Rs and LKR is the international currency code. This need to fix in all components of LibreOffice. https://en.wikipedia.org/wiki/Sri_Lankan_rupee Steps to Reproduce: 1. Open LibreOffice Calc 2. Select Currency formating 3. Search for Sri Lankan Rupee or LKR or Rs Actual Results: either LKR or Rs or Sri Lankan Rupee not found Expected Results: LKR or Rs. should be there. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118327] undo selects a list item
https://bugs.documentfoundation.org/show_bug.cgi?id=118327 l...@royal.net changed: What|Removed |Added Status|NEW |RESOLVED CC||l...@royal.net Resolution|--- |WORKSFORME --- Comment #5 from l...@royal.net --- Fixed in 6.2.4.2/linux -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125425] It's not possible to select a cell range with a finger
https://bugs.documentfoundation.org/show_bug.cgi?id=125425 Tomaz Vajngerl changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |qui...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126281] New: Data corruption of firebird numeric and decimal fields.
https://bugs.documentfoundation.org/show_bug.cgi?id=126281 Bug ID: 126281 Summary: Data corruption of firebird numeric and decimal fields. Product: LibreOffice Version: 6.2.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mike60...@live.com Data may be corrupted when coping data into numeric and decimal fields in the firebird database. These fields may also be corrupted when migrating from a HSQLDB databases. Steps: Created a table with the following schema: CREATE TABLE "Table1" (ID INTEGER GENERATED BY DEFAULT AS IDENTITY NOT NULL, "Numeric" NUMERIC(15, 4), "Decimal" DECIMAL(15, 4), "Double" DOUBLE PRECISION, PRIMARY KEY (ID)); Created a calc sheet with the following data: ID Numeric Decimal Double 1 123 2 1.1 2.1 3.1 3 1.12 2.12 3.12 4 1.1232.1233.123 5 1.1234 2.1234 3.1234 6 1.12345 2.12345 3.12345 Selected the calc sheet and pasted it into the firebird table. This resulted in the firebird table containing the following unexpected data: ID Numeric Decimal Double 10.00010.0002 3 20.00010.0002 3.1 30.00010.0002 3.12 40.00010.0002 3.123 50.00010.0002 3.1234 60.00010.0002 3.1235 Repeating the above with a similarly configured HSQLDB database resulted in the expected results. Similar issues exist when the numeric and decimal fields are migrated to the firebird database Used the above HSQLDB database and loaded it with the following data: ID Numeric Decimal Double 1 10.1 10.1 10.1 2 10.2 10.2 10.2 3 10.3 10.3 10.3 4 10.4 10.4 10.4 5 10.5 10.5 10.5 6 10.6 10.6 10.6 Closed the database, opened and migrated it to the firebird database. This resulted in the firebird table containing the following unexpected data: ID Numeric DecimalDouble 1 -1667.6216 -1667.6216 10.1 2 -1667.5216 -1667.5216 10.2 3 -1667.4216 -1667.4216 10.3 4 -1667.3216 -1667.3216 10.4 5 -1667.2216 -1667.2216 10.5 6 -1667.1216 -1667.1216 10.6 LibreOffice Version 6.2.4.2 LibreOffice Version 6.2.5.2 Linux Mint19 Possibly related issues: 126268 123591 116893 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Reveal code, old macros convert them to LO
On 08/07/19 03:04, Dan Lewis wrote: > One thing I do know: an .odt file is based on styles. The only codes > that are used are styles. This is obvious when looking at the > Content.xml file in the .odt zipped file. Word Perfect has a different > set of codes which it uses. I do not see any correlation between the > two. Without this, how can a do more than pretend to convert LO's > styles from WP's "reveal codes"? I don't get this ,,, which could be why this thread has been so long. WordPerfect has styles. Reveal Codes is nothing really to do with styles. Unless of course this is the old chestnut of "people use reveal codes to see the formatting". Would you call "bold" a style? Would you call a graphics box a style? The point is, reveal codes showed all of this. So if I used styles for my document, in my reveal codes window I might see [style:chapter:on]Chapter 1[style:chapter:off] or if I didn't know about styles particularly it would be [bold:on]Chapter 1[bold:off] and if I double-clicked the [chapter] "character" it would call up the style definition dialog, while if I clicked the [bold] "character" it would call up the font format dialog. A picture would appear as a character something like [graphics box:URI]. Etc etc. Can I ask how many people here have actually *used* WordPerfect and Reveal Codes, and how many people are simply going on what they've been told about reveal codes? Reveal Codes is a markup window. Those markups might happen to be styles. They might not. Cheers, Wol ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 126280] New: PRINTING: Clicking Print window's Properties button crashes Calc - Crash in: ml1750u.DLL
https://bugs.documentfoundation.org/show_bug.cgi?id=126280 Bug ID: 126280 Summary: PRINTING: Clicking Print window's Properties button crashes Calc - Crash in: ml1750u.DLL Product: LibreOffice Version: 6.2.4.2 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: whon...@gmail.com This bug was filed from the crash reporting server and is br-ac43b667-5481-4894-921a-1b7aa5bb103c. = In Calc with open spreadsheet... a) Click File | Select Print | Print window opens b) In General tab select a printer c) Click on Properties button d) Crash occurs Note: Printer selected in this crash report was 'Samsung ML-1750 Series PCL 6 (USB)'. However, crash also occurs if select the 'Print to File...' option. No crash occurs if selected one of the following printer options: - Fax - Microsoft Print to PDF - Microsoft XPS Document Writer - OneNote = Version: 6.2.4.2 (x64) Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126279] New: CRASH when resuming work with a WebDAV document when session has timed out
https://bugs.documentfoundation.org/show_bug.cgi?id=126279 Bug ID: 126279 Summary: CRASH when resuming work with a WebDAV document when session has timed out Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com LibreOffice crashes when it has a WebDAV document open, and had not communicated with the server for a while, thus the session has timed out on the server. Steps: 1. Open a document from a WebDAV server, like SharePoint. 2. Let LibreOffice stay idle for enough time - in my testing, I didn't touch it for about 30 minutes. 3. Switch back to LibreOffice, and try anything that would initiate a WebDAV operation: it could be e.g. opening File menu; or even just closing the document. LibreOffice crashes silently. Tested with Version: 6.2.5.2 (x64) Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded and current master toward 6.4. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126026] wrong window icon for an LO calc file started from file manager
https://bugs.documentfoundation.org/show_bug.cgi?id=126026 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126058] No inner borders after replaying a recorded macro
https://bugs.documentfoundation.org/show_bug.cgi?id=126058 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121934] Highlighting applied 2 days ago was gone tonight.
https://bugs.documentfoundation.org/show_bug.cgi?id=121934 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121934] Highlighting applied 2 days ago was gone tonight.
https://bugs.documentfoundation.org/show_bug.cgi?id=121934 --- Comment #4 from QA Administrators --- Dear Maurice Jaillet, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85398] To cut table contents does not set document-modified flag
https://bugs.documentfoundation.org/show_bug.cgi?id=85398 --- Comment #11 from QA Administrators --- Dear Matthew Francis, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117671] Comments (some or all not seen) are lost when a .fods file is saved with a new name
https://bugs.documentfoundation.org/show_bug.cgi?id=117671 --- Comment #5 from QA Administrators --- Dear Drew Jensen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 122387] Cannot change paper size for printing on an Epson L200
https://bugs.documentfoundation.org/show_bug.cgi?id=122387 --- Comment #7 from QA Administrators --- Dear randomly_chosen, 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 92813] PRINTING: Page format does not align when printing via Excel
https://bugs.documentfoundation.org/show_bug.cgi?id=92813 --- Comment #4 from QA Administrators --- Dear Drizzt, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 122426] FILEOPEN: DOC: Page has header when it shouldn't have it
https://bugs.documentfoundation.org/show_bug.cgi?id=122426 --- Comment #3 from QA Administrators --- Dear Xisco Faulí, 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121349] MacOS: The template table styles are missing in normal mode even after a profile reset (fine in safe mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=121349 --- Comment #9 from QA Administrators --- Dear Telesto, 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 122413] Changes to Impress not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=122413 --- Comment #5 from QA Administrators --- Dear jared.anrui, 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91180] Cannot find Philippine Peso in Special Characters
https://bugs.documentfoundation.org/show_bug.cgi?id=91180 --- Comment #15 from QA Administrators --- Dear Bamm, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116754] When saving a Writer document As RTF header text from p.2 appears in a footnote on p.1
https://bugs.documentfoundation.org/show_bug.cgi?id=116754 --- Comment #9 from QA Administrators --- Dear Bernard Moreton, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: Branch 'distro/collabora/cp-6.2' - include/sfx2 sfx2/source
include/sfx2/docfile.hxx |3 +
include/sfx2/strings.hrc |3 +
sfx2/source/doc/docfile.cxx | 73 ++-
sfx2/source/view/viewfrm.cxx | 43 +
4 files changed, 86 insertions(+), 36 deletions(-)
New commits:
commit 7943a3b4b7ab5891e0be61bcfedd7c55a1ef8bf4
Author: Mike Kaganski
AuthorDate: Fri Jul 5 17:56:38 2019 +1000
Commit: Mike Kaganski
CommitDate: Mon Jul 8 04:47:48 2019 +0200
Show who has locked the document when reopening a read-only document
Pass the locking data from SfxMedium::LockOrigFileOnDemand, to allow
clients to show it themselves when required.
Change-Id: I6afe46a1896e1b60771c080efa2f58794dbed8a6
Reviewed-on: https://gerrit.libreoffice.org/75113
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
Reviewed-on: https://gerrit.libreoffice.org/75137
Tested-by: Mike Kaganski
diff --git a/include/sfx2/docfile.hxx b/include/sfx2/docfile.hxx
index 2f7d9454c1e5..482c1e4ba3ce 100644
--- a/include/sfx2/docfile.hxx
+++ b/include/sfx2/docfile.hxx
@@ -169,7 +169,8 @@ public:
FailedLockFile, // there was only lock file that prevented success -
no syslock or IO error
Succeeded,
};
-LockFileResult LockOrigFileOnDemand( bool bLoading, bool bNoUI, bool
bTryIgnoreLockFile = false );
+LockFileResult LockOrigFileOnDemand(bool bLoading, bool bNoUI, bool
bTryIgnoreLockFile = false,
+LockFileEntry* pLockData = nullptr);
voidDisableUnlockWebDAV( bool bDisableUnlockWebDAV = true
);
voidUnlockFile( bool bReleaseLockStream );
/// Lets Transfer_Impl() not fsync the output file.
diff --git a/include/sfx2/strings.hrc b/include/sfx2/strings.hrc
index a77dbc86d77d..373ca649fa48 100644
--- a/include/sfx2/strings.hrc
+++ b/include/sfx2/strings.hrc
@@ -239,7 +239,8 @@
#define STR_ERROR_SEND_MAIL_CODE
NC_("STR_ERROR_SEND_MAIL_CODE", "An error occurred in sending the message.
Possible errors could be a missing user account or a defective setup.\n\nError
code is $1")
#define STR_ERROR_SEND_MAIL_HEADER
NC_("STR_ERROR_SEND_MAIL_HEADER", "Error sending mail")
#define STR_QUERY_OPENASTEMPLATE
NC_("STR_QUERY_OPENASTEMPLATE", "This document cannot be edited, possibly due
to missing access rights. Do you want to edit a copy of the document?")
-#define STR_QUERY_OPENASTEMPLATE_ALLOW_IGNORE
NC_("STR_QUERY_OPENASTEMPLATE_ALLOW_IGNORE", "This document cannot be edited,
because it is locked in another session. Do you want to edit a copy of the
document?\n\nYou can also try to ignore the lock and open the file for
editing.")
+#define STR_QUERY_OPENASTEMPLATE_LOCKED
NC_("STR_QUERY_OPENASTEMPLATE_LOCKED", "This document cannot be edited, because
it is locked in another session.%LOCKINFO\nDo you want to edit a copy of the
document?")
+#define STR_QUERY_OPENASTEMPLATE_ALLOW_IGNORE
NC_("STR_QUERY_OPENASTEMPLATE_ALLOW_IGNORE", "You can also try to ignore the
lock and open the file for editing.")
#define STR_QUERY_OPENASTEMPLATE_OPENCOPY_BTN
NC_("STR_QUERY_OPENASTEMPLATE_OPENCOPY_BTN", "Open ~Copy")
#define STR_QUERY_OPENASTEMPLATE_OPEN_BTN
NC_("STR_QUERY_OPENASTEMPLATE_OPEN_BTN", "~Open")
#define STR_REPAIREDDOCUMENTNC_("STR_REPAIREDDOCUMENT", "
(repaired document)")
diff --git a/sfx2/source/doc/docfile.cxx b/sfx2/source/doc/docfile.cxx
index bb153e5badb5..789f3b8b8dae 100644
--- a/sfx2/source/doc/docfile.cxx
+++ b/sfx2/source/doc/docfile.cxx
@@ -1117,7 +1117,9 @@ namespace
// sets SID_DOC_READONLY if the document cannot be opened for editing
// if user cancel the loading the ERROR_ABORT is set
-SfxMedium::LockFileResult SfxMedium::LockOrigFileOnDemand( bool bLoading, bool
bNoUI, bool bTryIgnoreLockFile )
+SfxMedium::LockFileResult SfxMedium::LockOrigFileOnDemand(bool bLoading, bool
bNoUI,
+ bool
bTryIgnoreLockFile,
+ LockFileEntry*
pLockData)
{
#if !HAVE_FEATURE_MULTIUSER_ENVIRONMENT
(void) bLoading;
@@ -1168,37 +1170,47 @@ SfxMedium::LockFileResult
SfxMedium::LockOrigFileOnDemand( bool bLoading, bool b
catch ( ucb::InteractiveLockingLockedException& )
{
// received when the resource is already locked
-// get the lock owner, using a special ucb.webdav
property
-// the owner property retrieved here is what the
other principal send the server
-// when activating the lock.
-// See
http://tools.ietf.org/html/rfc4918#section-14.17 for details
-LockFileEntry aLockData;
-aLockData[LockFileComponent::OOOUSERNAME] =
[Libreoffice-bugs] [Bug 118327] undo selects a list item
https://bugs.documentfoundation.org/show_bug.cgi?id=118327 --- Comment #4 from QA Administrators --- Dear lvm, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 81969] EDITING: Find and Replace does not replace text inside object with text
https://bugs.documentfoundation.org/show_bug.cgi?id=81969 --- Comment #5 from QA Administrators --- Dear Jonata, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103056] Endless scrolling upwards after reaching top of document
https://bugs.documentfoundation.org/show_bug.cgi?id=103056 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118465] RTF import does not repeat header / repeat heading / repeat as header row for table
https://bugs.documentfoundation.org/show_bug.cgi?id=118465 --- Comment #9 from QA Administrators --- Dear Michael J. Evans, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117254] PDF: has charts rendered in wrong position (imported as Star Obj Descr (XML))
https://bugs.documentfoundation.org/show_bug.cgi?id=117254 --- Comment #10 from QA Administrators --- Dear Lorenzo Chiola, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 41442] Control File Locking from Options
https://bugs.documentfoundation.org/show_bug.cgi?id=41442 --- Comment #17 from Mike Kaganski --- I propose this to be WORKSFORME. Rationale: 1. The requested functionality is a power user feature, requiring users to have clear understanding of what they do and what are the drawbacks (e.g. possible conflicts on simultaneous edits on filesystems without in-built locking present, or absent information about who has locked the file on another system). 2. Since version 4.2, we have Expert Configuration feature [1] allowing one to set different power-user settings from Options; since version 5.0, the feature allows searching [2], making it easier to search for needed settings. Find the feature on Options->LibreOffice->Advanced->Open Expert Configuration. 3. The requested functionality is already present using 'org.openoffice.Office.Common/Misc/UseLocking' setting (controlling creation of lockfiles and using locking in general), and 'org.openoffice.Office.Common/Misc/UseDocumentOOoLockFile' setting (controlling whether the present lockfile will be considered when deciding if the file is locked by someone else). For curious, the details about effects of the settings are in function SfxMedium::LockOrigFileOnDemand [3]. [1] https://wiki.documentfoundation.org/ReleaseNotes/4.2#GUI [2] https://wiki.documentfoundation.org/ReleaseNotes/5.0#Expert_Configuration_usability_improvements [3] https://opengrok.libreoffice.org/xref/core/sfx2/source/doc/docfile.cxx#LockOrigFileOnDemand -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Reveal code, old macros convert them to LO
On 7/7/19 4:35 PM, Wols Lists wrote: On 07/07/19 17:06, Tor Lillqvist wrote: For the reference: we have a bug report since 2011 https://bugs.documentfoundation.org/show_bug.cgi?id=34002 and the corresponding openoffice bug report from 2002 is linked in the ticket... Which should be a good indication that the request is unreasonable. I think you mean "impractical" :-( How is it unreasonable for support guys to want to be able to debug their lusers' documents? How is it unreasonable for people like me to want to use a modern word processor, but be able to use it in a manner that we are comfortable, rather than be forced into a "one size fits all" extremely uncomfortable fairy tale bed ... I was serious when I suggested that Uwe's best case for fixing his documents was to "save as plain text" and start again. Bit tricky if the document is full of graphics and other stuff ... Cheers, Wol I now possess a copy of the offending .docx document and the PDF version of it. (It contains 1.6MB, so it will take some time.) Tomorrow, I will be determining what is necessary to fix it. Rather than guess as to what would be required, I will find out. I think this would be much more useful for others. I will report back when I am finished. Additional observation as in a personal opinion: this discussion has grown to a great length without really solving the problem. Such was the case for similar discussions before. (I seem to remember that one time it involved OOo prior to 3.0.) One thing I do know: an .odt file is based on styles. The only codes that are used are styles. This is obvious when looking at the Content.xml file in the .odt zipped file. Word Perfect has a different set of codes which it uses. I do not see any correlation between the two. Without this, how can a do more than pretend to convert LO's styles from WP's "reveal codes"? Dan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 104241] Not possible to scroll past page 1 in GS51-GettingStartedLO.odt (large image on page 1)
https://bugs.documentfoundation.org/show_bug.cgi?id=104241 --- Comment #8 from Aron Budea --- The behavior slightly changed between 6.0.0.3 to 6.1.0.3 (and is still the same in 6.3 beta2): you eventually get to scroll down, the view only jumps back after each first couple of scrolls, but not afterwards. Another visible difference is that in 6.0.0.3 the caret flickers very quickly, and in 6.1.0.3 first it doesn't blink at all, and later blinks normally. Still, I'd expect scrolling to be visible right away... the situation definitely improved, though. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: vcl/inc vcl/opengl vcl/qa
vcl/inc/opengl/win/WinDeviceInfo.hxx |3 ---
vcl/opengl/opengl_blacklist_windows.xml| 12 +---
vcl/opengl/win/WinDeviceInfo.cxx |9 -
vcl/opengl/win/blocklist_parser.cxx| 12
vcl/qa/cppunit/blocklistparsertest.cxx | 25 +
vcl/qa/cppunit/test_blocklist_evaluate.xml | 11 +--
vcl/qa/cppunit/test_blocklist_parse.xml| 18 --
7 files changed, 3 insertions(+), 87 deletions(-)
New commits:
commit 49422a469646ad8be43ba828ca24c2484c26b9e8
Author: Gabor Kelemen
AuthorDate: Mon Jul 1 16:51:02 2019 +0200
Commit: Tomaž Vajngerl
CommitDate: Mon Jul 8 02:50:07 2019 +0200
Do not support GL blacklisting for Windows versions older than 7
Since we no longer install on such systems anyway
Change-Id: Ia3b5c202e1276857c97017bb5a7eb9f087d5626e
Reviewed-on: https://gerrit.libreoffice.org/74961
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/vcl/inc/opengl/win/WinDeviceInfo.hxx
b/vcl/inc/opengl/win/WinDeviceInfo.hxx
index b207b2f9c9df..773be7af0f7d 100644
--- a/vcl/inc/opengl/win/WinDeviceInfo.hxx
+++ b/vcl/inc/opengl/win/WinDeviceInfo.hxx
@@ -22,9 +22,6 @@ namespace wgl {
enum OperatingSystem {
DRIVER_OS_UNKNOWN = 0,
-DRIVER_OS_WINDOWS_XP,
-DRIVER_OS_WINDOWS_SERVER_2003,
-DRIVER_OS_WINDOWS_VISTA,
DRIVER_OS_WINDOWS_7,
DRIVER_OS_WINDOWS_8,
DRIVER_OS_WINDOWS_8_1,
diff --git a/vcl/opengl/opengl_blacklist_windows.xml
b/vcl/opengl/opengl_blacklist_windows.xml
index 4ed2bb2c61ba..034838b73f14 100644
--- a/vcl/opengl/opengl_blacklist_windows.xml
+++ b/vcl/opengl/opengl_blacklist_windows.xml
@@ -9,7 +9,7 @@
-
-
-
-
-
-
-
-
-
-
diff --git a/vcl/opengl/win/WinDeviceInfo.cxx b/vcl/opengl/win/WinDeviceInfo.cxx
index 2ebccf9ee6f4..5c86d9aca22f 100644
--- a/vcl/opengl/win/WinDeviceInfo.cxx
+++ b/vcl/opengl/win/WinDeviceInfo.cxx
@@ -153,9 +153,6 @@ uint32_t ParseIDFromDeviceID(const OUString , const
char *prefix, int length
// based on http://msdn.microsoft.com/en-us/library/ms724834(VS.85).aspx
enum {
kWindowsUnknown= 0,
-kWindowsXP = 0x00050001,
-kWindowsServer2003 = 0x00050002,
-kWindowsVista = 0x0006,
kWindows7 = 0x00060001,
kWindows8 = 0x00060002,
kWindows8_1= 0x00060003,
@@ -167,12 +164,6 @@ wgl::OperatingSystem
WindowsVersionToOperatingSystem(int32_t aWindowsVersion)
{
switch(aWindowsVersion)
{
-case kWindowsXP:
-return wgl::DRIVER_OS_WINDOWS_XP;
-case kWindowsServer2003:
-return wgl::DRIVER_OS_WINDOWS_SERVER_2003;
-case kWindowsVista:
-return wgl::DRIVER_OS_WINDOWS_VISTA;
case kWindows7:
return wgl::DRIVER_OS_WINDOWS_7;
case kWindows8:
diff --git a/vcl/opengl/win/blocklist_parser.cxx
b/vcl/opengl/win/blocklist_parser.cxx
index ab89c0e4d567..d7dd5de26258 100644
--- a/vcl/opengl/win/blocklist_parser.cxx
+++ b/vcl/opengl/win/blocklist_parser.cxx
@@ -33,18 +33,6 @@ wgl::OperatingSystem getOperatingSystem(const OString&
rString)
{
return wgl::DRIVER_OS_ALL;
}
-else if (rString == "xp")
-{
-return wgl::DRIVER_OS_WINDOWS_XP;
-}
-else if (rString == "server2003")
-{
-return wgl::DRIVER_OS_WINDOWS_SERVER_2003;
-}
-else if (rString == "vista")
-{
-return wgl::DRIVER_OS_WINDOWS_VISTA;
-}
else if (rString == "7")
{
return wgl::DRIVER_OS_WINDOWS_7;
diff --git a/vcl/qa/cppunit/blocklistparsertest.cxx
b/vcl/qa/cppunit/blocklistparsertest.cxx
index f9a692585ca0..7d99e87f3750 100644
--- a/vcl/qa/cppunit/blocklistparsertest.cxx
+++ b/vcl/qa/cppunit/blocklistparsertest.cxx
@@ -40,7 +40,7 @@ void BlocklistParserTest::testParse()
aBlocklistParser.parse();
size_t const n = aDriveInfos.size();
-CPPUNIT_ASSERT_EQUAL(static_cast(22), n);
+CPPUNIT_ASSERT_EQUAL(static_cast(16), n);
size_t i = 0;
@@ -54,23 +54,6 @@ void BlocklistParserTest::testParse()
aDriveInfo = aDriveInfos[i++];
CPPUNIT_ASSERT_EQUAL(bIsWhitelisted, aDriveInfo.mbWhitelisted);
-
CPPUNIT_ASSERT_EQUAL(WinOpenGLDeviceInfo::GetDeviceVendor(wgl::VendorIntel),
aDriveInfo.maAdapterVendor);
-
CPPUNIT_ASSERT_EQUAL(wgl::VersionComparisonOp::DRIVER_LESS_THAN_OR_EQUAL,
aDriveInfo.meComparisonOp);
-CPPUNIT_ASSERT_EQUAL(wgl::V(11,21,31,41), aDriveInfo.mnDriverVersion);
-
-aDriveInfo = aDriveInfos[i++];
-CPPUNIT_ASSERT_EQUAL(bIsWhitelisted, aDriveInfo.mbWhitelisted);
-
CPPUNIT_ASSERT_EQUAL(WinOpenGLDeviceInfo::GetDeviceVendor(wgl::VendorATI),
aDriveInfo.maAdapterVendor);
-CPPUNIT_ASSERT_EQUAL(wgl::VersionComparisonOp::DRIVER_GREATER_THAN,
aDriveInfo.meComparisonOp);
-
[Libreoffice-commits] core.git: Branch 'distro/collabora/cp-6.0' - desktop/source
desktop/source/lib/init.cxx | 11 +++
1 file changed, 11 insertions(+)
New commits:
commit 56edc43f2e7e3f560d2ba1873441222942bd2bf7
Author: Tomaž Vajngerl
AuthorDate: Tue Jul 2 14:48:31 2019 +0900
Commit: Tomaž Vajngerl
CommitDate: Mon Jul 8 02:01:07 2019 +0200
tdf#125655 disbale quick edit mode for iOS and Android
When clicking (tapping) on text in text based objects (shape with
text or a text frame), it automatically enters editing mode,
which is not a desired behaviour in a touch based environment.
This behaviour comes from a quick edit mode, which is enabled by
default on the desktop. For Andorid and iOS this is now disabled
when LOK is initialized.
For online this change might also make sense (if the user would
use a mobile device), however this is not implemented now as this
would require more than just changing the global configuration,
as it needs to behave differently depending on the view/user.
Change-Id: Ib4a71cba0aeb4238a5d5b708801a07b39fb5f316
Reviewed-on: https://gerrit.libreoffice.org/74986
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
(cherry picked from commit 7d32994ad9dc45c7846664ec5ccb03bb796bb071)
Reviewed-on: https://gerrit.libreoffice.org/74987
Tested-by: Jenkins CollaboraOffice
diff --git a/desktop/source/lib/init.cxx b/desktop/source/lib/init.cxx
index 6abda3e775a5..f3f3fd0f6f49 100644
--- a/desktop/source/lib/init.cxx
+++ b/desktop/source/lib/init.cxx
@@ -155,6 +155,7 @@
#include "lokinteractionhandler.hxx"
#include "lokclipboard.hxx"
+#include
using namespace css;
using namespace vcl;
@@ -5264,6 +5265,16 @@ static int lo_initialize(LibreOfficeKit* pThis, const
char* pAppPath, const char
rtl_alloc_preInit(rtlAllocPostInit);
}
+// Turn off quick editing on IOS and ANDROID
+#if defined IOS || defined ANDROID
+if (officecfg::Office::Impress::Misc::TextObject::QuickEditing::get())
+{
+std::shared_ptr
batch(comphelper::ConfigurationChanges::create());
+officecfg::Office::Impress::Misc::TextObject::QuickEditing::set(false,
batch);
+batch->commit();
+}
+#endif
+
return bInitialized;
}
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] online.git: loleaflet/src
loleaflet/src/control/Control.Header.js | 118 +++-
1 file changed, 101 insertions(+), 17 deletions(-)
New commits:
commit 8049e28aaf2178a0c261b50ac88d82193f7e7a25
Author: Tomaž Vajngerl
AuthorDate: Sun Jul 7 21:14:05 2019 +0900
Commit: Tomaž Vajngerl
CommitDate: Mon Jul 8 02:00:16 2019 +0200
tdf#124156 gesture support in Calc row/column header for resizing
The headers only worked when resizing with the mouse and the code
assumes that some variables are set when traveling with the mouse
over the header with mousemove. This adds pan gestures to resize
the row and column and refactors code so that it works without
the need for the varables (it recalculates then when gestrue
starts). Mouse events should still work as before.
Change-Id: I55d136497bed06f1be81be7709d34f95b17ab816
Reviewed-on: https://gerrit.libreoffice.org/75176
Reviewed-by: Tomaž Vajngerl
Tested-by: Tomaž Vajngerl
diff --git a/loleaflet/src/control/Control.Header.js
b/loleaflet/src/control/Control.Header.js
index e6be95ee0..81e784dcd 100644
--- a/loleaflet/src/control/Control.Header.js
+++ b/loleaflet/src/control/Control.Header.js
@@ -2,6 +2,7 @@
/*
* Control.Header
*/
+/* global L Hammer */
L.Control.Header = L.Control.extend({
options: {
@@ -24,6 +25,7 @@ L.Control.Header = L.Control.extend({
this._lastMouseOverIndex = undefined;
this._hitResizeArea = false;
this._overHeaderArea = false;
+ this._hammer = null;
this._selectionBackgroundGradient = [ '#3465A4', '#729FCF',
'#004586' ];
@@ -117,6 +119,14 @@ L.Control.Header = L.Control.extend({
},
mouseInit: function (element) {
+ var self = this;
+ if (this._hammer == null) {
+ this._hammer = new Hammer(element);
+ this._hammer.add(new Hammer.Pan({ threshold: 0,
pointers: 0 }));
+ this._hammer.on('panstart panmove panend', function
(event) {
+ self._onPan(event);
+ });
+ }
L.DomEvent.on(element, 'mousedown', this._onMouseDown, this);
},
@@ -256,6 +266,82 @@ L.Control.Header = L.Control.extend({
this._current = entry && !zeroSizeEntry ? entry.index : -1;
},
+ _onPan: function (event) {
+ if (event.pointerType != 'touch')
+ return;
+
+ if (event.type == 'panstart')
+ this._onPanStart(event);
+ else if (event.type == 'panmove') {
+ this._onPanMove(event);
+ }
+ else if (event.type == 'panend') {
+ this._onPanEnd(event);
+ }
+ },
+
+ _entryAtPoint: function(point) {
+ var position = this._getParallelPos(point);
+ position = position - this._position;
+
+ var eachEntry = this._data.getFirst();
+ while (eachEntry) {
+ var start = eachEntry.pos - eachEntry.size;
+ var end = eachEntry.pos;
+ if (position > start && position <= end) {
+ var resizeAreaStart = Math.max(start, end - 3);
+ if (this.isHeaderSelected(eachEntry.index)) {
+ resizeAreaStart = end -
this._resizeHandleSize;
+ }
+ var isMouseOverResizeArea = (position >
resizeAreaStart);
+ return {entry: eachEntry, hit:
isMouseOverResizeArea};
+ }
+ eachEntry = this._data.getNext();
+ }
+ return null;
+ },
+
+ _onPanStart: function (event) {
+ if (this._hitOutline(event))
+ return;
+
+ var target = event.target || event.srcElement;
+ if (!target)
+ return false;
+
+ var result =
this._entryAtPoint(this._hammerEventToCanvasPos(this._canvas, event));
+ if (!result)
+ return false;
+
+ this._mouseOverEntry = result.entry;
+ var rectangle =
this.getHeaderEntryBoundingClientRect(result.entry.index);
+ if (!rectangle)
+ return;
+
+ L.DomUtil.disableImageDrag();
+ L.DomUtil.disableTextSelection();
+
+ this._start = new L.Point(rectangle.left, rectangle.top);
+ this._offset = new L.Point(rectangle.right - event.center.x,
rectangle.bottom - event.center.y);
+ this._item = target;
+ this.onDragStart(this._item, this._start, this._offset,
{clientX: event.center.x, clientY:
[Libreoffice-bugs] [Bug 98627] Spell check options on right click shows junk characters
https://bugs.documentfoundation.org/show_bug.cgi?id=98627 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu --- Comment #15 from Aron Budea --- Can you please upload a sample document with a few of such words? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117050] Unable to copy or paste in the Hyperlink dialog box
https://bugs.documentfoundation.org/show_bug.cgi?id=117050 Aron Budea changed: What|Removed |Added CC||bugs.documentfoundation.org ||_190707-1...@ymy.be --- Comment #9 from Aron Budea --- *** Bug 126270 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126270] Pasting URL in Insert Hyperlink Dialog is impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=126270 Aron Budea changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||ba...@caesar.elte.hu --- Comment #2 from Aron Budea --- Should be fixed as per bug 117050. *** This bug has been marked as a duplicate of bug 117050 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
How do various apps and DEs handle the primary selection?
Hi I'm trying to gather information how various apps handle the primary selection, so I can fix tdf#104717 [1]. There is already a patch for that in Gerrit[2]. The KDE applications I tested keep the primary alive, while they are running and just clear it when they close. So I can select some text in kate and it'll stay in the primary even, if I close the document containing the selected text. AFAIK at least Writer, Calc and Draw use TransferableHelper::ClearSelection to clear the selection. Writer clears the selection in many more places then either Calc or Draw. See $ git grep -B 5 -A 5 SwTransferable::ClearSelection sw And Writer clears it when a Shell closes, while Calc (~ScTabView) and Draw (:~View) clear it when the view is closed. But I'm a bit confused by the terms Shell and View and then there is even a ViewShell... IMHO we shouldn't handle the primary selection lifetime different from the clipboard lifetime. When selecting stuff, the primary should stay alive, even if I close the document or module, just like the normal clipboard. I don't see a point of clearing the selection at all, except on application shutdown, when the application won't be able to serve it anymore. How do other applications you know handle the primary selection? Jan-Marek P.S. I use $ watch -n 1 "xclip -selection clipboard -out; echo; xclip -selection primary -out" to monitor the clibboard status. And if you want to test stuff, be sure to disable clipboard managers, as these often copy stuff between the different clipboards, also resulting in tdf#104717. [1] https://bugs.documentfoundation.org/show_bug.cgi?id=104717 [2] https://gerrit.libreoffice.org/#/c/73906/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 126111] FILEOPEN DOCX “Square” symbols replaced
https://bugs.documentfoundation.org/show_bug.cgi?id=126111 Khaled Hosny changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |dr.khaled.ho...@gmail.com |desktop.org | Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126278] Show in Styles sidebar only use specific styles
https://bugs.documentfoundation.org/show_bug.cgi?id=126278 andreas_k changed: What|Removed |Added CC||kain...@gmail.com Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126278] New: Show in Styles sidebar only use specific styles
https://bugs.documentfoundation.org/show_bug.cgi?id=126278 Bug ID: 126278 Summary: Show in Styles sidebar only use specific styles Product: LibreOffice Version: 6.4.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kain...@gmail.com Description: Styles are very powerfull for office suited also in LibreOffice (writer in special) the styles sidebar is very powerfull. The problem with powerfull stuff is, that it can be also confuse for users that use styles not regular. By default in the styles sidebar the default filter is Hierarchical (drop down menu on bottom). For example in an empty files Writer offers 122 Paragraph Styles to select (which are grouped in a treeview). From this 122 styles there are very common styles like header 1 - 10, title, subtitle, ... (styles that are also in the styles menubar section). But there are also styles that are needed for very specific or software internal stuff like signature, Addressee and Sender (which were used for Envelopes only). MSO offers you to show recommended styles (by default setting). As it's very difficult to define recommended styles (you need an additional GUI configure that the user can change it), I would say show the user ALL Styles (as it is now) BUT for styles that are used for specific toppics like Addressee and Sender were use only if you use the envelope dialog, ... this content related styles will be shown ONLY if you have this content in your document. So it will be an mix between All Styles and Applied Styles. Steps to Reproduce: 1. writer -> styles sidebar 2. Hierarchical selection Actual Results: style sidebar show by default an mix between styles that will be used for software internal stuff and styles the user should select from. Expected Results: Show all styles in Hierarchical form, but for styles that are related to specific tasks show the styles only if the task is available in the document. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126277] Writer Character Styles are not intuitive to read
https://bugs.documentfoundation.org/show_bug.cgi?id=126277 andreas_k changed: What|Removed |Added CC||kain...@gmail.com --- Comment #1 from andreas_k --- Created attachment 152631 --> https://bugs.documentfoundation.org/attachment.cgi?id=152631=edit writer styles sidebar with character styles -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126277] New: Writer Character Styles are not intuitive to read
https://bugs.documentfoundation.org/show_bug.cgi?id=126277 Bug ID: 126277 Summary: Writer Character Styles are not intuitive to read Product: LibreOffice Version: 6.4.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kain...@gmail.com Description: if you open the Character Styles in writer there is no Treeview like in Paragraph Styles and the names are not very intuitive at all. It's very difficult to understood which style is used for which result. In addition Character Styles combine internal used styles like Page Number, Line Numbering with styles with strange names like Example, Definition and styles that should be used from the user like Source Text, Strong Emphasis. Steps to Reproduce: 1. Writer open Styles Sidebar 2. Character Styles Actual Results: Not ready for the enduser Expected Results: Treeview and separate between styles that should be selected by the user and styles that are needed for internal stuff. Styles with strange names should be deleted. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Reveal code, old macros convert them to LO
On 07/07/19 17:06, Tor Lillqvist wrote: > > For the reference: we have a bug report since 2011 > https://bugs.documentfoundation.org/show_bug.cgi?id=34002 > and the corresponding openoffice bug report from 2002 is linked in the > ticket... > > > Which should be a good indication that the request is unreasonable. > I think you mean "impractical" :-( How is it unreasonable for support guys to want to be able to debug their lusers' documents? How is it unreasonable for people like me to want to use a modern word processor, but be able to use it in a manner that we are comfortable, rather than be forced into a "one size fits all" extremely uncomfortable fairy tale bed ... I was serious when I suggested that Uwe's best case for fixing his documents was to "save as plain text" and start again. Bit tricky if the document is full of graphics and other stuff ... Cheers, Wol ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Reveal code, old macros convert them to LO
On 07/07/19 16:42, Dennis Roczek wrote: > > Hi everybody, > > For the reference: we have a bug report since 2011 > https://bugs.documentfoundation.org/show_bug.cgi?id=34002 > and the corresponding openoffice bug report from 2002 is linked in the > ticket... > I notice the bug report mentions being able to edit/delete the formatting codes. If the macros implement THAT then this sounds a lot more promising. Cheers, Wol ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 126276] New: Writer Character Styles: remove Rubies character style
https://bugs.documentfoundation.org/show_bug.cgi?id=126276 Bug ID: 126276 Summary: Writer Character Styles: remove Rubies character style Product: LibreOffice Version: 6.4.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kain...@gmail.com Description: In the character styles there are a lot of different character styles, where it can be difficult for an user to select the correct character style. Rubies Character Style will be used for ruby source code (I think), as there is already an Source Text Character Style I would recommend to remove Ruby Character Style and change to Source Text style in the LibO source code. Steps to Reproduce: 1. writer open Style Sidebar 2. change to character styles 3. there is Rubies and Source Text style Actual Results: Rubies Character Style is not easy to understood what the style is used for and as it's an default style it should be easy understandable for the user what's an style used for. Expected Results: remove Rubies Character Style and use instead Source Text Character Style cause Ruby is an Source Code. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126142] ImageMap menu position inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=126142 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu --- Comment #3 from V Stuart Foote --- (In reply to andreas_k from comment #2) > I moved ImageMap in Draw and Impress in the Tools section. > > Here is the patch https://gerrit.libreoffice.org/#/c/70299/ > And discussion was done in Bug 124198 > > should I move ImageMap in sd and sc modules to? I think you meant sw and sc modules, but yes--moved consistently to under the Tools menu where the sd module already has it active for whole frame or for selected images in Draw & Impress. But it will need help article updates as well, similar to as was done with https://gerrit.libreoffice.org/#/c/71397/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 126142] ImageMap menu position inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=126142 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu --- Comment #3 from V Stuart Foote --- (In reply to andreas_k from comment #2) > I moved ImageMap in Draw and Impress in the Tools section. > > Here is the patch https://gerrit.libreoffice.org/#/c/70299/ > And discussion was done in Bug 124198 > > should I move ImageMap in sd and sc modules to? I think you meant sw and sc modules, but yes--moved consistently to under the Tools menu where the sd module already has it active for whole frame or for selected images in Draw & Impress. But it will need help article updates as well, similar to as was done with https://gerrit.libreoffice.org/#/c/71397/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 126272] Application Error on Debian 9.9 (Crash in: ld-2.24.so)
https://bugs.documentfoundation.org/show_bug.cgi?id=126272 --- Comment #4 from Max A. Dednev --- Additional information: SAL_USE_VCLPLUGIN=gtk3 libreoffice6.2 - works SAL_USE_VCLPLUGIN=gtk libreoffice6.2 - works SAL_USE_VCLPLUGIN=kde4 libreoffice6.2 - works with some UI issues (distorted main menu etc.) SAL_USE_VCLPLUGIN=gen libreoffice6.2 - works But, SAL_USE_VCLPLUGIN=genlo libreoffice6.2 - doesn't work (Application Error). SAL_USE_VCLPLUGIN=kde4lo libreoffice6.2 - doesn't work (Application Error). SAL_USE_VCLPLUGIN=kde5lo libreoffice6.2 - doesn't work (Application Error). SAL_USE_VCLPLUGIN=gtklo libreoffice6.2 - doesn't work (Application Error). SAL_USE_VCLPLUGIN=qt5lo libreoffice6.2 - doesn't work (Application Error). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113136] [META] Find & Replace Dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=113136 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||126275 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=126275 [Bug 126275] Can't find & replace by paragraph styles at once after find by font attributes -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126275] Can't find & replace by paragraph styles at once after find by font attributes
https://bugs.documentfoundation.org/show_bug.cgi?id=126275 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||113136 Version|4.3.0.4 release |4.2.8.2 release Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113136 [Bug 113136] [META] Find & Replace Dialog -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126275] New: Can't find & replace by paragraph styles at once after find by font attributes
https://bugs.documentfoundation.org/show_bug.cgi?id=126275 Bug ID: 126275 Summary: Can't find & replace by paragraph styles at once after find by font attributes Product: LibreOffice Version: 4.3.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: 79045_79...@mail.ru Description: Can't find & replace by paragraph styles at once after find by font attributes Steps to Reproduce: 1. Open Writer 2. Ctrl+H (Edit->Find & Replace) to open F dialog 3. Push Attributes button 4. Select Font weight in list and push OK (do not close F dialog!) 5. Push Attributes button again 6. Unselect Font weight in list and push OK (do not close F dialog!) 7. Check Paragraph styles checkbox 8. Try select style in find or replace drop-down list 9. It are empty 10. Close F dialog 11. Open F dialog 12. Check Paragraph styles checkbox 13. Try select style in find or replace drop-down list 14. It works as expected Actual Results: Can't find & replace by paragraph styles at once after find by font attributes Expected Results: Can find & replace by paragraph styles at once after find by font attributes Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.0.0.alpha0+ (x64) Build ID: a9885aed4ee65067613e5506771b6ae6b5e0bae0 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-07-04_01:38:09 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded and I checked it in to 4.2.8.2 build possible inherrited from OOo -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125961] [Website] Download page should support non-English users better
https://bugs.documentfoundation.org/show_bug.cgi?id=125961 --- Comment #6 from sbucks --- Thank you for caring about the issue. What do you mean by decoupling the l10n effort from the release cycle exactly? Where and when do discussions about bugs and/or UX take place? IMHO the outlined approach adds an extra barrier for end users before they can use LibO which they should not be forced to. For security and administration reasons plain end users (not administrators) usually don’t have permissions to install software. So they will have to enter administration credentials as an extra step. In governmental or enterprise environments where they don’t have them they will fail. Therefore either they would not have LibO in their native language or the organisation’s IT department has to build its own LibO software package including the language pack. I looked how the OpenOffice people handle this, see attachment. On their download site they detect the operating system and language. The user can change both. They offer a full installation package and a separate language pack. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125961] [Website] Download page should support non-English users better
https://bugs.documentfoundation.org/show_bug.cgi?id=125961 --- Comment #7 from sbucks --- Created attachment 152630 --> https://bugs.documentfoundation.org/attachment.cgi?id=152630=edit OpenOffice download site -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 125961] [Website] Download page should support non-English users better
https://bugs.documentfoundation.org/show_bug.cgi?id=125961 --- Comment #6 from sbucks --- Thank you for caring about the issue. What do you mean by decoupling the l10n effort from the release cycle exactly? Where and when do discussions about bugs and/or UX take place? IMHO the outlined approach adds an extra barrier for end users before they can use LibO which they should not be forced to. For security and administration reasons plain end users (not administrators) usually don’t have permissions to install software. So they will have to enter administration credentials as an extra step. In governmental or enterprise environments where they don’t have them they will fail. Therefore either they would not have LibO in their native language or the organisation’s IT department has to build its own LibO software package including the language pack. I looked how the OpenOffice people handle this, see attachment. On their download site they detect the operating system and language. The user can change both. They offer a full installation package and a separate language pack. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 125961] [Website] Download page should support non-English users better
https://bugs.documentfoundation.org/show_bug.cgi?id=125961 --- Comment #5 from sbucks --- Thank you for caring about the issue. What do you mean by decoupling the l10n effort from the release cycle exactly? Where and when do discussions about bugs and/or UX take place? IMHO the outlined approach adds an extra barrier for end users before they can use LibO which they should not be forced to. For security and administration reasons plain end users (not administrators) usually don’t have permissions to install software. So they will have to enter administration credentials as an extra step. In governmental or enterprise environments where they don’t have them they will fail. Therefore either they would not have LibO in their native language or the organisation’s IT department has to build its own LibO software package including the language pack. I looked how the OpenOffice people handles this, see attachment. On their download site they detect the operating system and language. The user can change both. They offer a full installation package and a separate language pack. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 125961] [Website] Download page should support non-English users better
https://bugs.documentfoundation.org/show_bug.cgi?id=125961 --- Comment #5 from sbucks --- Thank you for caring about the issue. What do you mean by decoupling the l10n effort from the release cycle exactly? Where and when do discussions about bugs and/or UX take place? IMHO the outlined approach adds an extra barrier for end users before they can use LibO which they should not be forced to. For security and administration reasons plain end users (not administrators) usually don’t have permissions to install software. So they will have to enter administration credentials as an extra step. In governmental or enterprise environments where they don’t have them they will fail. Therefore either they would not have LibO in their native language or the organisation’s IT department has to build its own LibO software package including the language pack. I looked how the OpenOffice people handles this, see attachment. On their download site they detect the operating system and language. The user can change both. They offer a full installation package and a separate language pack. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126268] FIREBIRD: Migration of DECIMAL creates unusable values
https://bugs.documentfoundation.org/show_bug.cgi?id=126268 MM changed: What|Removed |Added Version|6.3.0.0.beta2+ |6.3.0.0.alpha1+ Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from MM --- Confirmed on mint 19.1 x64 with Version: 6.4.0.0.alpha0+ Build ID: 7440ca952c51a756bdc49d436abff1af25fe745b CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-06-27_16:34:10 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded and Version: 6.3.0.0.alpha1+ Build ID: 77ae0abe21f672cf4b7d2e069f1d40d20edc49a7 CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-31_15:33:33 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126272] Application Error on Debian 9.9 (Crash in: ld-2.24.so)
https://bugs.documentfoundation.org/show_bug.cgi?id=126272 --- Comment #3 from Max A. Dednev --- Created attachment 152629 --> https://bugs.documentfoundation.org/attachment.cgi?id=152629=edit ld log file for libreoffice 6.2.5 Run results from LD_DEBUG=all libreoffice6.2 > log.txt 2>&1 Warning: about 280 MB decompressed file size. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 126142] ImageMap menu position inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=126142 --- Comment #2 from andreas_k --- I moved ImageMap in Draw and Impress in the Tools section. Here is the patch https://gerrit.libreoffice.org/#/c/70299/ And discussion was done in Bug 124198 should I move ImageMap in sd and sc modules to? -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 126142] ImageMap menu position inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=126142 --- Comment #2 from andreas_k --- I moved ImageMap in Draw and Impress in the Tools section. Here is the patch https://gerrit.libreoffice.org/#/c/70299/ And discussion was done in Bug 124198 should I move ImageMap in sd and sc modules to? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126274] New: Minimize presentation does not clip portions of images outside of slides
https://bugs.documentfoundation.org/show_bug.cgi?id=126274 Bug ID: 126274 Summary: Minimize presentation does not clip portions of images outside of slides Product: LibreOffice Version: 6.2.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com When using "Minimize Presentation..." in the Tools menu, the result still carries portions of images that go beyond the borders of the actual slides. This is something that's not shown on those slides and should -- similar to the "Delete cropped image areas" option in that function -- be either performed unconditionally or as an option. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126257] Writer styles: Heading subgroup for TOC related stuff
https://bugs.documentfoundation.org/show_bug.cgi?id=126257 --- Comment #4 from andreas_k --- Special is also fine and I would add only an group NO style changes. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 126257] Writer styles: Heading subgroup for TOC related stuff
https://bugs.documentfoundation.org/show_bug.cgi?id=126257 --- Comment #4 from andreas_k --- Special is also fine and I would add only an group NO style changes. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 126273] In Writer, Option Buttons Do Not Appear to be Functional
https://bugs.documentfoundation.org/show_bug.cgi?id=126273 Jim Brooking changed: What|Removed |Added CC||j...@jimbrooking.net --- Comment #1 from Jim Brooking --- Created attachment 152628 --> https://bugs.documentfoundation.org/attachment.cgi?id=152628=edit Test Option Buttons Function in Writer -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126272] Application Error on Debian 9.9 (Crash in: ld-2.24.so)
https://bugs.documentfoundation.org/show_bug.cgi?id=126272 --- Comment #2 from Max A. Dednev --- Latest working version is 6.2.3.2, but 6.2.4.1 doesn't start and says "Application Error". -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126273] New: In Writer, Option Buttons Do Not Appear to be Functional
https://bugs.documentfoundation.org/show_bug.cgi?id=126273 Bug ID: 126273 Summary: In Writer, Option Buttons Do Not Appear to be Functional Product: LibreOffice Version: 6.1.6.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j...@jimbrooking.net Description: Simplest example: Two Option Buttons inserted, Group Name = Group1 for both, Text=Yes for one and No for the other. Yes preset to be selected. Save document as PDF Form. Neither button is selected, neither reacts to a click in PDF viewers. Steps to Reproduce: 1. Open new document. View Form Controls & Form Design. 2. Insert Option Button 1, set Group Name to Group1, Default Status to Selected 3. Insert Option Button 2, set Group Name to Group1. 4. Save file as RB_Test.odt 5. Export file as PDF, General Options "Create PDF Form" only 6. Open resulting PDF file Actual Results: 1. Opened file shows Option Buttons 1 and 2 with neither selected. 2. Neither button reacts to a click. Expected Results: N/A Reproducible: Always User Profile Reset: No Additional Info: 1. Should have opened with Button 1 selected 2. Clicking either button should select that button and deselect the other. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126272] Application Error on Debian 9.9 (Crash in: ld-2.24.so)
https://bugs.documentfoundation.org/show_bug.cgi?id=126272 --- Comment #1 from Max A. Dednev --- Same bug from other user: https://superuser.com/questions/1451070/libreoffce-6-2-4-wont-start-after-upgrade-on-debian-9-9 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126271] Selecting of control points of curves not working correctly for combined polygons
https://bugs.documentfoundation.org/show_bug.cgi?id=126271 --- Comment #1 from Michael Köster --- Created attachment 152627 --> https://bugs.documentfoundation.org/attachment.cgi?id=152627=edit Picture showing the problem -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126271] New: Selecting of control points of curves not working correctly for combined polygons
https://bugs.documentfoundation.org/show_bug.cgi?id=126271 Bug ID: 126271 Summary: Selecting of control points of curves not working correctly for combined polygons Product: LibreOffice Version: 6.2.5.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michael.koes...@mkhs.de Description: Bending of curves on combined polygons does not work. If two polygons are combined and a curve is tried to be bended, Draw sometimes bends a curve of the wrong polygon. This problem refers to: Version: 6.2.5.2 (x64) Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 Steps to Reproduce: - Create two filled polygons, partially overlaying each other. - Combine the polygons. - Use the "Points" tool and select one of the vertices of the "2nd" polygons. Apply "Convert to curve" to convert the segment following the point to a curve. - Try to bend the curve. Click on the corresponding control point and try to move it. Actual Results: You can rather not select that control point. Instead, Draw selects either a vertex or a control point of the "1st" polygon, and moves it to the mouse position. Expected Results: The control point clicked on by the mouse should be selected, allowing the user to bend the curve. Reproducible: Always User Profile Reset: No Additional Info: Looks like this happens for the 2nd of the two polygons, the one that was drawn just before the two objects were combined. This indicates that a kind of index of the polygon is mistaken. Clicking on a control point on the 2nd polygon selects the corresponding control point on the 1st polygon (according to the index of the corresponding vertex). If the line segment on the 1st polygon is not a curve, it selects the vertex following the vertex with the same index as the one clicked on on the 2nd polygon. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sfx2/source
sfx2/source/appl/app.cxx |1 +
1 file changed, 1 insertion(+)
New commits:
commit e390011efa79588eca7ff7a3976a9ca3b3a780a4
Author: Tor Lillqvist
AuthorDate: Sun Jul 7 21:15:00 2019 +0300
Commit: Tor Lillqvist
CommitDate: Sun Jul 7 21:15:06 2019 +0300
Fix unused parameter 'pParent' when !HAVE_FEATURE_SCRIPTING
Change-Id: I1c4b58c55213ce9baadc0c1d4b4e394ee62fa053
diff --git a/sfx2/source/appl/app.cxx b/sfx2/source/appl/app.cxx
index 75ea2ff5e820..53d2aae37da0 100644
--- a/sfx2/source/appl/app.cxx
+++ b/sfx2/source/appl/app.cxx
@@ -523,6 +523,7 @@ SfxApplication::ChooseScript(weld::Window *pParent)
void SfxApplication::MacroOrganizer(weld::Window* pParent, sal_Int16 nTabId)
{
#if !HAVE_FEATURE_SCRIPTING
+(void) pParent;
(void) nTabId;
#else
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 126270] Pasting URL in Insert Hyperlink Dialog is impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=126270 --- Comment #1 from ymybe --- Created attachment 152626 --> https://bugs.documentfoundation.org/attachment.cgi?id=152626=edit step one of my workarround -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Reveal code, old macros convert them to LO
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Tor, On 07.07.2019 18:06, Tor Lillqvist wrote: > > For the reference: we have a bug report since 2011 > https://bugs.documentfoundation.org/show_bug.cgi?id=34002 > and the corresponding openoffice bug report from 2002 is linked in the > ticket... > > > Which should be a good indication that the request is unreasonable. Well or nobody wanted to invest the money/time in such a specialized fea ture and "better" invest the same time / money for "interoperability" of MS formats. It is a specialized feature for power users and thus the amount of potential users is very, VERY low. But that doesn't mean that the "few users" of this feature would fell in love. Hence read the forum entries: there are so many users who try to get the old WordPrefect somehow working... It is similar to old Opera12 users using the browser for special cases and miss many of these features in other browsers (luckily finally Vivaldi is catching up as a drop-in-replacement!) > --tml Best, Dennis -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEhYmMfFabYko4V91Tzj5B/c4qttkFAl0iK9MACgkQzj5B/c4q ttm1HhAAxr3a2TOMXgmejTyibheG8wmReDye75hUiqgC0GGxH0GToJdlMUSrgsgB nzyIq5cXAOMtpS/36YGjrbGtenx7DgglrjY9cikW4HFOQBFj2fm1WgodTLFCEfCA MYeXOTNixoKJXjcyPSmUfGmDHPTUrRQODgKfrgft5PV9wlHXyU4hMccWSBs5FTyJ xqLJSJYsFtf29U3vCKQ9lZb8IwGjEP7zt/8V3Q0KEr/YkatsjRl523aFFwK/P9vU qaIAn0rPsEv6rrVWpAmQTHEGwmQfgV/SHBE6eUKtG8zy0oPqTeEgTcYn4gw7aEbE NieMJyzdDDpxrOtu/IB1g+PJX8HuuLibbUL4rcQw5DKB0Hi8GqP/aKKqbbArTeGb reSS/zTmChT8jZa4Te1fA2kN/P6zMTWjqkt4BnNWNGWHac7ts2aRrDzU0Rzagssz 6RQvMnrAbCPoZx5AeFB3zuI5XDByUkc5tQzsyMnYLrRZ6cZvrtCgJGWaq1QjvF+A k99HPA5VZPDbCLCAg+Ed4TAlIzbLFz+swH7aInsOmRmcX31s8MX0T4yLonLalBij xrE3glueAbpyJPAwuKQHIEmjSvAUZ2z15KKqrbs11KBKOhC9IqUewSFo258yPjQS E/1nVeujEzJ4C+Qac6rJlzx+1+L4msv4pjPvKbwop1QxVn87Nkk= =hWHU -END PGP SIGNATURE- ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 126270] New: Pasting URL in Insert Hyperlink Dialog is impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=126270
Bug ID: 126270
Summary: Pasting URL in Insert Hyperlink Dialog is impossible
Product: LibreOffice Online
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: bugs.documentfoundation.org_190707-1...@ymy.be
Created attachment 152625
--> https://bugs.documentfoundation.org/attachment.cgi?id=152625=edit
although the clipboard was filled, nothing was pasteable.
When inserting a Hyperlink via Menu or what would be in offline CTRL+K Menue,
the clipboard isnt pasteable.
Even if copied inside the browser/office window there doesnt seem to be
anything on the clipboard, even via right click and "copy internal" it doesnt
work.
Desired behaviour would be: I paste from clipboard regularly via CTRL+v and the
URL appears in the URL field of the Hyperlink Dialoge-Box
Workaround when multiple Words in cell:
type some words,
paste your link regularly into the cell,
mark the link,
click the insert hyperlink menu,
and in the dialoge change the text to the URL and the text into the word/s you
want you want to appear...
Workaround with just one Word as a Link:
=HYPERLINK("https://;; "words which are clickabkle")
--
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118988] Portyrait/Landscape/Margins issue
https://bugs.documentfoundation.org/show_bug.cgi?id=118988 --- Comment #17 from sweet zzz --- It has been estimated by the Mattress Recycling Council that close to 20 million mattresses end up in a landfill every year, our goal here is to help you find better ways to dispose of your mattress, so we don’t damage our beautiful earth as much as possible. Besides, this will help you keep your houses curb appeal. regards https://sweetzzzmattress.com/blog/what-to-do-with-old-mattresses/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Reveal code, old macros convert them to LO
> > > For the reference: we have a bug report since 2011 > https://bugs.documentfoundation.org/show_bug.cgi?id=34002 > and the corresponding openoffice bug report from 2002 is linked in the > ticket... > Which should be a good indication that the request is unreasonable. --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 34002] EDITING - Add Reveal Codes feature like there is in WordPerfect.
https://bugs.documentfoundation.org/show_bug.cgi?id=34002 --- Comment #21 from Tor Lillqvist --- I would love to resolve this as WONTFIX but I can't handle the shitstorm. Anybody with more clout? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126254] Help - About is black with Linux gen backend
https://bugs.documentfoundation.org/show_bug.cgi?id=126254 Buovjaga changed: What|Removed |Added CC||caol...@redhat.com Keywords|bibisectRequest |bibisected, bisected --- Comment #2 from Buovjaga --- Bibisected with linux-64-6.4 to https://gerrit.libreoffice.org/plugins/gitiles/core/+/a30a5d1b8af18d19526f1980df41857f455cc8ef%5E!/ weld AboutDialog Adding Cc: to Caolán McNamara Note: in addition to Xavier up there, Xisco and jmux are unable to repro this -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Reveal code, old macros convert them to LO
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everybody, For the reference: we have a bug report since 2011 https://bugs.documentfoundation.org/show_bug.cgi?id=34002 and the corresponding openoffice bug report from 2002 is linked in the ticket... Best regards, Dennis Roczek On 04.07.2019 12:08, Uwe Brauer wrote: > > > From time to time the question pops up whether LO could support > Wordperfects reveal code. Sometimes it is stated that this feature could > be implemented by a macro/extension. > > Now I remember that long time ago such macros existed and using the > wayback machine I found them. They were written around 2005 for OO 1.2, > using the sxw format. > > I tried them out in LO 6.2 and they don't work. > > Is there somebody with enough knownledge in macros to translate those > macros to LO 6.2? > > Thanks and regards > > Uwe Brauer > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/libreoffice > -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEhYmMfFabYko4V91Tzj5B/c4qttkFAl0iEvYACgkQzj5B/c4q ttlQsw/9GqIBE9E+2AhB29Yn2ztGD4hHAU+4Twh5CL7rykbALiGQXQ60ISQH/zVZ OuEAt60ugKdC40p6xVpzcDE4xcfVZyG5S0ViTkNHzqLUEQ01zrlA5bYYTRKVetY3 Son3HawDHz3ONlhSozBUhkTeX4P3Ly0kBVcR7i12V3dFgQmvcts5gZJ/ya3HGOpG YeAHRjTmX4tBFwgJ9QHrrn+Hm7Q+xTVvYb9I09pf13lhGdQlvRkqUwrN9P+zsFLu t9BA7A6iiYtVFnx/+VVRIjRpk8gvJq8JMYmzHzKnYCrGkxDbibHba1AF60u9ULAB uvVdSBIwLDkiN3qh+zrkRlUxHks4dvmhE1E1FPkgHaPA7X1SfrVX0L8w8wDWp4AR 8I4xJRPhHPKIaNCN6rvcrxc8lLQ/R0ve0lC/UIZefPORcxQzO5IIzObVAoy/mUjT zK12LqAcLNoqyeI6E4wdbbxlKKNC3x+ItiEXaKDsZ8JuxRsgk22vQgAawNpsrxwk jCysbklW27dtoaD8E66T2/KvahQDOdV9R8kMdbaAULiaVEXebOg0IM9wI5NgEyzG Sikfi7C6gu//fKLxn1w34+NgweMfM6yYIG0byVmX/DP4j3p/ADnlzKpNr8Q4ul6+ M97yn6ltyPu9YyXFS6Ihwj49DZMdtNXMuQv1bX6tG3cmEjwAJMM= =3yAy -END PGP SIGNATURE- ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 126244] EDITING Category labels of bar chart are rotated vertically
https://bugs.documentfoundation.org/show_bug.cgi?id=126244 Jacques Guilleron changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||jal...@laposte.net --- Comment #5 from Jacques Guilleron --- Hi NISZ LibreOffice Team, I reproduce with LO 6.4.0.0.alpha0+ (x86) Build ID: 719f4a93e46a6b397356dbb605d2867639ca3942 CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; Locale: fr-FR (fr_FR); UI-Language: en-US Calc: CL and LO 5.3.7.1 Build ID: 376eaac300a303c4ad2193fb7f6a7522caf550b9 Threads CPU : 2; Version de l'OS :Windows 6.1; UI Render : par défaut; Moteur de mise en page : nouveau; Locale : fr-FR (fr_FR); Calc: CL Jacques -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 122015] Links to external data not preserved (doubled) for XLSX saving in Linux version 6.1.5
https://bugs.documentfoundation.org/show_bug.cgi?id=122015 --- Comment #11 from egc --- Still stuck in the company with LO 547 because of this bug (also in v. 625) ... -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/docvw/edtwin.cxx | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
New commits:
commit 1e4fa857873c0bc728143087ec692c4b75aaf820
Author: Arkadiy Illarionov
AuthorDate: Sun Jul 7 16:36:30 2019 +0300
Commit: Arkadiy Illarionov
CommitDate: Sun Jul 7 17:12:58 2019 +0200
Iterate over explicit array of sequences in QuickHelpData::FillStrArr
Change-Id: Ibce0ce85c8447b9b0d0f464f062306fde7e4a07a
Reviewed-on: https://gerrit.libreoffice.org/75177
Tested-by: Jenkins
Reviewed-by: Arkadiy Illarionov
diff --git a/sw/source/uibase/docvw/edtwin.cxx
b/sw/source/uibase/docvw/edtwin.cxx
index 5ed8668e2e0b..efd52d8ab2c9 100644
--- a/sw/source/uibase/docvw/edtwin.cxx
+++ b/sw/source/uibase/docvw/edtwin.cxx
@@ -5967,8 +5967,11 @@ void QuickHelpData::FillStrArr( SwWrtShell const & rSh,
const OUString& rWord )
(*pCalendar)->LoadDefaultCalendar( rSh.GetCurLang() );
// Add matching calendar month and day names
-uno::Sequence< i18n::CalendarItem2 > aNames( (*pCalendar)->getMonths() );
-for ( sal_uInt16 i = 0; i < 2; ++i )
+const std::array, 2> aCalendarItems = {
+(*pCalendar)->getMonths(),
+(*pCalendar)->getDays()
+};
+for ( const auto& aNames : aCalendarItems )
{
for ( const auto& rName : aNames )
{
@@ -5996,9 +5999,6 @@ void QuickHelpData::FillStrArr( SwWrtShell const & rSh,
const OUString& rWord )
m_aHelpStrings.push_back( rStr );
}
}
-// Data for second loop iteration
-if ( i == 0 )
-aNames = (*pCalendar)->getDays();
}
// Add matching current date in ISO 8601 format, for example 2016-01-30
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
Re: Reveal code, old macros convert them to LO
> On 06/07/19 07:36, Uwe Brauer wrote: > Plus I'm a *text* guy. MS is very much a *visual* company (as are most > people, actually). So the MS way of doing things is alien to me - the WP > way of "here's a gui, this drops into the text setup behind it" is just > *so* *easy*. If you are really a *text* guy, I'd recommend you to give GNU emacs a shot. Nowadays it comes with org mode, which is a sort of ASCII/UTF8 based enhanced text mode, including a very good table editor and best of all you can export it to all sort of formats, odt for example, if you use pandoc you can even save it to docx. https://orgmode.org/ smime.p7s Description: S/MIME cryptographic signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 126261] Right to left (RTL) writing doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=126261 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from V Stuart Foote --- Can not confirm on Windows 10 Home 64-bit en-US with Version: 6.4.0.0.alpha0+ (x64) Build ID: a9885aed4ee65067613e5506771b6ae6b5e0bae0 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-07-04_01:38:09 Locale: en-US (en_US); UI-Language: en-US Calc: threaded Text runs using the Unicode range (10C80-10CFF) with a font that supports it will be rendered RTL (via ICU library bidirectional calls) regardless of the containing paragraph's orientation RTL or LTR. Pre-Unicode PUA mappings onto Latin code points will not. To enable support for RTL, use Tools -> Options -> Language Settings -> Languages and place a check mark in the box for 'Complex text layout', any language the default Hindi, or Hebrew will suffice. That exposes the additional feature support to set the 'Paragraph' mode as either LTR or RTL Please verify use of a font with the Old Hungarian Unicode block. Please verify enabling a Complex text layout choice and that the LTR, RTL toolbar actions appear. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126269] diagonal lines are sticking out when pring, preview, exporting PDF.
https://bugs.documentfoundation.org/show_bug.cgi?id=126269 --- Comment #1 from jun meguro --- Created attachment 152623 --> https://bugs.documentfoundation.org/attachment.cgi?id=152623=edit sample pdf -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126269] New: diagonal lines are sticking out when pring, preview, exporting PDF.
https://bugs.documentfoundation.org/show_bug.cgi?id=126269 Bug ID: 126269 Summary: diagonal lines are sticking out when pring,preview,exporting PDF. Product: LibreOffice Version: 6.2.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jmag...@gmail.com Created attachment 152622 --> https://bugs.documentfoundation.org/attachment.cgi?id=152622=edit sample source file In CALC, when printing, previewing, and creating PDF, diagonal lines are sticking out. Please refer to the attached file. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126257] Writer styles: Heading subgroup for TOC related stuff
https://bugs.documentfoundation.org/show_bug.cgi?id=126257 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- may be better is - Heading - Heading 1 .. 10 - Title - Subtitle - Special - Bibliography Heading - Contents Heading - Figure Index Heading - Index Heading - Object Index Heading - Table Index Heading - User Index Heading and I would don't touch it -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 126257] Writer styles: Heading subgroup for TOC related stuff
https://bugs.documentfoundation.org/show_bug.cgi?id=126257 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- may be better is - Heading - Heading 1 .. 10 - Title - Subtitle - Special - Bibliography Heading - Contents Heading - Figure Index Heading - Index Heading - Object Index Heading - Table Index Heading - User Index Heading and I would don't touch it -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 118043] Firebird: Migration Data loss (change) when moving decimal datatype data defined in HSQL schema
https://bugs.documentfoundation.org/show_bug.cgi?id=118043 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6268 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126268] FIREBIRD: Migration of DECIMAL creates unusable values
https://bugs.documentfoundation.org/show_bug.cgi?id=126268 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||8043 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126268] FIREBIRD: Migration of DECIMAL creates unusable values
https://bugs.documentfoundation.org/show_bug.cgi?id=126268 --- Comment #1 from Robert Großkopf --- Created attachment 152621 --> https://bugs.documentfoundation.org/attachment.cgi?id=152621=edit Database for testing migration of Decimal-values All is tested with LO 6.3.0.0 beta2 on OpenSUSE 15 64bit rpm Linux -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126268] New: FIREBIRD: Migration of DECIMAL creates unusable values
https://bugs.documentfoundation.org/show_bug.cgi?id=126268 Bug ID: 126268 Summary: FIREBIRD: Migration of DECIMAL creates unusable values Product: LibreOffice Version: 6.3.0.0.beta2+ Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Created attachment 152620 --> https://bugs.documentfoundation.org/attachment.cgi?id=152620=edit Shows table before and after migration - unusable values in Decimal-field Open the attached *.pdf-file. It will show a table before and after migration by the migation-wizard from HSQLDB to Firebird. Time-bug is already supported. Migrating of Decimal values is problematic, as shown in bug 118043. The screenshot will show: Migration of decimal values is unusable here. Open the attached *.odb-file and try it yourself. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126267] New: [VIEWING] Incorrect rendering of SVG image while in normal mode but not in slideshow mode
https://bugs.documentfoundation.org/show_bug.cgi?id=126267 Bug ID: 126267 Summary: [VIEWING] Incorrect rendering of SVG image while in normal mode but not in slideshow mode Product: LibreOffice Version: 6.2.4.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ziga...@free.fr Created attachment 152619 --> https://bugs.documentfoundation.org/attachment.cgi?id=152619=edit The files showing the problem Hi ! My SVG image is incorrectly rendered when it is shown in normal view. When the image is rendered in slideshow mode, it is correctly rendered. It is also correctly rendered when exporting to PDF. The bug-affichage.zip file contains the following files: - bug-affichage.odp, a 1 slide file - rendu-vue-normal.png, what it looks like in normal mode on my computer - rendu-vue-slideshow.png, what it looks like in slideshow mode on my computer - schema.svg, the original SVG file created with Inkscape. In normal mode, the lens misses the circle and the cells have bigger frames (the grid looks bolder). Hope it helps! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 65458] FORMATTING: Format not handled correctly when copy paste text from Writer to Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=65458 --- Comment #14 from Xavier Van Wijmeersch --- repro with Version: 6.4.0.0.alpha0+ Build ID: fba2fe825e8dfb9fd084186e3171bbea35297c28 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126254] Help - About is black with Linux gen backend
https://bugs.documentfoundation.org/show_bug.cgi?id=126254 --- Comment #1 from Xavier Van Wijmeersch --- I can not reproduce Version: 6.4.0.0.alpha0+ Build ID: fba2fe825e8dfb9fd084186e3171bbea35297c28 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: x11; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125468] Crash when doing a file reload after recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=125468 Telesto changed: What|Removed |Added OS|All |Windows (All) Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #5 from Telesto --- No change.. still crashing Version: 6.4.0.0.alpha0+ (x86) Build ID: 849b837d1a3b185a8dd893a8f6eaed53605bcab1 CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-07-05_03:53:49 Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126266] LO63rc1: on macOS in Writer's tabbed notebookbar mode the tabs are missing/non switchable
https://bugs.documentfoundation.org/show_bug.cgi?id=126266 Martin Srebotnjak changed: What|Removed |Added Priority|medium |high CC||kain...@gmail.com, ||tima...@gmail.com Severity|normal |major -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126266] LO63rc1: on macOS in Writer's tabbed notebookbar mode the tabs are missing/non switchable
https://bugs.documentfoundation.org/show_bug.cgi?id=126266 --- Comment #1 from Martin Srebotnjak --- Created attachment 152617 --> https://bugs.documentfoundation.org/attachment.cgi?id=152617=edit No tabs in 6.3 RC1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126266] LO63rc1: on macOS in Writer's tabbed notebookbar mode the tabs are missing/non switchable
https://bugs.documentfoundation.org/show_bug.cgi?id=126266 --- Comment #2 from Martin Srebotnjak --- Created attachment 152618 --> https://bugs.documentfoundation.org/attachment.cgi?id=152618=edit Tabs available in 6.3 b1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126265] Slideshow start delayed
https://bugs.documentfoundation.org/show_bug.cgi?id=126265 Telesto changed: What|Removed |Added CC||tele...@surfxs.nl Ever confirmed|0 |1 Status|UNCONFIRMED |NEW OS|Linux (All) |All --- Comment #1 from Telesto --- Repro Version: 6.4.0.0.alpha0+ (x86) Build ID: 849b837d1a3b185a8dd893a8f6eaed53605bcab1 CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-07-05_03:53:49 Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126266] New: LO63rc1: on macOS in Writer's tabbed notebookbar mode the tabs are missing/non switchable
https://bugs.documentfoundation.org/show_bug.cgi?id=126266 Bug ID: 126266 Summary: LO63rc1: on macOS in Writer's tabbed notebookbar mode the tabs are missing/non switchable Product: LibreOffice Version: 6.3.0.0.beta2+ Hardware: All OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mi...@filmsi.net Description: In Writer in tabbed notebookbar UI mode there are no tabs visible so switching is not possible. I am attaching two screenshots, from b1 and from rc1 to make it clear. If confirmed, this seems a stopper for macOS release. Steps to Reproduce: 1. Open Writer with a document in tabbed notebookbar mode. 2. 3. Actual Results: No tabs seen. Expected Results: Tabs available. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
