[Libreoffice-bugs] [Bug 155182] XHTML-Export: Min-Width is set to 0cm together with bullets
https://bugs.documentfoundation.org/show_bug.cgi?id=155182 Robert Großkopf changed: What|Removed |Added Summary|XHTML-Export: Min-Width is |XHTML-Export: Min-Width is |set to 0cm together with|set to 0cm together with |bulltes |bullets -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155182] XHTML-Export: Min-Width is set to 0cm together with bulltes
https://bugs.documentfoundation.org/show_bug.cgi?id=155182 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=95 ||662 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95662] XHTML-Export: Export to html produces wrong decimalseparator together with bullets
https://bugs.documentfoundation.org/show_bug.cgi?id=95662 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5182 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155182] XHTML-Export: Min-Width is set to 0cm together with bulltes
https://bugs.documentfoundation.org/show_bug.cgi?id=155182 Robert Großkopf changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155182] New: XHTML-Export: Min-Width is set to 0cm together with bulltes
https://bugs.documentfoundation.org/show_bug.cgi?id=155182 Bug ID: 155182 Summary: XHTML-Export: Min-Width is set to 0cm together with bulltes Product: LibreOffice Version: 7.2.0.3 rc Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Open attachment https://bugs.documentfoundation.org/attachment.cgi?id=120369 from bug 95662. Go to File → Export. Chose export to xhtml. All content will be shown starting on left border. Margin-left and min-width will both be set to 0cm. This bug first appears with LO 7.2.0.3 on OpenSUSE 15.4 64bit rpm Linux. Reading this it is already bisected: https://bugs.documentfoundation.org/show_bug.cgi?id=95662#c27 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141436] EDITING: transposed formula object has "size zero" and is in wrong cell
https://bugs.documentfoundation.org/show_bug.cgi?id=141436 --- Comment #4 from BogdanB --- Regina, you can mark this bug as Resolved also here. The formula is not distorted anymore. Verified in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4f93995f2262cde0b16bacc83f4ba3c6161ada7f CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Bad in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141437] EDITING: transposed form objects (like circle or line) have wrong dimensions
https://bugs.documentfoundation.org/show_bug.cgi?id=141437 --- Comment #5 from BogdanB --- Regina, you can mark this bug as Resolved also here. Round circle remains the same shape. Verified in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4f93995f2262cde0b16bacc83f4ba3c6161ada7f CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Bad in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155095] Shape over collapsed group is incorrectly resized, when area is pasted
https://bugs.documentfoundation.org/show_bug.cgi?id=155095 --- Comment #3 from BogdanB --- Regina, you can mark this bug as Resolved also here. The group after paste is from D to K, as it should. Verified in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4f93995f2262cde0b16bacc83f4ba3c6161ada7f CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Bad in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155181] New: clicking anywhere in text area corrupts the line instead of putting the cursor in place
https://bugs.documentfoundation.org/show_bug.cgi?id=155181 Bug ID: 155181 Summary: clicking anywhere in text area corrupts the line instead of putting the cursor in place Product: LibreOffice Version: 3.3.4 release Hardware: All OS: other Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alignedtrain...@outlook.com Description: clicking anywhere in text area corrupts the line instead of putting the cursor in place. A few updates ago this started and you end up right justifying a line .. it is most annoying Didn't report it sooner as I imagined there would be a flood of reports over such a fundamental basic bug Steps to Reproduce: 1. open word document with multiple lines .. and pages 2. click on the page to go to the right line 3. watch justification be corrupted and cursor end up anywhere and adding lots of space but the end of the chosen line Actual Results: paragraphs are right justified out of the blue lots of space is added onto the line out to the position of the cursor Expected Results: as previously .. cursor ends up on the end of the line with no extra space added without deliberately adding it Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117090] EDITING: Firebird: migration: View definitions are lost from embedded hsql files using functions unknown to Firebird
https://bugs.documentfoundation.org/show_bug.cgi?id=117090 --- Comment #20 from Robert Großkopf --- Bug is still the same with LO 7.5.3.2 on OpenSUSE 15.4 64bit rpm Linux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155094] Paste transposed does not keep shapes in their cell
https://bugs.documentfoundation.org/show_bug.cgi?id=155094 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #4 from BogdanB --- Regina, you can mark this bug as Resolved also here. Images are well transposed. Verified in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4f93995f2262cde0b16bacc83f4ba3c6161ada7f CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Bad in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: 2 commits - cui/source docmodel/Library_docmodel.mk docmodel/source editeng/source include/docmodel include/editeng include/oox offapi/com offapi/UnoApi_offapi.mk sd/so
cui/source/tabpages/chardlg.cxx|9 +--
docmodel/Library_docmodel.mk |1
docmodel/source/theme/ColorSet.cxx | 12
docmodel/source/uno/UnoComplexColor.cxx| 37
editeng/source/items/textitem.cxx | 58 +++
editeng/source/uno/unotext.cxx |8 +-
include/docmodel/color/ComplexColor.hxx| 87 -
include/docmodel/theme/ColorSet.hxx|3 +
include/docmodel/theme/ThemeColor.hxx |5 +
include/docmodel/uno/UnoComplexColor.hxx | 50
include/editeng/colritem.hxx | 16 +
include/oox/export/ThemeExport.hxx |2
offapi/UnoApi_offapi.mk|1
offapi/com/sun/star/util/XComplexColor.idl | 26
sd/source/ui/view/drtxtob1.cxx |9 +--
sw/source/core/model/ThemeColorChanger.cxx | 16 +++--
sw/source/uibase/shells/textsh1.cxx|2
17 files changed, 284 insertions(+), 58 deletions(-)
New commits:
commit 900c3a2a854436fdbacd488ef1da12ea99fbceb0
Author: Tomaž Vajngerl
AuthorDate: Mon May 1 10:19:06 2023 +0900
Commit: Tomaž Vajngerl
CommitDate: Mon May 8 07:23:17 2023 +0200
svx: use ComplexColor in SvxColorItem instead of the ThemeColor
ComplexColor includes everything a ThemeColor has and in addition
also can have various other representations that are supported by
OOXML. This is important for compatibility reasons to preserve the
color information.
Change-Id: I65a96511dc1742c75b1949e002eaa8c622e2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151226
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/cui/source/tabpages/chardlg.cxx b/cui/source/tabpages/chardlg.cxx
index 0c600f83ab24..601dae8dce0e 100644
--- a/cui/source/tabpages/chardlg.cxx
+++ b/cui/source/tabpages/chardlg.cxx
@@ -1600,10 +1600,11 @@ bool SvxCharEffectsPage::FillItemSetColor_Impl(
SfxItemSet& rSet )
model::ThemeColorType eType =
model::convertToThemeColorType(aSelectedColor.m_nThemeIndex);
if (eType != model::ThemeColorType::Unknown)
{
-aItem.GetThemeColor().setType(eType);
-aItem.GetThemeColor().clearTransformations();
-
aItem.GetThemeColor().addTransformation({model::TransformationType::LumMod,
aSelectedColor.m_nLumMod});
-
aItem.GetThemeColor().addTransformation({model::TransformationType::LumOff,
aSelectedColor.m_nLumOff});
+model::ComplexColor aComplexColor;
+aComplexColor.setSchemeColor(eType);
+
aComplexColor.addTransformation({model::TransformationType::LumMod,
aSelectedColor.m_nLumMod});
+
aComplexColor.addTransformation({model::TransformationType::LumOff,
aSelectedColor.m_nLumOff});
+aItem.setComplexColor(aComplexColor);
}
rSet.Put(aItem);
diff --git a/docmodel/source/theme/ColorSet.cxx
b/docmodel/source/theme/ColorSet.cxx
index 55c03dadba8c..44cd5bdc6c4f 100644
--- a/docmodel/source/theme/ColorSet.cxx
+++ b/docmodel/source/theme/ColorSet.cxx
@@ -50,6 +50,18 @@ Color ColorSet::resolveColor(model::ThemeColor const&
rThemeColor) const
return rThemeColor.applyTransformations(aColor);
}
+Color ColorSet::resolveColor(model::ComplexColor const& rComplexColor) const
+{
+auto eSchemeType = rComplexColor.meSchemeType;
+if (eSchemeType == model::ThemeColorType::Unknown)
+{
+SAL_WARN("svx", "ColorSet::resolveColor with ThemeColorType::Unknown");
+return COL_AUTO;
+}
+Color aColor = getColor(eSchemeType);
+return rComplexColor.applyTransformations(aColor);
+}
+
void ColorSet::dumpAsXml(xmlTextWriterPtr pWriter) const
{
(void)xmlTextWriterStartElement(pWriter, BAD_CAST("ColorSet"));
diff --git a/editeng/source/items/textitem.cxx
b/editeng/source/items/textitem.cxx
index ece9a4a35237..153319ae8e75 100644
--- a/editeng/source/items/textitem.cxx
+++ b/editeng/source/items/textitem.cxx
@@ -1368,10 +1368,10 @@ SvxColorItem::SvxColorItem( const Color& rCol, const
sal_uInt16 nId ) :
{
}
-SvxColorItem::SvxColorItem(Color const& rColor, model::ThemeColor const&
rThemeColor, const sal_uInt16 nId)
+SvxColorItem::SvxColorItem(Color const& rColor, model::ComplexColor const&
rComplexColor, const sal_uInt16 nId)
: SfxPoolItem(nId)
, mColor(rColor)
-, maThemeColor(rThemeColor)
+, maComplexColor(rComplexColor)
{
}
@@ -1385,7 +1385,7 @@ bool SvxColorItem::operator==( const SfxPoolItem& rAttr )
const
const SvxColorItem& rColorItem = static_cast(rAttr);
return mColor == rColorItem.mColor &&
- maThemeColor == rColorItem.maThemeColor;
+ maComplexColor == rColorItem.maComplexColor;
}
bool SvxColorItem::QueryValue( uno::Any& rVal, sal_uInt8 nMemberId ) const
@@ -1406,13 +1406,13 @@ bool SvxColorItem::QueryValue( uno::Any& rVal,
sal_uInt8 nMemberId ) const
[Libreoffice-bugs] [Bug 155142] FORMCONTROLS: Add form control to prevent scrolling in text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=155142 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154969] PDF Export from LibreOffice Draw with colour scheme "LibreOffice Dark" produces a dark PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154969 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155142] FORMCONTROLS: Add form control to prevent scrolling in text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=155142 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148411] Accessing "Help" options crashes LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=148411 --- Comment #9 from QA Administrators --- Dear James Burke, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155060] Writer pdf export black page prints to white and black text
https://bugs.documentfoundation.org/show_bug.cgi?id=155060 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155060] Writer pdf export black page prints to white and black text
https://bugs.documentfoundation.org/show_bug.cgi?id=155060 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98851] Charts move in .xlsx files
https://bugs.documentfoundation.org/show_bug.cgi?id=98851 --- Comment #5 from QA Administrators --- Dear bugzilla-libreoffice, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93033] FORMATTING: Expanded spacing on zero-width characters
https://bugs.documentfoundation.org/show_bug.cgi?id=93033 --- Comment #17 from QA Administrators --- Dear j_mach_wust, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71281] [SECURITY] Password removed from ODS file when saving to XLS, XLT...
https://bugs.documentfoundation.org/show_bug.cgi?id=71281 --- Comment #8 from QA Administrators --- Dear Mikeyy - L10n HR, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72594] File links to range names don't work after re-opening file (unable to create VLOOKUP named range in another file)
https://bugs.documentfoundation.org/show_bug.cgi?id=72594 --- Comment #7 from QA Administrators --- Dear Dave, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 69697] Background color messed with numbered paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=69697 --- Comment #14 from QA Administrators --- Dear kaesezeh, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142045] Text database does not load source.CSV (filetype written in CAPS)
https://bugs.documentfoundation.org/show_bug.cgi?id=142045 --- Comment #5 from QA Administrators --- Dear derfred, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133770] SalUserEventList::isFrameAlive hang after crash
https://bugs.documentfoundation.org/show_bug.cgi?id=133770 --- Comment #31 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132880] Area properties don't match color handling the outline shape receives
https://bugs.documentfoundation.org/show_bug.cgi?id=132880 --- Comment #21 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124534] Extending the offapi documentation for 'AnchorPosition'
https://bugs.documentfoundation.org/show_bug.cgi?id=124534 --- Comment #7 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123543] Borders still on the sheet when move cells when ESC
https://bugs.documentfoundation.org/show_bug.cgi?id=123543 --- Comment #8 from QA Administrators --- Dear Vladimir Schuka, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117090] EDITING: Firebird: migration: View definitions are lost from embedded hsql files using functions unknown to Firebird
https://bugs.documentfoundation.org/show_bug.cgi?id=117090 --- Comment #19 from QA Administrators --- Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107787] Gradients steps don't save
https://bugs.documentfoundation.org/show_bug.cgi?id=107787 --- Comment #29 from QA Administrators --- Dear Leandro Martín Drudi, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155180] New: Format Does Not Work For Select All Cells
https://bugs.documentfoundation.org/show_bug.cgi?id=155180 Bug ID: 155180 Summary: Format Does Not Work For Select All Cells Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: flywi...@gmail.com Description: Selecting all cells in sheet and applying direct formatting only applies formatting to cells within current sheet range. Steps to Reproduce: 1. Enter "Test" in cell A1 2. Click rectangle above row number and to the left of column A to select all cells in sheet 3. Format, Text, Bold 4. In cell B4 enter "More" Actual Results: Cell A5 is not in bold despite all cells in sheet being selected with direct format applied. Formatting is only applied to cells in current sheet range. Expected Results: Direct formating should apply to all selected cells, ie all sheet cells like in excel, not just current range. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155060] Writer pdf export black page prints to white and black text
https://bugs.documentfoundation.org/show_bug.cgi?id=155060 --- Comment #2 from Jeremi Roivas --- What attachments you need, just follow steps and use pdf export and you have white export with black text rather than black page with color text. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148088] UI: Dialog "Load Master Slide" should name "Load Master Page" (alongside several other similar labels)
https://bugs.documentfoundation.org/show_bug.cgi?id=148088 Baole Fang changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #2 from Baole Fang --- Start working on this -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112182] [META] Text and object selection issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112182 Bug 112182 depends on bug 154211, which changed state. Bug 154211 Summary: Allow selecting a range between current cursor position and an element in Navigator with Shift + click (EDITING) https://bugs.documentfoundation.org/show_bug.cgi?id=154211 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Bug 103030 depends on bug 154211, which changed state. Bug 154211 Summary: Allow selecting a range between current cursor position and an element in Navigator with Shift + click (EDITING) https://bugs.documentfoundation.org/show_bug.cgi?id=154211 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154211] Allow selecting a range between current cursor position and an element in Navigator with Shift + click (EDITING)
https://bugs.documentfoundation.org/show_bug.cgi?id=154211 Jim Raykowski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Assignee|libreoffice-b...@lists.free |rayk...@gmail.com |desktop.org | Resolution|--- |FIXED --- Comment #14 from Jim Raykowski --- (In reply to BogdanB from comment #13) > Jim, you can mark as assign, resolved, so on... I will come back later with > Verified. Everything working fine in 7.6. Done. Thanks for the reminder. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108741] [META] Shapes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108741 Bug 108741 depends on bug 155091, which changed state. Bug 155091 Summary: Copy & past doubles object which spans over filtered rows https://bugs.documentfoundation.org/show_bug.cgi?id=155091 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155091] Copy & past doubles object which spans over filtered rows
https://bugs.documentfoundation.org/show_bug.cgi?id=155091 Regina Henschel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Assignee|libreoffice-b...@lists.free |rb.hensc...@t-online.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102593] [META] Paste bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102593 Bug 102593 depends on bug 125938, which changed state. Bug 125938 Summary: Paste cell with cell-anchored images does not put anchor in target cell. https://bugs.documentfoundation.org/show_bug.cgi?id=125938 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125938] Paste cell with cell-anchored images does not put anchor in target cell.
https://bugs.documentfoundation.org/show_bug.cgi?id=125938 Regina Henschel changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |rb.hensc...@t-online.de |desktop.org | Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154499] Accept consecutive words with spaces aka phrases in spellchecker
https://bugs.documentfoundation.org/show_bug.cgi?id=154499 László Németh changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |nem...@numbertext.org |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: writerfilter/source
writerfilter/source/dmapper/TrackChangesHandler.cxx | 21 ++--
1 file changed, 7 insertions(+), 14 deletions(-)
New commits:
commit 002ae41bb6088002ba3ed0188ac822fb823a23f9
Author: Julien Nabet
AuthorDate: Sun May 7 17:11:16 2023 +0200
Commit: Julien Nabet
CommitDate: Sun May 7 23:15:54 2023 +0200
Simplify some initializations in writerfilter
Change-Id: Ib9f653c6add8713a9acf9f6b4605323bcb2c6db6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151470
Tested-by: Julien Nabet
Reviewed-by: Julien Nabet
diff --git a/writerfilter/source/dmapper/TrackChangesHandler.cxx
b/writerfilter/source/dmapper/TrackChangesHandler.cxx
index 212f88261c4a..47a52d6df695 100644
--- a/writerfilter/source/dmapper/TrackChangesHandler.cxx
+++ b/writerfilter/source/dmapper/TrackChangesHandler.cxx
@@ -6,6 +6,7 @@
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/.
*/
+#include
#include "TrackChangesHandler.hxx"
#include "PropertyMap.hxx"
#include "ConversionHelper.hxx"
@@ -56,9 +57,6 @@ void TrackChangesHandler::lcl_attribute(Id rName, Value &
rVal)
uno::Sequence
TrackChangesHandler::getRedlineProperties() const
{
-uno::Sequence< beans::PropertyValue > aRedlineProperties(3);
-beans::PropertyValue* pRedlineProperties = aRedlineProperties.getArray();
-
OUString sType;
switch ( m_pRedlineParams->m_nToken & 0x )
{
@@ -75,17 +73,12 @@ uno::Sequence
TrackChangesHandler::getRedlineProperties()
sType = getPropertyName( PROP_TABLE_CELL_DELETE );
break;
}
-
-pRedlineProperties[0].Name = getPropertyName( PROP_REDLINE_TYPE );
-pRedlineProperties[0].Value <<= sType;
-pRedlineProperties[1].Name = getPropertyName( PROP_REDLINE_AUTHOR );
-pRedlineProperties[1].Value <<= m_pRedlineParams->m_sAuthor;
-pRedlineProperties[2].Name = getPropertyName( PROP_REDLINE_DATE_TIME );
-pRedlineProperties[2].Value <<=
ConversionHelper::ConvertDateStringToDateTime( m_pRedlineParams->m_sDate );
-//pRedlineProperties[3].Name = getPropertyName(
PROP_REDLINE_REVERT_PROPERTIES );
-//pRedlineProperties[3].Value <<= pRedline->m_aRevertProperties;
-
-return aRedlineProperties;
+return {
+ comphelper::makePropertyValue(getPropertyName(PROP_REDLINE_TYPE
), uno::Any(sType)),
+
comphelper::makePropertyValue(getPropertyName(PROP_REDLINE_AUTHOR),
uno::Any(m_pRedlineParams->m_sAuthor)),
+
comphelper::makePropertyValue(getPropertyName(PROP_REDLINE_DATE_TIME),
uno::Any(ConversionHelper::ConvertDateStringToDateTime(
m_pRedlineParams->m_sDate )))
+
//comphelper::makePropertyValue(getPropertyName(PROP_REDLINE_REVERT_PROPERTIES),
uno::Any(pRedline->m_aRevertProperties))
+ };
}
void TrackChangesHandler::lcl_sprm(Sprm &) {}
[Libreoffice-bugs] [Bug 148479] A new kind of list (beyond bulleted and numbered): Category indicators
https://bugs.documentfoundation.org/show_bug.cgi?id=148479 --- Comment #9 from Mike Kaganski --- I am afraid that I can't express myself clearly. So let me try in this way, too. A list (in a text document) is *a hierarchy of data* (i.e., a number of elements, which can contain sub-elements), with applied rules how to represent that data. The content of the elements themselves does *not* affect how the rules work. This is the most important thing that I try to say; and as soon as you suggest to make the rules consider anything else than the items' hierarchy, this breaks the idea put into the list feature. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148479] A new kind of list (beyond bulleted and numbered): Category indicators
https://bugs.documentfoundation.org/show_bug.cgi?id=148479 --- Comment #8 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #7) > (In reply to Mike Kaganski from comment #6) > > (In reply to Eyal Rozenberg from comment #5) > > Oh, you show a logical fallacy: you substitute my "this is a data, so should > > not be treated as metadata" with your "you can do that in a different way" > > ;) > > I argue that list indicator in unordered and in numbered lists also carry > data. Typically, they carry less data - since people don't restart their > lists very often - but they do carry it. Please let's be strict with definitions. We are not talking about the reader. We are talking about creator here. The reader might get the data printed, and have no clue which document markup was used for the printout, so the reader's perspective here is unimportant (and if you include those who parse documents to extract data into "reader" category, my following argumentation applies to them, too). 1. Restarting a list is not adding information. It is actually starting a new list, which happens to have the same formatting. Restarting is an artifact of an implementation, and brings no information itself. So no, this mention doesn't prove anything. 2. Later, you discuss unnumbered items. This example also is incorrect. Unfortunately, *in the UI* this is called as "unnumbered item", creating a false impression that this is *a list item* with some special properties. But this naming is completely misguiding. I advice you to create such a list (very simple, have a couple of "numbered" paragraphs, and one "unnumbered"), save to FODT, and inspect the XML. You will see, that there are only "numbered" (=normal) items in the list; but each *item* can contain *arbitrary number* of paragraphs. So basically, on UI level, it could be *more correct* (but unwanted by vast majority of users) to add selections of paragraphs as list items, so that users would understand the difference between paragraphs and list items. In a way, list item is like table cell: it can hold more that just a single paragraph. So - again, the argument is incorrect, since *every* list item is handles absolutely identically, which is "number its first line, and format the rest according to the formatting rules". 3. So the numbers/bullets get generated based on the fact that the *list* is rendered. Other than defining the list and its content, the user does not need to do anything to define the decorations. And levels are also part of this picture, with sub-items being *part* of higher-level items. Again, use FODT to inspect what ODF thinks about the respective document structure (and what I think about the mental model that should be used for this, incidentally). One defines a list item *content*, and then all decorations are applied automatically, uniformly. Now look at "Done" mark. To make this mark, you can't rely on the *list* properties. You only can define a specific item properties, which is the very difference between the "data" the you (as the writer) define for the specific element, vs. the formatting applied to a list structure. This has no place in the list ideology. It could be possibly implemented as a paragraph style, if one is allergic to tables (many people are, because they were taught that using tables for formatting is EVIL). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148479] A new kind of list (beyond bulleted and numbered): Category indicators
https://bugs.documentfoundation.org/show_bug.cgi?id=148479 Eyal Rozenberg changed: What|Removed |Added Summary|Support A new kind of list: |A new kind of list (beyond |Category indicators |bulleted and numbered): ||Category indicators -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148479] Support A new kind of list: Category indicators
https://bugs.documentfoundation.org/show_bug.cgi?id=148479 Eyal Rozenberg changed: What|Removed |Added Summary|Support category indicators |Support A new kind of list: |in lists|Category indicators -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148479] Support category indicators in lists
https://bugs.documentfoundation.org/show_bug.cgi?id=148479 --- Comment #7 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #6) > (In reply to Eyal Rozenberg from comment #5) > Oh, you show a logical fallacy: you substitute my "this is a data, so should > not be treated as metadata" with your "you can do that in a different way" ;) I argue that list indicator in unordered and in numbered lists also carry data. Typically, they carry less data - since people don't restart their lists very often - but they do carry it. > No, for any list, the fact that it is a list item (top-level element of a > list) *automatically* produces the respective decoration. This can not be > true for your example. Actually, that's not true. It produces the desired decoration usually, but not always: Not when you want to skip the bullet, or restart numbering. I'm suggesting a kind of list in which one injects data more frequently. Also, in at least one of my use cases, the appropriate decoration is produced by default: When you have a task list with not-yet-done and done (or unchecked and checked) - you start by writing the list of not-yet-done items, then over time, perhaps with more edits to the document, you'll mark more items as done. Your concern actually raises the possibility of offering a bit of GUI - when switching to a new paragraph, you might get a small tooltip-like window open up, making it convenient for you to change the category. As an optional feature of course. If I had a bit more time I'd try to sketch something for this with pen-pot. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: cui/source
cui/source/options/optlingu.cxx |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
New commits:
commit 28502c1ddb838381b6202c7b066f6964400a5ef9
Author: Julien Nabet
AuthorDate: Sun May 7 19:29:10 2023 +0200
Commit: Julien Nabet
CommitDate: Sun May 7 22:29:48 2023 +0200
Simplify initialization in cui/source/options/optlingu.cxx
Change-Id: Ie2d68ff2dc9cbc99a10fd3403a72737be4b991dd
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151478
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/cui/source/options/optlingu.cxx b/cui/source/options/optlingu.cxx
index 3530d20f8750..584c86c5f7d6 100644
--- a/cui/source/options/optlingu.cxx
+++ b/cui/source/options/optlingu.cxx
@@ -560,8 +560,11 @@ SvxLinguData_Impl::SvxLinguData_Impl() :
xLinguSrvcMgr = LinguServiceManager::create(xContext);
const Locale& rCurrentLocale =
Application::GetSettings().GetLanguageTag().getLocale();
-Sequence aArgs(2);//second arguments has to be empty!
-aArgs.getArray()[0] <<= LinguMgr::GetLinguPropertySet();
+Sequence aArgs
+{
+Any(LinguMgr::GetLinguPropertySet()),
+Any() // second argument has to be empty!
+};
//read spell checker
const Sequence< OUString > aSpellNames =
xLinguSrvcMgr->getAvailableServices(
[Libreoffice-commits] core.git: framework/inc framework/source
framework/inc/taskcreatordefs.hxx|5 +
framework/source/classes/taskcreator.cxx |2 +-
framework/source/services/taskcreatorsrv.cxx |2 +-
3 files changed, 7 insertions(+), 2 deletions(-)
New commits:
commit 5152841ad0c9e3307285b809b7432bee3df78471
Author: Julien Nabet
AuthorDate: Sun May 7 19:24:25 2023 +0200
Commit: Noel Grandin
CommitDate: Sun May 7 22:15:41 2023 +0200
framework/taskcreator: declare ARGUMENT_HIDDENFORCONVERSION and use it
Change-Id: Ie4e8c24bf776d0ba0e1b7f986fd506521816d2e0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151477
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/framework/inc/taskcreatordefs.hxx
b/framework/inc/taskcreatordefs.hxx
index d4cdcb13189c..c4036e08dc19 100644
--- a/framework/inc/taskcreatordefs.hxx
+++ b/framework/inc/taskcreatordefs.hxx
@@ -55,4 +55,9 @@ inline constexpr OUStringLiteral
ARGUMENT_SUPPORTPERSISTENTWINDOWSTATE
*/
inline constexpr OUStringLiteral ARGUMENT_ENABLE_TITLEBARUPDATE =
u"EnableTitleBarUpdate"; // bool
+/** [bool] enable/disable if the frame is explicitly requested to be hidden
+ Default = OFF !
+ */
+inline constexpr OUStringLiteral ARGUMENT_HIDDENFORCONVERSION =
u"HiddenForConversion"; // bool
+
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/framework/source/classes/taskcreator.cxx
b/framework/source/classes/taskcreator.cxx
index 1372dfeb7c1b..f84bcb711467 100644
--- a/framework/source/classes/taskcreator.cxx
+++ b/framework/source/classes/taskcreator.cxx
@@ -78,7 +78,7 @@ css::uno::Reference< css::frame::XFrame >
TaskCreator::createTask( const OUStrin
css::uno::Any(css::beans::NamedValue(ARGUMENT_MAKEVISIBLE,
css::uno::Any(false))),
css::uno::Any(css::beans::NamedValue(ARGUMENT_SUPPORTPERSISTENTWINDOWSTATE,
css::uno::Any(true))),
css::uno::Any(css::beans::NamedValue(ARGUMENT_FRAMENAME,
css::uno::Any(sName))),
-css::uno::Any(css::beans::NamedValue("HiddenForConversion",
css::uno::Any(rDescriptor.getUnpackedValueOrDefault("HiddenForConversion",
false
+css::uno::Any(css::beans::NamedValue(ARGUMENT_HIDDENFORCONVERSION,
css::uno::Any(rDescriptor.getUnpackedValueOrDefault(ARGUMENT_HIDDENFORCONVERSION,
false
};
css::uno::Reference< css::frame::XFrame >
xTask(xCreator->createInstanceWithArguments(lArgs), css::uno::UNO_QUERY_THROW);
return xTask;
diff --git a/framework/source/services/taskcreatorsrv.cxx
b/framework/source/services/taskcreatorsrv.cxx
index 0d09e30cf572..a4db7856d30a 100644
--- a/framework/source/services/taskcreatorsrv.cxx
+++ b/framework/source/services/taskcreatorsrv.cxx
@@ -128,7 +128,7 @@ css::uno::Reference< css::uno::XInterface > SAL_CALL
TaskCreatorService::createI
bool bSupportPersistentWindowState =
lArgs.getUnpackedValueOrDefault(ARGUMENT_SUPPORTPERSISTENTWINDOWSTATE , false );
bool bEnableTitleBarUpdate =
lArgs.getUnpackedValueOrDefault(ARGUMENT_ENABLE_TITLEBARUPDATE, true );
// If the frame is explicitly requested to be hidden.
-bool bHidden = lArgs.getUnpackedValueOrDefault("HiddenForConversion",
false);
+bool bHidden =
lArgs.getUnpackedValueOrDefault(ARGUMENT_HIDDENFORCONVERSION, false);
// We use FrameName property to set it as API name of the new created
frame later.
// But those frame names must be different from the set of special target
names as e.g. _blank, _self etcpp !
[Libreoffice-bugs] [Bug 148479] Support category indicators in lists
https://bugs.documentfoundation.org/show_bug.cgi?id=148479 --- Comment #6 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #5) > By your logic, a table is the "right tool" for almost any list. Unordered > list? You can either have the bullet on, or off if you type backspace at the > beginning of the paragraph. That's essentially data. So you should have a > two-column table, with one column being either empty or with a bullet. > Numbered list? You can restart the numbering at every paragraph, and change > the starting number, if you like, so - essentially you're storing a number > for every value. So you should have a two-column table, with an index column. Oh, you show a logical fallacy: you substitute my "this is a data, so should not be treated as metadata" with your "you can do that in a different way" ;) No, for any list, the fact that it is a list item (top-level element of a list) *automatically* produces the respective decoration. This can not be true for your example. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154795] Font selection pane offers choice of "language" - which isn't.
https://bugs.documentfoundation.org/show_bug.cgi?id=154795 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #2 from Eyal Rozenberg --- (In reply to Regina Henschel from comment #1) > The field there sets a language/country pair. If you select > "English(Israel)" you get fo:language="en" and fo:country="IL". > > You need this information, for example, to select the appropriate > dictionaries, thesauri, hyphenation rules, and AutoCorrect entries. ... none of which are relevant when choosing a _font_. Changing a font should have no effect on dictionaries, thesauri, hyphenation or autocorrect. So, clearly, the choice of country should be placed somewhere closed to where we control or configure the use of these features. > Are you sure there exists items, which are not considered somewhere? For > example, you can define your own AutoCorrect entries for each of the items > in this 'Language' drop-down list. Even if choosing a country is significant in some contexts, there is rarely a need to choose a pair from the Cartesian product of language x country (as opposed to local language variants). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154795] Font selection pane offers choice of "language" - which isn't.
https://bugs.documentfoundation.org/show_bug.cgi?id=154795 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #2 from Eyal Rozenberg --- (In reply to Regina Henschel from comment #1) > The field there sets a language/country pair. If you select > "English(Israel)" you get fo:language="en" and fo:country="IL". > > You need this information, for example, to select the appropriate > dictionaries, thesauri, hyphenation rules, and AutoCorrect entries. ... none of which are relevant when choosing a _font_. Changing a font should have no effect on dictionaries, thesauri, hyphenation or autocorrect. So, clearly, the choice of country should be placed somewhere closed to where we control or configure the use of these features. > Are you sure there exists items, which are not considered somewhere? For > example, you can define your own AutoCorrect entries for each of the items > in this 'Language' drop-down list. Even if choosing a country is significant in some contexts, there is rarely a need to choose a pair from the Cartesian product of language x country (as opposed to local language variants). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 155054] UI: Remediate frustration of unclear style names in style-name picklist contexts
https://bugs.documentfoundation.org/show_bug.cgi?id=155054 --- Comment #3 from R. Bingham --- FYI, this attachment/comment may show multiple times. I submitted it but it is now not showing in Bugzilla when I re-query this bug 155054. Thanks. I volunteer edit a wide range of documents, accumulating my own library of OTTs AND a library of 100s of styles (for all style types shown in Navigator) across multiple OTTs. I have become very sensitive to the clunky parts of the LO UI regards 'enterprise' style creation and curation for consistency across OTTs. I dream of an enterprise database of LO styles I can manage via a spreadsheet-like presentation for consistency and parameter-value patterns across all my OTTs. Sigh... In the meantime I must make do with the OTT by OTT, style-by-style tabbed-pane GUI. Navigator is my friend. Inheritance is my friend for managing commonality of parameter value sub-sets in tree children. The attached screenshot... well, no, Bugzilla Attachment submission not working at the moment, so laboriously re-create in text here Heading Appendix Hd VolSer 100 LOO LeftAlign Sans parent_only Hd VolSer 110 LOG LftA KeepNext Sans parent_only Hd VolSer 260 VS Vol L03 F/13_Mattr H FM_Title Hd VolSer 264 VS Vol LD4 F/13_Mattr L2 Hd VolSer 268 VS Vol LOS F/B_Mattr L3 Hd VolSer 320 VS Vol Wart L04 UB_I'vlattr LI Hd VolSer 330 VS Vol Wart L05 UB_Mattr L2 Hd VolSer 510 VS Vol Wart 1-StorySet L04 StorySetTitle Hd VolSer 520 VS Vol Wart 1-StorySet L05 F/B_Mattr L1 Hd VolSer 530 VS Vol Wart 1-StorySet LO6 F/B_Mattr L2 Hd VolSer 610 VS Vol Wart 1-StorySet Story LOS StoryTitle L1 Hd VolSer 620 VS Vol Vpart 1-StorySet Story LOS StoryTitle L2 Hd VolSer 710 Vol Wart 1-StorySet Story Chap LD6 ChapTitle L1 Hd VolSer 715 VS Vol Wart 1-StorySet Story Chap LO6 ChapTitle L1 AutoNbr Hd VolSer 720 VS Vol Vpart 1-StorySet Story Chap L06 ChapTitle L2 SubTitle Hd VolSer 730 VS Vol Vpart 1-StorySet Story Chap Anno L07 LO parent_only Hd VolSer 734 VS Vol Vpart 1-StorySet Story Chap Anna 1_07 L1 SubChapTitle Hd VolSer 740 VS Vol VPart 1-StorySet Story Chap Anno L08 L2 Topic Hd VolSer 740 Vol Wart 1-StorySet Story Chap Anno LOB L2 SH_Crono Hd VolSer 780 VS Vol Vpart 1-StorySet Story Chap Anna L10 L4 Char Hd VolSer 150 VS LO1 VolSerTitle Hd VolSer 210 VS Vol L02 VolTitle L1 Hd VolSer 220 VS Vol 1_02 VolTitle L2 SubTitle Hd VolSer 310 VS Vol Wart L03 VpartTitle Hd VolSer L09 LftA Hdr def placeholder Heading 1 ... shows a small part of one of my paragraph styles trees still evolving. Note how I use 'parent only' styles not intended for actual doc use to both encode key parameter value choices in the style name and as a holder of those values for the children. Note how I have had to develop a hints encoding scheme for the style terminal name for when it appears in a tabbed-pane flat picklist. The encoding scheme not only hints at parameter values but also leverages the style-name string sort that usefully happens in both picklist and Navigator presentations. Building up this sort/grouping gives each style-name item a surrounding context as an implicit additional hint of meaning. The encoding burden on the terminal sytle-name could be much less in the Navigator hierarchial view since the inheritance parents are there to also carry some of the encoding in their names as well. I note that Navigator does not offer inheritance for Pages, Lists, and Tables styles. Sadness, and my next UI enhancement requests. Regards. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155054] UI: Remediate frustration of unclear style names in style-name picklist contexts
https://bugs.documentfoundation.org/show_bug.cgi?id=155054 --- Comment #3 from R. Bingham --- FYI, this attachment/comment may show multiple times. I submitted it but it is now not showing in Bugzilla when I re-query this bug 155054. Thanks. I volunteer edit a wide range of documents, accumulating my own library of OTTs AND a library of 100s of styles (for all style types shown in Navigator) across multiple OTTs. I have become very sensitive to the clunky parts of the LO UI regards 'enterprise' style creation and curation for consistency across OTTs. I dream of an enterprise database of LO styles I can manage via a spreadsheet-like presentation for consistency and parameter-value patterns across all my OTTs. Sigh... In the meantime I must make do with the OTT by OTT, style-by-style tabbed-pane GUI. Navigator is my friend. Inheritance is my friend for managing commonality of parameter value sub-sets in tree children. The attached screenshot... well, no, Bugzilla Attachment submission not working at the moment, so laboriously re-create in text here Heading Appendix Hd VolSer 100 LOO LeftAlign Sans parent_only Hd VolSer 110 LOG LftA KeepNext Sans parent_only Hd VolSer 260 VS Vol L03 F/13_Mattr H FM_Title Hd VolSer 264 VS Vol LD4 F/13_Mattr L2 Hd VolSer 268 VS Vol LOS F/B_Mattr L3 Hd VolSer 320 VS Vol Wart L04 UB_I'vlattr LI Hd VolSer 330 VS Vol Wart L05 UB_Mattr L2 Hd VolSer 510 VS Vol Wart 1-StorySet L04 StorySetTitle Hd VolSer 520 VS Vol Wart 1-StorySet L05 F/B_Mattr L1 Hd VolSer 530 VS Vol Wart 1-StorySet LO6 F/B_Mattr L2 Hd VolSer 610 VS Vol Wart 1-StorySet Story LOS StoryTitle L1 Hd VolSer 620 VS Vol Vpart 1-StorySet Story LOS StoryTitle L2 Hd VolSer 710 Vol Wart 1-StorySet Story Chap LD6 ChapTitle L1 Hd VolSer 715 VS Vol Wart 1-StorySet Story Chap LO6 ChapTitle L1 AutoNbr Hd VolSer 720 VS Vol Vpart 1-StorySet Story Chap L06 ChapTitle L2 SubTitle Hd VolSer 730 VS Vol Vpart 1-StorySet Story Chap Anno L07 LO parent_only Hd VolSer 734 VS Vol Vpart 1-StorySet Story Chap Anna 1_07 L1 SubChapTitle Hd VolSer 740 VS Vol VPart 1-StorySet Story Chap Anno L08 L2 Topic Hd VolSer 740 Vol Wart 1-StorySet Story Chap Anno LOB L2 SH_Crono Hd VolSer 780 VS Vol Vpart 1-StorySet Story Chap Anna L10 L4 Char Hd VolSer 150 VS LO1 VolSerTitle Hd VolSer 210 VS Vol L02 VolTitle L1 Hd VolSer 220 VS Vol 1_02 VolTitle L2 SubTitle Hd VolSer 310 VS Vol Wart L03 VpartTitle Hd VolSer L09 LftA Hdr def placeholder Heading 1 ... shows a small part of one of my paragraph styles trees still evolving. Note how I use 'parent only' styles not intended for actual doc use to both encode key parameter value choices in the style name and as a holder of those values for the children. Note how I have had to develop a hints encoding scheme for the style terminal name for when it appears in a tabbed-pane flat picklist. The encoding scheme not only hints at parameter values but also leverages the style-name string sort that usefully happens in both picklist and Navigator presentations. Building up this sort/grouping gives each style-name item a surrounding context as an implicit additional hint of meaning. The encoding burden on the terminal sytle-name could be much less in the Navigator hierarchial view since the inheritance parents are there to also carry some of the encoding in their names as well. I note that Navigator does not offer inheritance for Pages, Lists, and Tables styles. Sadness, and my next UI enhancement requests. Regards. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 147680] Autotext replacement not willing to ignore space after shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=147680 --- Comment #9 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #8) > I see no benefit to including the trailing space for the F3 Autotext > shortcut handling The benefit is that half the time I type an autotext entry key, I also type a space, because I'm used to typing a space after every word. >, and a serious downside of inadvertent replacements by > allowing any non-exact matching. But that's the whole point - it's not inadvertant - it's advertant! It is what the user asked for. > The AutoText dialog +F3 shortcut field does not allow/accept space (or > other whitespace that I tried) for defining a AutoText passage. Even better - that means that there is even less doubt about what the user wanted. Now, if someone were to proposed generalized fuzzy matching - that certainly has downsides and I'd not make it the default behavior. Here we're talking about a very specific case where user intent is clear. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 147680] Autotext replacement not willing to ignore space after shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=147680 --- Comment #9 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #8) > I see no benefit to including the trailing space for the F3 Autotext > shortcut handling The benefit is that half the time I type an autotext entry key, I also type a space, because I'm used to typing a space after every word. >, and a serious downside of inadvertent replacements by > allowing any non-exact matching. But that's the whole point - it's not inadvertant - it's advertant! It is what the user asked for. > The AutoText dialog +F3 shortcut field does not allow/accept space (or > other whitespace that I tried) for defining a AutoText passage. Even better - that means that there is even less doubt about what the user wanted. Now, if someone were to proposed generalized fuzzy matching - that certainly has downsides and I'd not make it the default behavior. Here we're talking about a very specific case where user intent is clear. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 155134] Regression error: exporting files to DOCX results in freezing.
https://bugs.documentfoundation.org/show_bug.cgi?id=155134 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com Keywords||bisected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153041] Empty document ODT includes unnecessary font declarations
https://bugs.documentfoundation.org/show_bug.cgi?id=153041 --- Comment #6 from Eyal Rozenberg --- Seeing this with a recent 7.6 nightly: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5cd9de202765e243e41416802f3e4486b8a96f16 CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US ... and was seeing it in some earlier versions as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 147680] Autotext replacement not willing to ignore space after shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=147680 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #8 from V Stuart Foote --- I see no benefit to including the trailing space for the F3 Autotext shortcut handling, and a serious downside of inadvertent replacements by allowing any non-exact matching. The AutoText dialog +F3 shortcut field does not allow/accept space (or other whitespace that I tried) for defining a AutoText passage. Behaving as implemented. -1 to any change, and otherwise => NAB -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 147680] Autotext replacement not willing to ignore space after shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=147680 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #8 from V Stuart Foote --- I see no benefit to including the trailing space for the F3 Autotext shortcut handling, and a serious downside of inadvertent replacements by allowing any non-exact matching. The AutoText dialog +F3 shortcut field does not allow/accept space (or other whitespace that I tried) for defining a AutoText passage. Behaving as implemented. -1 to any change, and otherwise => NAB -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155179] New: Strange "=>" used in solver dialog for "greater or equal"
https://bugs.documentfoundation.org/show_bug.cgi?id=155179 Bug ID: 155179 Summary: Strange "=>" used in solver dialog for "greater or equal" Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: topicUI Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com In Solver dialog (menu Tools), the limiting conditions have Operator, which includes a normal "<=" for "less than or equal to", but has strange "=>" for "greater than or equal to", instead of widely accepted ">=". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155060] Writer pdf export black page prints to white and black text
https://bugs.documentfoundation.org/show_bug.cgi?id=155060 Tammy changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Tammy --- Is it possible to provide an attachment? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148479] Support category indicators in lists
https://bugs.documentfoundation.org/show_bug.cgi?id=148479 --- Comment #5 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #4) By your logic, a table is the "right tool" for almost any list. Unordered list? You can either have the bullet on, or off if you type backspace at the beginning of the paragraph. That's essentially data. So you should have a two-column table, with one column being either empty or with a bullet. Numbered list? You can restart the numbering at every paragraph, and change the starting number, if you like, so - essentially you're storing a number for every value. So you should have a two-column table, with an index column. > So IMO: mainly WF. The "What people do today" is *the* correct thing to do. Degenerate tables which wrap paragraphs in rows, take up the entire text width, continue over multiple pages, have no borders, and are not perceived by the reader as tables - are generally a fallback alternative to, or an emulation of, a more refined mechanism. Come on, you should be excited about this! After four decades of GUI word processors, there aren't many opportunities to introduce fundamental features. This is one of those! This feature has the potential to be one of the staple text formatting features that any self-respecting office suite has. It will be a "D'oh, how did we not have this before?" kind of an obvious feature. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/inc sw/source
sw/inc/pam.hxx | 16
sw/source/core/crsr/pam.cxx | 12
2 files changed, 4 insertions(+), 24 deletions(-)
New commits:
commit 059892da740e4272477ad0d69183b0e9b77129d7
Author: Mike Kaganski
AuthorDate: Sun May 7 17:39:01 2023 +0200
Commit: Mike Kaganski
CommitDate: Sun May 7 21:03:41 2023 +0200
Simplify a bit
Change-Id: Ibcf59feaa1631c06a393017d1b6342d4a646b9a0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151387
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/inc/pam.hxx b/sw/inc/pam.hxx
index 2a7a0cdb8bd3..62721beb0c4c 100644
--- a/sw/inc/pam.hxx
+++ b/sw/inc/pam.hxx
@@ -27,6 +27,7 @@
#include "nodeoffset.hxx"
#include
+#include
class SwDoc;
class SwPaM;
@@ -230,7 +231,7 @@ public:
void DeleteMark()
{
-if (m_pMark != m_pPoint)
+if (HasMark())
{
/** clear the mark position; this helps if mark's SwContentIndex is
registered at some node, and that node is then deleted */
@@ -238,20 +239,11 @@ public:
m_pMark = m_pPoint;
}
}
-#ifdef DBG_UTIL
-void Exchange();
-
-#else
void Exchange()
{
-if (m_pPoint != m_pMark)
-{
-SwPosition *pTmp = m_pPoint;
-m_pPoint = m_pMark;
-m_pMark = pTmp;
-}
+if (HasMark())
+std::swap(m_pPoint, m_pMark);
}
-#endif
/** A PaM marks a selection if Point and Mark are distinct positions.
@return true if the PaM spans a selection
diff --git a/sw/source/core/crsr/pam.cxx b/sw/source/core/crsr/pam.cxx
index 06690354a8b9..eafa38907fcd 100644
--- a/sw/source/core/crsr/pam.cxx
+++ b/sw/source/core/crsr/pam.cxx
@@ -652,18 +652,6 @@ void SwPaM::SetMark()
(*m_pMark) = *m_pPoint;
}
-#ifdef DBG_UTIL
-void SwPaM::Exchange()
-{
-if (m_pPoint != m_pMark)
-{
-SwPosition *pTmp = m_pPoint;
-m_pPoint = m_pMark;
-m_pMark = pTmp;
-}
-}
-#endif
-
/// movement of cursor
bool SwPaM::Move( SwMoveFnCollection const & fnMove, SwGoInDoc fnGo )
{
[Libreoffice-bugs] [Bug 147680] Autotext replacement not willing to ignore space after shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=147680 Eyal Rozenberg changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|UNCONFIRMED --- Comment #7 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #6) > Neither Dieter or me expect white-space being part of shortcuts. Dieter said that in his opinion this could be an enhancement. So, not enough grounds for closing this. > Consider also the word finalization Not sure what you mean by that. > some procedures run like spell checking and auto correction. => NAB I'm not sure how these things relate to my request. When you've typed some text and press the autotext shortcut (F3), two things can happen: A replacement, or nothing. Now, think about it: Why would I press this shortcut unless I expect a replacement? That's my extremely-likely intent. Now, if there's a "perfect" match for an autotext key in the preceding text, there's no dilemma and you just replace. And if we have no idea what to replace with, we shouldn't just guess. Also, if there are two entries which are just as likely, one could also argue we shouldn't arbitrarily choose one. But - in this case, we have a single candidate entry, and an extra space. What is more likely? That I would rather LO not replace anything, or that what I want is for the space to be elided? You will be hard-pressed to claim the first response is what the user wants, or expects. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108663] [META] AutoText bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108663 Bug 108663 depends on bug 147680, which changed state. Bug 147680 Summary: Autotext replacement not willing to ignore space after shortcut https://bugs.documentfoundation.org/show_bug.cgi?id=147680 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 147680] Autotext replacement not willing to ignore space after shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=147680 Eyal Rozenberg changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|UNCONFIRMED --- Comment #7 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #6) > Neither Dieter or me expect white-space being part of shortcuts. Dieter said that in his opinion this could be an enhancement. So, not enough grounds for closing this. > Consider also the word finalization Not sure what you mean by that. > some procedures run like spell checking and auto correction. => NAB I'm not sure how these things relate to my request. When you've typed some text and press the autotext shortcut (F3), two things can happen: A replacement, or nothing. Now, think about it: Why would I press this shortcut unless I expect a replacement? That's my extremely-likely intent. Now, if there's a "perfect" match for an autotext key in the preceding text, there's no dilemma and you just replace. And if we have no idea what to replace with, we shouldn't just guess. Also, if there are two entries which are just as likely, one could also argue we shouldn't arbitrarily choose one. But - in this case, we have a single candidate entry, and an extra space. What is more likely? That I would rather LO not replace anything, or that what I want is for the space to be elided? You will be hard-pressed to claim the first response is what the user wants, or expects. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sc/source
sc/source/ui/app/inputhdl.cxx | 72 +++---
sc/source/ui/inc/rfindlst.hxx | 12 +++
2 files changed, 53 insertions(+), 31 deletions(-)
New commits:
commit f6a783af88b571ff1f3df9bda31eb0aac66a2c5f
Author: Eike Rathke
AuthorDate: Tue Apr 25 16:44:25 2023 +0200
Commit: Caolán McNamara
CommitDate: Sun May 7 20:50:47 2023 +0200
Resolves: tdf#144547 ScRangeFindList: handle references in multi-line
formula
Also fix a color attribution error if when dragging the reference
the new reference string is longer (colored too short) or shorter
(colored too much including the next characters/operator/...) than
the old reference string.
Change-Id: I1b39fd5778d75290a0233f51a4198753fa858f48
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150979
Reviewed-by: Eike Rathke
Tested-by: Jenkins
(cherry picked from commit 82b887c026cb6b0506ebecdcbc8e4b30362ec55b)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151010
Reviewed-by: Caolán McNamara
diff --git a/sc/source/ui/app/inputhdl.cxx b/sc/source/ui/app/inputhdl.cxx
index 75655d807b73..422a9a128508 100644
--- a/sc/source/ui/app/inputhdl.cxx
+++ b/sc/source/ui/app/inputhdl.cxx
@@ -341,6 +341,20 @@ void ScInputHandler::SendReferenceMarks( const
SfxViewShell* pViewShell,
LOK_CALLBACK_REFERENCE_MARKS, aPayload.getStr() );
}
+static inline void incPos( const sal_Unicode c, sal_Int32& rPos, ESelection&
rSel )
+{
+++rPos;
+if (c == '\n')
+{
+++rSel.nEndPara;
+rSel.nEndPos = 0;
+}
+else
+{
+++rSel.nEndPos;
+}
+}
+
void ScInputHandler::InitRangeFinder( const OUString& rFormula )
{
DeleteRangeFinder();
@@ -350,7 +364,7 @@ void ScInputHandler::InitRangeFinder( const OUString&
rFormula )
ScDocument& rDoc = pDocSh->GetDocument();
const sal_Unicode cSheetSep = rDoc.GetSheetSeparator();
-OUString aDelimiters = ScEditUtil::ModifyDelimiters(" !~\"");
+OUString aDelimiters = ScEditUtil::ModifyDelimiters(" !~\"\t\n");
// delimiters (in addition to ScEditUtil): only characters that are
// allowed in formulas next to references and the quotation mark (so
// string constants can be skipped)
@@ -366,6 +380,7 @@ void ScInputHandler::InitRangeFinder( const OUString&
rFormula )
sal_Int32 nLen = rFormula.getLength();
sal_Int32 nPos = 0;
sal_Int32 nStart = 0;
+ESelection aSel;
sal_uInt16 nCount = 0;
ScRange aRange;
while ( nPos < nLen && nCount < RANGEFIND_MAX )
@@ -375,14 +390,16 @@ void ScInputHandler::InitRangeFinder( const OUString&
rFormula )
{
if ( pChar[nPos] == '"' ) // String
{
-++nPos;
+incPos( pChar[nPos], nPos, aSel);
while (nPosGetTitle() ));
}
-Color nColor = pRangeFindList->Insert( ScRangeFindData(
aRange, nFlags, nStart, nPos ) );
+Color nColor = pRangeFindList->Insert( ScRangeFindData(
aRange, nFlags, aSel));
-ESelection aSel( 0, nStart, 0, nPos );
SfxItemSet aSet( mpEditEngine->GetEmptyItemSet() );
aSet.Put( SvxColorItem( nColor, EE_CHAR_COLOR ) );
mpEditEngine->QuickSetAttribs( aSet, aSel );
@@ -620,8 +636,9 @@ static void lcl_Replace( EditView* pView, const OUString&
rNewStr, const ESelect
// To do that we need to cancel the selection from above (before
QuickInsertText)
pView->InsertText( OUString() );
-sal_Int32 nLen = pEngine->GetTextLen(0);
-ESelection aSel( 0, nLen, 0, nLen );
+const sal_Int32 nPara = pEngine->GetParagraphCount() - 1;
+const sal_Int32 nLen = pEngine->GetTextLen(nPara);
+ESelection aSel( nPara, nLen, nPara, nLen );
pView->SetSelection( aSel ); // Set cursor to the end
}
@@ -631,8 +648,6 @@ void ScInputHandler::UpdateRange( sal_uInt16 nIndex, const
ScRange& rNew )
if ( pDocView && pRangeFindList && nIndex < pRangeFindList->Count() )
{
ScRangeFindData& rData = pRangeFindList->GetObject( nIndex );
-sal_Int32 nOldStart = rData.nSelStart;
-sal_Int32 nOldEnd = rData.nSelEnd;
Color nNewColor = pRangeFindList->FindColor( rNew, nIndex );
ScRange aJustified = rNew;
@@ -640,32 +655,39 @@ void ScInputHandler::UpdateRange( sal_uInt16 nIndex,
const ScRange& rNew )
ScDocument& rDoc = pDocView->GetViewData().GetDocument();
const ScAddress::Details aAddrDetails( rDoc, aCursorPos );
OUString aNewStr(aJustified.Format(rDoc, rData.nFlags, aAddrDetails));
-ESelection aOldSel( 0, nOldStart, 0, nOldEnd );
SfxItemSet aSet( mpEditEngine->GetEmptyItemSet() );
DataChanging();
-lcl_Replace( pTopView, aNewStr, aOldSel );
-lcl_Replace( pTableView, aNewStr, aOldSel );
+lcl_Replace( pTopView, aNewStr,
[Libreoffice-bugs] [Bug 108252] [META] Cell-related bugs and enhancements (including formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=108252 Bug 108252 depends on bug 123156, which changed state. Bug 123156 Summary: Calc: When wrong or large number is converted to date, it should give #ERROR and not wrong date https://bugs.documentfoundation.org/show_bug.cgi?id=123156 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123156] Calc: When wrong or large number is converted to date, it should give #ERROR and not wrong date
https://bugs.documentfoundation.org/show_bug.cgi?id=123156 ady changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from ady --- This is no longer repro, since LO 7.3 > WFM. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155093] Pasted objects copied with cells are not accessible in Navigator because they are not assigned new names
https://bugs.documentfoundation.org/show_bug.cgi?id=155093 --- Comment #7 from BogdanB --- Created attachment 187132 --> https://bugs.documentfoundation.org/attachment.cgi?id=187132=edit the right screenshot In fact this is the right screenshot showing the wrong selection when clicked on the first element after paste. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155093] Pasted objects copied with cells are not accessible in Navigator because they are not assigned new names
https://bugs.documentfoundation.org/show_bug.cgi?id=155093 BogdanB changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155093] Pasted objects copied with cells are not accessible in Navigator because they are not assigned new names
https://bugs.documentfoundation.org/show_bug.cgi?id=155093 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #6 from BogdanB --- Created attachment 187131 --> https://bugs.documentfoundation.org/attachment.cgi?id=187131=edit Before and after Thanks Regina, now they are well numbered. Verified in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4f93995f2262cde0b16bacc83f4ba3c6161ada7f CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Bad in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155091] Copy & past doubles object which spans over filtered rows
https://bugs.documentfoundation.org/show_bug.cgi?id=155091 --- Comment #4 from BogdanB --- Regina you can mark as Assign, Resolved. I will verify later. The image is not duplicating anymore after pasting. It's fixed in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4f93995f2262cde0b16bacc83f4ba3c6161ada7f CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Is bad in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125938] Paste cell with cell-anchored images does not put anchor in target cell.
https://bugs.documentfoundation.org/show_bug.cgi?id=125938 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #7 from BogdanB --- Regina you can mark as Assign, Resolved. I will verify later. The anchor is where it should be now. It's fixed in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4f93995f2262cde0b16bacc83f4ba3c6161ada7f CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Is bad in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - desktop/source include/sfx2 sfx2/source
desktop/source/lib/init.cxx| 87 +
include/sfx2/viewsh.hxx|2
sfx2/source/view/lokhelper.cxx |3 -
sfx2/source/view/viewsh.cxx| 34 +---
4 files changed, 69 insertions(+), 57 deletions(-)
New commits:
commit fb1d24cbc66d37ac5f8217abe072a44a072af420
Author: Marco Cecchetti
AuthorDate: Sun May 7 11:52:14 2023 +0200
Commit: Marco Cecchetti
CommitDate: Sun May 7 20:31:01 2023 +0200
fixup! lok: accessibility event listener for focused paragraph
It seems it was not a good idea using a unique_ptr as smart pointer
for an instance of LOKDocumentFocusListener
Change-Id: I8e6b0f48fee3c5db3c9b074a663f7f3fb96a601e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151459
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Marco Cecchetti
diff --git a/desktop/source/lib/init.cxx b/desktop/source/lib/init.cxx
index 62d8a93733e4..2d1ad0e5a89c 100644
--- a/desktop/source/lib/init.cxx
+++ b/desktop/source/lib/init.cxx
@@ -1368,6 +1368,45 @@ vcl::Font FindFont_FallbackToDefault(std::u16string_view
rFontName)
return OutputDevice::GetDefaultFont(DefaultFontType::SANS_UNICODE,
LANGUAGE_NONE,
GetDefaultFontFlags::NONE);
}
+
+static int getDocumentType (LibreOfficeKitDocument* pThis)
+{
+SetLastExceptionMsg();
+
+LibLODocument_Impl* pDocument = static_cast(pThis);
+
+try
+{
+uno::Reference xDocument(pDocument->mxComponent,
uno::UNO_QUERY_THROW);
+
+if
(xDocument->supportsService("com.sun.star.sheet.SpreadsheetDocument"))
+{
+return LOK_DOCTYPE_SPREADSHEET;
+}
+else if
(xDocument->supportsService("com.sun.star.presentation.PresentationDocument"))
+{
+return LOK_DOCTYPE_PRESENTATION;
+}
+else if
(xDocument->supportsService("com.sun.star.drawing.DrawingDocument"))
+{
+return LOK_DOCTYPE_DRAWING;
+}
+else if (xDocument->supportsService("com.sun.star.text.TextDocument")
|| xDocument->supportsService("com.sun.star.text.WebDocument"))
+{
+return LOK_DOCTYPE_TEXT;
+}
+else
+{
+SetLastExceptionMsg("unknown document type");
+}
+}
+catch (const uno::Exception& exception)
+{
+SetLastExceptionMsg("exception: " + exception.Message);
+}
+return LOK_DOCTYPE_OTHER;
+}
+
} // anonymous namespace
LibLODocument_Impl::LibLODocument_Impl(uno::Reference
xComponent, int nDocumentId)
@@ -3634,40 +3673,7 @@ static int doc_getDocumentType (LibreOfficeKitDocument*
pThis)
comphelper::ProfileZone aZone("doc_getDocumentType");
SolarMutexGuard aGuard;
-SetLastExceptionMsg();
-
-LibLODocument_Impl* pDocument = static_cast(pThis);
-
-try
-{
-uno::Reference xDocument(pDocument->mxComponent,
uno::UNO_QUERY_THROW);
-
-if
(xDocument->supportsService("com.sun.star.sheet.SpreadsheetDocument"))
-{
-return LOK_DOCTYPE_SPREADSHEET;
-}
-else if
(xDocument->supportsService("com.sun.star.presentation.PresentationDocument"))
-{
-return LOK_DOCTYPE_PRESENTATION;
-}
-else if
(xDocument->supportsService("com.sun.star.drawing.DrawingDocument"))
-{
-return LOK_DOCTYPE_DRAWING;
-}
-else if (xDocument->supportsService("com.sun.star.text.TextDocument")
|| xDocument->supportsService("com.sun.star.text.WebDocument"))
-{
-return LOK_DOCTYPE_TEXT;
-}
-else
-{
-SetLastExceptionMsg("unknown document type");
-}
-}
-catch (const uno::Exception& exception)
-{
-SetLastExceptionMsg("exception: " + exception.Message);
-}
-return LOK_DOCTYPE_OTHER;
+return getDocumentType(pThis);
}
static int doc_getParts (LibreOfficeKitDocument* pThis)
@@ -3792,7 +3798,7 @@ static char*
doc_getPartPageRectangles(LibreOfficeKitDocument* pThis)
static char* doc_getA11yFocusedParagraph(LibreOfficeKitDocument* pThis)
{
SolarMutexGuard aGuard;
-
+SetLastExceptionMsg();
ITiledRenderable* pDoc = getTiledRenderable(pThis);
if (!pDoc)
@@ -3812,7 +3818,7 @@ static char*
doc_getA11yFocusedParagraph(LibreOfficeKitDocument* pThis)
static int doc_getA11yCaretPosition(LibreOfficeKitDocument* pThis)
{
SolarMutexGuard aGuard;
-
+SetLastExceptionMsg();
ITiledRenderable* pDoc = getTiledRenderable(pThis);
if (!pDoc)
@@ -7002,14 +7008,13 @@ static void doc_setViewTimezone(SAL_UNUSED_PARAMETER
LibreOfficeKitDocument* /*p
static void doc_setAccessibilityState(SAL_UNUSED_PARAMETER
LibreOfficeKitDocument* pThis, int nId, bool nEnabled)
{
-int nDocType = doc_getDocumentType(pThis);
+SolarMutexGuard aGuard;
+SetLastExceptionMsg();
+
+int nDocType = getDocumentType(pThis);
if (nDocType !=
[Libreoffice-bugs] [Bug 115709] [META] DOCX (OOXML) Tracking changes-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=115709 Bug 115709 depends on bug 151834, which changed state. Bug 151834 Summary: A __DDElink bookmark remains after deleting tracked changes https://bugs.documentfoundation.org/show_bug.cgi?id=151834 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151834] A __DDElink bookmark remains after deleting tracked changes
https://bugs.documentfoundation.org/show_bug.cgi?id=151834 Eyal Rozenberg changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED --- Comment #3 from Eyal Rozenberg --- If this happens to me agagin I'll reopen. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154211] Allow selecting a range between current cursor position and an element in Navigator with Shift + click (EDITING)
https://bugs.documentfoundation.org/show_bug.cgi?id=154211 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #13 from BogdanB --- Jim, you can mark as assign, resolved, so on... I will come back later with Verified. Everything working fine in 7.6. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4f93995f2262cde0b16bacc83f4ba3c6161ada7f CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Was not working in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155178] New: Writer hangs after opening a very large document
https://bugs.documentfoundation.org/show_bug.cgi?id=155178 Bug ID: 155178 Summary: Writer hangs after opening a very large document Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: chris.carter@protonmail.com Description: Opening a very large document in Writer, containing a lot of text and images, starts well and initially seems to render but Writer then hangs displaying a 'busy' icon instead of a cursor and the file cannot be edited or worked with at all. The only action possible is to abort the program through Windows, even after waiting many minutes. I am now unable to edit this document in Writer at all. Steps to Reproduce: 1) Attempt to open a very large Writer (.odt) file containing lots of text and images 2) Writer will open it and correctly display the visible content (i.e. first page) 3) Any attempt to edit, scroll or work with the document results in Writer hanging and becoming permanently unresponsive. Only way out is to abort Writer in Widnows. Actual Results: Writer becomes unresponsive and document cannot be edited or worked with. Expected Results: Writer would allow editing and normal use of the document. Reproducible: Always User Profile Reset: No Additional Info: The .odt file is ~1.3 GB (1,402,548,224 bytes) in size according to Windows. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: 2 commits - desktop/source drawinglayer/source forms/source slideshow/source vcl/source
desktop/source/lib/init.cxx |2 -
drawinglayer/source/primitive2d/graphicprimitivehelper2d.cxx |4 +-
forms/source/component/imgprod.cxx |4 +-
slideshow/source/engine/shapes/gdimtftools.cxx |2 -
vcl/source/bitmap/dibtools.cxx | 22 +--
vcl/source/filter/egif/egif.cxx |2 -
vcl/source/filter/eps/eps.cxx|8 ++--
vcl/source/filter/wmf/emfwr.cxx |6 +--
vcl/source/filter/wmf/wmfwr.cxx |6 +--
9 files changed, 20 insertions(+), 36 deletions(-)
New commits:
commit 1c7cbd685633d44eac554629572f3401c450f855
Author: Noel Grandin
AuthorDate: Sun May 7 16:56:21 2023 +0200
Commit: Noel Grandin
CommitDate: Sun May 7 20:17:16 2023 +0200
use AlphaMask for variables when calling GetAlphaMask
Right now this doesn't make any difference, since Bitmap is the
superclass of AlphaMask.
But when I switch to using alpha instead of transparency, passing
AlphaMask around is going to mean something different to passing plain
Bitmap around.
Change-Id: Ic1541e5f0a3b97331793cd23e23115faa7f382b0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151463
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/desktop/source/lib/init.cxx b/desktop/source/lib/init.cxx
index d6ce62b38be4..7cd3304a2185 100644
--- a/desktop/source/lib/init.cxx
+++ b/desktop/source/lib/init.cxx
@@ -3944,7 +3944,7 @@ static void doc_paintTile(LibreOfficeKitDocument* pThis,
pDevice->EnableMapMode(false);
BitmapEx aBmpEx = pDevice->GetBitmapEx({ 0, 0 }, { nCanvasWidth,
nCanvasHeight });
Bitmap aBmp = aBmpEx.GetBitmap();
-Bitmap aAlpha = aBmpEx.GetAlphaMask();
+AlphaMask aAlpha = aBmpEx.GetAlphaMask();
Bitmap::ScopedReadAccess sraBmp(aBmp);
Bitmap::ScopedReadAccess sraAlpha(aAlpha);
diff --git a/drawinglayer/source/primitive2d/graphicprimitivehelper2d.cxx
b/drawinglayer/source/primitive2d/graphicprimitivehelper2d.cxx
index 8e0c8a980f33..a95df2474744 100644
--- a/drawinglayer/source/primitive2d/graphicprimitivehelper2d.cxx
+++ b/drawinglayer/source/primitive2d/graphicprimitivehelper2d.cxx
@@ -257,7 +257,7 @@ namespace drawinglayer::primitive2d
case Disposal::Not:
{
maVirtualDevice->DrawBitmapEx(rAnimationFrame.maPositionPixel,
rAnimationFrame.maBitmapEx);
-Bitmap aAlphaMask =
rAnimationFrame.maBitmapEx.GetAlphaMask();
+AlphaMask aAlphaMask =
rAnimationFrame.maBitmapEx.GetAlphaMask();
if (aAlphaMask.IsEmpty())
{
@@ -277,7 +277,7 @@ namespace drawinglayer::primitive2d
case Disposal::Back:
{
// #i70772# react on no mask, for primitives, too.
-const Bitmap &
rMask(rAnimationFrame.maBitmapEx.GetAlphaMask());
+const AlphaMask &
rMask(rAnimationFrame.maBitmapEx.GetAlphaMask());
const Bitmap &
rContent(rAnimationFrame.maBitmapEx.GetBitmap());
maVirtualDeviceMask->Erase();
diff --git a/forms/source/component/imgprod.cxx
b/forms/source/component/imgprod.cxx
index faa8663a2461..46439682519f 100644
--- a/forms/source/component/imgprod.cxx
+++ b/forms/source/component/imgprod.cxx
@@ -366,7 +366,7 @@ void ImageProducer::ImplUpdateConsumer( const Graphic&
rGraphic )
if( !pBmpAcc )
return;
-Bitmap aMask( aBmpEx.GetAlphaMask() );
+AlphaMask aMask( aBmpEx.GetAlphaMask() );
BitmapReadAccess* pMskAcc = !aMask.IsEmpty() ? aMask.AcquireReadAccess()
: nullptr;
const tools::Long nWidth = pBmpAcc->Width();
const tools::Long nHeight = pBmpAcc->Height();
@@ -380,7 +380,7 @@ void ImageProducer::ImplUpdateConsumer( const Graphic&
rGraphic )
if( !pMskAcc )
{
aMask = Bitmap(aBmp.GetSizePixel(), vcl::PixelFormat::N8_BPP,
::GetGreyPalette(256));
-aMask.Erase( COL_BLACK );
+aMask.Erase( 0 );
pMskAcc = aMask.AcquireReadAccess();
}
diff --git a/slideshow/source/engine/shapes/gdimtftools.cxx
b/slideshow/source/engine/shapes/gdimtftools.cxx
index 0c9e432850c6..990d9d26caac 100644
--- a/slideshow/source/engine/shapes/gdimtftools.cxx
+++ b/slideshow/source/engine/shapes/gdimtftools.cxx
@@ -283,7 +283,7 @@ bool getAnimationFromGraphic( VectorOfMtfAnimationFrames&
o_rFrames,
{
pVDev->DrawBitmapEx(rAnimationFrame.maPositionPixel,
rAnimationFrame.maBitmapEx);
-Bitmap aMask = rAnimationFrame.maBitmapEx.GetAlphaMask();
+
[Libreoffice-bugs] [Bug 109272] Wrong cursor position when deleting a selection in Show Changes mode
https://bugs.documentfoundation.org/show_bug.cgi?id=109272 --- Comment #27 from Mike Kaganski --- (In reply to Aron Budea from comment #8) > To me where the cursor ends up after deletion with change tracking seems > like a minor detail, as it doesn't affect the behavior, unlike when change > tracking is disabled. (In reply to Heiko Tietze from comment #11) > Kind of academic question to me voting for WONTFIX. (In reply to Heiko Tietze from comment #19) > The current implementation is straight-forward and keeps the cursor at its > place. It is good that the decision was still "let's do it". However, the very idea that it is just a matter of implementation, and that the behavior is unchanged either case, is wrong. (In reply to Rosemary Sebastian from comment #6) > Bug 103458 is related. You may have a look at it. I do hope that you had a look at it. And now think not about the single action, but in a sequence of actions. When user presses Backspace, and then moves somewhere else, it might seem OK either way. But often, the first backspace is followed by more backspaces. Now compare two cases (change tracking enabled, of course): 1. When you have "word", put cursor after "d", and press Backspace four times. 2. When you have "word", *select* "d" left to right, and press Backspace four times. The results would be different. One could tell, that this needs the mentioned bug 103458 fixed. If so, then still the behavior after the first Backspace would be absolutely counter-intuitive, basically wrong: the cursor was placed *at the right of deleted "d"*, but the next backspace removes the character that is not adjacent. And what if you select more than fits to screen? Your cursor is on screen, and you even don't see what will be removed next by the following Backspace. Clear bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155165] Does not show the whole table
https://bugs.documentfoundation.org/show_bug.cgi?id=155165 m.a.riosv changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155165] Does not show the whole table
https://bugs.documentfoundation.org/show_bug.cgi?id=155165 --- Comment #2 from m.a.riosv --- Created attachment 187130 --> https://bugs.documentfoundation.org/attachment.cgi?id=187130=edit Sample file as odt (saved with word) Please don't send private message, the only exception it's if there is no way to eliminate private data from it, to get a sample file. Find attached your sample file, saved as odt with word (it uses odf 1.2), that open fine with 7.4 Tested your file show the whole table with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3bc7cc14706f47d740dfc5715970054922ca470c CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Reproducible with Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: threaded Maybe some of Miklos's latest works about tables has solved the issue. You can download 7.6 from https://dev-builds.libreoffice.org/daily/master/ but they are development versions, not for productivity, at your risk. Lets it resolved as works for me, because it works with v.7.6, and we don't know what has fix it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 BogdanB changed: What|Removed |Added Depends on||57613 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=57613 [Bug 57613] To insert a formula with multiplication generate a loops -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 56856] Incorrect cell size in a 2 column table with resized pictures
https://bugs.documentfoundation.org/show_bug.cgi?id=56856 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #12 from BogdanB --- Also in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6c042848b688f64b3c56d65dd9dc5fe85412660a CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 54778] Unicode issue when pasting into several table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=54778 --- Comment #14 from BogdanB --- Please retest. It seems solved Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6c042848b688f64b3c56d65dd9dc5fe85412660a CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/core/doc/DocumentContentOperationsManager.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 4f93995f2262cde0b16bacc83f4ba3c6161ada7f Author: Mike Kaganski AuthorDate: Sun May 7 17:11:21 2023 +0300 Commit: Mike Kaganski CommitDate: Sun May 7 19:53:27 2023 +0200 tdf#137972: when correcting PaMs, move them to the end The cursor position is pushed in SwView::ExecSpellPopup, and popped in the end, to restore the changed position e.g. when the action is cancelled. In the replacement, the PaM of the pushed cursor is updated in DocumentContentOperationsManager::ReplaceRangeImpl, likely to avoid several updates during the further processing. The stated goal is to move all PaMs out of the deleted range, but the direction is not stated explicitly. If this correction is removed, the cursor PaM gets corrected anyway, and arrives at the end of the replaced text. So, to fix the bug, and to be compliant with the default case, let's correct to the end of the range, instead of the random direction (GetPoint() may return a position at either end, depending how PaM was created). Change-Id: I83bcf01bcc0bf7277a9a34263b524b1212785814 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151462 Tested-by: Jenkins Reviewed-by: Mike Kaganski diff --git a/sw/source/core/doc/DocumentContentOperationsManager.cxx b/sw/source/core/doc/DocumentContentOperationsManager.cxx index 3a158e26a9a1..373532db1eab 100644 --- a/sw/source/core/doc/DocumentContentOperationsManager.cxx +++ b/sw/source/core/doc/DocumentContentOperationsManager.cxx @@ -4480,7 +4480,7 @@ bool DocumentContentOperationsManager::ReplaceRangeImpl( SwPaM& rPam, const OUSt // the other views out of the deletion range. // Except for itself! SwPaM aDelPam( *rPam.GetMark(), *rPam.GetPoint() ); -::PaMCorrAbs( aDelPam, *aDelPam.GetPoint() ); +::PaMCorrAbs( aDelPam, *aDelPam.End() ); auto [pStt, pEnd] = aDelPam.StartEnd(); // SwPosition* bool bOneNode = pStt->GetNode() == pEnd->GetNode();
[Libreoffice-bugs] [Bug 96000] [META] Spelling and grammar checking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=96000 Bug 96000 depends on bug 137972, which changed state. Bug 137972 Summary: Correcting with spell checker context menu places cursor at the left (previously right) https://bugs.documentfoundation.org/show_bug.cgi?id=137972 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137972] Correcting with spell checker context menu places cursor at the left (previously right)
https://bugs.documentfoundation.org/show_bug.cgi?id=137972 Mike Kaganski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit f06b19e0f6d6861b0fcec56fb6de3b2dcaaed0c5 Author: Olivier Hallot AuthorDate: Sun May 7 14:52:15 2023 -0300 Commit: Gerrit Code Review CommitDate: Sun May 7 19:52:15 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to bcabd26061bf9740878cdbbbf09c2efb686d2b24 - Put back string for related topics Change-Id: I63fecc145ddab0948931ffbd8898fd3d1096cff3 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151485 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 35f61fce1428..bcabd26061bf 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 35f61fce142836d5bc2542d474e779532f7e68d7 +Subproject commit bcabd26061bf9740878cdbbbf09c2efb686d2b24
[Libreoffice-commits] help.git: source/text
source/text/shared/00/0004.xhp |5 - 1 file changed, 4 insertions(+), 1 deletion(-) New commits: commit bcabd26061bf9740878cdbbbf09c2efb686d2b24 Author: Olivier Hallot AuthorDate: Sun May 7 14:47:17 2023 -0300 Commit: Olivier Hallot CommitDate: Sun May 7 19:52:15 2023 +0200 Put back string for related topics Change-Id: I63fecc145ddab0948931ffbd8898fd3d1096cff3 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151485 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/shared/00/0004.xhp b/source/text/shared/00/0004.xhp index 3ab4260779..2c05e9f4b8 100644 --- a/source/text/shared/00/0004.xhp +++ b/source/text/shared/00/0004.xhp @@ -28,7 +28,10 @@ To access this command... - + +Related Topics + + Open file with example:
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit ece20eb780d116c891f3286163389006b716b010 Author: Olivier Hallot AuthorDate: Sun May 7 14:50:41 2023 -0300 Commit: Gerrit Code Review CommitDate: Sun May 7 19:50:41 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 35f61fce142836d5bc2542d474e779532f7e68d7 - Update Help page for Line and Filling toolbar + several updates and refactoring Change-Id: I218204d3c37def5acfc89a5eb5b36a19ed3b38be Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151484 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index b8c81e75d909..35f61fce1428 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit b8c81e75d9094cddd2b62f7835d67e6fe2070254 +Subproject commit 35f61fce142836d5bc2542d474e779532f7e68d7
[Libreoffice-commits] help.git: source/text
source/text/sdraw/main0210.xhp |2 - source/text/shared/01/0507.xhp | 15 +- source/text/shared/01/05200100.xhp |1 source/text/shared/01/05240100.xhp | 18 source/text/shared/01/05240200.xhp | 18 source/text/shared/01/grid.xhp | 34 +-- source/text/shared/02/01171400.xhp | 11 +++ source/text/simpress/01/05250500.xhp | 13 +++- source/text/simpress/01/05250600.xhp | 16 -- source/text/simpress/02/1003.xhp |4 +- source/text/simpress/main0202.xhp| 51 +-- 11 files changed, 104 insertions(+), 79 deletions(-) New commits: commit 35f61fce142836d5bc2542d474e779532f7e68d7 Author: Olivier Hallot AuthorDate: Sun May 7 14:41:07 2023 -0300 Commit: Olivier Hallot CommitDate: Sun May 7 19:50:41 2023 +0200 Update Help page for Line and Filling toolbar + several updates and refactoring Change-Id: I218204d3c37def5acfc89a5eb5b36a19ed3b38be Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151484 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/sdraw/main0210.xhp b/source/text/sdraw/main0210.xhp index b4e3891908..0842f26474 100644 --- a/source/text/sdraw/main0210.xhp +++ b/source/text/sdraw/main0210.xhp @@ -32,7 +32,7 @@ Line Color Sets the line color of the selected object. - + Fill Color Sets the area color of the selected object. diff --git a/source/text/shared/01/0507.xhp b/source/text/shared/01/0507.xhp index 9ab4a2f137..ac7702d4db 100644 --- a/source/text/shared/01/0507.xhp +++ b/source/text/shared/01/0507.xhp @@ -19,25 +19,26 @@ --> -Align Objects +Align Objects /text/shared/01/0507.xhp -aligning; objects +aligning; objects positioning; objects ordering; objects - -Align Objects -Aligns selected objects with respect to one another. + +Align Objects +Aligns selected objects with respect to one another. -If one of the selected objects is anchored as a character, some of the alignment options do not work. + +If one of the selected objects is anchored as a character, some of the alignment options do not work. -Not all types of objects can be selected together. Not all modules (Writer, Calc, Impress, Draw) support all types of alignment. +Not all types of objects can be selected together. Not all modules (Writer, Calc, Impress, Draw) support all types of alignment. diff --git a/source/text/shared/01/05200100.xhp b/source/text/shared/01/05200100.xhp index e2cc79d9dc..3b45a1347d 100644 --- a/source/text/shared/01/05200100.xhp +++ b/source/text/shared/01/05200100.xhp @@ -46,6 +46,7 @@ Select a color for the line. + Widths diff --git a/source/text/shared/01/05240100.xhp b/source/text/shared/01/05240100.xhp index 4f1035a2d3..e124fb042f 100644 --- a/source/text/shared/01/05240100.xhp +++ b/source/text/shared/01/05240100.xhp @@ -1,7 +1,4 @@ - - - - - - + -Vertically +Vertically /text/shared/01/05240100.xhp - - -Vertically -Flips the selected object(s) vertically from top to bottom. + + +Flip Vertically +Flips the selected object(s) vertically from top to bottom. + diff --git a/source/text/shared/01/05240200.xhp b/source/text/shared/01/05240200.xhp index 9784688ec9..650b8aa586 100644 --- a/source/text/shared/01/05240200.xhp +++ b/source/text/shared/01/05240200.xhp @@ -1,7 +1,4 @@ - - - - - - + -Horizontally +Horizontally /text/shared/01/05240200.xhp - - -Horizontally -Flips the selected object(s) horizontally from left to right. + + +Flip Horizontally +Flips the selected object(s) horizontally from left to right. + diff --git a/source/text/shared/01/grid.xhp b/source/text/shared/01/grid.xhp index 9786287511..0651b2ae28 100644 --- a/source/text/shared/01/grid.xhp +++ b/source/text/shared/01/grid.xhp @@ -20,7 +20,7 @@ -Grid +Grid /text/shared/01/grid.xhp @@ -28,14 +28,14 @@ - + grids;display options (Impress/Draw) - + -Grid -Sets the display properties of a grid. +Grid +Sets the display properties of a grid. @@ -43,24 +43,28 @@ -Display Grid -Displays or hides grid lines that you can use to align objects such as graphics on a page. + Display Grid +Displays or hides grid lines that you can use to align objects such as graphics on a page. + -Snap to Gridissue 112000 for new key -Automatically aligns objects to vertical and horizontal grid lines. To override this feature, hold down the Option key -Alt key when you drag an object.UFI: copied from shared\optionen\01050100.xhp -UFI removed GridFront help id + + Snap to Grid +Automatically aligns objects to vertical and horizontal grid lines. + + + +To override this feature, hold down the OptionAlt key when you drag an object. -Grid to Front -Displays the grid lines in front of the objects
[Libreoffice-commits] help.git: source/text
source/text/shared/00/00040502.xhp |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit b8c81e75d9094cddd2b62f7835d67e6fe2070254 Author: Olivier Hallot AuthorDate: Sun May 7 14:38:44 2023 -0300 Commit: Olivier Hallot CommitDate: Sun May 7 19:50:09 2023 +0200 Update icon Change-Id: I2bf5920120d2c96a06cd17edef7666ca5c7c2901 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151483 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/shared/00/00040502.xhp b/source/text/shared/00/00040502.xhp index 8b80d15574..c7369f0886 100644 --- a/source/text/shared/00/00040502.xhp +++ b/source/text/shared/00/00040502.xhp @@ -217,7 +217,7 @@ -Icon Position and Size +Icon Position and Size Position and SizeUFI: in Form Design toolbar
[Libreoffice-commits] core.git: 2 commits - helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 5cbfb519aa68465dc4ad6a3fa5ad385e94b2f447 Author: Olivier Hallot AuthorDate: Sun May 7 14:50:09 2023 -0300 Commit: Gerrit Code Review CommitDate: Sun May 7 19:50:09 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to b8c81e75d9094cddd2b62f7835d67e6fe2070254 - Update icon Change-Id: I2bf5920120d2c96a06cd17edef7666ca5c7c2901 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151483 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 9eff87dfdf14..b8c81e75d909 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 9eff87dfdf14777f4a867c5f6614868a9f8bb631 +Subproject commit b8c81e75d9094cddd2b62f7835d67e6fe2070254 commit 3f30e2e60683b83a93e9be918a69ad34b9631b06 Author: Olivier Hallot AuthorDate: Sun May 7 14:49:52 2023 -0300 Commit: Gerrit Code Review CommitDate: Sun May 7 19:49:52 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 9eff87dfdf14777f4a867c5f6614868a9f8bb631 - Refactor - no change in contents Change-Id: Ib8d52fee2054790a97ce5fa57ba573884a96fecf Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151482 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 4bb76d76debd..9eff87dfdf14 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 4bb76d76debdcb5d63ac58da66723759b2af92eb +Subproject commit 9eff87dfdf14777f4a867c5f6614868a9f8bb631
[Libreoffice-commits] help.git: source/text
source/text/simpress/00/0413.xhp | 129 +-- 1 file changed, 66 insertions(+), 63 deletions(-) New commits: commit 9eff87dfdf14777f4a867c5f6614868a9f8bb631 Author: Olivier Hallot AuthorDate: Sun May 7 14:37:50 2023 -0300 Commit: Olivier Hallot CommitDate: Sun May 7 19:49:52 2023 +0200 Refactor - no change in contents Change-Id: Ib8d52fee2054790a97ce5fa57ba573884a96fecf Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151482 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/simpress/00/0413.xhp b/source/text/simpress/00/0413.xhp index 0ca06c2b86..3cc4373dd5 100644 --- a/source/text/simpress/00/0413.xhp +++ b/source/text/simpress/00/0413.xhp @@ -1,6 +1,4 @@ - - - -Shape Menu +Shape Menu /text/simpress/00/0413.xhp @@ -32,136 +29,142 @@ Shape Menu -Choose Shape - Convert (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Convert +Choose Shape - Convert (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Convert -Choose Shape - Convert - To Curve (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Convert - To Curve +Choose Shape - Convert - To Curve (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Convert - To Curve -Choose Shape - Convert - To Polygon (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Convert - To Polygon +Choose Shape - Convert - To Polygon (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Convert - To Polygon -Choose Shape - Convert - To 3D (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Convert - To 3D +Choose Shape - Convert - To 3D (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Convert - To 3D -Choose Shape - Convert - To 3D Rotation Object (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Convert - To 3D Rotation Body +Choose Shape - Convert - To 3D Rotation Object (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Convert - To 3D Rotation Body -Choose Shape - Convert - To Bitmap (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Convert - To Bitmap +Choose Shape - Convert - To Bitmap (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Convert - To Bitmap -Choose Shape - Convert - To Metafile (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Convert - To Metafile +Choose Shape - Convert - To Metafile (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Convert - To Metafile -Choose Shape - Convert - To Contour (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Convert - To Contour +Choose Shape - Convert - To Contour (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Convert - To Contour -Choose Shape - Arrange - In Front of Object (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Arrange - In Front of Object +Choose Shape - Arrange - In Front of Object (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Arrange - In Front of Object -On the Drawing bar, open the Arrange toolbar and click: +On the Drawing bar, open the Arrange toolbar and click: + + - - -Icon - + + +Icon In Front of Object - -In Front of Object + +In Front of Object + -Choose Shape - Arrange - Behind Object (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Arrange - Behind Object +Choose Shape - Arrange - Behind Object (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Arrange - Behind Object -On the Drawing bar, open the Arrange toolbar and click: +On the Drawing bar, open the Arrange toolbar and click: + + - - -Icon - + + +Icon Behind Object - -Behind Object + +Behind Object + -Choose Shape - Arrange - Reverse (%PRODUCTNAME Draw only) -Open the context menu of a selected object and choose Arrange - Reverse +Choose Shape - Arrange - Reverse (%PRODUCTNAME Draw only) +Open the context menu of a selected object and choose Arrange - Reverse -On the Drawing bar, open the Arrange toolbar and click: +On the Drawing bar, open the Arrange toolbar and click: + + - - -Icon - + + +Icon Reverse - -Reverse + +Reverse + -Choose Shape - Combine (%PRODUCTNAME Draw only) -Select two or more objects, open the context menu and choose Combine. +Choose Shape - Combine (%PRODUCTNAME Draw only) +Select two or more objects, open the context menu and choose Combine. -Choose Shape - Split (%PRODUCTNAME Draw
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 6776268604a1282bff26fa9827ac50aa5cd5cb0b Author: Olivier Hallot AuthorDate: Sun May 7 14:49:18 2023 -0300 Commit: Gerrit Code Review CommitDate: Sun May 7 19:49:18 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 4bb76d76debdcb5d63ac58da66723759b2af92eb - Refactor help file, no content change Change-Id: I7f8034e20776809112d86f9253d2980dd343de8c Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151481 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 8b3d7e6a7832..4bb76d76debd 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 8b3d7e6a7832b4c0dd6b489b9ca0f3229dfeb79b +Subproject commit 4bb76d76debdcb5d63ac58da66723759b2af92eb
[Libreoffice-commits] help.git: source/text
source/text/shared/00/00040501.xhp | 14 +- 1 file changed, 9 insertions(+), 5 deletions(-) New commits: commit 4bb76d76debdcb5d63ac58da66723759b2af92eb Author: Olivier Hallot AuthorDate: Sun May 7 14:05:02 2023 -0300 Commit: Olivier Hallot CommitDate: Sun May 7 19:49:18 2023 +0200 Refactor help file, no content change Change-Id: I7f8034e20776809112d86f9253d2980dd343de8c Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151481 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/shared/00/00040501.xhp b/source/text/shared/00/00040501.xhp index df82926e69..75afef4ab4 100644 --- a/source/text/shared/00/00040501.xhp +++ b/source/text/shared/00/00040501.xhp @@ -231,7 +231,8 @@ Choose Shape - Arrange - Bring Forward ($[officename] Draw). CommandCtrl+plus sign ($[officename] Impress, $[officename] Draw) Open context menu - choose Arrange - Bring Forward ($[officename] Impress). - + + Icon Bring Forward @@ -240,14 +241,16 @@ Bring Forward - + + Choose Format - Arrange - Send Backward ($[officename] Writer, $[officename] Calc). Choose Shape - Arrange - Send Backward ($[officename] Draw). CommandCtrl+minus sign ($[officename] Impress, $[officename] Draw) Open context menu - choose Arrange - Send Backward ($[officename] Impress). - + + Icon Send Backward @@ -256,7 +259,8 @@ Send Backward - + + Choose Format - Arrange - Send to Back ($[officename] Writer, $[officename] Calc). @@ -418,7 +422,7 @@ For a selected object, choose Format - Anchor. -Right-click on a selected object - choose Anchor. +Right-click on a selected object - choose Anchor. On Drawing Object Properties bar, Image bar, Frame bar, OLE Objects bar or Form Design bar, click
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 912b25d6bd93a00410592f5b8a8374e0df8bda45 Author: Olivier Hallot AuthorDate: Sun May 7 14:48:39 2023 -0300 Commit: Gerrit Code Review CommitDate: Sun May 7 19:48:39 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 8b3d7e6a7832b4c0dd6b489b9ca0f3229dfeb79b - Refactor - Visit help file for icon updates Change-Id: I69004353c7b6df30e3679900fa9bbe877983d1fc Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151480 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index fb88bf7fa8e5..8b3d7e6a7832 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit fb88bf7fa8e5909ef7da5dde76545eb3b944279b +Subproject commit 8b3d7e6a7832b4c0dd6b489b9ca0f3229dfeb79b
