[Libreoffice-bugs] [Bug 152229] Form Control: Read only doesn't work for special characters. (MacOS only)
https://bugs.documentfoundation.org/show_bug.cgi?id=152229 Robert Großkopf changed: What|Removed |Added Summary|Form Control: Read only |Form Control: Read only |doesn't work for special|doesn't work for special |characters. |characters. (MacOS only) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 Bug 103378 depends on bug 102914, which changed state. Bug 102914 Summary: Synthetic italic in fonts with partial coverage exported as regular in PDF https://bugs.documentfoundation.org/show_bug.cgi?id=102914 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103342] [META] Font substitution bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103342 Bug 103342 depends on bug 102914, which changed state. Bug 102914 Summary: Synthetic italic in fonts with partial coverage exported as regular in PDF https://bugs.documentfoundation.org/show_bug.cgi?id=102914 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Bug 43808 depends on bug 102914, which changed state. Bug 102914 Summary: Synthetic italic in fonts with partial coverage exported as regular in PDF https://bugs.documentfoundation.org/show_bug.cgi?id=102914 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: 2 commits - vcl/inc vcl/quartz vcl/source
vcl/inc/pdf/pdfwriter_impl.hxx|8 +---
vcl/quartz/salgdi.cxx |5 -
vcl/source/gdi/pdfwriter_impl.cxx | 25 -
3 files changed, 21 insertions(+), 17 deletions(-)
New commits:
commit ae2d1315766581259756c819f0227270d344f4d4
Author: Khaled Hosny
AuthorDate: Sun Nov 27 05:10:29 2022 +0200
Commit: خالد حسني
CommitDate: Sun Nov 27 06:00:56 2022 +0100
tdf#102914: keep font attributes for the substituted fallback font
Setting italic to that of the found font seems to prevent artificial
italic in PDF export. We want to keep the original select pattern
attributes so that we know we asked for italic font but got a non-italic
one.
Change-Id: I0cf400e86d802028dffdabbb98e35e3ee584626e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143339
Tested-by: Jenkins
Reviewed-by: خالد حسني
diff --git a/vcl/quartz/salgdi.cxx b/vcl/quartz/salgdi.cxx
index 661a7e76735e..1058b7bc31e9 100644
--- a/vcl/quartz/salgdi.cxx
+++ b/vcl/quartz/salgdi.cxx
@@ -111,11 +111,6 @@ bool
CoreTextGlyphFallbackSubstititution::FindFontSubstitute(vcl::font::FontSele
rPattern.maSearchName = rAttr.GetFamilyName();
-rPattern.SetWeight(rAttr.GetWeight());
-rPattern.SetItalic(rAttr.GetItalic());
-rPattern.SetPitch(rAttr.GetPitch());
-rPattern.SetWidthType(rAttr.GetWidthType());
-
CFRelease(pFallback);
CFRelease(pDesc);
}
commit 521ba0f495919022a77a189c52f632baef02a05c
Author: Khaled Hosny
AuthorDate: Sun Nov 27 03:58:47 2022 +0200
Commit: خالد حسني
CommitDate: Sun Nov 27 06:00:38 2022 +0100
tdf#102914: fix artificial italic of fallback fonts in PDF export
Check the LogicalFontInstance that the glyphs actually use when
deciding whether to do artificial italic or not.
Change-Id: Iefb60cf512285b94ff56d48923c3c33c6a6fbc40
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143338
Tested-by: Jenkins
Reviewed-by: خالد حسني
diff --git a/vcl/inc/pdf/pdfwriter_impl.hxx b/vcl/inc/pdf/pdfwriter_impl.hxx
index b3222f4072fd..6f68478f2f61 100644
--- a/vcl/inc/pdf/pdfwriter_impl.hxx
+++ b/vcl/inc/pdf/pdfwriter_impl.hxx
@@ -615,6 +615,7 @@ struct PDFGlyph
{
DevicePoint const m_aPos;
const GlyphItem* m_pGlyph;
+const LogicalFontInstance* m_pFont;
sal_Int32 const m_nNativeWidth;
sal_Int32 const m_nMappedFontId;
sal_uInt8 const m_nMappedGlyphId;
@@ -622,11 +623,12 @@ struct PDFGlyph
PDFGlyph( const DevicePoint& rPos,
const GlyphItem* pGlyph,
+ const LogicalFontInstance* pFont,
sal_Int32 nNativeWidth,
sal_Int32 nFontId,
sal_uInt8 nMappedGlyphId,
int nCharPos )
-: m_aPos( rPos ), m_pGlyph(pGlyph), m_nNativeWidth( nNativeWidth ),
+: m_aPos( rPos ), m_pGlyph(pGlyph), m_pFont(pFont), m_nNativeWidth(
nNativeWidth ),
m_nMappedFontId( nFontId ), m_nMappedGlyphId( nMappedGlyphId ),
m_nCharPos(nCharPos)
{}
@@ -861,8 +863,8 @@ i12626
/* emits a text object according to the passed layout */
/* TODO: remove rText as soon as SalLayout will change so that rText is
not necessary anymore */
-void drawVerticalGlyphs( const std::vector& rGlyphs,
OStringBuffer& rLine, const Point& rAlignOffset, const Matrix3& rRotScale,
double fAngle, double fXScale, double fSkew, sal_Int32 nFontHeight );
-void drawHorizontalGlyphs( const std::vector& rGlyphs,
OStringBuffer& rLine, const Point& rAlignOffset, bool bFirst, double fAngle,
double fXScale, double fSkew, sal_Int32 nFontHeight, sal_Int32 nPixelFontHeight
);
+void drawVerticalGlyphs( const std::vector& rGlyphs,
OStringBuffer& rLine, const Point& rAlignOffset, const Matrix3& rRotScale,
double fAngle, double fXScale, sal_Int32 nFontHeight );
+void drawHorizontalGlyphs( const std::vector& rGlyphs,
OStringBuffer& rLine, const Point& rAlignOffset, bool bFirst, double fAngle,
double fXScale, sal_Int32 nFontHeight, sal_Int32 nPixelFontHeight );
void drawLayout( SalLayout& rLayout, const OUString& rText, bool
bTextLines );
void drawRelief( SalLayout& rLayout, const OUString& rText, bool
bTextLines );
void drawShadow( SalLayout& rLayout, const OUString& rText, bool
bTextLines );
diff --git a/vcl/source/gdi/pdfwriter_impl.cxx
b/vcl/source/gdi/pdfwriter_impl.cxx
index d107e8996629..34785e2da3f7 100644
--- a/vcl/source/gdi/pdfwriter_impl.cxx
+++ b/vcl/source/gdi/pdfwriter_impl.cxx
@@ -6315,7 +6315,6 @@ void PDFWriterImpl::drawVerticalGlyphs(
const Matrix3& rRotScale,
double fAngle,
double fXScale,
-double fSkew,
sal_Int32 nFontHeight)
{
double nXOffset = 0;
@@ -6327,6 +6326,12 @@ void PDFWriterImpl::drawVerticalGlyphs(
double fDeltaAngle = 0.0;
double fYScale = 1.0;
double fTempXScale = fXScale;
+
+
[Libreoffice-bugs] [Bug 108417] FILEOPEN DOCX Some embedded Arabic fonts are substituted
https://bugs.documentfoundation.org/show_bug.cgi?id=108417 خالد حسني changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5967 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108417] FILEOPEN DOCX Some embedded Arabic fonts are substituted
https://bugs.documentfoundation.org/show_bug.cgi?id=108417 --- Comment #11 from خالد حسني --- (In reply to خالد حسني from comment #10) > May be we should add an info bar informing the user that > the document has embedded fonts but we are not using them, but this would be > a separate enhancement. This is already tracked in bug 145967. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113338] [META] Embedded fonts bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113338 Bug 113338 depends on bug 108417, which changed state. Bug 108417 Summary: FILEOPEN DOCX Some embedded Arabic fonts are substituted https://bugs.documentfoundation.org/show_bug.cgi?id=108417 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145563] LibreOffice and NeoOffice fail to respect each other's selections of Pfeffer Mediaeval due to a ligature in the name
https://bugs.documentfoundation.org/show_bug.cgi?id=145563 --- Comment #3 from MarjaE --- Created attachment 183826 --> https://bugs.documentfoundation.org/attachment.cgi?id=183826=edit 4 lines from LO, 4 lines from NO, same fonts, different renderings -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104520] [META] DOCX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=104520 Bug 104520 depends on bug 108417, which changed state. Bug 108417 Summary: FILEOPEN DOCX Some embedded Arabic fonts are substituted https://bugs.documentfoundation.org/show_bug.cgi?id=108417 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108417] FILEOPEN DOCX Some embedded Arabic fonts are substituted
https://bugs.documentfoundation.org/show_bug.cgi?id=108417 خالد حسني changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #10 from خالد حسني --- The embedded fonts in this document has restricted rights and so we reject them and use substitute fonts. And even if we skipped that, most of the fonts are actually empty so they are rather unusable, the rest are subsetted so also unusable. May be we should add an info bar informing the user that the document has embedded fonts but we are not using them, but this would be a separate enhancement. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103342] [META] Font substitution bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103342 Bug 103342 depends on bug 108417, which changed state. Bug 108417 Summary: FILEOPEN DOCX Some embedded Arabic fonts are substituted https://bugs.documentfoundation.org/show_bug.cgi?id=108417 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148369] Redo of deleting a row track and changes enabled deletes the wrong cell content
https://bugs.documentfoundation.org/show_bug.cgi?id=148369 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152223] 7.4.3.2 Calc has a problem, some keys need [Alt] in quit dialog box.
https://bugs.documentfoundation.org/show_bug.cgi?id=152223 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152110] LanguageTool ext. prevents adding words to dictionaries with 2+ dictionaries present
https://bugs.documentfoundation.org/show_bug.cgi?id=152110 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 152110] LanguageTool ext. prevents adding words to dictionaries with 2+ dictionaries present
https://bugs.documentfoundation.org/show_bug.cgi?id=152110 --- 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 152041] Unixy-like configuration for some variables?
https://bugs.documentfoundation.org/show_bug.cgi?id=152041 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 152041] Unixy-like configuration for some variables?
https://bugs.documentfoundation.org/show_bug.cgi?id=152041 --- 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 149192] UI: Tab menu missing on one screen
https://bugs.documentfoundation.org/show_bug.cgi?id=149192 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149192] UI: Tab menu missing on one screen
https://bugs.documentfoundation.org/show_bug.cgi?id=149192 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 149051] BASE-FORMS: LO hangs when using search function
https://bugs.documentfoundation.org/show_bug.cgi?id=149051 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 149051] BASE-FORMS: LO hangs when using search function
https://bugs.documentfoundation.org/show_bug.cgi?id=149051 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142008] Grid control with multiline text column doesn't wrap
https://bugs.documentfoundation.org/show_bug.cgi?id=142008 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142843] Font hinting of Arial font bit excessive?
https://bugs.documentfoundation.org/show_bug.cgi?id=142843 --- Comment #6 from QA Administrators --- Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142843] Font hinting of Arial font bit excessive?
https://bugs.documentfoundation.org/show_bug.cgi?id=142843 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142008] Grid control with multiline text column doesn't wrap
https://bugs.documentfoundation.org/show_bug.cgi?id=142008 --- Comment #7 from QA Administrators --- Dear patrick.gelin, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149373] Defect report of number of characters vs number of characters excluding spaces plus number of words minus 1 in statistics tab in a big document
https://bugs.documentfoundation.org/show_bug.cgi?id=149373 --- Comment #2 from QA Administrators --- Dear nazem alghazali, 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 149366] Writer crashes on printing doc with graphics
https://bugs.documentfoundation.org/show_bug.cgi?id=149366 --- Comment #3 from QA Administrators --- Dear TimStevenson, 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 149339] window on secondary external monitor cannot maximize
https://bugs.documentfoundation.org/show_bug.cgi?id=149339 --- Comment #4 from QA Administrators --- Dear thekswenson, 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 47256] MAILMERGE: Field "Statistics - Pages" becomes static number in resulting merged document
https://bugs.documentfoundation.org/show_bug.cgi?id=47256 --- Comment #13 from QA Administrators --- Dear FDF, 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 147114] Slovak keyboard shortcut conflict right_Alt+3
https://bugs.documentfoundation.org/show_bug.cgi?id=147114 --- Comment #4 from QA Administrators --- Dear henten, 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 138501] Distance-Based Dash Patterns Drawn Incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=138501 --- Comment #7 from QA Administrators --- Dear Alfred Hellstern, 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 133245] Collabora Office Android 9 opens file read only from Samsung My Files, R/W OK from Collabora file browser.
https://bugs.documentfoundation.org/show_bug.cgi?id=133245 --- Comment #4 from QA Administrators --- Dear Glenn Talbott, 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 126712] FILEOPEN DOC: Anchor to character for image in header is located off page
https://bugs.documentfoundation.org/show_bug.cgi?id=126712 --- Comment #4 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 113789] ActiveX button's icon is not saved back to DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=113789 --- Comment #19 from QA Administrators --- Dear Tamás Zolnai, 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 114832] Filesave: "File name without Extension" and "Path" Fields saved as DOCX open as "File name" in Writer while correctly shown in Word
https://bugs.documentfoundation.org/show_bug.cgi?id=114832 --- Comment #7 from QA Administrators --- Dear Timur, 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 111622] FILEOPEN DOCX - Writer gets wrong color scheme, if color is set to 'Automatic'
https://bugs.documentfoundation.org/show_bug.cgi?id=111622 --- Comment #13 from QA Administrators --- Dear Mike, 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 107407] DOCX: Shadow, emboss and engrave text effects not imported correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=107407 --- Comment #8 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103207] FILEOPEN: Vertical lines missing from margins (added with table/fame in the header), at wrong position in DOCX (Pleading document)
https://bugs.documentfoundation.org/show_bug.cgi?id=103207 --- Comment #6 from QA Administrators --- Dear Robinson Tryon (qubit), 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. You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 103206] FILEOPEN: Vertical numbers (added with a table/frame in the header) missing from left margin in DOCX (Pleading document)
https://bugs.documentfoundation.org/show_bug.cgi?id=103206 --- Comment #10 from QA Administrators --- Dear Robinson Tryon (qubit), 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. You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 102913] FILEOPEN DOCX Pleading line on right margin not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=102913 --- Comment #6 from QA Administrators --- Dear Buovjaga, 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 100972] Wrong rendering of distance of hatch
https://bugs.documentfoundation.org/show_bug.cgi?id=100972 --- 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 145563] LibreOffice and NeoOffice fail to respect each other's selections of Pfeffer Mediaeval due to a ligature in the name
https://bugs.documentfoundation.org/show_bug.cgi?id=145563 خالد حسني changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from خالد حسني --- Please attach document created with LibreOffice and win NeoOffice. I don’t have NeoOffice, but when I select the font in LibreOffice, I get the font name “Pfeffer Mediæval” which matches what Font Book shows. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102914] Synthetic italic in fonts with partial coverage exported as regular in PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=102914 خالد حسني changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |kha...@aliftype.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 65509] FILESAVE "Automatically save" (Found in Options > LO > Advanced > Expert Configuration ) not running (summary comment 33)
https://bugs.documentfoundation.org/show_bug.cgi?id=65509 Justin L changed: What|Removed |Added Summary|FILESAVE "Automatically |FILESAVE "Automatically |save" (Found in Options > |save" (Found in Options > |LO > Advanced > Expert |LO > Advanced > Expert |Configuration ) not running |Configuration ) not running ||(summary comment 33) --- Comment #41 from Justin L --- Explaining the meaning of attachment 119311 ExpertConfig search for AutoSave AutoSave: corresponds to Options - Load/Save - Save Autorecovery information AutoSaveTimeInterval: every x minutes AutoSavePrompt - ??? UserAutoSaveEnabled: corresponds to Options - Load/Save - Automatically save the document too. (visible False - see commit 10 patch). In the current implementation, "user auto save" is completely dependent on "recovery auto save". Separating the two would not be easy. (Things like impress slide-show temporarily disable autosave/autorecovery, and things like --headless need to prevent both altogether. > (1) After enabling the option “Automatically save the document too” > LibreOffice has to be closed and restarted again A dialog warns about this now, so not a big deal. > (2) New documents that have not been saved by the user at least once, > are not saved automatically Not surprising. What name would you give it? Where would you save it? I guess that is where it would need to pop up a save-as dialog. But this entire thing seems SUPER FRAGILE. In debugging this, I frequently had to delete the user profile in order to have the autorecovery subsystem start up at all. After two or three option modifications, it would be messed up somehow. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 Bug 71732 depends on bug 105699, which changed state. Bug 105699 Summary: Arial and Times New Roman italics not falling back correctly, when used with Arabic text https://bugs.documentfoundation.org/show_bug.cgi?id=105699 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105699] Arial and Times New Roman italics not falling back correctly, when used with Arabic text
https://bugs.documentfoundation.org/show_bug.cgi?id=105699 خالد حسني changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #9 from خالد حسني --- *** This bug has been marked as a duplicate of bug 102914 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102914] Synthetic italic in fonts with partial coverage exported as regular in PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=102914 --- Comment #17 from خالد حسني --- *** Bug 105699 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152239] Font hinting does not work as expected inside document view
https://bugs.documentfoundation.org/show_bug.cgi?id=152239 --- Comment #5 from Radu Rendec --- I agree, you definitely do not want the document to re-flow due to changes in hinting mode. However, hinting should only affect kerning, not glyph advances. In other words, it should not cause the document to re-flow. As always with full hinting, I am willing to sacrifice kerning for glyph aspect. I totally understand you cannot have both. In the meantime, I tried to start LibreOffice with the SAL_USE_VCLPLUGIN environment variable set to "gen", as suggested here: https://wiki.documentfoundation.org/QA/FirstSteps#Rendering_issues_specific_to_Linux. The UI is messed up (which is expected), but font hinting inside the document view works as expected. I'm not sure if it's relevant, but my desktop environment is MATE. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152238] FILESAVE: The structure of the book is broken when saving to LO in the .xlsm format in the case when the book (sheet) module has macros.
https://bugs.documentfoundation.org/show_bug.cgi?id=152238 --- Comment #4 from Justin L --- I'm not sure why this would be marked as a duplicate. There is nothing in this report about making StarBASIC macros and then exporting to MS Formats. This is just a round-tripping without modifications error report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152239] Font hinting does not work as expected inside document view
https://bugs.documentfoundation.org/show_bug.cgi?id=152239 خالد حسني changed: What|Removed |Added CC||caol...@redhat.com --- Comment #4 from خالد حسني --- I believe this is intentional because strong hinting modes change glyph advances and we use unhinted glyph advances in text layout so that document does not re-flow due changes in hinting mode, so both are incompatible. CC’ing Caolán McNamara for a definitive answer. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152243] character width depends on font coloring
https://bugs.documentfoundation.org/show_bug.cgi?id=152243 خالد حسني changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from خالد حسني --- I can reproduce with 7.4, but not with master, so I believe this is fixed in some of the recent changes related to text positioning. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139938] by exporting an *.ods file with makros to an *.xlsm file no VBAProject created
https://bugs.documentfoundation.org/show_bug.cgi?id=139938 m.a.riosv changed: What|Removed |Added CC||so...@comec92.ru --- Comment #14 from m.a.riosv --- *** Bug 152238 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152238] FILESAVE: The structure of the book is broken when saving to LO in the .xlsm format in the case when the book (sheet) module has macros.
https://bugs.documentfoundation.org/show_bug.cgi?id=152238 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |DUPLICATE --- Comment #3 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 139938 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152223] 7.4.3.2 Calc has a problem, some keys need [Alt] in quit dialog box.
https://bugs.documentfoundation.org/show_bug.cgi?id=152223 m.a.riosv changed: What|Removed |Added Summary|7.4.3.2 Calc has a problem |7.4.3.2 Calc has a problem, ||some keys need [Alt] in ||quit dialog box. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152223] 7.4.3.2 Calc has a problem
https://bugs.documentfoundation.org/show_bug.cgi?id=152223 m.a.riosv changed: What|Removed |Added Status|NEEDINFO|NEW Keywords||regression CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Working with Version: 7.3.7.2 (x64) / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL Fails with Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en- Calc: CL and Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1435c5b12646269e2b5b58ec7d51626dce6505db CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 Bug 103378 depends on bug 152210, which changed state. Bug 152210 Summary: Export to PDF not working for hyperlinks https://bugs.documentfoundation.org/show_bug.cgi?id=152210 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146575] Writer won't export hyperlinks to pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=146575 m.a.riosv changed: What|Removed |Added CC||jaroslav.kratochvil@antholo ||gy.com --- Comment #11 from m.a.riosv --- *** Bug 152210 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152210] Export to PDF not working for hyperlinks
https://bugs.documentfoundation.org/show_bug.cgi?id=152210 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 146575 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152208] PDF: Inserting images in pdf 1.5 format in LibreOffice Impress leads to broken files if the document is exported as pdf.
https://bugs.documentfoundation.org/show_bug.cgi?id=152208 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #3 from m.a.riosv --- Can you attach the Impress file, that produces the bad PDF. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147906] Use std::hypot for Pythagorean addition
https://bugs.documentfoundation.org/show_bug.cgi?id=147906 --- Comment #14 from Commit Notification --- Bogdan B committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/5b18eebc2c95321ce7e6edf10f4df81557382a48 tdf#147906 used std::hypot for Pythagorean addition It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svx/source
svx/source/engine3d/view3d.cxx |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
New commits:
commit 5b18eebc2c95321ce7e6edf10f4df81557382a48
Author: Bogdan B
AuthorDate: Thu Nov 24 21:06:35 2022 +0100
Commit: Hossein
CommitDate: Sat Nov 26 23:39:26 2022 +0100
tdf#147906 used std::hypot for Pythagorean addition
Change-Id: I28f3996b777c99b771f1cbcde236b5a1a1c0f18f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143168
Tested-by: Jenkins
Reviewed-by: Hossein
diff --git a/svx/source/engine3d/view3d.cxx b/svx/source/engine3d/view3d.cxx
index 18df6d5a6a98..ece5281baf63 100644
--- a/svx/source/engine3d/view3d.cxx
+++ b/svx/source/engine3d/view3d.cxx
@@ -843,9 +843,7 @@ void E3dView::ConvertMarkedObjTo3D(bool bExtrude, const
basegfx::B2DPoint& rPnt1
if(bExtrude)
{
-double fW = static_cast(aRect.GetWidth());
-double fH = static_cast(aRect.GetHeight());
-fDepth = sqrt(fW*fW + fH*fH) / 6.0;
+fDepth = std::hypot(aRect.GetWidth(), aRect.GetHeight()) / 6.0;
}
if(!bExtrude)
{
[Libreoffice-bugs] [Bug 103427] [META] Styles and Formatting sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103427 Bug 103427 depends on bug 152201, which changed state. Bug 152201 Summary: Cell styles' previews are not shown in Calc's sidebar's Styles deck https://bugs.documentfoundation.org/show_bug.cgi?id=152201 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151142] UI: Font Preview in the Styles sidebar is not working for Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=151142 m.a.riosv changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from m.a.riosv --- *** Bug 152201 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152201] Cell styles' previews are not shown in Calc's sidebar's Styles deck
https://bugs.documentfoundation.org/show_bug.cgi?id=152201 m.a.riosv changed: What|Removed |Added Status|NEW |RESOLVED CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |DUPLICATE --- Comment #4 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 151142 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143015] Calc Issue with the [Text Language] section of the status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=143015 --- Comment #6 from Tammy --- I was able to reproduce the issue on: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 3b0b9fcb80242abcedc01eb388a57b1016916353 CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded The causal ticket may relate to bug 127856. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107742] [META] Form control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742 Hossein changed: What|Removed |Added Depends on||152246 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152246 [Bug 152246] Wrong horizontal position for the RTL content control fields in the exported PDF file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152246] Wrong horizontal position for the RTL content control fields in the exported PDF file
https://bugs.documentfoundation.org/show_bug.cgi?id=152246 Hossein changed: What|Removed |Added CC||vmik...@collabora.com Blocks||107742 --- Comment #1 from Hossein --- @Miklos: I would like to fix this issue. Could you please give me some advise/code pointers? I see boundary calculations inside SwContentControlPortion::DescribePDFControl in sw/source/core/text/itrform2.cxx. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107742 [Bug 107742] [META] Form control bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46444] Calc doesn't filter any comments
https://bugs.documentfoundation.org/show_bug.cgi?id=46444 --- Comment #10 from Commit Notification --- Balazs Varga committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/c9807faad6a154b57a99adfdf9b02bd9e588250f Related: tdf#46444 tdf#152081 sc: add unit test for note hiding It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/qa sc/source
sc/qa/unit/data/ods/tdf152081_UndoHideColsWithNotes.ods |binary
sc/qa/unit/scshapetest.cxx | 31
sc/source/core/data/drwlayer.cxx|2 -
3 files changed, 32 insertions(+), 1 deletion(-)
New commits:
commit c9807faad6a154b57a99adfdf9b02bd9e588250f
Author: Balazs Varga
AuthorDate: Fri Nov 25 14:03:45 2022 +0100
Commit: Balazs Varga
CommitDate: Sat Nov 26 22:41:04 2022 +0100
Related: tdf#46444 tdf#152081 sc: add unit test for note hiding
Add unit test for column hiding with notes and undo that.
Change-Id: I880ca1565dbefea5e8776b0d137da409ce816ac1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143299
Tested-by: Jenkins
Reviewed-by: Balazs Varga
diff --git a/sc/qa/unit/data/ods/tdf152081_UndoHideColsWithNotes.ods
b/sc/qa/unit/data/ods/tdf152081_UndoHideColsWithNotes.ods
new file mode 100644
index ..6d2b480db7b6
Binary files /dev/null and
b/sc/qa/unit/data/ods/tdf152081_UndoHideColsWithNotes.ods differ
diff --git a/sc/qa/unit/scshapetest.cxx b/sc/qa/unit/scshapetest.cxx
index af3d7308ee0e..58a9623ec4ec 100644
--- a/sc/qa/unit/scshapetest.cxx
+++ b/sc/qa/unit/scshapetest.cxx
@@ -61,6 +61,7 @@ public:
void testLoadVerticalFlip();
void testTdf117948_CollapseBeforeShape();
void testTdf137355_UndoHideRows();
+void testTdf152081_UndoHideColsWithNotes();
void testTdf115655_HideDetail();
void testFitToCellSize();
void testCustomShapeCellAnchoredRotatedShape();
@@ -88,6 +89,7 @@ public:
CPPUNIT_TEST(testLoadVerticalFlip);
CPPUNIT_TEST(testTdf117948_CollapseBeforeShape);
CPPUNIT_TEST(testTdf137355_UndoHideRows);
+CPPUNIT_TEST(testTdf152081_UndoHideColsWithNotes);
CPPUNIT_TEST(testTdf115655_HideDetail);
CPPUNIT_TEST(testFitToCellSize);
CPPUNIT_TEST(testCustomShapeCellAnchoredRotatedShape);
@@ -945,6 +947,35 @@ void ScShapeTest::testTdf137355_UndoHideRows()
aSnapRectUndo, 1);
}
+void ScShapeTest::testTdf152081_UndoHideColsWithNotes()
+{
+createScDoc("tdf152081_UndoHideColsWithNotes.ods");
+
+// Get document and shape
+ScDocument* pDoc = getScDoc();
+SdrObject* pObj = lcl_getSdrObjectWithAssert(*pDoc, 0);
+
+CPPUNIT_ASSERT_MESSAGE("Load: Note object should be visible",
pObj->IsVisible());
+
+// Hide B column
+uno::Sequence aPropertyValues = {
+comphelper::makePropertyValue("ToPoint", OUString("$B$2:$B$2")),
+};
+dispatchCommand(mxComponent, ".uno:GoToCell", aPropertyValues);
+ScTabViewShell* pViewShell = getViewShell();
+pViewShell->GetViewData().GetDispatcher().Execute(FID_COL_HIDE);
+
+// Check object is invisible
+CPPUNIT_ASSERT_MESSAGE("Hide: Note object should be invisible",
!pObj->IsVisible());
+
+// Undo
+pViewShell->GetViewData().GetDispatcher().Execute(SID_UNDO);
+
+// Check object is visible
+CPPUNIT_ASSERT_MESSAGE("Undo: Note object should exist", pObj);
+CPPUNIT_ASSERT_MESSAGE("Undo: Note object should be visible",
pObj->IsVisible());
+}
+
void ScShapeTest::testTdf115655_HideDetail()
{
// The document contains an image inside a cell anchored "To Cell (resize
with cell)". The cell
diff --git a/sc/source/core/data/drwlayer.cxx b/sc/source/core/data/drwlayer.cxx
index 9474d5859407..ec4fee275ed1 100644
--- a/sc/source/core/data/drwlayer.cxx
+++ b/sc/source/core/data/drwlayer.cxx
@@ -1035,7 +1035,7 @@ void ScDrawLayer::RecalcPos( SdrObject* pObj,
ScDrawObjData& rData, bool bNegati
additional boolean stating if the cells are already moved. */
/* tdf #152081 Do not change hidden objects. That would produce zero
height
or width and loss of caption.*/
-if (pObj->IsVisible() && bUpdateNoteCaptionPos)
+if (bUpdateNoteCaptionPos && pObj->IsVisible())
{
/* When inside an undo action, there may be pending note captions
where cell note is already deleted (thus document cannot find
[Libreoffice-bugs] [Bug 152246] Wrong horizontal position for the RTL content control fields in the exported PDF file
https://bugs.documentfoundation.org/show_bug.cgi?id=152246 Hossein changed: What|Removed |Added Summary|Wrong horizontal position |Wrong horizontal position |for the RTL content control |for the RTL content control |fields |fields in the exported PDF ||file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149192] UI: Tab menu missing on one screen
https://bugs.documentfoundation.org/show_bug.cgi?id=149192 Fabrice changed: What|Removed |Added Attachment #183824|0 |1 is obsolete|| --- Comment #3 from Fabrice --- Created attachment 183825 --> https://bugs.documentfoundation.org/attachment.cgi?id=183825=edit Tab menu on working screen I had the wrong attachement in the previous comment. This is the menu open / working. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149192] UI: Tab menu missing on one screen
https://bugs.documentfoundation.org/show_bug.cgi?id=149192 --- Comment #2 from Fabrice --- Created attachment 183824 --> https://bugs.documentfoundation.org/attachment.cgi?id=183824=edit Tab menu on working screen Hi, I mean the tabs at the bottom of the spreadsheet: "Sheet1", "Sheet2"... Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152246] New: Wrong horizontal position for the RTL content control fields
https://bugs.documentfoundation.org/show_bug.cgi?id=152246 Bug ID: 152246 Summary: Wrong horizontal position for the RTL content control fields Product: LibreOffice Version: 7.4.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 183823 --> https://bugs.documentfoundation.org/attachment.cgi?id=183823=edit PDF output from LO 7.5 dev master Description: When exporting/printing a file containing content control fields, horizontal position for RTL fields is wrong, and overlaps text. Steps to Reproduce: 1. Open attachment 182846. 2. Open "File" > "Export as" > "Export as PDF" menu option 3. In "General" tab, column 2, check "Create PDF form", and set "Submit Format" to "FDF". 4. Click "Export" to export the document to PDF. 5. Open the exported file either in "Adobe Acrobat" or "Mozilla Firefox" to see the exported fields. Or, simply open the PDF attachment in Acrobat or Firefox. Actual Results: The RTL fields from page 1 are incorrectly place horizontally and overlap other parts of text. On the other hand, LTR fields from the last page are placed correctly. Expected Results: The fields in PDF file should be placed in the position that were in the source file. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 6bf5dd8faea420aa0dbc7c429952c9868bcadb9e CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
How to remove frame in SdrCustomShape during import from docx?
Hi all, Problem is: The fact, that the shape should be a text warp (WordArt, Fontwork) is detected in WpsContext in case prstTxWarp exists. At that time a frame already exists in the shape. But with a frame it is impossible to put the custom shape into text path mode. How can I remove the frame when in WpsContext? Kind regards Regina
[Libreoffice-bugs] [Bug 143002] [META] Tracked Changes of tables
https://bugs.documentfoundation.org/show_bug.cgi?id=143002 raal changed: What|Removed |Added Depends on||148369 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148369 [Bug 148369] Redo of deleting a row track and changes enabled deletes the wrong cell content -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148369] Redo of deleting a row track and changes enabled deletes the wrong cell content
https://bugs.documentfoundation.org/show_bug.cgi?id=148369 raal changed: What|Removed |Added Blocks||143002 Keywords||regression Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||r...@post.cz --- Comment #3 from raal --- Tested with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ebe151d919a454f98c36013245bca9eb41d92707 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded after Redo the "e" doesn't remains, but row is not deleted ->bug. Works in Version: 5.2.0.0.alpha1+ Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143002 [Bug 143002] [META] Tracked Changes of tables -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152116] Navigator dialog: State of outline headings is lost when navigator is closed then reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=152116 Jim Raykowski changed: What|Removed |Added CC||rayk...@gmail.com --- Comment #10 from Jim Raykowski --- Here is effort that provides for same session restore of the Navigator headings outline expand state when the Navigator is closed and then reopened: https://gerrit.libreoffice.org/c/core/+/143326 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/gdi/metaact.cxx | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
New commits:
commit 21b88575af9e5a6b124d8d9cb4e0a95e9fea
Author: Caolán McNamara
AuthorDate: Sat Nov 26 19:27:03 2022 +
Commit: Caolán McNamara
CommitDate: Sat Nov 26 21:36:52 2022 +0100
ofz#53764 Integer-overflow
Change-Id: I0d0ec07801fd612fde3028d4aad2f154c27bc551
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143327
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/vcl/source/gdi/metaact.cxx b/vcl/source/gdi/metaact.cxx
index ef32bc0f3fb3..0c426d1f930d 100644
--- a/vcl/source/gdi/metaact.cxx
+++ b/vcl/source/gdi/metaact.cxx
@@ -736,8 +736,25 @@ MetaTextRectAction::MetaTextRectAction( const
tools::Rectangle& rRect,
mnStyle ( nStyle )
{}
+static bool AllowRect(const tools::Rectangle& rRect)
+{
+static bool bFuzzing = utl::ConfigManager::IsFuzzing();
+if (bFuzzing)
+{
+if (rRect.Top() > 0x2000 || rRect.Top() < -0x2000)
+{
+SAL_WARN("vcl", "skipping huge rect top: " << rRect.Top());
+return false;
+}
+}
+return true;
+}
+
void MetaTextRectAction::Execute( OutputDevice* pOut )
{
+if (!AllowRect(maRect))
+return;
+
pOut->DrawText( maRect, maStr, mnStyle );
}
@@ -850,7 +867,8 @@ MetaBmpScaleAction::MetaBmpScaleAction( const Point& rPt,
const Size& rSz,
static bool AllowScale(const Size& rSource, const Size& rDest)
{
-if (utl::ConfigManager::IsFuzzing())
+static bool bFuzzing = utl::ConfigManager::IsFuzzing();
+if (bFuzzing)
{
constexpr int nMaxScaleWhenFuzzing = 512;
[Libreoffice-bugs] [Bug 149192] UI: Tab menu missing on one screen
https://bugs.documentfoundation.org/show_bug.cgi?id=149192 raal changed: What|Removed |Added CC||r...@post.cz Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71843] Missing "Surround header" and "Surround footer" Page Border options in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=71843 Christopher POTTER changed: What|Removed |Added CC||cpot...@ceo-vision.com --- Comment #19 from Christopher POTTER --- Still present in : Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145978] Macro Selector should remember last run module/macro
https://bugs.documentfoundation.org/show_bug.cgi?id=145978 --- Comment #8 from Commit Notification --- Rafael Lima committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/bc5856c5c77a7ee18377cd274960950d8943178f Related tdf#145978 Fix workaround in kf5 It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: cui/source
cui/source/customize/cfgutil.cxx |5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) New commits: commit bc5856c5c77a7ee18377cd274960950d8943178f Author: Rafael Lima AuthorDate: Fri Nov 25 20:13:51 2022 +0100 Commit: Jim Raykowski CommitDate: Sat Nov 26 20:51:30 2022 +0100 Related tdf#145978 Fix workaround in kf5 In commit 792e41314f321f54b3b2fc4d01c8b62a3b704e9e (about saving the last used macro) I used a workaround to make scroll_to_row work in kf5. However, this workaround based on hide() / show() calls was causing an error: qt.qpa.xcb: internal error: void QXcbWindow::setNetWmStateOnUnmappedWindow() called on mapped window. As pointed out by Jim in the original patch, using resize_to_request has the same effect and does not cause the aforementioned error. Change-Id: Ie61e8529fccfdae88d56f223573eb0fd6a82b8b0 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143261 Tested-by: Jenkins Reviewed-by: Jim Raykowski diff --git a/cui/source/customize/cfgutil.cxx b/cui/source/customize/cfgutil.cxx index 2b7a4ef0c226..621238da0cb8 100644 --- a/cui/source/customize/cfgutil.cxx +++ b/cui/source/customize/cfgutil.cxx @@ -1162,9 +1162,8 @@ SvxScriptSelectorDialog::SvxScriptSelectorDialog( m_aStylesInfo.init(aModuleName, xModel); m_xCategories->SetStylesInfo(_aStylesInfo); -// The hide/show commands below are a workaround to make scroll_to_row work as expected in kf5/x11 -m_xDialog->hide(); -m_xDialog->show(); +// The following call is a workaround to make scroll_to_row work as expected in kf5/x11 +m_xDialog->resize_to_request(); LoadLastUsedMacro(); UpdateUI();
[Libreoffice-commits] core.git: oox/source
oox/source/export/drawingml.cxx | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
New commits:
commit 9bef99518e910db078149bef08e300afc8b4aaf2
Author: Caolán McNamara
AuthorDate: Sat Nov 26 16:43:57 2022 +
Commit: Caolán McNamara
CommitDate: Sat Nov 26 20:12:43 2022 +0100
crashtesting: failure to export various docs to xlsx/docx
e.g. ooo74880-2.ods since:
commit 3f70375cf160841b6140f5f1b2b79af3652897f8
Date: Fri Nov 18 12:06:59 2022 +0100
tdf#152069 tdf#108356 PPTX export: fix missing tile properties
bodge a workaround to not crash at least
Change-Id: I23e0fc4e0f7a2c6d0b182945e252470f2338da09
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143325
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/oox/source/export/drawingml.cxx b/oox/source/export/drawingml.cxx
index bf9f246ed751..1da6391412fc 100644
--- a/oox/source/export/drawingml.cxx
+++ b/oox/source/export/drawingml.cxx
@@ -1928,12 +1928,15 @@ void
DrawingML::WriteXGraphicTile(uno::Reference const& rXP
Reference xDrawPages(xDPS->getDrawPages(),
UNO_SET_THROW);
// in this case, the size of the first slide is enough, because all
slides are the same size
Reference xDrawPage(xDrawPages->getByIndex(0), UNO_QUERY);
-css::uno::Reference mXPagePropSet(xDrawPage,
UNO_QUERY);
-double nPageWidth, nPageHeight;
-mXPagePropSet->getPropertyValue("Width") >>= nPageWidth;
-mXPagePropSet->getPropertyValue("Height") >>= nPageHeight;
-nSizeX = nPageWidth / aOriginalSize.Width() * std::abs(nSizeX);
-nSizeY = nPageHeight / aOriginalSize.Height() * std::abs(nSizeY);
+css::uno::Reference xPagePropSet(xDrawPage,
UNO_QUERY);
+if (xPagePropSet)
+{
+double nPageWidth, nPageHeight;
+xPagePropSet->getPropertyValue("Width") >>= nPageWidth;
+xPagePropSet->getPropertyValue("Height") >>= nPageHeight;
+nSizeX = nPageWidth / aOriginalSize.Width() * std::abs(nSizeX);
+nSizeY = nPageHeight / aOriginalSize.Height() * std::abs(nSizeY);
+}
}
OUString sRectanglePoint;
[Libreoffice-bugs] [Bug 130937] Mouse-hold preview differs from result when changing a connector via dragging
https://bugs.documentfoundation.org/show_bug.cgi?id=130937 --- Comment #4 from Pasi --- Bug is still present in version 7.4.2.3. No change to this behavior has happened to this within past almost two years. Additionally, if the drawing has many connectors then selecting connector takes a long long time - unless the drawing is zoomed so that something is outside of view. Are these related - I don't know. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152245] New: Crash when i copy-parted from LO-Calc to a docx with change control
https://bugs.documentfoundation.org/show_bug.cgi?id=152245 Bug ID: 152245 Summary: Crash when i copy-parted from LO-Calc to a docx with change control Product: LibreOffice Version: 7.4.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ignaciohr...@gmail.com Description: I'm working in a .docx file that has several graph and tables that i had to modify. For the second time, when i copy-paste a table from LibreOffice Calc to this document, all the LibreOffice suit froze. I tried to wait a few minutes, but still, the only way was to force the exit. Steps to Reproduce: 1. create a file in MS Word with tables 2. open the file in LO Writer 3. try to modify the tables by pasting content from LO Calc (same number of rows and columns) with "change control" enabled Actual Results: all the LibreOffice suite freeze and the only option is to force exit Expected Results: to paste the new values in each cell, marking them as changes to be accepted Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.4.3.2 Build ID: 40(Build:2) CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: es-AR (es_AR.UTF-8); UI: es-ES Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152240] tabStops should not change with the BeforeText
https://bugs.documentfoundation.org/show_bug.cgi?id=152240 --- Comment #1 from tor...@yahoo.com --- Created attachment 183822 --> https://bugs.documentfoundation.org/attachment.cgi?id=183822=edit file with tabStops -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 Stéphane Guillou (stragu) changed: What|Removed |Added Status|RESOLVED|VERIFIED Keywords|needsUXEval | -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 Stéphane Guillou (stragu) changed: What|Removed |Added Status|RESOLVED|VERIFIED Keywords|needsUXEval | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112125] [META] Hyperlink dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112125 Bug 112125 depends on bug 152115, which changed state. Bug 152115 Summary: Hyperlink Target in document: The last user setting is not remembered https://bugs.documentfoundation.org/show_bug.cgi?id=152115 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 Stéphane Guillou (stragu) changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #13 from Stéphane Guillou (stragu) --- Thanks Jim! Verified as fixed in: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 6bf5dd8faea420aa0dbc7c429952c9868bcadb9e CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 Stéphane Guillou (stragu) changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #13 from Stéphane Guillou (stragu) --- Thanks Jim! Verified as fixed in: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 6bf5dd8faea420aa0dbc7c429952c9868bcadb9e CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152244] New: default arrowhead size is inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=152244 Bug ID: 152244 Summary: default arrowhead size is inconsistent Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aaalmo...@gmail.com Description: Creating an arrow and adding an arrow ending to a line result in arrowheads of different sizes. At first it looks like the default arrow is impossible to reproduce manually, because none of the endings in the drop-down list matches the default one, and it's not trivial that the arrowhead can be resized. Here are the default arrowhead sizes: Writer: new arrow 0.18cm, add arrowhead 0.35cm Impress: new arrow 0.30cm, add arrowhead 0.20cm Steps to Reproduce: 1. create an arrow 2. add an arrow ending to the other end 3. Actual Results: they have different size Expected Results: they have the same size Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: x11 Locale: en-GB (en_GB.UTF-8); UI: en-GB Debian package version: 1:7.4.1-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134511] Fontwork favorite 18 (Asphalt) has two values in draw:modifiers, should be only one
https://bugs.documentfoundation.org/show_bug.cgi?id=134511 Regina Henschel changed: What|Removed |Added Priority|medium |low Severity|normal |minor --- Comment #3 from Regina Henschel --- The shape of the Fontwork Gallery has still the wrong additional adjustment value. But the export to pptx has been changed in the meantime. Now only one guide is exported and PowerPoint can render the shape. Therefore I decrease Importance. Tested in Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 17dfc9a9da009cc23de3fb4e2cef9c97d581 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152243] character width depends on font coloring
https://bugs.documentfoundation.org/show_bug.cgi?id=152243 --- Comment #1 from almos --- Created attachment 183820 --> https://bugs.documentfoundation.org/attachment.cgi?id=183820=edit hexdump.odp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152243] New: character width depends on font coloring
https://bugs.documentfoundation.org/show_bug.cgi?id=152243 Bug ID: 152243 Summary: character width depends on font coloring Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aaalmo...@gmail.com Description: Font coloring affects the width of the characters, depending on the zoom level. This is very noticeable when using fixed-width font. Cannot reproduce in Writer. Steps to Reproduce: 1. open the attached presentation 2. play with the zoom slider 3. Actual Results: the | characters don't align in lines with colored parts Expected Results: fixed character width Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: x11 Locale: en-GB (en_GB.UTF-8); UI: en-GB Debian package version: 1:7.4.1-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152242] New: textbox animation is always line-by-line
https://bugs.documentfoundation.org/show_bug.cgi?id=152242 Bug ID: 152242 Summary: textbox animation is always line-by-line Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aaalmo...@gmail.com Description: If I have a textbox and I add an animation to it I expect the whole box to appear at once. On the main slide text area when multiple lines are selected for animation, the first line gets to appear on click, and the subsequent lines appear with the previous. The textbox is a single item in the animation list, yet it appears line-by-line. Steps to Reproduce: 1. Add textbox with multiple lines of text 2. Add animation to the box 3. Text appears line-by-line, not at once even though it's a single item on the animation list Actual Results: Line-by-line reveal Expected Results: Reveal all at once Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: x11 Locale: en-GB (en_GB.UTF-8); UI: en-GB Debian package version: 1:7.4.1-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/ui/vba/vbacontentcontrollistentry.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 7d86a6db7a64219e599abfbd28464e3f93022929
Author: Andrea Gelmini
AuthorDate: Sat Nov 26 11:08:02 2022 +0100
Commit: Julien Nabet
CommitDate: Sat Nov 26 17:58:55 2022 +0100
Fix typo
Change-Id: Ief6a37b977f464c50888291ec9764c7b05cba297
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143320
Tested-by: Julien Nabet
Reviewed-by: Julien Nabet
diff --git a/sw/source/ui/vba/vbacontentcontrollistentry.cxx
b/sw/source/ui/vba/vbacontentcontrollistentry.cxx
index 7be9c758f19d..44bfd161bcdf 100644
--- a/sw/source/ui/vba/vbacontentcontrollistentry.cxx
+++ b/sw/source/ui/vba/vbacontentcontrollistentry.cxx
@@ -94,7 +94,7 @@ void SwVbaContentControlListEntry::Delete()
void SwVbaContentControlListEntry::MoveDown()
{
std::shared_ptr pCC =
m_rCC.GetContentControl().GetContentControl();
-// if already at last positin, can't move down
+// if already at last position, can't move down
if (m_nZIndex >= pCC->GetListItems().size() - 1)
return;
[Libreoffice-bugs] [Bug 152110] LanguageTool ext. prevents adding words to dictionaries with 2+ dictionaries present
https://bugs.documentfoundation.org/show_bug.cgi?id=152110 --- Comment #5 from Marcin Segit --- Ah, sorry. 151508 can be closed as a flawed duplicate of sorts. Back then I didn't realize that the issue is connected to having multiple dictionaries (and there is no way to edit the initial entry). Please close 151508 and keep 152110. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa
sw/qa/extras/ooxmlexport/ooxmlexport18.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 9ac9a510d8162cff3fded1d3d8312d21a677618a Author: Andrea Gelmini AuthorDate: Sat Nov 26 11:07:18 2022 +0100 Commit: Julien Nabet CommitDate: Sat Nov 26 17:56:25 2022 +0100 Fix typo Change-Id: I63136468d4c5b5680cf3d7b240943b6029c4f29b Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143319 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx index 8e2732faead8..79ea4323274d 100644 --- a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx +++ b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx @@ -205,7 +205,7 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf152200) // - Expected greater than: 6 // - Actual : 5 CPPUNIT_ASSERT_GREATER(nRunsBeforeFldCharEnd, nRunsBeforeAlternateContent); -// Make sure we only have one paragraph in body, and only three field characters overal, +// Make sure we only have one paragraph in body, and only three field characters overall, // located directly in runs of this paragraph assertXPath(pXmlDoc, "/w:document/w:body/w:p"); assertXPath(pXmlDoc, "/w:document/w:body/w:p/w:r/w:fldChar", 3);
