[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - 2 commits - comphelper/source include/comphelper include/vcl svx/source vcl/source
comphelper/source/streaming/seqstream.cxx| 52 ++-
include/comphelper/seqstream.hxx | 29 ---
include/vcl/BinaryDataContainer.hxx |4 ++
svx/source/sdr/contact/viewobjectcontact.cxx | 10 +++--
vcl/source/gdi/vectorgraphicdata.cxx |6 +--
vcl/source/graphic/BinaryDataContainer.cxx | 20 ++
6 files changed, 77 insertions(+), 44 deletions(-)
New commits:
commit acae249396c39a6fd98551078d391ca50fe3bc61
Author: Noel Grandin
AuthorDate: Wed May 31 13:53:43 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Jun 1 07:58:32 2023 +0200
speed up tab-switching in a calc document with a lot of graphic objects
if we are in the destructor, and we have never painted the object in
question, then we don't need to do an expensive object-range calculation
and invalidation
Change-Id: I857c3d927142f4e90d54f79fa6c293731382f0d9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152434
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Noel Grandin
diff --git a/svx/source/sdr/contact/viewobjectcontact.cxx
b/svx/source/sdr/contact/viewobjectcontact.cxx
index 2e2ecfe8f711..f0f5c1499ca2 100644
--- a/svx/source/sdr/contact/viewobjectcontact.cxx
+++ b/svx/source/sdr/contact/viewobjectcontact.cxx
@@ -166,10 +166,14 @@ ViewObjectContact::ViewObjectContact(ObjectContact&
rObjectContact, ViewContact&
ViewObjectContact::~ViewObjectContact()
{
-// invalidate in view
-if(!getObjectRange().isEmpty())
+// if the object range is empty, then we have never had the primitive
range change, so nothing to invalidate
+if (!maObjectRange.isEmpty())
{
-GetObjectContact().InvalidatePartOfView(maObjectRange);
+// invalidate in view
+if(!getObjectRange().isEmpty())
+{
+GetObjectContact().InvalidatePartOfView(maObjectRange);
+}
}
// delete PrimitiveAnimation
commit a4d24f9a2af7cf5d6cceeedfaaa744d4da62c7a8
Author: Noel Grandin
AuthorDate: Thu May 18 11:48:26 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Jun 1 07:58:21 2023 +0200
tdf#63130 reduce large memory copies when reading from BinaryDataContainer
rather than writing a bunch more code, extract the common part from
comphelper::SequenceInputStream into a new base class
Change-Id: I0d3561e3ca2e748b904128e3b5955e27196d7170
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151943
Tested-by: Jenkins
Reviewed-by: Noel Grandin
(cherry picked from commit 5a4d78d9a9b45c7fa387b66f5e310447ec813034)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151916
Tested-by: Jenkins CollaboraOffice
diff --git a/comphelper/source/streaming/seqstream.cxx
b/comphelper/source/streaming/seqstream.cxx
index 1f37a7967b04..49eebc1a99c2 100644
--- a/comphelper/source/streaming/seqstream.cxx
+++ b/comphelper/source/streaming/seqstream.cxx
@@ -36,26 +36,27 @@ using namespace ::osl;
-SequenceInputStream::SequenceInputStream(
-css::uno::Sequence const & rData)
-: m_aData(rData)
+MemoryInputStream::MemoryInputStream(
+const sal_Int8* pData, sal_Int32 nDataLength)
+: m_pMemoryData(pData)
+, m_nMemoryDataLength(nDataLength)
, m_nPos(0)
{
}
// checks if closed, returns available size, not mutex-protected
-inline sal_Int32 SequenceInputStream::avail()
+inline sal_Int32 MemoryInputStream::avail()
{
if (m_nPos == -1)
throw NotConnectedException(OUString(), *this);
-return m_aData.getLength() - m_nPos;
+return m_nMemoryDataLength - m_nPos;
}
// css::io::XInputStream
-sal_Int32 SAL_CALL SequenceInputStream::readBytes( Sequence& aData,
sal_Int32 nBytesToRead )
+sal_Int32 SAL_CALL MemoryInputStream::readBytes( Sequence& aData,
sal_Int32 nBytesToRead )
{
if (nBytesToRead < 0)
throw BufferSizeExceededException(OUString(),*this);
@@ -68,13 +69,13 @@ sal_Int32 SAL_CALL SequenceInputStream::readBytes(
Sequence& aData, sa
nBytesToRead = nAvail;
aData.realloc(nBytesToRead);
-memcpy(aData.getArray(), m_aData.getConstArray() + m_nPos, nBytesToRead);
+memcpy(aData.getArray(), m_pMemoryData + m_nPos, nBytesToRead);
m_nPos += nBytesToRead;
return nBytesToRead;
}
-sal_Int32 SequenceInputStream::readSomeBytes( sal_Int8* pData, sal_Int32
nBytesToRead )
+sal_Int32 MemoryInputStream::readSomeBytes( sal_Int8* pData, sal_Int32
nBytesToRead )
{
if (nBytesToRead < 0)
throw BufferSizeExceededException(OUString(),*this);
@@ -86,27 +87,20 @@ sal_Int32 SequenceInputStream::readSomeBytes( sal_Int8*
pData, sal_Int32 nBytesT
if (nAvail < nBytesToRead)
nBytesToRead = nAvail;
-memcpy(pData, m_aData.getConstArray() + m_nPos, nBytesToRead);
+memcpy(pData, m_pMemoryData + m_nPos, nBytesToRead);
m_nPos += nBytesToRead;
return nBytesToRead;
}
-sal_Int64 SAL_CALL SequenceInputStream::getSomething( const
Re: Enhancement proposal: Download free fonts
On 1.6.2023 1.02, o lu wrote: Would it be a valid enhancement to propose the following: LibreOffice should download free/libre fonts if they are not on the users' system. * Download and not install: o Install seems to be a system task, and is different among platforms * Libre and Free o Avoid licensing issues Feel free to direct me to another list or bugzilla. There is a proposal to offer font downloads on the libreoffice.org website: https://bugs.documentfoundation.org/show_bug.cgi?id=113496 Ilmari
Re: Enhancement proposal: Download free fonts
Hi! A side note first: Please note that using an explicit text color in your messages is a questionable thing. Unless you definitely know how people will read your messages. Light grey on white looks funny. On 01.06.2023 1:02, o lu wrote: Would it be a valid enhancement to propose the following: LibreOffice should download free/libre fonts if they are not on the users' system. * Download and not install: o Install seems to be a system task, and is different among platforms * Libre and Free o Avoid licensing issues Surely it would be the proper use of resources, if TDF hires people to (1) continuously monitor unlimited number of font foundries and their fonts; (2) checking legal issues with each of those fonts on any system, any country with its local legislation, and any use (commercial/personal), with possible change at any time by author; and (3) be legally responsible for possible mistakes, because it wasn't the user's decision, but it was LibreOffice that told user that "it's OK to install this font, and it's already downloaded"; including errors because of using older LibreOffice versions, that didn't know that author of the font changed its license in later versions. Or do I miss something? -- Best regards, Mike Kaganski
[Libreoffice-bugs] [Bug 150285] [META] Problems with Kashida, Justified Arabic/Persian text
https://bugs.documentfoundation.org/show_bug.cgi?id=150285 Bug 150285 depends on bug 17, which changed state. Bug 17 Summary: Wrong rendering of underline for justified mixed RTL/LTR script text https://bugs.documentfoundation.org/show_bug.cgi?id=17 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155557] Wrong rendering of underline for justified mixed RTL/LTR script text
https://bugs.documentfoundation.org/show_bug.cgi?id=17 خالد حسني changed: What|Removed |Added Status|NEW |RESOLVED Assignee|libreoffice-b...@lists.free |kha...@libreoffice.org |desktop.org | Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155557] Wrong rendering of underline for justified mixed RTL/LTR script text
https://bugs.documentfoundation.org/show_bug.cgi?id=17 --- Comment #2 from Commit Notification --- Khaled Hosny committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/99d22fd79c5532fd6c1b167996e1c27216b92469 tdf#17: Fix drawing mixed direction underlined text It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155557] Wrong rendering of underline for justified mixed RTL/LTR script text
https://bugs.documentfoundation.org/show_bug.cgi?id=17 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source vcl/qa
sw/qa/extras/layout/layout2.cxx|2 -
sw/source/core/txtnode/swfont.cxx | 61 -
vcl/qa/cppunit/pdfexport/pdfexport.cxx |7 ---
3 files changed, 1 insertion(+), 69 deletions(-)
New commits:
commit 99d22fd79c5532fd6c1b167996e1c27216b92469
Author: Khaled Hosny
AuthorDate: Wed May 31 17:37:27 2023 +0300
Commit: خالد حسني
CommitDate: Thu Jun 1 07:09:45 2023 +0200
tdf#17: Fix drawing mixed direction underlined text
The code here first unsets the underline style, draws the text, then
measures the text size, change the text to two blank spaces, sets the
measured width back and tries to guess how much space was added by
justification, sets the underline style back and then draws again.
I have no idea why it is doing it in this highly convoluted way, but
this code goes all way back to the initial import. However, it currently
fails to account for Arabic justification when the Arabic text does not
have any space characters.
Instead of trying to guess more how much width the Arabic justification
adds, I’m removing this code altogether to let the normal drawing code
handle the underline drawing.
Lets see what will break.
Update text expectation because we now do one-less drawing.
Change-Id: I8158bd15370005a78b866c8192414e4b46af2727
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152452
Tested-by: Jenkins
Reviewed-by: خالد حسني
diff --git a/sw/qa/extras/layout/layout2.cxx b/sw/qa/extras/layout/layout2.cxx
index b4b004951bf0..e9f2372c0d97 100644
--- a/sw/qa/extras/layout/layout2.cxx
+++ b/sw/qa/extras/layout/layout2.cxx
@@ -875,7 +875,7 @@ CPPUNIT_TEST_FIXTURE(SwLayoutWriter2, testRedlineMoving2)
// text and numbering colors show moving of the list item
// These were 0 (other color, not COL_GREEN, color of the tracked text
movement)
assertXPath(pXmlDoc,
"/metafile/push/push/push/textcolor[@color='#008000']", 5);
-assertXPath(pXmlDoc, "/metafile/push/push/push/font[@color='#008000']",
11);
+assertXPath(pXmlDoc, "/metafile/push/push/push/font[@color='#008000']", 9);
}
CPPUNIT_TEST_FIXTURE(SwLayoutWriter2, testRedlineMovingDOCX)
diff --git a/sw/source/core/txtnode/swfont.cxx
b/sw/source/core/txtnode/swfont.cxx
index c0149d9a6573..a4ac4f675aea 100644
--- a/sw/source/core/txtnode/swfont.cxx
+++ b/sw/source/core/txtnode/swfont.cxx
@@ -1099,16 +1099,6 @@ void SwSubFont::DrawText_( SwDrawTextInfo , const
bool bGrey )
if (TextFrameIndex(COMPLETE_STRING) == rInf.GetLen())
rInf.SetLen( nLn );
-FontLineStyle nOldUnder = LINESTYLE_NONE;
-SwUnderlineFont* pUnderFnt = nullptr;
-
-if( rInf.GetUnderFnt() )
-{
-nOldUnder = GetUnderline();
-SetUnderline( LINESTYLE_NONE );
-pUnderFnt = rInf.GetUnderFnt();
-}
-
if( !pLastFont || pLastFont->GetOwner() != m_nFontCacheId )
ChgFnt( rInf.GetShell(), rInf.GetOut() );
@@ -1165,57 +1155,6 @@ void SwSubFont::DrawText_( SwDrawTextInfo , const
bool bGrey )
}
}
-if( pUnderFnt && nOldUnder != LINESTYLE_NONE )
-{
-Size aFontSize = GetTextSize_( rInf );
-const OUString oldStr = rInf.GetText();
-
-TextFrameIndex const nOldIdx = rInf.GetIdx();
-TextFrameIndex const nOldLen = rInf.GetLen();
-tools::Long nSpace = 0;
-if( rInf.GetSpace() )
-{
-TextFrameIndex nTmpEnd = nOldIdx + nOldLen;
-if (nTmpEnd > TextFrameIndex(oldStr.getLength()))
-nTmpEnd = TextFrameIndex(oldStr.getLength());
-
-const SwScriptInfo* pSI = rInf.GetScriptInfo();
-
-const bool bAsianFont =
-( rInf.GetFont() && SwFontScript::CJK ==
rInf.GetFont()->GetActual() );
-for (TextFrameIndex nTmp = nOldIdx; nTmp < nTmpEnd; ++nTmp)
-{
-if (CH_BLANK == oldStr[sal_Int32(nTmp)] || bAsianFont ||
-(nTmp + TextFrameIndex(1) <
TextFrameIndex(oldStr.getLength())
- && pSI
- && i18n::ScriptType::ASIAN == pSI->ScriptType(nTmp +
TextFrameIndex(1
-{
-++nSpace;
-}
-}
-
-// if next portion if a hole portion we do not consider any
-// extra space added because the last character was ASIAN
-if ( nSpace && rInf.IsSpaceStop() && bAsianFont )
- --nSpace;
-
-nSpace *= rInf.GetSpace() / SPACING_PRECISION_FACTOR;
-}
-
-rInf.SetWidth( sal_uInt16(aFontSize.Width() + nSpace) );
-rInf.SetTextIdxLen( " ", TextFrameIndex(0), TextFrameIndex(2) );
-SetUnderline( nOldUnder );
-rInf.SetUnderFnt( nullptr );
-
-// set position for underline font
-rInf.SetPos( pUnderFnt->GetPos() );
-
-pUnderFnt->GetFont().DrawStretchText_( rInf );
-
-
[Libreoffice-bugs] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 --- Comment #44 from William Friedman --- Created attachment 187634 --> https://bugs.documentfoundation.org/attachment.cgi?id=187634=edit Document showing another cursor problem The attached document suffers from another problem with cursor placement. 1. Set the alignment to "right." 2. Type a character. 3. Press space. 4. The cursor is now beyond the right margin. If you show formatting marks, you will see the space is beyond the right margin. Why? I cannot reproduce this using a new document, however. If this issue is unrelated to our current discussion, I will file a new bug report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 --- Comment #44 from William Friedman --- Created attachment 187634 --> https://bugs.documentfoundation.org/attachment.cgi?id=187634=edit Document showing another cursor problem The attached document suffers from another problem with cursor placement. 1. Set the alignment to "right." 2. Type a character. 3. Press space. 4. The cursor is now beyond the right margin. If you show formatting marks, you will see the space is beyond the right margin. Why? I cannot reproduce this using a new document, however. If this issue is unrelated to our current discussion, I will file a new bug report. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153994] Sidebar character deck/tab shows Western font with no excuse
https://bugs.documentfoundation.org/show_bug.cgi?id=153994 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149004] Libreoffice crashes when remote instances using the installation
https://bugs.documentfoundation.org/show_bug.cgi?id=149004 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155357] Provide a command line parameter to select GPU used for Skia hardware rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=155357 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155195] FILEOPEN File on SMB share cannot be opened via file dialog of KDE
https://bugs.documentfoundation.org/show_bug.cgi?id=155195 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155266] VIEWING: v7.5.3.2 Release MacOSX Monterey, MacBook Air M1 (ARM) Writer: scroll lag
https://bugs.documentfoundation.org/show_bug.cgi?id=155266 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155316] Function Wizard should remember the Category field selection from its prior use, at least per session (RFE)
https://bugs.documentfoundation.org/show_bug.cgi?id=155316 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155299] Enhancement: E-Mail by using mail-merge needs handling of: "messages per connection"
https://bugs.documentfoundation.org/show_bug.cgi?id=155299 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153994] Sidebar character deck/tab shows Western font with no excuse
https://bugs.documentfoundation.org/show_bug.cgi?id=153994 --- 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 151856] Cannot get rid of paint can in Impress Version 7.4.2.3
https://bugs.documentfoundation.org/show_bug.cgi?id=151856 --- Comment #4 from QA Administrators --- Dear Markl, 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 152450] PostgreSQL JDBC: Creating query - table alias is always appended by GUI, special settings wont work here
https://bugs.documentfoundation.org/show_bug.cgi?id=152450 --- 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 149549] recent files list deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=149549 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151425] LIBRE OFFICE WRITER Crashes when scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=151425 --- Comment #3 from QA Administrators --- Dear Shane White, 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 150648] EAN13 function works in spreadsheet with LibreOffice 7.3 not 7.4
https://bugs.documentfoundation.org/show_bug.cgi?id=150648 --- Comment #7 from QA Administrators --- Dear robert.bassi...@free.fr, 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 149549] recent files list deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=149549 --- Comment #10 from QA Administrators --- Dear Graham GADGET, 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 145094] Minimal Row Height Reduction problem, Doesn't reduce certain rows and they have to be reduced one by one, doesn't work properly
https://bugs.documentfoundation.org/show_bug.cgi?id=145094 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145094] Minimal Row Height Reduction problem, Doesn't reduce certain rows and they have to be reduced one by one, doesn't work properly
https://bugs.documentfoundation.org/show_bug.cgi?id=145094 --- Comment #3 from QA Administrators --- Dear yueisklwfcqpgfuiik, 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 144391] Calc: link to files management.
https://bugs.documentfoundation.org/show_bug.cgi?id=144391 --- Comment #8 from QA Administrators --- Dear Arnaldo, 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 146067] MA trend lines are displayed with inconsistent X offset, depending on the label values
https://bugs.documentfoundation.org/show_bug.cgi?id=146067 --- Comment #13 from QA Administrators --- Dear Hernan, 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 144391] Calc: link to files management.
https://bugs.documentfoundation.org/show_bug.cgi?id=144391 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111721] Add support for Tagged Image File Format ( .tiff )
https://bugs.documentfoundation.org/show_bug.cgi?id=111721 --- Comment #2 from QA Administrators --- Dear vihsa, 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 94735] Transparent gradient of kind draw:style="square" is rendered wrong in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=94735 --- 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 142440] Merge cells with different border styles create unexpected result
https://bugs.documentfoundation.org/show_bug.cgi?id=142440 --- Comment #6 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 142509] Tabs and other paragraph attributes not exported from Impress to PowerPoint correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=142509 --- Comment #6 from QA Administrators --- Dear Thorsten Wagner, 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 142318] FILESAVE DOCX export of group with wrap "in line" has wrong vertical position
https://bugs.documentfoundation.org/show_bug.cgi?id=142318 --- Comment #4 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 117123] Editing: Using ALT + number moves position in a table
https://bugs.documentfoundation.org/show_bug.cgi?id=117123 --- Comment #5 from QA Administrators --- Dear MM, 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 137090] Impress: cannot run custom slide show with hidden slides
https://bugs.documentfoundation.org/show_bug.cgi?id=137090 --- Comment #2 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 137112] Header Spacing dialog setting behave as expected or different for docx
https://bugs.documentfoundation.org/show_bug.cgi?id=137112 --- 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 134900] FILEOPEN: DOCX: position of objects in drawing canvas not as in original
https://bugs.documentfoundation.org/show_bug.cgi?id=134900 --- Comment #9 from QA Administrators --- Dear rominator, 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 107201] EDITING: Selecting few table rows and the the paragraph below it at once isn't possible
https://bugs.documentfoundation.org/show_bug.cgi?id=107201 --- Comment #10 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 155133] FILEOPEN DOCX Image in background does not overlap header/footer content
https://bugs.documentfoundation.org/show_bug.cgi?id=155133 --- Comment #5 from Justin L --- I don't think you will win this battle. LO would need a fundamental change in how it paints the header/footer. We've been fighting this battle forever. See bug 143793 for some of the trouble it has caused. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144812] Textbox in caption frame wrongly positioned after DOCX export
https://bugs.documentfoundation.org/show_bug.cgi?id=144812 --- Comment #4 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137272] Superscripted font is cut off and line spacing increased when smaller block quoted text has footnote or endnote in it, due to use of one font size for all footnotes in
https://bugs.documentfoundation.org/show_bug.cgi?id=137272 --- Comment #17 from Telesto --- @TH (In reply to Buovjaga from comment #12) > I don't understand how to do step 2, so setting back to needinfo. Would you mind to attach a sample document where the steps in comment 0/ comment 16 are applied (so we can open the document and see the - broken - end result) The steps are apparently less obvious -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137272] Superscripted font is cut off and line spacing increased when smaller block quoted text has footnote or endnote in it, due to use of one font size for all footnotes in
https://bugs.documentfoundation.org/show_bug.cgi?id=137272 Telesto changed: What|Removed |Added Status|REOPENED|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152844] FILEOPEN DOCX: Footnote separator alignment changes in PS
https://bugs.documentfoundation.org/show_bug.cgi?id=152844 --- Comment #7 from Justin L --- (In reply to Dieter from comment #6) > Second issue > Text direction in PS Footnote changes from "Use superordinate object > settings" to LTR (Filepen not filesafe problem) MS Formats do not have "superordinate object settings" - so either right or left is assigned on export. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90316] FILEOPEN: Support contour wrap on DOCX SmartArt
https://bugs.documentfoundation.org/show_bug.cgi?id=90316 --- Comment #9 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142284] FILEOPEN: DOC Wrap lost on contoured images (is it auto-contour?)
https://bugs.documentfoundation.org/show_bug.cgi?id=142284 Justin L changed: What|Removed |Added Summary|FILEOPEN: DOC Wrap on |FILEOPEN: DOC Wrap lost on |contoured images broken in |contoured images (is it |6.4 |auto-contour?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124615] FILESAVE AND FILEOPEN: rotated images not rotated on import or export
https://bugs.documentfoundation.org/show_bug.cgi?id=124615 --- Comment #10 from Justin L --- (In reply to Luke from comment #8) > Did you try creating 2 documents with only the rotation angle changed? Good idea. Unfortunately, using Word 2010 I get a very clear entry. But "RotatedPenguin.doc" doesn't have this... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96579] FILESAVE ODT->DOC/X: Figure caption badly converted in Word format because image anchoring and wrapping is changed to as-character/DML
https://bugs.documentfoundation.org/show_bug.cgi?id=96579 Justin L changed: What|Removed |Added Summary|[WRITER] Figure caption |FILESAVE ODT->DOC/X: Figure |badly converted in Word |caption badly converted in |format because image|Word format because image |anchoring and wrapping is |anchoring and wrapping is |changed to as-character/DML |changed to as-character/DML -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135003] Image in exported DOC moves the wrong direction (jump right when pressing down)
https://bugs.documentfoundation.org/show_bug.cgi?id=135003 Justin L changed: What|Removed |Added Severity|normal |minor Priority|medium |low --- Comment #6 from Justin L --- repro 7.6+ I imagine the difference is some compatibility flag relating to wrapping, as well as having multiple flies to contend with when the anchor moves down to the next empty paragraph. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141223] FILEOPEN DOC: Grouped images positioned and scaled differently than in Microsoft Word
https://bugs.documentfoundation.org/show_bug.cgi?id=141223 Justin L changed: What|Removed |Added Summary|FILEOPEN DOC: Embedded |FILEOPEN DOC: Grouped |image positioned and scaled |images positioned and |differently than in |scaled differently than in |Microsoft Word |Microsoft Word -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 52436] Fileopen DOC: AutoShape position not displayed correctly in Writer (likely due to CR/font/paragraph properties)
https://bugs.documentfoundation.org/show_bug.cgi?id=52436 Justin L changed: What|Removed |Added Summary|Fileopen DOC: AutoShape |Fileopen DOC: AutoShape |position not displayed |position not displayed |correctly in Writer |correctly in Writer (likely ||due to CR/font/paragraph ||properties) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93832] Import of Word .doc file with frames and drawings objects is wrong due to complex wrapping
https://bugs.documentfoundation.org/show_bug.cgi?id=93832 Justin L changed: What|Removed |Added Summary|Import of Word .doc file|Import of Word .doc file |with frames and drawings|with frames and drawings |objects is wrong|objects is wrong due to ||complex wrapping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155619] New: screen size incorrectly detected
https://bugs.documentfoundation.org/show_bug.cgi?id=155619 Bug ID: 155619 Summary: screen size incorrectly detected Product: LibreOffice Version: 7.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jeanmarcran...@gmail.com Possibly related to bug #150236 and similars. Problem: given some specific conditions, opening an existing (or new) document will result in a mis-sized screen, in which the status bar is not be visible. Simplest steps to reproduce: - start with --safe-mode command-line argument - when asked, click "continue in safe mode" - once the start center is visible, maximize the window - create a new calc document (procedure also works with Writer document) - on the bottom, notice that the status bar (i.e. the line indicating the zoom level) is visible, as well as the tab list - close the document - create a new one - on the bottom, notice that the tab list is visible, but that the status bar is not - possibly hidden by the OS's taskbar - from this point, all documents created or opened will not show the status bar - de-maximizing and re-maximizing the window resolves the issue... but it's annoying. Additional notes - bibisected on the "relases" version to 7.4.0.0.beta1 - see log below - only reproduced on one specific machine, which runs Debian/KDE. Not reproduced on Windows 10 on the same computer - only reproduced on the laptop's built-in 1366x768 screen. Not reproduced when the same computer is connected to an external 2560x1440 display. - I can bibisect it on the 7.4.0 tree later this week if it helps, but given the changes that were done to fix #150236, I suspect that it might not be worthwhile. Let me know. - I'm assuming that --safe-mode eliminates all possible configuration issues. Let me know if I'm missing something. Thanks. # bad: [f74cdf1695a86287473f938714d5634d5aa263be] libreoffice-7.4.7.2 # good: [2770c66a6f192f50ab95369500f9aa173b9feb6e] libreoffice-7.2.0.2 git bisect start 'f74cdf169' '2770c66a6' # good: [27f3ae17bc2accde669b29cdd0f76b18a621] libreoffice-7.3.3.2 git bisect good 27f3ae17bc2accde669b29cdd0f76b18a621 # bad: [454d6018ad36e040bfa38e15a11abebaf37f09f2] libreoffice-7.4.0.3 git bisect bad 454d6018ad36e040bfa38e15a11abebaf37f09f2 # good: [a97b011777104b40d94bba98771b7534af453b96] libreoffice-7.3.6.2 git bisect good a97b011777104b40d94bba98771b7534af453b96 # good: [ecd3442e06c86e68a30e733be8480477ad128b0e] libreoffice-7.4.0.0.alpha1 git bisect good ecd3442e06c86e68a30e733be8480477ad128b0e # bad: [c193b6c5f4ca36c29b8fac56db586600c59d3acc] libreoffice-7.4.0.1 git bisect bad c193b6c5f4ca36c29b8fac56db586600c59d3acc # bad: [07e204c86738205a6225f6277f26a739611bf885] libreoffice-7.4.0.0.beta1 git bisect bad 07e204c86738205a6225f6277f26a739611bf885 # first bad commit: [07e204c86738205a6225f6277f26a739611bf885] libreoffice-7.4.0.0.beta1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33263] FILEOPEN DOC: OPTIMAL wrap never means parallel in MSO, but it does for tiny frames in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=33263 Justin L changed: What|Removed |Added Priority|medium |low Summary|FILEOPEN wrong wrap at |FILEOPEN DOC: OPTIMAL wrap |frame in imported .doc from |never means parallel in |original Wrap Around tables |MSO, but it does for tiny |used as bullets |frames in LO CC||jl...@mail.com --- Comment #16 from Justin L --- OK - I believe I understand. LibreOffice designed OPTIMAL wrap to mean parallel wrap if the frame was some arbitrarily chosen small enough size. OK - I can accept that. (This is called AUTO in MSO - meaning the computer is allowed to intelligently decide how to wrap the text, which is precisely what is happening.) MSO treats AUTO as "pick the best side" and never parallel. I imagine we could add a flag to optimal to tell it never to parallel wrap for compatibility purposes. Better though is to just have a human modify the affected documents and specify whether the wrapping should be before or after. Extremely low priority. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 78405] FILEOPEN: WPS DOC - Image size not correct (fixed by round-tripping in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=78405 Justin L changed: What|Removed |Added Hardware|Other |All Summary|FILEOPEN: WPS DOC - Image |FILEOPEN: WPS DOC - Image |size not correct|size not correct (fixed by ||round-tripping in MSO) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100580] FILESAVE: ODT->DOC/X document (two high frames anchored to page ..) rendered as two pages, has only one page in doc/DOCX export
https://bugs.documentfoundation.org/show_bug.cgi?id=100580 Justin L changed: What|Removed |Added Summary|FILESAVE: Odt document (two |FILESAVE: ODT->DOC/X |high frames anchored to |document (two high frames |page ..) rendered as two|anchored to page ..) |pages, has only one page |rendered as two pages, has |in doc/DOCX eport |only one page in doc/DOCX ||export -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108734] [META] Character dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108734 Bug 108734 depends on bug 107405, which changed state. Bug 107405 Summary: Setting fixed kerning (text spacing) is limited to -2pt https://bugs.documentfoundation.org/show_bug.cgi?id=107405 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- 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 107405, which changed state. Bug 107405 Summary: Setting fixed kerning (text spacing) is limited to -2pt https://bugs.documentfoundation.org/show_bug.cgi?id=107405 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148066] Warning dialog open above other window
https://bugs.documentfoundation.org/show_bug.cgi?id=148066 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report. Please test again in a version that is currently supported, namely version 7.5, and report back to let us know if the issue is still present. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101686] Text render changes to RTL depending on zoom level
https://bugs.documentfoundation.org/show_bug.cgi?id=101686 خالد حسني changed: What|Removed |Added Assignee|kha...@libreoffice.org |libreoffice-b...@lists.free ||desktop.org Status|ASSIGNED|NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: configure.ac
configure.ac | 34 +-
1 file changed, 9 insertions(+), 25 deletions(-)
New commits:
commit 70fd835b4cf75e386ee115c705241a4059fb68a8
Author: Khaled Hosny
AuthorDate: Tue May 30 12:25:22 2023 +0300
Commit: خالد حسني
CommitDate: Thu Jun 1 01:57:07 2023 +0200
Fix ccache cache size detection
I have ccache 4.8.1 and it reports:
(/home/khaled/.config/ccache/ccache.conf) max_size = 30.0 GB
With a space between the number and the unit and the configure check
with then see a unit-less 30 and will warn:
ccache's cache size is less than 1GB using it is counter-productive:
Disabling auto-ccache detection
Instead of relying on the human readable output, use --print-stats
which prints machine-readable output and is available since 3.7 (thanks
to Cloph for the suggestion).
Change-Id: I69f994a07cfbf08b66a2010f9c99401881d4acf3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152382
Reviewed-by: Christian Lohmaier
Tested-by: Jenkins
diff --git a/configure.ac b/configure.ac
index e86e3c30141d..06a60ebf8d8d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3316,31 +3316,15 @@ AC_SUBST(CCACHE_DEPEND_MODE)
# sccache defaults are good enough
if test "$CCACHE" != "" -a -z "$SCCACHE"; then
-# e.g. (/home/rene/.config/ccache/ccache.conf) max_size = 20.0G
-# -p works with both 4.2 and 4.4
-ccache_size_msg=$([$CCACHE -p | $AWK /max_size/'{ print $4 }' | sed -e
's/\.[0-9]*//'])
-ccache_size=$(echo "$ccache_size_msg" | grep "G" | sed -e 's/G.*$//')
-if test "$ccache_size" = ""; then
-ccache_size=$(echo "$ccache_size_msg" | grep "M" | sed -e 's/\ M.*$//')
-if test "$ccache_size" = ""; then
-ccache_size=0
-fi
-# we could not determine the size or it was less than 1GB -> disable
auto-ccache
-if test $ccache_size -lt 1024; then
-CCACHE=""
-AC_MSG_WARN([ccache's cache size is less than 1GB using it is
counter-productive: Disabling auto-ccache detection])
-add_warning "ccache's cache size is less than 1GB using it is
counter-productive: auto-ccache detection disabled"
-else
-# warn that ccache may be too small for debug build
-AC_MSG_WARN([ccache's cache size is less than 5GB using it may be
counter-productive for debug or symbol-enabled build])
-add_warning "ccache's cache size is less than 5GB using it may be
counter-productive for debug or symbol-enabled build"
-fi
-else
-if test $ccache_size -lt 5; then
-#warn that ccache may be too small for debug build
-AC_MSG_WARN([ccache's cache size is less than 5GB using it may be
counter-productive for debug or symbol-enabled build])
-add_warning "ccache's cache size is less than 5GB using it may be
counter-productive for debug or symbol-enabled build"
-fi
+ccache_size=$($CCACHE --print-stats | $AWK /cache_size_kibibyte/'{ print
$2 }')
+if test $ccache_size -lt 976563; then
+CCACHE=""
+AC_MSG_WARN([ccache's cache size is less than 1GB using it is
counter-productive: Disabling auto-ccache detection])
+add_warning "ccache's cache size is less than 1GB using it is
counter-productive: auto-ccache detection disabled"
+elif test $ccache_size -lt 4883000; then
+# warn that ccache may be too small for debug build
+AC_MSG_WARN([ccache's cache size is less than 5GB using it may be
counter-productive for debug or symbol-enabled build])
+add_warning "ccache's cache size is less than 5GB using it may be
counter-productive for debug or symbol-enabled build"
fi
fi
[Libreoffice-bugs] [Bug 148408] Pasting a not-so-long section of a webpage takes lots of time
https://bugs.documentfoundation.org/show_bug.cgi?id=148408 --- Comment #9 from Stéphane Guillou (stragu) --- (In reply to Eyal Rozenberg from comment #8) > (In reply to Stéphane Guillou (stragu) from comment #7) > > I feel like this is probably related to bug 148408 and how LO fetches images > > from the web. .. duplicate of bug 148408. > > _This_ is bug 148408. I'm guessing you meant some other bug? :-P yup, sorry, wrong copy and paste :) I meant bug 45307. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137272] Superscripted font is cut off and line spacing increased when smaller block quoted text has footnote or endnote in it, due to use of one font size for all footnotes in
https://bugs.documentfoundation.org/show_bug.cgi?id=137272 --- Comment #16 from TH --- OS: Windows 10 Pro All versions of LibreOffice through the latest one Description: Superscripted font is cut off and line spacing increased when smaller block quoted text has footnote or endnote in it, due to use of one font size for all footnotes in document. While I realize this may be caused by a limitation of the .odt format itself, given that it may not support saving different anchor text font sizes for footnotes against different main document text sizes, there IS a way to program a workaround, and that should be done. Simply look at the size of the surrounding text (to the anchor text of the footnote) and if that surrounding text is a smaller point size than the default text (e.g., of a document's main body), then calculate the size and position of the superscript for the anchor text (i.e., footnote or endnote indicator) to be proportionally smaller. For example, if my main document text, in the Default style, is 11 points, and that is the size used as the basis for calculating the footnote anchor text size and position when it is superscripted in the main document, things are fine. But as soon as my main document has a block quote of text that is say 9 points in its style, then when I place a footnote in that block quote or at the end of it, LibreOffice 7.x calculates the size of the anchor text for that note based upon the 11 point size of the anchor text style, and NOT based upon the proper 9 point size of the actual document text being footnoted. Consequently, the size of the anchor text in or at the end of the block quote ends up being TOO LARGE and its position TOO HIGH, so that a) the top of the anchor text-styled note number may be cut off AND the line spacing of the block quote line containing the footnote is thrown off and made too large, messing up the appearance of the document. That looks very poor and can be rectified with slightly better programming that takes into account the point size of surrounding document text (e.g., 9 points instead of the default 11 points). The above has been a problem with Apache OpenOffice and LibreOffice from the start, and has been a carried-over issue from the IBM Lotus Symphony days as well. Given the LibreOffice strives to be a more polished product and even compete to an extent against paid suites (e.g., Microsoft Office) this SHOULD and CAN be fixed, regardless of any possible .odt file format limitation. STEPS TO REPRODUCE (PAY ATTENTION): 1. Create a document with a default text size of 11, for example. Create a paragraph using that default. Set the anchor text style for footnotes to use the same font at the same 11 point size, as its basis for calculating the superscript size and position of the note anchor text 2. Create a block quote with the same font but using a 9 point text size, and place a paragraph of text in the document using that block quote. Then place a footnote in or at the end of that block quote. 3. Having done step 2, you will notice that the line of text in the block quote containing the footnote anchor text is a) misaligned with line spacing that is too large for the block quote (e.g., when the latter is single spaced text) and b) the footnote anchor text (e.g., "1" for the first footnote) will likely be cut off at the top, showing only a portion of the "1", and that is because the size of the anchor text and its superscripted placement are both being calculated on the basis of the anchor text style for footnotes using an 11 point text size rather than the 9 point text size of the surrounding document. Actual Results: The footnote (or endnote if that's what's used) anchor text is too large and cut off at the top when the footnote (or endnote) is placed in or at the end of the block quote in the document. Expected Results: The anchor text for the footnote in the smaller-point block quote (which is 9 points rather than the 11 points of the default style) should be smaller and a bit lower than corresponding anchor text for a footnote placed in the text based upon the default style having an 11 point size. In other words, even a note anchor placed in a block quote having a somewhat smaller point size than the point size of the main document's text should NOT be cut off or cause the line of text in which it's placed to have line spacing that is too large and obviously different from the rest of the lines in the block quote. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155547] Provide a more direct way to write tests for low level text layout issues
https://bugs.documentfoundation.org/show_bug.cgi?id=155547 --- Comment #3 from خالد حسني --- Looking at sw layout tests, looks like GDIMetaFile is the thing I want (I probably saw it before then forgot about it), now I need to see if it has all the information I need. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137272] Superscripted font is cut off and line spacing increased when smaller block quoted text has footnote or endnote in it, due to use of one font size for all footnotes in
https://bugs.documentfoundation.org/show_bug.cgi?id=137272 TH changed: What|Removed |Added Resolution|INSUFFICIENTDATA|--- Status|RESOLVED|REOPENED --- Comment #15 from TH --- For anyone actually reading carefully and paying close attention, there IS sufficient information in my original description (below) to CONFIRM the bug! Don't be lazy. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103309] [META] Print dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103309 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||155124 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155124 [Bug 155124] macOS print options do not provide page size settings to export as PDF. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155124] macOS print options do not provide page size settings to export as PDF.
https://bugs.documentfoundation.org/show_bug.cgi?id=155124 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW CC||stephane.guillou@libreoffic ||e.org Blocks||103309 Component|Calc|Printing and PDF export Ever confirmed|0 |1 --- Comment #11 from Stéphane Guillou (stragu) --- Reproduced. Even with "scale to fit paper size" off, which reduces the white margins, there is still a margin left and the result does not match the preview. I have been using the "PDF" button at the bottom of the dialog. Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 2; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fc6806c4be8585ce0d35a6b581bf8b3dbf858500 CPU threads: 2; OS: Mac OS X 13.2.1; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded On Linux, PDF is like previewed, no margins. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103309 [Bug 103309] [META] Print dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112701] [META] DOC (binary) image-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112701 Bug 112701 depends on bug 112595, which changed state. Bug 112595 Summary: FILEOPEN: DOC - Rotation of Image differs by 2 degrees/by 220 degrees (comment 6) https://bugs.documentfoundation.org/show_bug.cgi?id=112595 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124615] FILESAVE AND FILEOPEN: rotated images not rotated on import or export
https://bugs.documentfoundation.org/show_bug.cgi?id=124615 Justin L changed: What|Removed |Added CC||bugzilla@mkr.email --- Comment #9 from Justin L --- *** Bug 112595 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 112595] FILEOPEN: DOC - Rotation of Image differs by 2 degrees/by 220 degrees (comment 6)
https://bugs.documentfoundation.org/show_bug.cgi?id=112595 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #12 from Justin L --- *** This bug has been marked as a duplicate of bug 124615 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125905] [META] DOC: Regressions introduced by 705a8c226aee3e68db492083b7cf8b704335328b
https://bugs.documentfoundation.org/show_bug.cgi?id=125905 Bug 125905 depends on bug 119803, which changed state. Bug 119803 Summary: FILEOPEN Table in frame in DOC not displayed in Writer https://bugs.documentfoundation.org/show_bug.cgi?id=119803 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112700] [META] DOC (binary) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112700 Bug 112700 depends on bug 119803, which changed state. Bug 119803 Summary: FILEOPEN Table in frame in DOC not displayed in Writer https://bugs.documentfoundation.org/show_bug.cgi?id=119803 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117447] FILEOPEN Floating table in attached DOC(X) is lost(hidden) during import
https://bugs.documentfoundation.org/show_bug.cgi?id=117447 --- Comment #15 from Justin L --- *** Bug 119803 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 112698] [META] DOC (binary) frame-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112698 Bug 112698 depends on bug 119803, which changed state. Bug 119803 Summary: FILEOPEN Table in frame in DOC not displayed in Writer https://bugs.documentfoundation.org/show_bug.cgi?id=119803 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119803] FILEOPEN Table in frame in DOC not displayed in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=119803 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Justin L --- *** This bug has been marked as a duplicate of bug 117447 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 --- Comment #43 from Justin L --- Not my area. Nothing of value to add. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 --- Comment #43 from Justin L --- Not my area. Nothing of value to add. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 155128] Cell highlighting in spreadsheets lags when using arrows on keyboard to navigate sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=155128 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Whiteboard| QA:needsComment| --- Comment #2 from Stéphane Guillou (stragu) --- I couldn't reproduce on: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 2; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Can you please update to the most recent release in 7.5, and test again? Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155280] Allow reducing height of text box with multiple columns (even if "fit height to text" is on)
https://bugs.documentfoundation.org/show_bug.cgi?id=155280 --- Comment #2 from Stéphane Guillou (stragu) --- Created attachment 187632 --> https://bugs.documentfoundation.org/attachment.cgi?id=187632=edit multi-column text box and shape for comparison -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148893] Improve multicolumn text behavior while typing inside Draw shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=148893 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5280 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155280] Allow reducing height of text box with multiple columns (even if "fit height to text" is on)
https://bugs.documentfoundation.org/show_bug.cgi?id=155280 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Allow adjusting height of |Allow reducing height of |text box when setting |text box with multiple |columns |columns (even if "fit ||height to text" is on) Status|UNCONFIRMED |NEW Whiteboard| QA:needsComment| CC||mikekagan...@hotmail.com, ||stephane.guillou@libreoffic ||e.org OS|Windows (All) |All See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8893 Blocks||142729 Ever confirmed|0 |1 Version|7.4.6.2 release |7.2.0.0.beta1+ --- Comment #1 from Stéphane Guillou (stragu) --- Thank you, Don. Reproduced in a recent master build: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fc4f7db59152f606b6aa88cf32197700959d0f8b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded And since columns in shapes were implemented: Version: 7.2.0.0.beta1 / LibreOffice Community Build ID: c6974f7afec4cd5195617ae48c6ef9aacfe85ddd CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I understand this has to do with the fact that text boxes have the setting "fit height to text" on by default, which behaves unexpectedly with multiple columns. Mike, what do you think? I can see how users would expect the text to be redistributed between columns when reducing the height even when "fit height to text" is on (until it eventually runs out of space and actually blocks the resizing). The current behaviour is a bit unexpected and erratic (e.g. it sometimes is possible to "push" a single line into the second column when trying to reduce the height). Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142729 [Bug 142729] [META] Text box's column bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142729] [META] Text box's column bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142729 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||155280 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155280 [Bug 155280] Allow reducing height of text box with multiple columns (even if "fit height to text" is on) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155054] UI: Remediate frustration of unclear style names in style-name picklist contexts
https://bugs.documentfoundation.org/show_bug.cgi?id=155054 --- Comment #7 from R. Bingham --- (In reply to Eyal Rozenberg from comment #6) > Lots of text in this request - enough to make it a bit inaccessible to > readers to be honest. > > Anyway, IMHO, it would be beneficial to see the hierarchy when selecting a > style for "Next Style" or "Inherit from"; but if this were made into too big > of a spectacle, then the benefit would be outweighed by the detriment. So, I > would only support a visually subtle solution if one were available. Agreed, thus my suggestion B2 above: B2) In generating the text of a picklist entry, prepend a context clue from the next higher level(s) of the Navigator hierarchical tree, i.e., in a '|' (bar) separated format "higher_context_clue | terminal_phrase_name" Note that the bar-separator hierarchy presentation is already used in Tools->Customize->Target drop box to show the first two levels of menu hierarchy for context. This I am not proposing a new UI visual pattern, just re-use of an existing pattern in yet another drop box context. Regards. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155054] UI: Remediate frustration of unclear style names in style-name picklist contexts
https://bugs.documentfoundation.org/show_bug.cgi?id=155054 --- Comment #7 from R. Bingham --- (In reply to Eyal Rozenberg from comment #6) > Lots of text in this request - enough to make it a bit inaccessible to > readers to be honest. > > Anyway, IMHO, it would be beneficial to see the hierarchy when selecting a > style for "Next Style" or "Inherit from"; but if this were made into too big > of a spectacle, then the benefit would be outweighed by the detriment. So, I > would only support a visually subtle solution if one were available. Agreed, thus my suggestion B2 above: B2) In generating the text of a picklist entry, prepend a context clue from the next higher level(s) of the Navigator hierarchical tree, i.e., in a '|' (bar) separated format "higher_context_clue | terminal_phrase_name" Note that the bar-separator hierarchy presentation is already used in Tools->Customize->Target drop box to show the first two levels of menu hierarchy for context. This I am not proposing a new UI visual pattern, just re-use of an existing pattern in yet another drop box context. Regards. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 V Stuart Foote changed: What|Removed |Added CC||jl...@mail.com --- Comment #42 from V Stuart Foote --- Sorry, not intending to be difficult. And, I agree that we do reasonable things with the handling of justified lines of text, i.e. to start and end at the margins with a character--I didn't mean to imply that handling needed to change. It is more just a question of what to do with the *excess* spaces when justification is applied. Keeping them hanging around beyond the page/paragraph margin, where the cursor can get lost, simply suggests an obvious action to either truncate or wrap. Otherwise when alignment is not justified, as DF or paragraph style, then it would be a simple and consistent action for the spaces to wrap by default. But also, establish an option to globally truncate 3 or more spaces--and selectively apply [M] [T] Autocorrect table action. In general multiple spaces are never a helpful occurrence and should be pruned. @Justin, what is your take on this? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 V Stuart Foote changed: What|Removed |Added CC||jl...@mail.com --- Comment #42 from V Stuart Foote --- Sorry, not intending to be difficult. And, I agree that we do reasonable things with the handling of justified lines of text, i.e. to start and end at the margins with a character--I didn't mean to imply that handling needed to change. It is more just a question of what to do with the *excess* spaces when justification is applied. Keeping them hanging around beyond the page/paragraph margin, where the cursor can get lost, simply suggests an obvious action to either truncate or wrap. Otherwise when alignment is not justified, as DF or paragraph style, then it would be a simple and consistent action for the spaces to wrap by default. But also, establish an option to globally truncate 3 or more spaces--and selectively apply [M] [T] Autocorrect table action. In general multiple spaces are never a helpful occurrence and should be pruned. @Justin, what is your take on this? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148893] Improve multicolumn text behavior while typing inside Draw shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=148893 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Blocks||142729 Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced in: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fc4f7db59152f606b6aa88cf32197700959d0f8b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded - lines of text are distributed equally between columns - when exiting edit mode, content jumps to fill columns in order - entering edit mode again goes back to the distributed display Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142729 [Bug 142729] [META] Text box's column bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142729] [META] Text box's column bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142729 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||148893 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148893 [Bug 148893] Improve multicolumn text behavior while typing inside Draw shapes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104704] FILESAVE as DOC: Table in footer mangled following page style change to same style
https://bugs.documentfoundation.org/show_bug.cgi?id=104704 --- Comment #6 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a05dc1591ca9122056e95cb2801e7f924bb7ecdb tdf#104704 tdf#145998 doc/rtf import: don't lose section page break It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104704] FILESAVE as DOC: Table in footer mangled following page style change to same style
https://bugs.documentfoundation.org/show_bug.cgi?id=104704 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/ww8export/data/tdf104704_mangledFooter.odt |binary
sw/qa/extras/ww8export/ww8export4.cxx |5 +
sw/source/filter/ww8/ww8atr.cxx |5 +++--
3 files changed, 8 insertions(+), 2 deletions(-)
New commits:
commit a05dc1591ca9122056e95cb2801e7f924bb7ecdb
Author: Justin Luth
AuthorDate: Wed May 31 15:33:24 2023 -0400
Commit: Justin Luth
CommitDate: Thu Jun 1 00:29:31 2023 +0200
tdf#104704 tdf#145998 doc/rtf import: don't lose section page break
This fixes a LO 7.5 regression from
commit c37f62b71fa59917ef85ff98480dff18aa936e41
That 7.5 fix focused on DOCX, and didn't realize that the doc/rtf path
couldn't handle the same logic.
Just reverting to previous behaviour for DOC/RTF for now.
(It is too hard to find relevant documents because any document
starting with a section break on the first paragraph
[and there are MANY of these - an ODT default],
and that scenario harmlessly matches this code path.)
Change-Id: I82cfe10e217269448d38df0ca03ce6cae3536e56
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152467
Reviewed-by: Justin Luth
Tested-by: Jenkins
diff --git a/sw/qa/extras/ww8export/data/tdf104704_mangledFooter.odt
b/sw/qa/extras/ww8export/data/tdf104704_mangledFooter.odt
new file mode 100644
index ..2bd8c10f9ca4
Binary files /dev/null and
b/sw/qa/extras/ww8export/data/tdf104704_mangledFooter.odt differ
diff --git a/sw/qa/extras/ww8export/ww8export4.cxx
b/sw/qa/extras/ww8export/ww8export4.cxx
index 4a290a53f2d9..9b0f1f321b7b 100644
--- a/sw/qa/extras/ww8export/ww8export4.cxx
+++ b/sw/qa/extras/ww8export/ww8export4.cxx
@@ -142,6 +142,11 @@ CPPUNIT_TEST_FIXTURE(Test, testDontBreakWrappedTables)
CPPUNIT_ASSERT(bDontBreakWrappedTables);
}
+DECLARE_WW8EXPORT_TEST(testTdf104704_mangledFooter,
"tdf104704_mangledFooter.odt")
+{
+CPPUNIT_ASSERT_EQUAL(2, getPages());
+}
+
CPPUNIT_PLUGIN_IMPLEMENT();
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/filter/ww8/ww8atr.cxx b/sw/source/filter/ww8/ww8atr.cxx
index 041abc5c65c5..30df5b265b46 100644
--- a/sw/source/filter/ww8/ww8atr.cxx
+++ b/sw/source/filter/ww8/ww8atr.cxx
@@ -532,8 +532,9 @@ void MSWordExportBase::OutputSectionBreaks( const
SfxItemSet *pSet, const SwNode
// sections during import, so minimize unnecessary duplication
// by substituting a simple page break when the resulting section
is identical,
// unless this is needed to re-number the page.
-if (!bNewPageDesc && !pItem->GetNumOffset() && m_pCurrentPageDesc
-&& m_pCurrentPageDesc->GetFollow() == pItem->GetPageDesc())
+// DOCX only.
+if (!bNewPageDesc && !pItem->GetNumOffset() &&
!PreferPageBreakBefore()
+&& m_pCurrentPageDesc && m_pCurrentPageDesc->GetFollow() ==
pItem->GetPageDesc())
{
// A section break on the very first paragraph is ignored by
LO/Word
// and should NOT be turned into a page break.
[Libreoffice-bugs] [Bug 155618] table behaviour can't be customized
https://bugs.documentfoundation.org/show_bug.cgi?id=155618 --- Comment #1 from ksso --- Created attachment 187631 --> https://bugs.documentfoundation.org/attachment.cgi?id=187631=edit cant modify table behavior, bookbar doesn't hide easy cant modify table behavior, bookbar doesn't hide easy -- You are receiving this mail because: You are the assignee for the bug.
Enhancement proposal: Download free fonts
Would it be a valid enhancement to propose the following: LibreOffice should download free/libre fonts if they are not on the users' system. - Download and not install: - Install seems to be a system task, and is different among platforms - Libre and Free - Avoid licensing issues Feel free to direct me to another list or bugzilla.
[Libreoffice-bugs] [Bug 155618] New: table behaviour can't be customized
https://bugs.documentfoundation.org/show_bug.cgi?id=155618 Bug ID: 155618 Summary: table behaviour can't be customized Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kep...@gmail.com Description: try to customize table behavior (fixed or variable) but can't be done Steps to Reproduce: 1.create a table 2.try to modify its behavior 3.can't be done Actual Results: can't modify table behavior Expected Results: modify Reproducible: Always User Profile Reset: No Additional Info: other issues with tables and display with views -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155614] Background image stretched ignoring aspect ratio
https://bugs.documentfoundation.org/show_bug.cgi?id=155614 --- Comment #7 from Felix Rudolphi --- Comments keep getting lost, now I type this for 3rd time... Making adjustments by hand actually works, but is not convenient and requires 'visual judgement'. If format of slides is changed subsequently, all backgrounds would require re-adjustment. Should be automatic, maintaining aspect ratio. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155617] can't center or align right a table
https://bugs.documentfoundation.org/show_bug.cgi?id=155617 --- Comment #1 from ksso --- Created attachment 187630 --> https://bugs.documentfoundation.org/attachment.cgi?id=187630=edit table can't be centered table can't be centered -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155614] Background image stretched ignoring aspect ratio
https://bugs.documentfoundation.org/show_bug.cgi?id=155614 Felix Rudolphi changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #6 from Felix Rudolphi --- Comment was lost after uploading the attachments... Finding an aspect ratio by 'visual judgement' actually works, but is not convenient. Changes of slide format would require manual re-adjustments. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155617] New: can't center or align right a table
https://bugs.documentfoundation.org/show_bug.cgi?id=155617 Bug ID: 155617 Summary: can't center or align right a table Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kep...@gmail.com Description: can't center or align right a table as a whole Steps to Reproduce: 1.make a table 2.reduce its width 3.try to center or align right it Actual Results: can't be centered or aligned Expected Results: able to center and align Reproducible: Always User Profile Reset: No Additional Info: the table could be customized to be created and don't occupy all width page? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155614] Background image stretched ignoring aspect ratio
https://bugs.documentfoundation.org/show_bug.cgi?id=155614 --- Comment #5 from Felix Rudolphi --- Created attachment 187629 --> https://bugs.documentfoundation.org/attachment.cgi?id=187629=edit Manually adjusting in cm (visual judgement) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155614] Background image stretched ignoring aspect ratio
https://bugs.documentfoundation.org/show_bug.cgi?id=155614 --- Comment #4 from Felix Rudolphi --- Created attachment 187628 --> https://bugs.documentfoundation.org/attachment.cgi?id=187628=edit Manually adjusting in % (visual judgement) -- You are receiving this mail because: You are the assignee for the bug.
