[Libreoffice-ux-advise] [Bug 153525] Styles Preview should be able to show a grid of list styles (Tabbed UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=153525 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | Status|UNCONFIRMED |NEW CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Ever confirmed|0 |1 --- Comment #12 from Heiko Tietze --- We discussed this in the design meeting. Improvements to the styles preview widget in the notebookbar is needed. The idea to have a More... option, could also be some kind of expander at the right bottom, might simplify the implementation but does not meet the user expectations. The proposed maximize function sounds like a low hanging fruit. The expand thing could be more challenging. Maybe split these topics into separate tickets. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153525] Styles Preview should be able to show a grid of list styles (Tabbed UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=153525 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | Status|UNCONFIRMED |NEW CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Ever confirmed|0 |1 --- Comment #12 from Heiko Tietze --- We discussed this in the design meeting. Improvements to the styles preview widget in the notebookbar is needed. The idea to have a More... option, could also be some kind of expander at the right bottom, might simplify the implementation but does not meet the user expectations. The proposed maximize function sounds like a low hanging fruit. The expand thing could be more challenging. Maybe split these topics into separate tickets. -- You are receiving this mail because: You are the assignee for the bug.
Re: ESC meeting agenda: 2023-02-16 16:00 CET
Hi, On Thu, Feb 16, 2023 at 10:14:00AM +0300, Mike Kaganski wrote: > > 5.4 : 0/41 - 0 % (+0) > > 5.3 : 0/54 - 0 % (+0) > > 5.2 : 0/43 - 0 % (+0) > > 5.1 : 0/35 - 0 % (+0) > > 5.0 : 0/64 - 0 % (+0) > > 4.4 : 0/76 - 0 % (+0) > > 4.3 : 0/73 - 0 % (+0) > > 4.2 : 2/134 - 1 % (+0) > > 4.1 : 2/85 - 2 % (+0) > > 4.0 : 1/82 - 1 % (+0) > > old : 1/246 - 0 % (+0) > > IMO, this section is long obsolete, and gives no value. Maybe it's time to > retire this section? :) Xisco: could you please give Mike a code pointer where is the script that generates this? Thanks, Miklos
[Libreoffice-bugs] [Bug 153658] Not Commitment
https://bugs.documentfoundation.org/show_bug.cgi?id=153658 Megha Malik changed: What|Removed |Added Keywords||accessibility URL||https://www.meghamalik.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153658] New: Not Commitment
https://bugs.documentfoundation.org/show_bug.cgi?id=153658 Bug ID: 153658 Summary: Not Commitment Product: Impress Remote Version: 1.0.1 Hardware: Other OS: other Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hotmeghama...@gmail.com Description: I have been done that very well. I like spend nice time with peoples always with good, positive energy and fun. I like to make peoples happy. I think that is my talent in this world. And I’m very happy in what I do. I’m expensive because I offer to you a unique and a exclusive service and experience. Actual Results: Working Expected Results: Not Excpet Reproducible: Always User Profile Reset: Yes Additional Info: CCtplus -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svl/source
svl/source/fsstor/fsstorage.cxx | 88 ++--
svl/source/fsstor/fsstorage.hxx | 17 +--
2 files changed, 63 insertions(+), 42 deletions(-)
New commits:
commit a38f13e364f9416a1a6d1163eba431eb1c6d5908
Author: Noel Grandin
AuthorDate: Wed Feb 15 18:47:57 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Feb 16 07:23:57 2023 +
osl::Mutex->std::mutex in FSStorage
Change-Id: I62980bec76425980804368ba009ffaeb6bef800a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147104
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/svl/source/fsstor/fsstorage.cxx b/svl/source/fsstor/fsstorage.cxx
index 68e82feb0121..65e243d7ddad 100644
--- a/svl/source/fsstor/fsstorage.cxx
+++ b/svl/source/fsstor/fsstorage.cxx
@@ -75,10 +75,10 @@ FSStorage::FSStorage( const ::ucbhelper::Content& aContent,
FSStorage::~FSStorage()
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
osl_atomic_increment(_refCount); // to call dispose
try {
-dispose();
+disposeImpl(aGuard);
}
catch( uno::RuntimeException& )
{}
@@ -103,7 +103,7 @@ bool FSStorage::MakeFolderNoUI( std::u16string_view rFolder
)
ucbhelper::Content& FSStorage::GetContent()
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
return m_aContent;
}
@@ -244,14 +244,14 @@ uno::Sequence< sal_Int8 > SAL_CALL
FSStorage::getImplementationId()
void SAL_CALL FSStorage::copyToStorage( const uno::Reference< embed::XStorage
>& xDest )
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
if ( !xDest.is() || xDest == uno::Reference< uno::XInterface >(
static_cast< OWeakObject*> ( this ), uno::UNO_QUERY ) )
throw lang::IllegalArgumentException(); // TODO:
try
{
-CopyContentToStorage_Impl( GetContent(), xDest );
+CopyContentToStorage_Impl( m_aContent, xDest );
}
catch( embed::InvalidStorageException& )
{
@@ -285,8 +285,14 @@ void SAL_CALL FSStorage::copyToStorage( const
uno::Reference< embed::XStorage >&
uno::Reference< io::XStream > SAL_CALL FSStorage::openStreamElement(
const OUString& aStreamName, sal_Int32 nOpenMode )
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
+return openStreamElementImpl(aGuard, aStreamName, nOpenMode);
+}
+uno::Reference< io::XStream > FSStorage::openStreamElementImpl(
+std::unique_lock& /*rGuard*/,
+std::u16string_view aStreamName, sal_Int32 nOpenMode )
+{
// TODO/LATER: may need possibility to create folder if it was removed,
since the folder can not be locked
INetURLObject aFileURL( m_aURL );
aFileURL.Append( aStreamName );
@@ -383,8 +389,14 @@ uno::Reference< io::XStream > SAL_CALL
FSStorage::openEncryptedStreamElement(
uno::Reference< embed::XStorage > SAL_CALL FSStorage::openStorageElement(
const OUString& aStorName, sal_Int32 nStorageMode )
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
+return openStorageElementImpl(aGuard, aStorName, nStorageMode);
+}
+uno::Reference< embed::XStorage > FSStorage::openStorageElementImpl(
+std::unique_lock& /*rGuard*/,
+std::u16string_view aStorName, sal_Int32 nStorageMode )
+{
if ( ( nStorageMode & embed::ElementModes::WRITE )
&& !( m_nMode & embed::ElementModes::WRITE ) )
throw io::IOException(); // TODO: error handling
@@ -460,7 +472,7 @@ uno::Reference< embed::XStorage > SAL_CALL
FSStorage::openStorageElement(
uno::Reference< io::XStream > SAL_CALL FSStorage::cloneStreamElement( const
OUString& aStreamName )
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
// TODO/LATER: may need possibility to create folder if it was removed,
since the folder can not be locked
INetURLObject aFileURL( m_aURL );
@@ -532,7 +544,7 @@ void SAL_CALL FSStorage::copyStorageElementLastCommitTo(
const OUString& aStorName,
const uno::Reference< embed::XStorage >& xTargetStorage )
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
uno::Reference< embed::XStorage > xSourceStor( openStorageElement(
aStorName, embed::ElementModes::READ ),
uno::UNO_SET_THROW );
@@ -541,7 +553,7 @@ void SAL_CALL FSStorage::copyStorageElementLastCommitTo(
sal_Bool SAL_CALL FSStorage::isStreamElement( const OUString& aElementName )
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
INetURLObject aURL( m_aURL );
aURL.Append( aElementName );
@@ -551,7 +563,7 @@ sal_Bool SAL_CALL FSStorage::isStreamElement( const
OUString& aElementName )
sal_Bool SAL_CALL FSStorage::isStorageElement( const OUString& aElementName )
{
-::osl::MutexGuard aGuard(
[Libreoffice-commits] core.git: 2 commits - sw/source unotools/source
sw/source/core/access/accmap.cxx | 38 -
unotools/source/ucbhelper/ucblockbytes.cxx | 16 +++-
unotools/source/ucbhelper/ucblockbytes.hxx | 15 +++
3 files changed, 41 insertions(+), 28 deletions(-)
New commits:
commit 17827ea4974fce0a52d9986679223c670d9889ae
Author: Noel Grandin
AuthorDate: Wed Feb 15 15:38:39 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Feb 16 07:23:48 2023 +
osl::Mutex->std::mutex in UcbLockBytes
Change-Id: Ia84af116b705299ff4b9070f145e149c1a8a2c47
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147101
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/unotools/source/ucbhelper/ucblockbytes.cxx
b/unotools/source/ucbhelper/ucblockbytes.cxx
index 83ef4f75ad0a..ad5289f9310f 100644
--- a/unotools/source/ucbhelper/ucblockbytes.cxx
+++ b/unotools/source/ucbhelper/ucblockbytes.cxx
@@ -978,35 +978,39 @@ UcbLockBytes::~UcbLockBytes()
Reference < XInputStream > UcbLockBytes::getInputStream()
{
-osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
m_bDontClose = true;
return m_xInputStream;
}
void UcbLockBytes::setStream( const Reference& aStream )
{
-osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
if ( aStream.is() )
{
m_xOutputStream = aStream->getOutputStream();
-setInputStream( aStream->getInputStream(), false );
+setInputStreamImpl( aGuard, aStream->getInputStream(), false );
m_xSeekable.set( aStream, UNO_QUERY );
}
else
{
m_xOutputStream.clear();
-setInputStream( Reference < XInputStream >() );
+setInputStreamImpl( aGuard, Reference < XInputStream >() );
}
}
bool UcbLockBytes::setInputStream( const Reference
, bool bSetXSeekable )
+{
+std::unique_lock aGuard( m_aMutex );
+return setInputStreamImpl(aGuard, rxInputStream, bSetXSeekable);
+}
+
+bool UcbLockBytes::setInputStreamImpl( std::unique_lock&
/*rGuard*/, const Reference , bool bSetXSeekable )
{
bool bRet = false;
try
{
-osl::MutexGuard aGuard( m_aMutex );
-
if ( !m_bDontClose && m_xInputStream.is() )
m_xInputStream->closeInput();
diff --git a/unotools/source/ucbhelper/ucblockbytes.hxx
b/unotools/source/ucbhelper/ucblockbytes.hxx
index 67a2d6216316..d866015b250f 100644
--- a/unotools/source/ucbhelper/ucblockbytes.hxx
+++ b/unotools/source/ucbhelper/ucblockbytes.hxx
@@ -21,9 +21,9 @@
#include
#include
-#include
#include
#include
+#include
namespace com
{
@@ -63,7 +63,7 @@ class UcbLockBytes : public SvLockBytes
{
osl::Condition m_aInitialized;
osl::Condition m_aTerminated;
-osl::Mutex m_aMutex;
+std::mutex m_aMutex;
css::uno::Reference < css::io::XInputStream > m_xInputStream;
css::uno::Reference < css::io::XOutputStream > m_xOutputStream;
@@ -112,19 +112,19 @@ public:
css::uno::Reference < css::io::XInputStream > getInputStream() const
{
-osl::MutexGuard aGuard( const_cast<
UcbLockBytes* >(this)->m_aMutex );
+std::unique_lock aGuard( const_cast<
UcbLockBytes* >(this)->m_aMutex );
return m_xInputStream;
}
css::uno::Reference < css::io::XOutputStream > getOutputStream() const
{
-osl::MutexGuard aGuard( const_cast<
UcbLockBytes* >(this)->m_aMutex );
+std::unique_lock aGuard( const_cast<
UcbLockBytes* >(this)->m_aMutex );
return m_xOutputStream;
}
css::uno::Reference < css::io::XSeekable > getSeekable() const
{
-osl::MutexGuard aGuard( const_cast<
UcbLockBytes* >(this)->m_aMutex );
+std::unique_lock aGuard( const_cast<
UcbLockBytes* >(this)->m_aMutex );
return m_xSeekable;
}
@@ -132,6 +132,11 @@ public:
{ m_bDontClose = true; }
voidSetStreamValid();
+
+private:
+boolsetInputStreamImpl( std::unique_lock&
rGuard,
+ const css::uno::Reference <
css::io::XInputStream > ,
+ bool bSetXSeekable = true );
};
}
commit e8bb6e555cb4579ece3a9627d19a0a324620568a
Author: Noel Grandin
AuthorDate: Wed Feb 15 19:08:40 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Feb 16 07:23:38 2023 +
osl::Mutex->std::mutex in SwDrawModellListener_Impl
Change-Id: I150ac67a3f053046a6d6a7cd79323fa4595078c3
Reviewed-on:
[Libreoffice-commits] core.git: sw/inc sw/source
sw/inc/strings.hrc |1 +
sw/inc/swundo.hxx |1 +
sw/source/core/undo/undobj.cxx |3 +++
sw/source/uibase/shells/textfld.cxx |4 ++--
4 files changed, 7 insertions(+), 2 deletions(-)
New commits:
commit 5543faac1b4a92455c9c8e9f081688411f4a0cc5
Author: Miklos Vajna
AuthorDate: Wed Feb 15 20:13:35 2023 +0100
Commit: Miklos Vajna
CommitDate: Thu Feb 16 07:17:08 2023 +
sw: fix undo comment of FN_UPDATE_TEXT_FORMFIELDS
It's updates, not an insert. One has to dispatch .uno:TextFormFields to
see this in action.
Change-Id: I3049fa34110731e15082a0163de4b08e83c76098
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147109
Tested-by: Jenkins
Reviewed-by: Miklos Vajna
diff --git a/sw/inc/strings.hrc b/sw/inc/strings.hrc
index af916bf78422..6c2119fb78dc 100644
--- a/sw/inc/strings.hrc
+++ b/sw/inc/strings.hrc
@@ -589,6 +589,7 @@
#define STR_UNDO_TABLE_DELETE NC_("STR_UNDO_TABLE_DELETE",
"Delete table")
#define STR_UNDO_INSERT_FORM_FIELD
NC_("STR_UNDO_INSERT_FORM_FIELD", "Insert form field")
#define STR_UNDO_UPDATE_FORM_FIELD
NC_("STR_UNDO_UPDATE_FORM_FIELD", "Update form field")
+#define STR_UNDO_UPDATE_FORM_FIELDS
NC_("STR_UNDO_UPDATE_FORM_FIELDS", "Update form fields")
#define STR_UNDO_INSERT_PAGE_NUMBER
NC_("STR_UNDO_INSERT_PAGE_NUMBER", "Insert page number")
#define STR_DROP_DOWN_FIELD_ITEM_LIMIT
NC_("STR_DROP_DOWN_FIELD_ITEM_LIMIT", "You can specify maximum of 25 items for
a drop-down form field.")
diff --git a/sw/inc/swundo.hxx b/sw/inc/swundo.hxx
index 6b067dbec700..a387757bfd6b 100644
--- a/sw/inc/swundo.hxx
+++ b/sw/inc/swundo.hxx
@@ -168,6 +168,7 @@ enum class SwUndoId
OUTLINE_EDIT, // 136
INSERT_PAGE_NUMBER,// 137
UPDATE_FORM_FIELD, // 138
+UPDATE_FORM_FIELDS,// 139
};
OUString GetUndoComment(SwUndoId eId);
diff --git a/sw/source/core/undo/undobj.cxx b/sw/source/core/undo/undobj.cxx
index 0f12d8ef96d0..8a23ae1f03ff 100644
--- a/sw/source/core/undo/undobj.cxx
+++ b/sw/source/core/undo/undobj.cxx
@@ -649,6 +649,9 @@ OUString GetUndoComment(SwUndoId eId)
case SwUndoId::UPDATE_FORM_FIELD:
pId = STR_UNDO_UPDATE_FORM_FIELD;
break;
+case SwUndoId::UPDATE_FORM_FIELDS:
+pId = STR_UNDO_UPDATE_FORM_FIELDS;
+break;
}
assert(pId);
diff --git a/sw/source/uibase/shells/textfld.cxx
b/sw/source/uibase/shells/textfld.cxx
index b60df6477bf5..02f6b8d29a63 100644
--- a/sw/source/uibase/shells/textfld.cxx
+++ b/sw/source/uibase/shells/textfld.cxx
@@ -917,7 +917,7 @@ FIELD_INSERT:
pFields->GetValue() >>= aFields;
}
-
rSh.GetDoc()->GetIDocumentUndoRedo().StartUndo(SwUndoId::INSERT_FORM_FIELD,
nullptr);
+
rSh.GetDoc()->GetIDocumentUndoRedo().StartUndo(SwUndoId::UPDATE_FORM_FIELDS,
nullptr);
rSh.StartAction();
IDocumentMarkAccess* pMarkAccess =
rSh.GetDoc()->getIDocumentMarkAccess();
@@ -964,7 +964,7 @@ FIELD_INSERT:
}
rSh.EndAction();
-
rSh.GetDoc()->GetIDocumentUndoRedo().EndUndo(SwUndoId::INSERT_FORM_FIELD,
nullptr);
+
rSh.GetDoc()->GetIDocumentUndoRedo().EndUndo(SwUndoId::UPDATE_FORM_FIELDS,
nullptr);
}
break;
case FN_DELETE_TEXT_FORMFIELDS:
Re: ESC meeting agenda: 2023-02-16 16:00 CET
Hi! On 15.02.2023 19:01, Miklos Vajna wrote: * Highest-Priority bugs (aka "MABs"): + http://bit.ly/2lJAAJI 6.0 : 2/54 - 3 % (+0) 5.4 : 0/41 - 0 % (+0) 5.3 : 0/54 - 0 % (+0) 5.2 : 0/43 - 0 % (+0) 5.1 : 0/35 - 0 % (+0) 5.0 : 0/64 - 0 % (+0) 4.4 : 0/76 - 0 % (+0) 4.3 : 0/73 - 0 % (+0) 4.2 : 2/134 - 1 % (+0) 4.1 : 2/85 - 2 % (+0) 4.0 : 1/82 - 1 % (+0) old : 1/246 - 0 % (+0) IMO, this section is long obsolete, and gives no value. Maybe it's time to retire this section? :) -- Best regards, Mike Kaganski
Re: [Libreoffice-qa] ESC meeting agenda: 2023-02-16 16:00 CET
Hi! On 15.02.2023 19:01, Miklos Vajna wrote: * Highest-Priority bugs (aka "MABs"): + http://bit.ly/2lJAAJI 6.0 : 2/54 - 3 % (+0) 5.4 : 0/41 - 0 % (+0) 5.3 : 0/54 - 0 % (+0) 5.2 : 0/43 - 0 % (+0) 5.1 : 0/35 - 0 % (+0) 5.0 : 0/64 - 0 % (+0) 4.4 : 0/76 - 0 % (+0) 4.3 : 0/73 - 0 % (+0) 4.2 : 2/134 - 1 % (+0) 4.1 : 2/85 - 2 % (+0) 4.0 : 1/82 - 1 % (+0) old : 1/246 - 0 % (+0) IMO, this section is long obsolete, and gives no value. Maybe it's time to retire this section? :) -- Best regards, Mike Kaganski
[Libreoffice-bugs] [Bug 153657] New: NVDA dose not read Fontwork style title
https://bugs.documentfoundation.org/show_bug.cgi?id=153657 Bug ID: 153657 Summary: NVDA dose not read Fontwork style title Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: afs...@libreoffice.org Hello. I use NVDA screen reader. Insert >> Fontwork >> Select Fontwork style: The screen reader should read the Fontwork style title, but it doesn't! Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: 50(Build:3) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fa-IR (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.5.0~rc3-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: ucb/source
ucb/source/ucp/ext/ucpext_datasupplier.cxx | 14 +++---
ucb/source/ucp/ext/ucpext_datasupplier.hxx |3 ++-
2 files changed, 9 insertions(+), 8 deletions(-)
New commits:
commit 46ceb1ccb792b1a9ee12b73c499c4763502ef1e3
Author: Noel Grandin
AuthorDate: Wed Feb 15 15:33:05 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Feb 16 07:10:32 2023 +
osl::Mutex->std::mutex in ucb::ucp::ext::DataSupplier
Change-Id: Id195c7cb676d4c7e0741adeb31f4b1a9854e8230
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147100
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/ucb/source/ucp/ext/ucpext_datasupplier.cxx
b/ucb/source/ucp/ext/ucpext_datasupplier.cxx
index b718ef076c34..9470cdeb4c1e 100644
--- a/ucb/source/ucp/ext/ucpext_datasupplier.cxx
+++ b/ucb/source/ucp/ext/ucpext_datasupplier.cxx
@@ -151,7 +151,7 @@ namespace ucb::ucp::ext
OUString DataSupplier::queryContentIdentifierString( sal_uInt32 i_nIndex )
{
-::osl::Guard< ::osl::Mutex > aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
if ( i_nIndex < m_aResults.size() )
{
@@ -167,7 +167,7 @@ namespace ucb::ucp::ext
Reference< XContentIdentifier > DataSupplier::queryContentIdentifier(
sal_uInt32 i_nIndex )
{
-::osl::Guard< ::osl::Mutex > aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
if ( i_nIndex < m_aResults.size() )
{
@@ -190,7 +190,7 @@ namespace ucb::ucp::ext
Reference< XContent > DataSupplier::queryContent( sal_uInt32 i_nIndex )
{
-::osl::Guard< ::osl::Mutex > aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
ENSURE_OR_RETURN( i_nIndex < m_aResults.size(), "illegal index!",
nullptr );
@@ -222,7 +222,7 @@ namespace ucb::ucp::ext
bool DataSupplier::getResult( sal_uInt32 i_nIndex )
{
-::osl::ClearableGuard< ::osl::Mutex > aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
// true if result already present.
return m_aResults.size() > i_nIndex;
@@ -231,7 +231,7 @@ namespace ucb::ucp::ext
sal_uInt32 DataSupplier::totalCount()
{
-::osl::ClearableGuard< ::osl::Mutex > aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
return m_aResults.size();
}
@@ -250,7 +250,7 @@ namespace ucb::ucp::ext
Reference< XRow > DataSupplier::queryPropertyValues( sal_uInt32 i_nIndex )
{
-::osl::MutexGuard aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
ENSURE_OR_RETURN( i_nIndex < m_aResults.size(),
"DataSupplier::queryPropertyValues: illegal index!", nullptr );
Reference< XRow > xRow = m_aResults[ i_nIndex ].xRow;
@@ -291,7 +291,7 @@ namespace ucb::ucp::ext
void DataSupplier::releasePropertyValues( sal_uInt32 i_nIndex )
{
-::osl::Guard< ::osl::Mutex > aGuard( m_aMutex );
+std::unique_lock aGuard( m_aMutex );
if ( i_nIndex < m_aResults.size() )
m_aResults[ i_nIndex ].xRow.clear();
diff --git a/ucb/source/ucp/ext/ucpext_datasupplier.hxx
b/ucb/source/ucp/ext/ucpext_datasupplier.hxx
index f0bea109e683..a7198fc9ba3b 100644
--- a/ucb/source/ucp/ext/ucpext_datasupplier.hxx
+++ b/ucb/source/ucp/ext/ucpext_datasupplier.hxx
@@ -24,6 +24,7 @@
#include
#include
+#include
#include
@@ -75,7 +76,7 @@ namespace ucb::ucp::ext
css::uno::Reference< css::sdbc::XRow > xRow;
};
typedef ::std::vector< ResultListEntry >ResultList;
-::osl::Mutexm_aMutex;
+std::mutex m_aMutex;
ResultList m_aResults;
::rtl::Reference< Content > m_xContent;
css::uno::Reference< css::uno::XComponentContext > m_xContext;
[Libreoffice-bugs] [Bug 136901] Calc: When you Drag tabs, it is dragging them in the opposite direction (Hebrew language)
https://bugs.documentfoundation.org/show_bug.cgi?id=136901 ady changed: What|Removed |Added Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
Re: [libreoffice-design] Minutes from the UX/design meeting 2023-Feb-15
Hi Eyal, the meeting agenda is always announced in advance. This time it was on Wednesday what I assume to be possible for you. You could have sent a notice to postpone a topic. Flagging tickets as to-be-discussed sounds easy but adds noise to the report and wouldn't solve your problem. For the two topics from yesterday I think one was unanimously resolved/NAB and the other considered to not benefit the modification. Please don't understand input from UX as a gatekeeper to the development, you are free to reopen tickets and seek for response from other people. Cheers, Heiko On 15.02.23 22:41, Eyal Rozenberg wrote: Heiko, you again scheduled bugs of mine for a discussion without taking a moment to check whether I can join the meeting. I asked you not to do that and I'm asking you again. This is unfair, especially after I've explicitly asked that you not do that. The treatment of these bugs is usually entirely different based on whether I attend the session or not. What seems to happen when I'm not there is that the case for the issue is not made seriously, and thus objections or claims which I would probably be able to convincingly rebut or disprove are stated and accepted with no retort or objection. Now, I won't deny that this is not something specific to bugs I file: A user who does not have design committee participant support from the get-go, and who does not attend a committee session, will often not have any participant serve as the advocate or champion for that bug / that user - and may not get a "fair shake" in the evaluation of their bug. The difference in my case that you know that I can occasionally - but not always nor most times - attend. And session agendae are announced just a single day in advance, and not on the relevant bug pages - so, not enough time for me to notice. Finally, it is usually the case that multiple bugs I have filed are placed on the agenda for the same session, i.e. there are "Eyal's filings sessions", which are scheduled without me being able to react. This is quite inappropriate and I again ask that you stop doing that. Either ping me before scheduling my filings, or make the announcement a good number of days in advance. Also, and for the benefit of other bug filers, it would not be a bad idea to post a comment on the pages of bugs which are about to come up in committee, about the upcoming committee session. Eyal On 15/02/2023 22:21, Heiko Tietze wrote: Present: John, Cor, Heiko Comments: Stuart, John, Pedro, Rafael Tickets/Topics * Styles Preview should be able to show a grid of list styles (Tabbed UI) + https://bugs.documentfoundation.org/show_bug.cgi?id=153525 + a "More..." button could open the Stylist in the sidebar (Stuart, Heiko) + could be a small expander button on the lower right edge (Cor) + strong support for a Tabbed NB in general and completely implemented features in particular (John, Pedro, Rafael) + take the full space is easy to achieve, expanding into a list might a bit more difficult => do it * Most bundled page styles are nonsensical and/or redundant + https://bugs.documentfoundation.org/show_bug.cgi?id=153534 + every single page style has a use case (Cor) + never had any problems with the list of page styles (John) + the (small) list can also be filtered (Heiko) => resolve WF/NAB * Style organizer's "Next style"'s function not clear to user + https://bugs.documentfoundation.org/show_bug.cgi?id=153600 + label and help is clear (John) + labeling it "Next paragraph style" adds no information and it's reasonably clear what the dialog/label is talking about (Cor) => resolve WF/NAB * Editing:- Feature Request "go to - special" feature needed + https://bugs.documentfoundation.org/show_bug.cgi?id=149933 + introduce function to search for special content like blanks, constants etc. sounds like a good idea (Cor) + would be a comfortable shortcut for many searches (Heiko) + alternatively we could have a special entry in the sidebar + would be inconsistent as blank evaluates data while the existing Navigator options detect model content (Cor) => do it * Change "heading level" to "outline level" + https://bugs.documentfoundation.org/show_bug.cgi?id=152605 + see comment 14 for (tentatively accepted) proposal + https://bugs.documentfoundation.org/show_bug.cgi?id=153499 + use index level for index entry outlines + https://bugs.documentfoundation.org/show_bug.cgi?id=153596 + see also ToC dialog => consistency in naming is good, go for it * Permit "No User Input" as a data validation which would then permit filter sorting + https://bugs.documentfoundation.org/show_bug.cgi?id=149497 + reasonable request + (Standard/Auto-) Filter work on protected sheets + Sorting should work too, at least optional (Cor) +
Re: [Libreoffice-qa] [libreoffice-design] Minutes from the UX/design meeting 2023-Feb-15
Hi Eyal, the meeting agenda is always announced in advance. This time it was on Wednesday what I assume to be possible for you. You could have sent a notice to postpone a topic. Flagging tickets as to-be-discussed sounds easy but adds noise to the report and wouldn't solve your problem. For the two topics from yesterday I think one was unanimously resolved/NAB and the other considered to not benefit the modification. Please don't understand input from UX as a gatekeeper to the development, you are free to reopen tickets and seek for response from other people. Cheers, Heiko On 15.02.23 22:41, Eyal Rozenberg wrote: Heiko, you again scheduled bugs of mine for a discussion without taking a moment to check whether I can join the meeting. I asked you not to do that and I'm asking you again. This is unfair, especially after I've explicitly asked that you not do that. The treatment of these bugs is usually entirely different based on whether I attend the session or not. What seems to happen when I'm not there is that the case for the issue is not made seriously, and thus objections or claims which I would probably be able to convincingly rebut or disprove are stated and accepted with no retort or objection. Now, I won't deny that this is not something specific to bugs I file: A user who does not have design committee participant support from the get-go, and who does not attend a committee session, will often not have any participant serve as the advocate or champion for that bug / that user - and may not get a "fair shake" in the evaluation of their bug. The difference in my case that you know that I can occasionally - but not always nor most times - attend. And session agendae are announced just a single day in advance, and not on the relevant bug pages - so, not enough time for me to notice. Finally, it is usually the case that multiple bugs I have filed are placed on the agenda for the same session, i.e. there are "Eyal's filings sessions", which are scheduled without me being able to react. This is quite inappropriate and I again ask that you stop doing that. Either ping me before scheduling my filings, or make the announcement a good number of days in advance. Also, and for the benefit of other bug filers, it would not be a bad idea to post a comment on the pages of bugs which are about to come up in committee, about the upcoming committee session. Eyal On 15/02/2023 22:21, Heiko Tietze wrote: Present: John, Cor, Heiko Comments: Stuart, John, Pedro, Rafael Tickets/Topics * Styles Preview should be able to show a grid of list styles (Tabbed UI) + https://bugs.documentfoundation.org/show_bug.cgi?id=153525 + a "More..." button could open the Stylist in the sidebar (Stuart, Heiko) + could be a small expander button on the lower right edge (Cor) + strong support for a Tabbed NB in general and completely implemented features in particular (John, Pedro, Rafael) + take the full space is easy to achieve, expanding into a list might a bit more difficult => do it * Most bundled page styles are nonsensical and/or redundant + https://bugs.documentfoundation.org/show_bug.cgi?id=153534 + every single page style has a use case (Cor) + never had any problems with the list of page styles (John) + the (small) list can also be filtered (Heiko) => resolve WF/NAB * Style organizer's "Next style"'s function not clear to user + https://bugs.documentfoundation.org/show_bug.cgi?id=153600 + label and help is clear (John) + labeling it "Next paragraph style" adds no information and it's reasonably clear what the dialog/label is talking about (Cor) => resolve WF/NAB * Editing:- Feature Request "go to - special" feature needed + https://bugs.documentfoundation.org/show_bug.cgi?id=149933 + introduce function to search for special content like blanks, constants etc. sounds like a good idea (Cor) + would be a comfortable shortcut for many searches (Heiko) + alternatively we could have a special entry in the sidebar + would be inconsistent as blank evaluates data while the existing Navigator options detect model content (Cor) => do it * Change "heading level" to "outline level" + https://bugs.documentfoundation.org/show_bug.cgi?id=152605 + see comment 14 for (tentatively accepted) proposal + https://bugs.documentfoundation.org/show_bug.cgi?id=153499 + use index level for index entry outlines + https://bugs.documentfoundation.org/show_bug.cgi?id=153596 + see also ToC dialog => consistency in naming is good, go for it * Permit "No User Input" as a data validation which would then permit filter sorting + https://bugs.documentfoundation.org/show_bug.cgi?id=149497 + reasonable request + (Standard/Auto-) Filter work on protected sheets + Sorting should work too, at least optional (Cor) +
[Libreoffice-commits] core.git: sw/source
sw/source/core/unocore/unoidx.cxx | 36 +---
1 file changed, 17 insertions(+), 19 deletions(-)
New commits:
commit ae5fda223143bb7a2cddf90d741e7376046da0b6
Author: Noel Grandin
AuthorDate: Wed Feb 15 14:53:29 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Feb 16 07:02:54 2023 +
osl::Mutex->std::mutex in SwXDocumentIndex::Impl
Change-Id: Iaaa57af9bb298f4495b4a51d3553c55a63c5b069
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147099
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/unocore/unoidx.cxx
b/sw/source/core/unocore/unoidx.cxx
index 5e98a98a45cc..bb620b31a4c1 100644
--- a/sw/source/core/unocore/unoidx.cxx
+++ b/sw/source/core/unocore/unoidx.cxx
@@ -30,9 +30,7 @@
#include
#include
-#include
#include
-#include
#include
#include
#include
@@ -291,12 +289,13 @@ lcl_TypeToPropertyMap_Index(const TOXTypes eType)
class SwXDocumentIndex::Impl final: public SvtListener
{
private:
-::osl::Mutex m_Mutex; // just for OInterfaceContainerHelper2
SwSectionFormat* m_pFormat;
public:
unotools::WeakReference m_wThis;
-::comphelper::OMultiTypeInterfaceContainerHelper2 m_Listeners;
+std::mutex m_Mutex; // just for OInterfaceContainerHelper4
+::comphelper::OInterfaceContainerHelper4
m_RefreshListeners;
+::comphelper::OInterfaceContainerHelper4
m_EventListeners;
SfxItemPropertySet const& m_rPropSet;
const TOXTypes m_eTOXType;
bool m_bIsDescriptor;
@@ -307,7 +306,6 @@ public:
Impl(SwDoc& rDoc, const TOXTypes eType, SwTOXBaseSection *const
pBaseSection)
: m_pFormat(pBaseSection ? pBaseSection->GetFormat() : nullptr)
-, m_Listeners(m_Mutex)
,
m_rPropSet(*aSwMapProvider.GetPropertySet(lcl_TypeToPropertyMap_Index(eType)))
, m_eTOXType(eType)
, m_bIsDescriptor(nullptr == pBaseSection)
@@ -376,8 +374,10 @@ void SwXDocumentIndex::Impl::Notify(const SfxHint& rHint)
{ // fdo#72695: if UNO object is already dead, don't revive it with
event
return;
}
+std::unique_lock g(m_Mutex);
lang::EventObject const
ev(static_cast(xThis.get()));
-m_Listeners.disposeAndClear(ev);
+m_RefreshListeners.disposeAndClear(g, ev);
+m_EventListeners.disposeAndClear(g, ev);
}
}
@@ -1282,13 +1282,11 @@ void SAL_CALL SwXDocumentIndex::refresh()
pTOXBase->UpdatePageNum();
}
-::comphelper::OInterfaceContainerHelper2 *const pContainer(
-m_pImpl->m_Listeners.getContainer(
-cppu::UnoType::get()));
-if (pContainer)
+std::unique_lock g(m_pImpl->m_Mutex);
+if (m_pImpl->m_RefreshListeners.getLength(g))
{
lang::EventObject const event(static_cast<
::cppu::OWeakObject*>(this));
-pContainer->notifyEach(& util::XRefreshListener::refreshed, event);
+m_pImpl->m_RefreshListeners.notifyEach(g, &
util::XRefreshListener::refreshed, event);
}
}
@@ -1296,16 +1294,16 @@ void SAL_CALL SwXDocumentIndex::addRefreshListener(
const uno::Reference& xListener)
{
// no need to lock here as m_pImpl is const and container threadsafe
-m_pImpl->m_Listeners.addInterface(
-cppu::UnoType::get(), xListener);
+std::unique_lock g(m_pImpl->m_Mutex);
+m_pImpl->m_RefreshListeners.addInterface(g, xListener);
}
void SAL_CALL SwXDocumentIndex::removeRefreshListener(
const uno::Reference& xListener)
{
// no need to lock here as m_pImpl is const and container threadsafe
-m_pImpl->m_Listeners.removeInterface(
-cppu::UnoType::get(), xListener);
+std::unique_lock g(m_pImpl->m_Mutex);
+m_pImpl->m_RefreshListeners.removeInterface(g, xListener);
}
void SAL_CALL
@@ -1407,8 +1405,8 @@ SwXDocumentIndex::addEventListener(
const uno::Reference< lang::XEventListener > & xListener)
{
// no need to lock here as m_pImpl is const and container threadsafe
-m_pImpl->m_Listeners.addInterface(
-cppu::UnoType::get(), xListener);
+std::unique_lock g(m_pImpl->m_Mutex);
+m_pImpl->m_EventListeners.addInterface(g, xListener);
}
void SAL_CALL
@@ -1416,8 +1414,8 @@ SwXDocumentIndex::removeEventListener(
const uno::Reference< lang::XEventListener > & xListener)
{
// no need to lock here as m_pImpl is const and container threadsafe
-m_pImpl->m_Listeners.removeInterface(
-cppu::UnoType::get(), xListener);
+std::unique_lock g(m_pImpl->m_Mutex);
+m_pImpl->m_EventListeners.removeInterface(g, xListener);
}
OUString SAL_CALL SwXDocumentIndex::getName()
[Libreoffice-bugs] [Bug 153656] Font preview uses black font color in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153656 Faisal changed: What|Removed |Added OS|All |Windows (All) Blocks||150915 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150915 [Bug 150915] [META] Windows Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150915] [META] Windows Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=150915 Faisal changed: What|Removed |Added Depends on||153656 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153656 [Bug 153656] Font preview uses black font color in dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153656] New: Font preview uses black font color in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153656 Bug ID: 153656 Summary: Font preview uses black font color in dark mode Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: leem...@protonmail.com Description: Font preview in the paragraph style dialog uses black as font color, which is not visible when dark mode is enabled. Steps to Reproduce: 1. Modify a paragraph style to open the paragraph style dialog 2. Navigate to the "Font" tab Actual Results: Font preview box has text printed in black color Expected Results: Text in the font preview box should use the dark mode default text color, which is white Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100486] "Shift+Enter" shortcut not working after Tab
https://bugs.documentfoundation.org/show_bug.cgi?id=100486 --- Comment #6 from ady --- Still repro in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9788a565b3241d1bd62394b9e29c322361d05f80 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded As Luke said in comment 2, it happens with: A. [TAB], [SHIFT]+[ENTER] and/or with: B. [SHIFT]+[TAB], [SHIFT]+[ENTER] -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153652] Input Line in Calc Version 7.4.5.1 on Windows 11 does not show numbers properly unless box is expanded
https://bugs.documentfoundation.org/show_bug.cgi?id=153652 ady changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from ady --- Does any of the following look the same as yours? bug 150664 bug 153492 bug 151682 If you can, try a dev daily build for a test (not for usual work). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: chart2/inc chart2/source
chart2/inc/ChartView.hxx |3 ++-
chart2/source/view/main/ChartView.cxx |4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)
New commits:
commit 3ca80266b730d7557dc41568b62cc29f932706b4
Author: Noel Grandin
AuthorDate: Wed Feb 15 14:14:38 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Feb 16 06:27:59 2023 +
osl::Mutex->std::mutex in ChartView
Change-Id: Iebb2d1352b76108e803605dc856407ce2484e5a3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147098
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/chart2/inc/ChartView.hxx b/chart2/inc/ChartView.hxx
index d0f64d047b05..b521f2e8715b 100644
--- a/chart2/inc/ChartView.hxx
+++ b/chart2/inc/ChartView.hxx
@@ -40,6 +40,7 @@
#include
#include
+#include
#include
@@ -247,7 +248,7 @@ private: //member
css::awt::Rectangle m_aResultingDiagramRectangleExcludingAxes;
TimeBasedInfo maTimeBased;
-osl::Mutex maTimeMutex;
+std::mutex maTimeMutex;
};
}
diff --git a/chart2/source/view/main/ChartView.cxx
b/chart2/source/view/main/ChartView.cxx
index da37dd659f9e..2f87382bde56 100644
--- a/chart2/source/view/main/ChartView.cxx
+++ b/chart2/source/view/main/ChartView.cxx
@@ -1357,7 +1357,7 @@ void ChartView::createShapes()
{
SolarMutexGuard aSolarGuard;
-osl::MutexGuard aTimedGuard(maTimeMutex);
+std::unique_lock aTimedGuard(maTimeMutex);
if(mrChartModel.isTimeBased())
{
maTimeBased.bTimeBased = true;
@@ -1844,7 +1844,7 @@ void ChartView::dumpAsXml(xmlTextWriterPtr pWriter) const
void ChartView::setViewDirty()
{
-osl::MutexGuard aGuard(maTimeMutex);
+std::unique_lock aGuard(maTimeMutex);
m_bViewDirty = true;
}
[Libreoffice-commits] core.git: vcl/inc vcl/unx
vcl/inc/unx/gtk/gtkdata.hxx |2 +-
vcl/unx/gtk3/gtkdata.cxx|6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
New commits:
commit acf37c3a0b54a46de29bafd27ec9b0618bd2d84a
Author: Noel Grandin
AuthorDate: Wed Feb 15 15:59:57 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Feb 16 06:26:22 2023 +
osl::Mutex->std::mutex in GtkSalData
Change-Id: I86fdee3310715256a76f2b6560d27d3302402ab9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147102
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/vcl/inc/unx/gtk/gtkdata.hxx b/vcl/inc/unx/gtk/gtkdata.hxx
index 3a1a9094d3ec..39cb7907ae7f 100644
--- a/vcl/inc/unx/gtk/gtkdata.hxx
+++ b/vcl/inc/unx/gtk/gtkdata.hxx
@@ -278,7 +278,7 @@ public:
class GtkSalData final : public GenericUnixSalData
{
GSource*m_pUserEvent;
-osl::Mutex m_aDispatchMutex;
+std::mutex m_aDispatchMutex;
osl::Condition m_aDispatchCondition;
std::exception_ptr m_aException;
diff --git a/vcl/unx/gtk3/gtkdata.cxx b/vcl/unx/gtk3/gtkdata.cxx
index cc8535ff2ad2..1fb5c1edfe1f 100644
--- a/vcl/unx/gtk3/gtkdata.cxx
+++ b/vcl/unx/gtk3/gtkdata.cxx
@@ -358,7 +358,7 @@ GtkSalData::~GtkSalData()
// up anyway before the condition they're waiting on gets destroyed.
m_aDispatchCondition.set();
-osl::MutexGuard g( m_aDispatchMutex );
+std::unique_lock g( m_aDispatchMutex );
if (m_pUserEvent)
{
g_source_destroy (m_pUserEvent);
@@ -389,7 +389,7 @@ bool GtkSalData::Yield( bool bWait, bool
bHandleAllCurrentEvents )
{
// release YieldMutex (and re-acquire at block end)
SolarMutexReleaser aReleaser;
-if( m_aDispatchMutex.tryToAcquire() )
+if( m_aDispatchMutex.try_lock() )
bDispatchThread = true;
else if( ! bWait )
{
@@ -423,7 +423,7 @@ bool GtkSalData::Yield( bool bWait, bool
bHandleAllCurrentEvents )
if( bDispatchThread )
{
-m_aDispatchMutex.release();
+m_aDispatchMutex.unlock();
if( bWasEvent )
m_aDispatchCondition.set(); // trigger non dispatch thread yields
}
[Libreoffice-bugs] [Bug 153644] Calc: Undo doesn't remove cell's borders
https://bugs.documentfoundation.org/show_bug.cgi?id=153644 --- Comment #3 from ady --- (In reply to Timur from comment #1) > As for existing sheet with content, I could reproduce sometimes but not > always, maybe depending on the content or if clicked outside the table > before Undo. > That should be also tested. I have the same exact behavior. It is not exactly in each and every situation, but I wasn't able to determine in which case(s) it doesn't happen. What I _can_ say is that when I undo, the relevant cell(s) look as if they were "selected", while the focus is still elsewhere (but this is probably not a surprise): 1. Click once on one cell. 2. Apply one outer border combination (it doesn't have to be all the 4 sides). 3. Click on some other cell. 4. [CTRL]+[Z] 5. Note that the border is still on, the cell looks as if it was "selected", while the focus is on the second cell (as demonstrated by the cell address shown on the top-left box between column A and row 1). > > There's another Undo problem, but not from the referenced commit as it was > reproducible also before (to be tested separately): > Open a new calc sheet > Mark some cells > Apply borders to the cells: Criss-Cross Border > Undo to remove the borders > Wrong behavior: Borders are half removed (slashed) In the case of diagonal lines, it varies depending on how many cells I select to apply the border attribute. For one cell only, I can apply both diagonal borders at _once_, and then undo _twice_ (yes, 2 actions are available), effectively going back to the status before applying both diagonal lines. But when the lines are applied simultaneously to several cells (also at once), the first undo works whereas the second doesn't – it is available, but it doesn't undo the "second" diagonal. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151769] Text disappearing from slide after saving presentation with animation
https://bugs.documentfoundation.org/show_bug.cgi?id=151769 zcrhonek changed: What|Removed |Added CC||zcrho...@gmail.com --- Comment #11 from zcrhonek --- No repro with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8431cbbed5b5665571cbb27d1330abd3dd0868f4 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: en-US Calc: threaded Can you test dev version? Thank you https://dev-builds.libreoffice.org/daily/master/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153057] Calc and Base can not filter time values
https://bugs.documentfoundation.org/show_bug.cgi?id=153057 zcrhonek changed: What|Removed |Added CC||balazs.varga...@gmail.com, ||zcrho...@gmail.com Keywords|bibisectRequest |bibisected, bisected --- Comment #6 from zcrhonek --- bisected to 5bee333e16cc9879991346f7d6ee49e0b9b11315 is the first bad commit commit 5bee333e16cc9879991346f7d6ee49e0b9b11315 Author: Norbert Thiebaud Date: Tue Jun 15 19:25:40 2021 -0700 source sha:1f755525189884e4b2824889a6b9dea8933402db https://gerrit.libreoffice.org/c/core/+/116115 CC to Balazs Varga -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115688] Add Checkbox option to disable animated overlay to Tools -> Options -> Accessibility panel
https://bugs.documentfoundation.org/show_bug.cgi?id=115688 --- Comment #12 from V Stuart Foote --- (In reply to QA Administrators from comment #10) still valid, no Tools -> Options -> Accessibility option for toggling off the "AnimationsEnabled" settings. Still requires use of Expert Configuration to toggle to boolean. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141450] Writer table row and column selection arrows are not centered
https://bugs.documentfoundation.org/show_bug.cgi?id=141450 zcrhonek changed: What|Removed |Added CC||zcrho...@gmail.com --- Comment #4 from zcrhonek --- (In reply to Stéphane Guillou (stragu) from comment #3) > > It's a regression as 6.2 didn't have the issue: > Stepháne, can you bisect it? I doesn't see the issue.. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151395] EPS is not rendered if Ghostscript not installed
https://bugs.documentfoundation.org/show_bug.cgi?id=151395 --- Comment #11 from zcrhonek --- message in command line: TIFFFetchDirectory: Sanity check on directory count failed, this is probably not a valid IFD offset. TIFFReadDirectory: Failed to read directory at offset 342152. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151395] EPS is not rendered if Ghostscript not installed
https://bugs.documentfoundation.org/show_bug.cgi?id=151395 zcrhonek changed: What|Removed |Added CC||caol...@redhat.com, ||zcrho...@gmail.com Keywords|bibisectRequest |bibisected, bisected --- Comment #10 from zcrhonek --- bisected to 468664d8d9ca2f290d691b927b31a0fbd0365bb6 is the first bad commit commit 468664d8d9ca2f290d691b927b31a0fbd0365bb6 Author: Norbert Thiebaud Date: Sat May 21 03:07:20 2022 -0700 source sha:22b50f1937de67e4ad9e692d6964aa5b8d33af7a https://gerrit.libreoffice.org/c/core/+/134647 CC to Caolán McNamara -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115688] Add Checkbox option to disable animated overlay to Tools -> Options -> Accessibility panel
https://bugs.documentfoundation.org/show_bug.cgi?id=115688 --- Comment #11 from crx...@hotmail.com --- Still valid and still waiting. Almost 12 years now, for a logical and user-friendly way to present an important accessibility option to the users. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153655] New: How to Be Attractive
https://bugs.documentfoundation.org/show_bug.cgi?id=153655 Bug ID: 153655 Summary: How to Be Attractive Product: cppunit Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: placeye...@gmail.com CC: markus.mohrh...@googlemail.com Are you ready to become a more vibrant, memorable, and attractive person? Are you ready to build your charisma and create strong relationships with others who generally enjoy your company? Stop thinking you are boring or unattractive and take proactive steps to improve your own self-confidence and gain a greater appreciation in the eyes of others. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153431] PostgreSQL native connector: Field Memo [Text] is filled with 0 instead of character content where postgres server version is greater than or equal to 13
https://bugs.documentfoundation.org/show_bug.cgi?id=153431 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153627] V7.5 error message, not opening on Win7, 32 bit
https://bugs.documentfoundation.org/show_bug.cgi?id=153627 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149506] Slow start-up and opening of files since 7.3 release
https://bugs.documentfoundation.org/show_bug.cgi?id=149506 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149506] Slow start-up and opening of files since 7.3 release
https://bugs.documentfoundation.org/show_bug.cgi?id=149506 --- Comment #16 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149836] in addition to "Load Styles fro Template", "Load Template" -- replace the underlying old one
https://bugs.documentfoundation.org/show_bug.cgi?id=149836 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149836] in addition to "Load Styles fro Template", "Load Template" -- replace the underlying old one
https://bugs.documentfoundation.org/show_bug.cgi?id=149836 --- Comment #3 from QA Administrators --- Dear peter josvai, 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 146958] Inconsistent page count in properties dialogue and status line
https://bugs.documentfoundation.org/show_bug.cgi?id=146958 --- Comment #6 from QA Administrators --- Dear Albrecht Müller, 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 146958] Inconsistent page count in properties dialogue and status line
https://bugs.documentfoundation.org/show_bug.cgi?id=146958 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 141615] Documents fail to render properly with LibreOffice 7 on big endian
https://bugs.documentfoundation.org/show_bug.cgi?id=141615 --- Comment #10 from QA Administrators --- Dear chmeeedalf+lo, 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 135446] Writer hangs Special Characters dialog context menu 'Copy to clipboard'
https://bugs.documentfoundation.org/show_bug.cgi?id=135446 --- Comment #15 from QA Administrators --- Dear Rachmiel Langer, 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 89557] UI: keyboard shortcut to move to end of document does not work if cursor within table of contents
https://bugs.documentfoundation.org/show_bug.cgi?id=89557 --- Comment #18 from QA Administrators --- Dear Frank Fuchs, 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 62909] FORMATTING: Context Pop-Up Window Location
https://bugs.documentfoundation.org/show_bug.cgi?id=62909 --- Comment #5 from QA Administrators --- Dear John, 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 58070] RTL [HE] EDITING Switching paragraph style changes character orientation
https://bugs.documentfoundation.org/show_bug.cgi?id=58070 --- Comment #11 from QA Administrators --- Dear Inkbug, 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 55838] EDITING: ctrl + end does not jump to end of document
https://bugs.documentfoundation.org/show_bug.cgi?id=55838 --- Comment #8 from QA Administrators --- Dear stfhell, 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 138876] User should be able to selectively decide which styles are imported from an updated template
https://bugs.documentfoundation.org/show_bug.cgi?id=138876 --- Comment #6 from QA Administrators --- Dear sdc.blanco, 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 46950] Hebrew: Spell-checking breaks Hebrew words at intra-word single and double quotes
https://bugs.documentfoundation.org/show_bug.cgi?id=46950 --- Comment #24 from QA Administrators --- Dear Nadav Har'El, 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 44418] FORMATTING: Headline spacing after page break
https://bugs.documentfoundation.org/show_bug.cgi?id=44418 --- Comment #20 from QA Administrators --- Dear André Rebentisch, 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 136899] Captioning editing on Calc is done from left to right instead of right to left on the Hebrew language
https://bugs.documentfoundation.org/show_bug.cgi?id=136899 --- Comment #10 from QA Administrators --- Dear ori, 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 136901] Calc: When you Drag tabs, it is dragging them in the opposite direction (Hebrew language)
https://bugs.documentfoundation.org/show_bug.cgi?id=136901 --- Comment #4 from QA Administrators --- Dear ori, 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 123491] FILEOPEN Word 2003 XML, shapes missing
https://bugs.documentfoundation.org/show_bug.cgi?id=123491 --- Comment #5 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 135706] Text behind image frame after saving DOCX (as character frame)
https://bugs.documentfoundation.org/show_bug.cgi?id=135706 --- 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 123407] Copy in Date-Cells from XLSX to ODS
https://bugs.documentfoundation.org/show_bug.cgi?id=123407 --- Comment #9 from QA Administrators --- Dear amersdorfer, 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 120403] Save As does not default to current directory if MS Office document without extension is open
https://bugs.documentfoundation.org/show_bug.cgi?id=120403 --- Comment #3 from QA Administrators --- Dear Kai Uwe Broulik, 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 115688] Add Checkbox option to disable animated overlay to Tools -> Options -> Accessibility panel
https://bugs.documentfoundation.org/show_bug.cgi?id=115688 --- Comment #10 from QA Administrators --- Dear V Stuart Foote, 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 115274] .desktop file magic number error
https://bugs.documentfoundation.org/show_bug.cgi?id=115274 --- Comment #4 from QA Administrators --- Dear Fudoka, 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 100486] "Shift+Enter" shortcut not working after Tab
https://bugs.documentfoundation.org/show_bug.cgi?id=100486 --- Comment #5 from QA Administrators --- Dear Luke, 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 153115] Deleted tracked information re-inserted after undo of text to table & Assertion failed: (!pLayout->HasMergedParas() || pNd->GetRedlineMergeFlag() != SwNode::Merge::Hidd
https://bugs.documentfoundation.org/show_bug.cgi?id=153115 csyu@gmail.com changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153115] Deleted tracked information re-inserted after undo of text to table & Assertion failed: (!pLayout->HasMergedParas() || pNd->GetRedlineMergeFlag() != SwNode::Merge::Hidd
https://bugs.documentfoundation.org/show_bug.cgi?id=153115 csyu@gmail.com changed: What|Removed |Added CC||csyu@gmail.com, ||michael.st...@allotropia.de --- Comment #3 from csyu@gmail.com --- I think the regression was introduced here but I want to note two things that happened while I was bibisecting: 1) the header separated from rest of the document, making it two pages instead of one 2) the red line surrounding the table disappeared https://git.libreoffice.org/core/+/471212d464f54054f7419ef1890267d0def852d9%5E%21 commit 471212d464f54054f7419ef1890267d0def852d9[log] author Michael Stahl Tue Sep 04 18:55:13 2018 committer Michael Stahl Wed Sep 19 10:18:30 2018 tree16b90833fc4f410f2d3a8fc6601cf492f0fcfda7 parent 12a841e1f102ff7f47a7281120fe777bf440d2fd [diff] Bibisected with: bibisect-win32-6.3 Adding Cc: to Michael Stahl -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153627] V7.5 error message, not opening on Win7, 32 bit
https://bugs.documentfoundation.org/show_bug.cgi?id=153627 --- Comment #4 from Steven --- Yes, that fixed itversion 7.5.1.1 now works (opens and loads). Thank you. Regards Steve. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153549] Rename Tools > "Chapter Numbering" to "Heading Numbering"
https://bugs.documentfoundation.org/show_bug.cgi?id=153549 sdc.bla...@youmail.dk changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153549] Rename Tools > "Chapter Numbering" to "Heading Numbering"
https://bugs.documentfoundation.org/show_bug.cgi?id=153549 sdc.bla...@youmail.dk changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139924] Tools > Autocorrect > Apply with "Replace bullets with" only works with Default Style in [M], while hyphen is not converted to chosen symbol in [T], and chosen bullet s
https://bugs.documentfoundation.org/show_bug.cgi?id=139924 --- Comment #7 from sdc.bla...@youmail.dk --- In short: no changes. Problems remain. repro comment 0 with 7.6.0.0.alpha0+ only Default PS works (with List 1 ps as noted in comment 1) Text Body and Text Body Indent do not. comment 3 repro (but see comment 5) using Default PS or Text Body, then the symbols (-, +, *) are converted to bullets, again with hyphen remaining as hyphen, and the other two symbols being converted to what was assigned. comment 4 - repro, with slight variation. After editing the bullet for [t], it appears in the right place, but after closing and opening the dialog, it then appears in [m]. (similarly if m is edited, then the bullet appears under [t]) In both cases, the actually-applied bullet corresponds to what is shown by the other. That is, the [t] bullet is applied with [m] and vice versa. comment 5 - repro. [t] only works if [m] is selected. [m] works without having [t] being selected. Tested with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d466df5bc220eb80b8a51ff64507de881b938ed3 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149506] Slow start-up and opening of files since 7.3 release
https://bugs.documentfoundation.org/show_bug.cgi?id=149506 --- Comment #15 from bunkem --- Hmm. I don't think I did this right. git bisect good 846a5c424a6c16dc07eefb6827b362efed5075b1 is the first bad commit commit 846a5c424a6c16dc07eefb6827b362efed5075b1 Author: libreoffice Date: Tue Dec 21 03:15:32 2021 +0100 source sha:ce69f71983a09416514f0569c6cdfbcde87d4b99 source sha:ce69f71983a09416514f0569c6cdfbcde87d4b99 LibreOffice.app/Contents/Frameworks/libswlo.dylib | Bin 19027692 -> 19027692 bytes LibreOffice.app/Contents/Resources/setuprc| 2 +- LibreOffice.app/Contents/Resources/versionrc | 2 +- 3 files changed, 2 insertions(+), 2 deletions(-) The last version seems to be OK. From the Get Info it is 7.3 beta. However I found the issue originally in 7.3.3.2. Can you confirm that the bibisect-mac64-7.3 is the right one to test? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41316] Page styles should support hierarchical parent-child relationships (like paragraph or character styles)
https://bugs.documentfoundation.org/show_bug.cgi?id=41316 jonathon changed: What|Removed |Added CC||toki.kant...@gmail.com --- Comment #39 from jonathon --- (In reply to Regina Henschel from comment #14) > Currently inheritance is not supported by the file format. The needed > attribute > style:parent-style-name is missing, because the > element is > not child of a element. Such > new feature will only be possible in > extended mode anytime soon. (In reply to Regina Henschel from comment #21) > (In reply to Dieter from comment #20) > > Regina, is it now possible with ODF 1.3? > > No, it is not possible in ODF 1.3. > > ODF 1.3 gives the possibility to use in > Writer and Calc too. That allows e.g. gradient fill (not implemented for > Calc yet). But an attribute for reference to a parent does still not exist. >From a file format perspective, are these two items the only stumbling blocks. ( Hand-waving aside implementation related issues.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153637] Rename "Use level from source chapter" to "Use outline level from document headings" in Type tab of Insert Table of Contents, Index, or Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153637 --- Comment #3 from sdc.bla...@youmail.dk --- (In reply to jonathon from comment #2) > "Headings" is structural, but one isn't necessarily indexing structure. The label in question in the OP can only index tables, graphics, frames, and OLE objects. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153637] Rename "Use level from source chapter" to "Use outline level from document headings" in Type tab of Insert Table of Contents, Index, or Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153637 --- Comment #3 from sdc.bla...@youmail.dk --- (In reply to jonathon from comment #2) > "Headings" is structural, but one isn't necessarily indexing structure. The label in question in the OP can only index tables, graphics, frames, and OLE objects. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153600] Style organizer's "Next style"'s function not clear to user
https://bugs.documentfoundation.org/show_bug.cgi?id=153600 --- Comment #2 from jonathon --- (In reply to Eyal Rozenberg from comment #0) > In the Style dialogs, under the Organizer page, one of the rows is a > drop-down list with the label "Next Style". > > The function of this (pair of) control(s) is not clear, especially to the > newbie user: This is a documentation/User Guide issue, *not* a UI issue. _Creating and Using Styles: Component_ (Write, Calc, Presentation, Drawing, Formula, Base, 7thComponent ) Each type (Paragraph, Character,Frame, Page, List, Table, Cell, Format, etc.) of style used by that component has one chapter that describes: * what each item within the style composition does; * what the acceptable parameters for that item are; * how the item affects the style overall; * how to utilize that item within the style; Note: The document describes the style type. EG _Page Style_. It does not go into the differences between the styles that are shipped with Libo. IOW, it does not explain why Endnote pages exist, or how to correctly use Footnote pages. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153600] Style organizer's "Next style"'s function not clear to user
https://bugs.documentfoundation.org/show_bug.cgi?id=153600 --- Comment #2 from jonathon --- (In reply to Eyal Rozenberg from comment #0) > In the Style dialogs, under the Organizer page, one of the rows is a > drop-down list with the label "Next Style". > > The function of this (pair of) control(s) is not clear, especially to the > newbie user: This is a documentation/User Guide issue, *not* a UI issue. _Creating and Using Styles: Component_ (Write, Calc, Presentation, Drawing, Formula, Base, 7thComponent ) Each type (Paragraph, Character,Frame, Page, List, Table, Cell, Format, etc.) of style used by that component has one chapter that describes: * what each item within the style composition does; * what the acceptable parameters for that item are; * how the item affects the style overall; * how to utilize that item within the style; Note: The document describes the style type. EG _Page Style_. It does not go into the differences between the styles that are shipped with Libo. IOW, it does not explain why Endnote pages exist, or how to correctly use Footnote pages. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153654] New: Problem with template shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=153654 Bug ID: 153654 Summary: Problem with template shortcut Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: teckn...@tecknode.digitalspacemail17.net I have a Writer Template in the Writer folder. In previous LO version this template was NOT set to save at a different directory, therefore if I created a shortcut in another folder a using the template would create a Writer Doc that would save in the SAME folder the short cut was launched from. On this LO version, using a template shortcut will save in the folder that the template was created in. Please fix so template shortcuts save created Writer Docs in the same folder the shortcut was used. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104524] [META] DOCX (OOXML) Table of Contents (ToC) and Index related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104524 Bug 104524 depends on bug 153090, which changed state. Bug 153090 Summary: FILEOPEN DOCX TOF incorrect when based on para style instead of category https://bugs.documentfoundation.org/show_bug.cgi?id=153090 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153308] Coloring styles used on Documents
https://bugs.documentfoundation.org/show_bug.cgi?id=153308 --- Comment #2 from jonathon --- (In reply to micet2004-linux from comment #0) > Description: > Add a mode to color used styles in Document. > > I propose a specific appearance which looks similar to the user colors in > multi edit environments. This appearance should be able to activate If you > are in the Sheet overview. If you activate it. The Style overview shows the > color legend. Can you please rephrase your request, and provide two or three use-cases. If you are asking for what I think you are asking for, it is implemented in LibO. However, based on the vocabulary used, I doubt that what I think you are asking for, is what you are requesting. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153308] Coloring styles used on Documents
https://bugs.documentfoundation.org/show_bug.cgi?id=153308 --- Comment #2 from jonathon --- (In reply to micet2004-linux from comment #0) > Description: > Add a mode to color used styles in Document. > > I propose a specific appearance which looks similar to the user colors in > multi edit environments. This appearance should be able to activate If you > are in the Sheet overview. If you activate it. The Style overview shows the > color legend. Can you please rephrase your request, and provide two or three use-cases. If you are asking for what I think you are asking for, it is implemented in LibO. However, based on the vocabulary used, I doubt that what I think you are asking for, is what you are requesting. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153637] Rename "Use level from source chapter" to "Use outline level from document headings" in Type tab of Insert Table of Contents, Index, or Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153637 --- Comment #2 from jonathon --- (In reply to sdc.blanco from comment #0) > 2. "headings" is better than "source", because they are the operative element "Headings" is structural, but one isn't necessarily indexing structure. By way of example, an Index of People and Places in a mega-novel. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153637] Rename "Use level from source chapter" to "Use outline level from document headings" in Type tab of Insert Table of Contents, Index, or Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153637 --- Comment #2 from jonathon --- (In reply to sdc.blanco from comment #0) > 2. "headings" is better than "source", because they are the operative element "Headings" is structural, but one isn't necessarily indexing structure. By way of example, an Index of People and Places in a mega-novel. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153653] Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name
https://bugs.documentfoundation.org/show_bug.cgi?id=153653 --- Comment #2 from sdc.bla...@youmail.dk --- Proposal for help page update: https://gerrit.libreoffice.org/c/help/+/147115 Proposal for tooltip addition (and some extended tip improvement): https://gerrit.libreoffice.org/c/core/+/147116 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153653] Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name
https://bugs.documentfoundation.org/show_bug.cgi?id=153653 --- Comment #2 from sdc.bla...@youmail.dk --- Proposal for help page update: https://gerrit.libreoffice.org/c/help/+/147115 Proposal for tooltip addition (and some extended tip improvement): https://gerrit.libreoffice.org/c/core/+/147116 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 149506] Slow start-up and opening of files since 7.3 release
https://bugs.documentfoundation.org/show_bug.cgi?id=149506 bunkem changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151452] : Tools/AutoCorrect/AutoCorrect Options window
https://bugs.documentfoundation.org/show_bug.cgi?id=151452 steph.h...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149506] Slow start-up and opening of files since 7.3 release
https://bugs.documentfoundation.org/show_bug.cgi?id=149506 --- Comment #14 from bunkem --- Hi. I'm going to try this bibisect. I'm learning as I go and will have questions. This afternoon, I downloaded 7.2.5 again and tested it on MacOS 12.6.3. It is so fast, it is unbelievable. So this change happened between 7.2.5 and 7.3. 7.5.0.2 is as slow as 7.3. So I hope this bibisect can determine what changed and then it can get fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122497 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153653 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153653 [Bug 153653] Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120200] [META] Update or correct help for features
https://bugs.documentfoundation.org/show_bug.cgi?id=120200 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153653 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153653 [Bug 153653] Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153653] Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name
https://bugs.documentfoundation.org/show_bug.cgi?id=153653 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||120200, 122497 Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from sdc.bla...@youmail.dk --- Will ask UXEval as part of this ticket for now. In the Styles tab (of TOC dialog), there is a "Default" button. Select a level, press "Default" Actual: The assigned style is deleted. Expected: Style is "reset" to default (factory) setting. Documentation explains that default paragraph style is used. (have not tested). Questions to UXEval. 1. Wouldn't it be better if Default actually reset to factory setting? 2. Alternatively, if the functionality is not changed, then: a. wouldn't it be better if "Default Paragraph Style" was displayed in the Levels window, rather than , and b. maybe a better label should be found for the button (e.g., Delete) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120200 [Bug 120200] [META] Update or correct help for features https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153653] Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name
https://bugs.documentfoundation.org/show_bug.cgi?id=153653 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||120200, 122497 Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from sdc.bla...@youmail.dk --- Will ask UXEval as part of this ticket for now. In the Styles tab (of TOC dialog), there is a "Default" button. Select a level, press "Default" Actual: The assigned style is deleted. Expected: Style is "reset" to default (factory) setting. Documentation explains that default paragraph style is used. (have not tested). Questions to UXEval. 1. Wouldn't it be better if Default actually reset to factory setting? 2. Alternatively, if the functionality is not changed, then: a. wouldn't it be better if "Default Paragraph Style" was displayed in the Levels window, rather than , and b. maybe a better label should be found for the button (e.g., Delete) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120200 [Bug 120200] [META] Update or correct help for features https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153653] New: Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name
https://bugs.documentfoundation.org/show_bug.cgi?id=153653 Bug ID: 153653 Summary: Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk CC: olivier.hal...@libreoffice.org Help page for Styles: https://help.libreoffice.org/7.6/en-US/text/swriter/01/04120201.html 1. The "icon" for the Assign button is not correct. 2. Formatting and grammatical problems should be corrected. 3. Some entries can be improved. Missing tooltip in Styles dialog. 1. Insert - Table of Contents and Index - Table of Contents, Index, or Bibliography 2. Select "Styles" tab. 3. Hover mouse over "<" icon in middle of dialog. Actual: Nothing Expected (or better): "Assign" should appear as "tooltip" The extended tip needs correction. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41316] Page styles should support hierarchical parent-child relationships (like paragraph or character styles)
https://bugs.documentfoundation.org/show_bug.cgi?id=41316 Eyal Rozenberg changed: What|Removed |Added Blocks||153534 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153534 [Bug 153534] Most bundled page styles are nonsensical and/or redundant -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153534] Most bundled page styles are nonsensical and/or redundant
https://bugs.documentfoundation.org/show_bug.cgi?id=153534 Eyal Rozenberg changed: What|Removed |Added Depends on||41316 --- Comment #8 from Eyal Rozenberg --- (In reply to jonathon from comment #7) > A right hand page is, by definition, an odd numbered page. 1. If what you said were true, a "Right Hand Page" would not be, and could not be, a page style - since continuing with a second (numbered) page of the same style would have it contradict the definition. 2. Who said the pages are numbered at all? Not LO Writer, in which a "Right Page" and a "Left Page" are not numbered by default. 3. Welcome to Earth, my friend. On our planet, many cultures / written language communities write from right to left and flip pages from left to right. The odd/even, left/right etc. conventions for such languages are typically flipped. > A left hand page is, by definition, an even numbered page. See above. > [Landscape] ... this is a quick and dirty way to switch from portrait to > landscape, reminding the writer that the page is in landscape. That would be true if the Landscape style inherited the Default Page Style. So once any change has been made to the default style (e.g. margins, text direction etc.) - selecting this style makes a bunch of changes which are not what the user expects. > In an ideal world, page styles would be inheritable. I hardly think fixing 41316 means achieving an ideal world... I just think the order of business is fixing 41316 first, adding this style later. Anyway, marking this bug dependent on 41316. > Index pages have ... Does Writer have "Index Pages"? When I insert an Index, it's inserted inline. Does LO ever create "Index Pages"? ... I don't think it does. > Index pages have a very specific page layout and markup criteria. On the contrary. Indices don't have to be placed on separate pages, and thus naturally have no "specific page layout and markup criteria". If that were the case, that should have been a feature of Indices, not some general page style you can apply anywhere. > The > blatantly obvious example being that lower case Roman numerals are used for > page numbers. See my "welcome to earth" comment above... in non-Latin alphabet languages, this is certainly not common, let alone necessary. That kind of convention belongs in a document template, I would say. > Less obvious is that they have either two or three columns. Not in LibreOffice they don't; at least, not by default. When you insert an index, it has one column. And, in fact, LO's "Index" page style only has one column. (Personally, I use 2 or 3 columns in my alphabetical indices.) > Endnote pages ... have also have very specific page layout and > markup criteria. Here I'm not sure; I was not aware there was a universal convention. But - ok, suppose that's true. In that case: 1. This style should be named "Endnotes" (or "Endnotes Page"), not "Endnote". 2. It should probably not be applicable to non-endnote pages. > The first printed page that follow End note pages... is a Right Hand Side page That can't be true, because if there is any such restriction, it must be reversed for RTL document layout. Moreover, some documents don't _have_ right-hand-side and left-hand-side pages. Example: A document to be printed on one side of each sheet of paper, and not bound on one side of the sheets. > Point size of text is smaller than on regular pages, being an equally > unobvious differentiator. This is actually a rather interesting point... does the Default Paragraph Style inherit anything from the Page Style? Perhaps it should. > I have seen a single footnote ramble on for almost 100 pages. Those would be 100 regular pages of text. If a footnote doesn't fit on the same page as where the footnote reference is located, then it continues to take up some part of later pages of text. But they would still be regular pages of text. Even if the footnote extends past the last page of text - it is a degenerate case of a regular page of text, with no lines of no-footnote text. And that's how it works in LibreOffice. > A trend that began in the early/mid-sixties in British & US publishing, was > to throw anything longer than a single line, from footnotes into end notes. > Hence, today (2023) the majority of time one comes across footnote pages, is > in reprints of material that was originally published more than fifty years > ago. Historical point taken - but that's not how footnotes work in LibreOffice. LO has no footnote pages and I don't know of a plan for this to change... > The page layout for Table of Contents, and for Indices is different. The > blatantly obvious difference being that Table of Contents is a single > column, whilst Index Pages are two or three columns. It may or may not be blatantly obvious - but it is not true in LO right now. Indices
[Libreoffice-ux-advise] [Bug 153534] Most bundled page styles are nonsensical and/or redundant
https://bugs.documentfoundation.org/show_bug.cgi?id=153534 Eyal Rozenberg changed: What|Removed |Added Depends on||41316 --- Comment #8 from Eyal Rozenberg --- (In reply to jonathon from comment #7) > A right hand page is, by definition, an odd numbered page. 1. If what you said were true, a "Right Hand Page" would not be, and could not be, a page style - since continuing with a second (numbered) page of the same style would have it contradict the definition. 2. Who said the pages are numbered at all? Not LO Writer, in which a "Right Page" and a "Left Page" are not numbered by default. 3. Welcome to Earth, my friend. On our planet, many cultures / written language communities write from right to left and flip pages from left to right. The odd/even, left/right etc. conventions for such languages are typically flipped. > A left hand page is, by definition, an even numbered page. See above. > [Landscape] ... this is a quick and dirty way to switch from portrait to > landscape, reminding the writer that the page is in landscape. That would be true if the Landscape style inherited the Default Page Style. So once any change has been made to the default style (e.g. margins, text direction etc.) - selecting this style makes a bunch of changes which are not what the user expects. > In an ideal world, page styles would be inheritable. I hardly think fixing 41316 means achieving an ideal world... I just think the order of business is fixing 41316 first, adding this style later. Anyway, marking this bug dependent on 41316. > Index pages have ... Does Writer have "Index Pages"? When I insert an Index, it's inserted inline. Does LO ever create "Index Pages"? ... I don't think it does. > Index pages have a very specific page layout and markup criteria. On the contrary. Indices don't have to be placed on separate pages, and thus naturally have no "specific page layout and markup criteria". If that were the case, that should have been a feature of Indices, not some general page style you can apply anywhere. > The > blatantly obvious example being that lower case Roman numerals are used for > page numbers. See my "welcome to earth" comment above... in non-Latin alphabet languages, this is certainly not common, let alone necessary. That kind of convention belongs in a document template, I would say. > Less obvious is that they have either two or three columns. Not in LibreOffice they don't; at least, not by default. When you insert an index, it has one column. And, in fact, LO's "Index" page style only has one column. (Personally, I use 2 or 3 columns in my alphabetical indices.) > Endnote pages ... have also have very specific page layout and > markup criteria. Here I'm not sure; I was not aware there was a universal convention. But - ok, suppose that's true. In that case: 1. This style should be named "Endnotes" (or "Endnotes Page"), not "Endnote". 2. It should probably not be applicable to non-endnote pages. > The first printed page that follow End note pages... is a Right Hand Side page That can't be true, because if there is any such restriction, it must be reversed for RTL document layout. Moreover, some documents don't _have_ right-hand-side and left-hand-side pages. Example: A document to be printed on one side of each sheet of paper, and not bound on one side of the sheets. > Point size of text is smaller than on regular pages, being an equally > unobvious differentiator. This is actually a rather interesting point... does the Default Paragraph Style inherit anything from the Page Style? Perhaps it should. > I have seen a single footnote ramble on for almost 100 pages. Those would be 100 regular pages of text. If a footnote doesn't fit on the same page as where the footnote reference is located, then it continues to take up some part of later pages of text. But they would still be regular pages of text. Even if the footnote extends past the last page of text - it is a degenerate case of a regular page of text, with no lines of no-footnote text. And that's how it works in LibreOffice. > A trend that began in the early/mid-sixties in British & US publishing, was > to throw anything longer than a single line, from footnotes into end notes. > Hence, today (2023) the majority of time one comes across footnote pages, is > in reprints of material that was originally published more than fifty years > ago. Historical point taken - but that's not how footnotes work in LibreOffice. LO has no footnote pages and I don't know of a plan for this to change... > The page layout for Table of Contents, and for Indices is different. The > blatantly obvious difference being that Table of Contents is a single > column, whilst Index Pages are two or three columns. It may or may not be blatantly obvious - but it is not true in LO right now. Indices
[Libreoffice-bugs] [Bug 33201] UI: Highlight (not select) current row and column in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=33201 --- Comment #62 from Rafael Lima --- (In reply to mtness from comment #61) > Is there anybody here who can point me in the right direction were to look > for the right place to do this in the sources? Se Comment #45 in this bug ticket. I would start here: https://opengrok.libreoffice.org/xref/core/sc/source/ui/inc/gridwin.hxx https://opengrok.libreoffice.org/xref/core/sc/source/ui/view/gridwin.cxx https://opengrok.libreoffice.org/xref/core/sc/source/ui/view/gridwin4.cxx To implement this, one will have to add a new sdr::overlay::OverlayObjectList to handle this new highlight overlay. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153652] New: Input Line in Calc Version 7.4.5.1 on Windows 11 does not show numbers properly unless box is expanded
https://bugs.documentfoundation.org/show_bug.cgi?id=153652 Bug ID: 153652 Summary: Input Line in Calc Version 7.4.5.1 on Windows 11 does not show numbers properly unless box is expanded Product: LibreOffice Version: 7.4.5.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: humpbacklo...@protonmail.com Description: Input Line box cuts off the bottom of numbers or letters input. Input Line box also not lined up with the Name Box, fx, X, =, checkmark icons. Calc Versions 7.3.x.x do not have this problem. Actual Results: Just start Calc in Windows 11 (x64) Expected Results: Problem persists Reproducible: Always User Profile Reset: Yes Additional Info: Input Line box should align with Name Box, fx, X, =, checkmark icons and be large enough to not cut off the bottom of the numbers input -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: configmgr/qa configmgr/source
configmgr/qa/unit/test.cxx |7 +++
configmgr/source/access.cxx | 12 ++--
2 files changed, 13 insertions(+), 6 deletions(-)
New commits:
commit c3bd52f81bf733a0b9b0560794a54b2ac1e0f444
Author: Stephan Bergmann
AuthorDate: Wed Feb 15 21:22:51 2023 +0100
Commit: Stephan Bergmann
CommitDate: Wed Feb 15 23:24:12 2023 +
Use the (first segment of the) original locale value for the workaround
again
cf7c9599e776eba8e14614cecb528d3da5778190 "Make comphelper/configuration.hxx
work
for localized properties", which had originally introduced this code, had
been
careful to ensure that the
> assert(
> !locale.isEmpty() && locale.indexOf('-') == -1 &&
> locale.indexOf('_') == -1);
would always hold here (it had already removed all trailing "-..." and
"_..."
segments, but had made sure to stop before `locale`, which is known to
initially
be no non-empty, would have become empty, by treating a leading "-" or "_"
not
as a segment delimiter, but rather as a first segment).
dfc28be2487c13be36a90efd778b8d8f179c589d "configmgr: Use a proper
LanguageTag-based locale fallback mechanism" had changed that, instead
setting
`locale` to some value obtained from `LanguageTag::getFallbackStrings`,
which
might or might not satisfy the assert.
But there was no good reason for that part of
dfc28be2487c13be36a90efd778b8d8f179c589d in the first place: The
workaround (as
explained in the leading code comment) was meant to be carried out with the
first segment of the original `locale` value, not with some fallback value.
So
put back here the computation of that first segment of the original `locale`
value. (And drop the misleading empty line that
dfc28be2487c13be36a90efd778b8d8f179c589d had, for no good reason, introduced
between the workaround's leading code comment and its actual code.)
However, it turns out that there was one flaw in
cf7c9599e776eba8e14614cecb528d3da5778190: When the original `locale` starts
with "-" or "_", the resulting `locale` representing the first segment will
be
"-" or "_", so the `locale.indexOf('-') == -1 && locale.indexOf('_') == -1`
part
of the assert would be false. But that wouldn't be an issue for the
following
code (the only issue would be if `locale` had become empty, in which case
the
`name2.startsWiht(locale)` check would trivially become true, and that for
loop
would erroneously pick the child with the empty `name2`), and that part of
the
assert had merely been there to reinforce that `locale` had indeed been
stripped
down to the first segment. A correct version of the assert would have used
`locale.indexOf('-', 1) == -1 && locale.indexOf('_', 1) == -1` instead, but
as
the code now makes it obvious anyway that `locale` has been cut down here
to the
first segment, we can just as well simplify the assert to just the
`!locale.isEmpty()` part.
(The added test code unfortunately doesn't actually test this piece of
code, and
somewhat unexpectedly receives the "default" value from the empty string
locale
default, rather than the "en-US" value from the higher precedence "en-US"
locale
default, because `aFallbacks` happens to contain an empty string, so we
already
leave Access::getChild early in the "Find the best match using the
LanguageTag
fallback mechanism, excluding the original tag" block.)
Change-Id: Ib92e714c9db4879be058529ec905e631df975424
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147113
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann
diff --git a/configmgr/qa/unit/test.cxx b/configmgr/qa/unit/test.cxx
index 3de93a6672df..7aa2daf6f96d 100644
--- a/configmgr/qa/unit/test.cxx
+++ b/configmgr/qa/unit/test.cxx
@@ -324,6 +324,13 @@ void Test::testLocalizedProperty() {
access->getByHierarchicalName("/org.libreoffice.unittest/localized/*pt") >>= v);
CPPUNIT_ASSERT_EQUAL(OUString("pt-PT"), v);
}
+{
+// Make sure a degenerate passed-in "-" locale is handled gracefully:
+OUString v;
+CPPUNIT_ASSERT(
+
access->getByHierarchicalName("/org.libreoffice.unittest/localized/*-") >>= v);
+CPPUNIT_ASSERT_EQUAL(OUString("default"), v);
+}
}
void Test::testReadCommands()
diff --git a/configmgr/source/access.cxx b/configmgr/source/access.cxx
index 48d9b46ddc26..9d71c7fa2978 100644
--- a/configmgr/source/access.cxx
+++ b/configmgr/source/access.cxx
@@ -68,6 +68,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -1407,12 +1408,11 @@ rtl::Reference< ChildAccess > Access::getChild(OUString
const & name) {
// xml:lang attributes, look for the first entry with the same
first
// segment as the requested language tag before falling back to
[Libreoffice-bugs] [Bug 151452] : Tools/AutoCorrect/AutoCorrect Options window
https://bugs.documentfoundation.org/show_bug.cgi?id=151452 --- Comment #6 from steph.h...@gmail.com --- I'm also seeing the same bug. It also can be triggered by toggling 'Enable word completion' and then clicking between the tabs in the AutoCorrect menu. Each click, or scroll in the options list, or mouseover of the +/- buttons for Min word length etc will cause the window to widen further. Also still happens in safe mode. Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39750] [META] General Math formula editor improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=39750 Rafael Lima changed: What|Removed |Added Blocks||89356 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89356 [Bug 89356] in exported PDF sqrt sign has displaced horizontal bar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89356] in exported PDF sqrt sign has displaced horizontal bar
https://bugs.documentfoundation.org/show_bug.cgi?id=89356 Rafael Lima changed: What|Removed |Added Depends on||39750 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=39750 [Bug 39750] [META] General Math formula editor improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39750] [META] General Math formula editor improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=39750 Rafael Lima changed: What|Removed |Added Depends on||149700 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149700 [Bug 149700] Square root symbol misaligned in certain font sizes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149700] Square root symbol misaligned in certain font sizes
https://bugs.documentfoundation.org/show_bug.cgi?id=149700 Rafael Lima changed: What|Removed |Added Blocks||39750 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=39750 [Bug 39750] [META] General Math formula editor improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 73596] FILEOPEN: docx Index field not get imported and hence get lost while saving
https://bugs.documentfoundation.org/show_bug.cgi?id=73596 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com --- Comment #11 from Gabor Kelemen (allotropia) --- (In reply to Stéphane Guillou (stragu) from comment #10) > Not exactly sure how to reproduce this. > Could someone share some precise steps we could follow? This is about the References ribbon - Index group. First you need to use the Mark Entry button to mark a few words in the document, then Insert Index button creates this Index (in Word) or Alphabetical Index (as Writer calls it). This report is kinda generic, it would be better to split it up to smaller issues. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: i18nlangtag/qa i18nlangtag/source
i18nlangtag/qa/cppunit/test_languagetag.cxx| 97 +
i18nlangtag/source/languagetag/languagetag.cxx |6 +
2 files changed, 101 insertions(+), 2 deletions(-)
New commits:
commit 88d0559134103fdcc8bdbf77a6dbd5b93de41249
Author: Eike Rathke
AuthorDate: Wed Feb 15 21:42:25 2023 +0100
Commit: Eike Rathke
CommitDate: Wed Feb 15 22:45:28 2023 +
Add unit tests for zh-Hans and zh-Hant mapping and fallbacks
Change-Id: I99db25676e38a85639f4f2fb09b7fc42cc6f8755
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147111
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/i18nlangtag/qa/cppunit/test_languagetag.cxx
b/i18nlangtag/qa/cppunit/test_languagetag.cxx
index c64a3baa61d6..751cb01c6703 100644
--- a/i18nlangtag/qa/cppunit/test_languagetag.cxx
+++ b/i18nlangtag/qa/cppunit/test_languagetag.cxx
@@ -482,6 +482,103 @@ void TestLanguageTag::testAllTags()
CPPUNIT_ASSERT_EQUAL( s_es_ES_tradnl, es_ES_tradnl.getBcp47MS() );
}
+// 'zh-Hans-CN' maps to 'zh-CN' and fallbacks
+{
+LanguageTag zh_Hans_CN( "zh-Hans-CN", true );
+lang::Locale aLocale = zh_Hans_CN.getLocale();
+CPPUNIT_ASSERT_EQUAL( OUString("zh-CN"), zh_Hans_CN.getBcp47() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), aLocale.Language );
+CPPUNIT_ASSERT_EQUAL( OUString("CN"), aLocale.Country );
+CPPUNIT_ASSERT( aLocale.Variant.isEmpty() );
+CPPUNIT_ASSERT_EQUAL( LANGUAGE_CHINESE_SIMPLIFIED,
zh_Hans_CN.getLanguageType() );
+CPPUNIT_ASSERT( zh_Hans_CN.isValidBcp47() );
+CPPUNIT_ASSERT( zh_Hans_CN.isIsoLocale() );
+CPPUNIT_ASSERT( zh_Hans_CN.isIsoODF() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), zh_Hans_CN.getLanguage() );
+CPPUNIT_ASSERT_EQUAL( OUString("CN"), zh_Hans_CN.getCountry() );
+CPPUNIT_ASSERT( zh_Hans_CN.getScript().isEmpty() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"),
zh_Hans_CN.getLanguageAndScript() );
+::std::vector< OUString > zh_Hans_CN_Fallbacks(
zh_Hans_CN.getFallbackStrings( true));
+CPPUNIT_ASSERT_EQUAL( static_cast(2),
zh_Hans_CN_Fallbacks.size());
+CPPUNIT_ASSERT_EQUAL( OUString("zh-CN"), zh_Hans_CN_Fallbacks[0]);
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), zh_Hans_CN_Fallbacks[1]);
+CPPUNIT_ASSERT_EQUAL( OUString("zh-CN"),
zh_Hans_CN.makeFallback().getBcp47());
+}
+
+// 'zh-Hant-TW' maps to 'zh-TW' and fallbacks
+{
+LanguageTag zh_Hant_TW( "zh-Hant-TW", true );
+lang::Locale aLocale = zh_Hant_TW.getLocale();
+CPPUNIT_ASSERT_EQUAL( OUString("zh-TW"), zh_Hant_TW.getBcp47() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), aLocale.Language );
+CPPUNIT_ASSERT_EQUAL( OUString("TW"), aLocale.Country );
+CPPUNIT_ASSERT( aLocale.Variant.isEmpty() );
+CPPUNIT_ASSERT_EQUAL( LANGUAGE_CHINESE_TRADITIONAL,
zh_Hant_TW.getLanguageType() );
+CPPUNIT_ASSERT( zh_Hant_TW.isValidBcp47() );
+CPPUNIT_ASSERT( zh_Hant_TW.isIsoLocale() );
+CPPUNIT_ASSERT( zh_Hant_TW.isIsoODF() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), zh_Hant_TW.getLanguage() );
+CPPUNIT_ASSERT_EQUAL( OUString("TW"), zh_Hant_TW.getCountry() );
+CPPUNIT_ASSERT( zh_Hant_TW.getScript().isEmpty() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"),
zh_Hant_TW.getLanguageAndScript() );
+::std::vector< OUString > zh_Hant_TW_Fallbacks(
zh_Hant_TW.getFallbackStrings( true));
+CPPUNIT_ASSERT_EQUAL( static_cast(3),
zh_Hant_TW_Fallbacks.size());
+CPPUNIT_ASSERT_EQUAL( OUString("zh-TW"), zh_Hant_TW_Fallbacks[0]);
+CPPUNIT_ASSERT_EQUAL( OUString("zh-CN"), zh_Hant_TW_Fallbacks[1]);
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), zh_Hant_TW_Fallbacks[2]);
+CPPUNIT_ASSERT_EQUAL( OUString("zh-TW"),
zh_Hant_TW.makeFallback().getBcp47());
+}
+
+// 'zh-SG' and fallbacks
+{
+OUString s_zh_SG( "zh-SG" );
+LanguageTag zh_SG( s_zh_SG, true );
+lang::Locale aLocale = zh_SG.getLocale();
+CPPUNIT_ASSERT_EQUAL( s_zh_SG, zh_SG.getBcp47() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), aLocale.Language );
+CPPUNIT_ASSERT_EQUAL( OUString("SG"), aLocale.Country );
+CPPUNIT_ASSERT( aLocale.Variant.isEmpty() );
+CPPUNIT_ASSERT_EQUAL( LANGUAGE_CHINESE_SINGAPORE,
zh_SG.getLanguageType() );
+CPPUNIT_ASSERT( zh_SG.isValidBcp47() );
+CPPUNIT_ASSERT( zh_SG.isIsoLocale() );
+CPPUNIT_ASSERT( zh_SG.isIsoODF() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), zh_SG.getLanguage() );
+CPPUNIT_ASSERT_EQUAL( OUString("SG"), zh_SG.getCountry() );
+CPPUNIT_ASSERT( zh_SG.getScript().isEmpty() );
+CPPUNIT_ASSERT_EQUAL( OUString("zh"), zh_SG.getLanguageAndScript() );
+::std::vector< OUString > zh_SG_Fallbacks( zh_SG.getFallbackStrings(
true));
+CPPUNIT_ASSERT_EQUAL( static_cast(3), zh_SG_Fallbacks.size());
+
[Libreoffice-bugs] [Bug 121471] [Enhancement] pre-print options and pdf/X PDF export support
https://bugs.documentfoundation.org/show_bug.cgi?id=121471 --- Comment #3 from peter josvai --- totally agree, PDF/X is a must.. LO apparently is meant to be able to handle book editing, so... after all that editing... there must me way to generate a proper file output, which is PDF/X-1a -- You are receiving this mail because: You are the assignee for the bug.
