[Libreoffice-bugs] [Bug 152229] New: Form Control: Read only doesn't work for special characters.
https://bugs.documentfoundation.org/show_bug.cgi?id=152229 Bug ID: 152229 Summary: Form Control: Read only doesn't work for special characters. Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Created attachment 183796 --> https://bugs.documentfoundation.org/attachment.cgi?id=183796=edit Open the form. Try to input special characters into field "Name", which is set to "Read only" → 'yes' Open the attached Base file. Open the form. Try to input new content to the field "Name". Reported for Mac (https://www.libreoffice-forum.de/viewtopic.php?f=10=38384): Special characters like "ß ´ § ` ü Ü ö Ö ä Ä" will ignore "Read only" → 'yes'. You could input this characters and save the changed content. Couldn't find any second person for testing this with a Mac. Don't have Mac here. Bug doesn't appear on Linux systems or on Windows. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148514] Filternavigator in Base is always minimized
https://bugs.documentfoundation.org/show_bug.cgi?id=148514 Robert Großkopf changed: What|Removed |Added OS|Windows (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148514] Filternavigator in Base is always minimized
https://bugs.documentfoundation.org/show_bug.cgi?id=148514 Robert Großkopf changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148514] Filternavigator in Base is always minimized
https://bugs.documentfoundation.org/show_bug.cgi?id=148514 --- Comment #5 from Robert Großkopf --- Created attachment 183795 --> https://bugs.documentfoundation.org/attachment.cgi?id=183795=edit Bug still there: Screenshot LO 7.4.3.2 under OpenSUSE 15.3 64bit rpm Linux Will reopen the bug. Tested it for another bug again with current LO-Version, clean user profile. See the buggy behavior under Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144343] Form - Form-Based Filters: Filter navigator shows up every second filtering
https://bugs.documentfoundation.org/show_bug.cgi?id=144343 --- Comment #8 from Robert Großkopf --- Created attachment 183794 --> https://bugs.documentfoundation.org/attachment.cgi?id=183794=edit Open the form. Press Formbased Filter, apply, press Foirmbased Filter again Filter navigator will be shown first time - but very small in LO 7.4.3.2 … Apply filter and press "Formbased Filter" again. No Navigator will be shown. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135648] PARAGRAPH STYLE DIALOG: "Tab" buttons in the dialog move
https://bugs.documentfoundation.org/show_bug.cgi?id=135648 raal changed: What|Removed |Added Version|6.4.5.2 release |4.1.0.4 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138713] Frame and background color will be separated on drag (DOCX?)
https://bugs.documentfoundation.org/show_bug.cgi?id=138713 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #6 from raal --- No repro with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ebe151d919a454f98c36013245bca9eb41d92707 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Telesto, please can you retest? Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139826] Image disappears when moving to certain spot.. And image vanishes after undo
https://bugs.documentfoundation.org/show_bug.cgi?id=139826 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #5 from raal --- @Telesto, please can you retest it? WFM in Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ebe151d919a454f98c36013245bca9eb41d92707 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144343] Form - Form-Based Filters: Filter navigator shows up every second filtering
https://bugs.documentfoundation.org/show_bug.cgi?id=144343 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #7 from raal --- (In reply to Robert Großkopf from comment #6) > I'm missing some steps to show a buggy behavior here: > > 1. Open a form in Base. Can you attach a test file, please? Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 --- Comment #12 from Jim Raykowski --- (In reply to Stéphane Guillou (stragu) from comment #10) > (In reply to Jim Raykowski from comment #9) > > Can anyone confirm the gtk3 only misbehavior mentioned in Comment 4 of the > > last tree entry not being selected (highlighted) when the Target in document > > dialog is reopened? > > Yes, selection is lost when reopening with GTK3: Thanks for confirming. Should be fixed with the above patch. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 --- Comment #12 from Jim Raykowski --- (In reply to Stéphane Guillou (stragu) from comment #10) > (In reply to Jim Raykowski from comment #9) > > Can anyone confirm the gtk3 only misbehavior mentioned in Comment 4 of the > > last tree entry not being selected (highlighted) when the Target in document > > dialog is reopened? > > Yes, selection is lost when reopening with GTK3: Thanks for confirming. Should be fixed with the above patch. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 --- Comment #11 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ff1c7080086191a5a7670d20b59936fcb79a91dc tdf#152115 related: Make selected entry stay selected (gtk3 only) It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 --- Comment #11 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ff1c7080086191a5a7670d20b59936fcb79a91dc tdf#152115 related: Make selected entry stay selected (gtk3 only) It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152115] Hyperlink Target in document: The last user setting is not remembered
https://bugs.documentfoundation.org/show_bug.cgi?id=152115 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: cui/source
cui/source/dialogs/hlmarkwn.cxx |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) New commits: commit ff1c7080086191a5a7670d20b59936fcb79a91dc Author: Jim Raykowski AuthorDate: Wed Nov 23 23:05:52 2022 -0900 Commit: Jim Raykowski CommitDate: Sat Nov 26 07:15:03 2022 +0100 tdf#152115 related: Make selected entry stay selected (gtk3 only) For unknown reason the selected entry loses selection here only for gtk3. Swapping the order of the select and scroll_to_row functions makes the selection remain selected for gtk3. This patch replaces the select and scroll_to_row functions with the set_cursor function which makes the focused entry selected and shown in the visible range as expected for gtk3 as well as x11 and qt5. Change-Id: If003afa73851573e61704cc847d7152db90a0d14 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143207 Tested-by: Jenkins Reviewed-by: Jim Raykowski diff --git a/cui/source/dialogs/hlmarkwn.cxx b/cui/source/dialogs/hlmarkwn.cxx index ff7730db55c0..04b50b44e309 100644 --- a/cui/source/dialogs/hlmarkwn.cxx +++ b/cui/source/dialogs/hlmarkwn.cxx @@ -456,8 +456,7 @@ bool SvxHlinkDlgMarkWnd::SelectEntry(std::u16string_view aStrMark) std::unique_ptr xEntry = FindEntry(aStrMark); if (!xEntry) return false; -mxLbTree->select(*xEntry); -mxLbTree->scroll_to_row(*xEntry); +mxLbTree->set_cursor(*xEntry); return true; }
[Libreoffice-commits] core.git: sw/source
sw/source/core/layout/frmtool.cxx| 44 +--
sw/source/filter/html/htmlfly.cxx|4 +-
sw/source/filter/html/swhtml.cxx | 11 +++---
sw/source/filter/ww8/docxattributeoutput.cxx | 14
sw/source/uibase/docvw/edtwin.cxx| 17 +-
5 files changed, 45 insertions(+), 45 deletions(-)
New commits:
commit 9a2d15d3358816043016af79588e0eb3bb2fa5ef
Author: Noel Grandin
AuthorDate: Fri Nov 25 14:43:21 2022 +0200
Commit: Noel Grandin
CommitDate: Sat Nov 26 07:13:38 2022 +0100
use more SwFormatAnchor::GetAnchorNode method
as a step towards switching away from using SwPosition inside
SwFormatAnchor (because SwFormatAnchor wants to do weird stuff with the
internals of SwPosition)
Change-Id: I1cdbe2fc6623d8fe2bb0c1bc629b570ca4d0cb0c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143298
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/layout/frmtool.cxx
b/sw/source/core/layout/frmtool.cxx
index 93f02c5bf756..7f04626a6b03 100644
--- a/sw/source/core/layout/frmtool.cxx
+++ b/sw/source/core/layout/frmtool.cxx
@@ -960,12 +960,12 @@ void SwContentNotify::ImplDestroy()
SwFrameFormat *pFormat = (*pTable)[i];
const SwFormatAnchor = pFormat->GetAnchor();
if ( RndStdIds::FLY_AT_PAGE != rAnch.GetAnchorId() ||
- rAnch.GetContentAnchor() == nullptr )
+ rAnch.GetAnchorNode() == nullptr )
{
continue;
}
-if (FrameContainsNode(*pCnt,
rAnch.GetContentAnchor()->GetNodeIndex()))
+if (FrameContainsNode(*pCnt,
rAnch.GetAnchorNode()->GetIndex()))
{
OSL_FAIL( " - to page
anchored object with content position." );
if ( !pPage )
@@ -1102,8 +1102,8 @@ static bool IsShown(SwNodeOffset const nIndex,
SwTextNode const*const pFirstNode, SwTextNode const*const pLastNode)
{
assert(!pIter || *pIter == *pEnd || (*pIter)->pNode->GetIndex() == nIndex);
-SwPosition const& rAnchor(*rAnch.GetContentAnchor());
-if (rAnchor.GetNodeIndex() != nIndex)
+SwNode* pAnchorNode = rAnch.GetAnchorNode();
+if (pAnchorNode->GetIndex() != nIndex)
{
return false;
}
@@ -,7 +,7 @@ static bool IsShown(SwNodeOffset const nIndex,
{
return pIter == nullptr // not merged
|| pIter != pEnd// at least one char visible in node
-|| !IsSelectFrameAnchoredAtPara(rAnchor,
+|| !IsSelectFrameAnchoredAtPara(*rAnch.GetContentAnchor(),
SwPosition(*pFirstNode, 0),
SwPosition(*pLastNode, pLastNode->Len()));
}
@@ -1126,7 +1126,7 @@ static bool IsShown(SwNodeOffset const nIndex,
{
assert(iter->nStart != iter->nEnd); // TODO possible?
assert(iter->pNode->GetIndex() == nIndex);
-if (rAnchor.GetContentIndex() < iter->nStart)
+if (rAnch.GetContentAnchor()->GetContentIndex() < iter->nStart)
{
return false;
}
@@ -1144,7 +1144,7 @@ static bool IsShown(SwNodeOffset const nIndex,
// the interesting corner cases are on the edge of the extent!
// no need to check for > the last extent because those
// are never visible.
-if (rAnchor.GetContentIndex() <= iter->nEnd)
+if (rAnch.GetContentAnchor()->GetContentIndex() <= iter->nEnd)
{
if (iter->nStart == 0)
{
@@ -1162,7 +1162,7 @@ static bool IsShown(SwNodeOffset const nIndex,
: pFirstNode->Len() // previous node;
simplification but should get right result
: (iter-1)->nEnd); // previous extent
SwPosition const end(*iter->pNode, iter->nStart);
-return !IsDestroyFrameAnchoredAtChar(rAnchor, start,
end);
+return
!IsDestroyFrameAnchoredAtChar(*rAnch.GetContentAnchor(), start, end);
}
}
else if (iter == *pEnd - 1) // special case: after last extent
@@ -1179,7 +1179,7 @@ static bool IsShown(SwNodeOffset const nIndex,
iter->pNode == pLastNode
? iter->pNode->Len()
: 0);
-return !IsDestroyFrameAnchoredAtChar(rAnchor, start,
end);
+return
!IsDestroyFrameAnchoredAtChar(*rAnch.GetContentAnchor(), start, end);
}
}
}
@@ -1187,7 +1187,7 @@ static bool IsShown(SwNodeOffset const nIndex,
{
assert(rAnch.GetAnchorId() == RndStdIds::FLY_AS_CHAR);
[Libreoffice-commits] core.git: sw/source
sw/source/core/text/txtfrm.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit cb7153403a55a0e565584aedd8a4dc8da149b08c
Author: Mike Kaganski
AuthorDate: Sat Nov 26 00:21:57 2022 +0300
Commit: Mike Kaganski
CommitDate: Sat Nov 26 07:07:37 2022 +0100
Unneeded const_cast
Change-Id: I135498592857a624b72db519724e8f189e60e9a3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143310
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/source/core/text/txtfrm.cxx b/sw/source/core/text/txtfrm.cxx
index 29e98cfca5b9..8db5779293d3 100644
--- a/sw/source/core/text/txtfrm.cxx
+++ b/sw/source/core/text/txtfrm.cxx
@@ -1259,7 +1259,7 @@ TextFrameIndex SwTextFrame::MapModelToView(SwTextNode
const*const pNode, sal_Int
}
else
{
-
assert(static_cast(const_cast(SwFrame::GetDep()))
== pNode);
+assert(static_cast(SwFrame::GetDep()) == pNode);
return TextFrameIndex(nIndex);
}
}
[Libreoffice-bugs] [Bug 151918] LO Default per-language-group language choice must only apply to a document on creation
https://bugs.documentfoundation.org/show_bug.cgi?id=151918 --- Comment #16 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #15) > > and wherever it gets finally landed, it may get a "make default" > > button, to allow *also* to store this piece of settings into the > > profile as a default value for newly created documents. > > I'm not against this in principle, but: > > * If you did this everywhere it is possible, you would need to allow every > feature of, say, the default page style and default paragraph style to be > "made default". That's a lot of buttons... > * You may also/instead want to consider the 'mirror' approach to your > suggestion, i.e. having the LO options dialog have buttons for "adopt > settings in current document as the default for new documents". > * Wouldn't some of these "default value" settings actually belong in the > template file rather than the app option? Every default may (and best does) apply to templates. But yet: 1. There are these existing controls in Options, that allow to set the non-template defaults; and if they are needed at all, we should decide where they are; 2. There are cases where even templates don't suffice - like Calc column default width/height, something hardcoded, and used e.g. when you delete some rows/columns, and Calc appends the new stuff, and there are people who consider impossibility to customize it to be a bad thing; 3. It is good to not multiply places where you configure one thing. E.g., when you think about font, you go to Format->Character; and having font settings *also* in other place (in Options just for defaults) is a bad UX; 4. Having a single "apply this document settings as global defaults" would be inconvenient, given how many things may come from the document, which user is even unaware of (does user know e.g. if the printer setting would be stored, and then cause delays when the network printer is turned off?). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/core/text/txtfrm.cxx | 52 -
1 file changed, 26 insertions(+), 26 deletions(-)
New commits:
commit e52cf954a1dcd0f26096fcdb89f068e76c3fa9f2
Author: Mike Kaganski
AuthorDate: Sat Nov 26 00:27:23 2022 +0300
Commit: Mike Kaganski
CommitDate: Sat Nov 26 06:35:00 2022 +0100
Use reference instead of pointer
Change-Id: I2d15ee96373d21b6501fa956601378d7f698a099
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143311
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/source/core/text/txtfrm.cxx b/sw/source/core/text/txtfrm.cxx
index f0400c3cb91d..29e98cfca5b9 100644
--- a/sw/source/core/text/txtfrm.cxx
+++ b/sw/source/core/text/txtfrm.cxx
@@ -1800,48 +1800,48 @@ static void lcl_SetWrong( SwTextFrame& rFrame,
SwTextNode const& rNode,
{
if ( !rFrame.IsFollow() )
{
-SwTextNode* pTextNode = const_cast();
-sw::GrammarContact* pGrammarContact =
sw::getGrammarContactFor(*pTextNode);
+SwTextNode& rTextNode = const_cast(rNode);
+sw::GrammarContact* pGrammarContact =
sw::getGrammarContactFor(rTextNode);
SwGrammarMarkUp* pWrongGrammar = pGrammarContact ?
-pGrammarContact->getGrammarCheck( *pTextNode, false ) :
-pTextNode->GetGrammarCheck();
-bool bGrammarProxy = pWrongGrammar != pTextNode->GetGrammarCheck();
+pGrammarContact->getGrammarCheck( rTextNode, false ) :
+rTextNode.GetGrammarCheck();
+bool bGrammarProxy = pWrongGrammar != rTextNode.GetGrammarCheck();
if( bMove )
{
-if( pTextNode->GetWrong() )
-pTextNode->GetWrong()->Move( nPos, nCnt );
+if( rTextNode.GetWrong() )
+rTextNode.GetWrong()->Move( nPos, nCnt );
if( pWrongGrammar )
pWrongGrammar->MoveGrammar( nPos, nCnt );
-if( bGrammarProxy && pTextNode->GetGrammarCheck() )
-pTextNode->GetGrammarCheck()->MoveGrammar( nPos, nCnt );
-if( pTextNode->GetSmartTags() )
-pTextNode->GetSmartTags()->Move( nPos, nCnt );
+if( bGrammarProxy && rTextNode.GetGrammarCheck() )
+rTextNode.GetGrammarCheck()->MoveGrammar( nPos, nCnt );
+if( rTextNode.GetSmartTags() )
+rTextNode.GetSmartTags()->Move( nPos, nCnt );
}
else
{
-if( pTextNode->GetWrong() )
-pTextNode->GetWrong()->Invalidate( nPos, nCnt );
+if( rTextNode.GetWrong() )
+rTextNode.GetWrong()->Invalidate( nPos, nCnt );
if( pWrongGrammar )
pWrongGrammar->Invalidate( nPos, nCnt );
-if( pTextNode->GetSmartTags() )
-pTextNode->GetSmartTags()->Invalidate( nPos, nCnt );
+if( rTextNode.GetSmartTags() )
+rTextNode.GetSmartTags()->Invalidate( nPos, nCnt );
}
const sal_Int32 nEnd = nPos + (nCnt > 0 ? nCnt : 1 );
-if ( !pTextNode->GetWrong() && !pTextNode->IsWrongDirty() )
+if ( !rTextNode.GetWrong() && !rTextNode.IsWrongDirty() )
{
-pTextNode->SetWrong( std::make_unique(
WRONGLIST_SPELL ) );
-pTextNode->GetWrong()->SetInvalid( nPos, nEnd );
+rTextNode.SetWrong( std::make_unique( WRONGLIST_SPELL
) );
+rTextNode.GetWrong()->SetInvalid( nPos, nEnd );
}
-if ( !pTextNode->GetSmartTags() && !pTextNode->IsSmartTagDirty() )
+if ( !rTextNode.GetSmartTags() && !rTextNode.IsSmartTagDirty() )
{
-pTextNode->SetSmartTags( std::make_unique(
WRONGLIST_SMARTTAG ) );
-pTextNode->GetSmartTags()->SetInvalid( nPos, nEnd );
+rTextNode.SetSmartTags( std::make_unique(
WRONGLIST_SMARTTAG ) );
+rTextNode.GetSmartTags()->SetInvalid( nPos, nEnd );
}
-pTextNode->SetWrongDirty(sw::WrongState::TODO);
-pTextNode->SetGrammarCheckDirty( true );
-pTextNode->SetWordCountDirty( true );
-pTextNode->SetAutoCompleteWordDirty( true );
-pTextNode->SetSmartTagDirty( true );
+rTextNode.SetWrongDirty(sw::WrongState::TODO);
+rTextNode.SetGrammarCheckDirty( true );
+rTextNode.SetWordCountDirty( true );
+rTextNode.SetAutoCompleteWordDirty( true );
+rTextNode.SetSmartTagDirty( true );
}
SwRootFrame *pRootFrame = rFrame.getRootFrame();
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Dieter changed: What|Removed |Added Depends on||152040 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152040 [Bug 152040] Table: drag column border (to resize) leaves lines -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152040] Table: drag column border (to resize) leaves lines
https://bugs.documentfoundation.org/show_bug.cgi?id=152040 Dieter changed: What|Removed |Added Blocks||129062 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129062 [Bug 129062] [META] Skia library bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-4' - vcl/inc vcl/source
vcl/inc/window.h |2 ++
vcl/source/window/window.cxx |2 ++
vcl/source/window/window2.cxx | 37 ++---
3 files changed, 26 insertions(+), 15 deletions(-)
New commits:
commit 3dcea050438ace1ace5e013c0c7326aec3c82c6b
Author: Jonas Eyov
AuthorDate: Fri Nov 18 03:40:57 2022 +
Commit: Adolfo Jayme Barrientos
CommitDate: Sat Nov 26 05:35:41 2022 +0100
tdf#143209 vcl: track partial scroll deltas
this makes scrolling in calc smoother and makes left/up scrolling
the same speed as right/down scrolling, which was previously not the
case.
prior to this change, Window::HandleScrollCommand only checked each
event for being a large enough scroll to advance one unit. this
happened in lcl_HandleScrollHelper by way of o3tl::saturating_cast,
which meant that nonzero upward/leftward scrolls were always worth at
least one unit, while downward/rightward scrolls needed to be larger
than 1 to count.
now, we accumulate partial scroll offsets in WindowImpl and perform a
saturating cast on the absolute value, so behavior is symmetric and
sensitive to accumulated small scroll values. this feels smoother
and is more correct.
Change-Id: Id3692d14edd45ed26f2952e3418e4d82806e1fc4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142948
Tested-by: Jenkins
Tested-by: Caolán McNamara
Reviewed-by: Caolán McNamara
(cherry picked from commit fe21365c5a9083ae1f086ea48614263b3a75ab3e)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143122
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/vcl/inc/window.h b/vcl/inc/window.h
index b0395330e19e..87afc6cda56c 100644
--- a/vcl/inc/window.h
+++ b/vcl/inc/window.h
@@ -256,6 +256,8 @@ public:
vcl::Cursor*mpCursor;
PointerStylemaPointer;
FractionmaZoom;
+double mfPartialScrollX;
+double mfPartialScrollY;
OUStringmaText;
std::optional
mpControlFont;
diff --git a/vcl/source/window/window.cxx b/vcl/source/window/window.cxx
index fe6f788e8ecc..aabd1778c11a 100644
--- a/vcl/source/window/window.cxx
+++ b/vcl/source/window/window.cxx
@@ -590,6 +590,8 @@ WindowImpl::WindowImpl( vcl::Window& rWindow, WindowType
nType )
{
mxOutDev = VclPtr::Create(rWindow);
maZoom = Fraction( 1, 1 );
+mfPartialScrollX= 0.0;
+mfPartialScrollY= 0.0;
maWinRegion = vcl::Region(true);
maWinClipRegion = vcl::Region(true);
mpWinData = nullptr; //
Extra Window Data, that we don't need for all windows
diff --git a/vcl/source/window/window2.cxx b/vcl/source/window/window2.cxx
index c20dc471120b..ad7677195dab 100644
--- a/vcl/source/window/window2.cxx
+++ b/vcl/source/window/window2.cxx
@@ -597,12 +597,14 @@ tools::Long Window::GetDrawPixel( OutputDevice const *
pDev, tools::Long nPixels
return nP;
}
-static void lcl_HandleScrollHelper( ScrollBar* pScrl, double nN, bool
isMultiplyByLineSize )
+// returns how much was actually scrolled (so that abs(retval) <= abs(nN))
+static double lcl_HandleScrollHelper( ScrollBar* pScrl, double nN, bool
isMultiplyByLineSize )
{
if ( !pScrl || !nN || !pScrl->IsEnabled() || !pScrl->IsInputEnabled() ||
pScrl->IsInModalMode() )
-return;
+return 0.0;
tools::Long nNewPos = pScrl->GetThumbPos();
+double scrolled = nN;
if ( nN == double(-LONG_MAX) )
nNewPos += pScrl->GetPageSize();
@@ -615,13 +617,22 @@ static void lcl_HandleScrollHelper( ScrollBar* pScrl,
double nN, bool isMultiply
nN*=pScrl->GetLineSize();
}
-const double fVal = nNewPos - nN;
+// compute how many quantized units to scroll
+tools::Long magnitude = o3tl::saturating_cast(abs(nN));
+tools::Long change = copysign(magnitude, nN);
+
+nNewPos = nNewPos - change;
-nNewPos = o3tl::saturating_cast(fVal);
+scrolled = double(change);
+// convert back to chunked/continuous
+if(isMultiplyByLineSize){
+scrolled /= pScrl->GetLineSize();
+}
}
pScrl->DoScroll( nNewPos );
+return scrolled;
}
bool Window::HandleScrollCommand( const CommandEvent& rCmd,
@@ -667,6 +678,9 @@ bool Window::HandleScrollCommand( const CommandEvent& rCmd,
{
double nScrollLines = pData->GetScrollLines();
double nLines;
+double* partialScroll = pData->IsHorz()
+? >mfPartialScrollX
+: >mfPartialScrollY;
if ( nScrollLines == COMMAND_WHEEL_PAGESCROLL )
{
if (
[Libreoffice-bugs] [Bug 152175] Black square
https://bugs.documentfoundation.org/show_bug.cgi?id=152175 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 152175] Black square
https://bugs.documentfoundation.org/show_bug.cgi?id=152175 --- Comment #12 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152040] Table: drag column border (to resize) leaves lines
https://bugs.documentfoundation.org/show_bug.cgi?id=152040 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152040] Table: drag column border (to resize) leaves lines
https://bugs.documentfoundation.org/show_bug.cgi?id=152040 --- 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 146069] Property Let multiple arguments ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=146069 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146069] Property Let multiple arguments ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=146069 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144000] MAILMERGE: LO crashes on any mailmerge attempt - because of three-letter registered database name?
https://bugs.documentfoundation.org/show_bug.cgi?id=144000 --- Comment #12 from QA Administrators --- Dear Michael Boxall, 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 144000] MAILMERGE: LO crashes on any mailmerge attempt - because of three-letter registered database name?
https://bugs.documentfoundation.org/show_bug.cgi?id=144000 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 142885] FILESAVE: Cursor jumps to beginning of "File name" field in "Save As" dialog box after selecting text with mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=142885 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 142885] FILESAVE: Cursor jumps to beginning of "File name" field in "Save As" dialog box after selecting text with mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=142885 --- Comment #12 from QA Administrators --- Dear pidkameny, 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 142573] createLibraryLink() does not honor read-only parameter
https://bugs.documentfoundation.org/show_bug.cgi?id=142573 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 142573] createLibraryLink() does not honor read-only parameter
https://bugs.documentfoundation.org/show_bug.cgi?id=142573 --- Comment #4 from QA Administrators --- Dear Vieri, 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 149051] BASE-FORMS: LO hangs when using search function
https://bugs.documentfoundation.org/show_bug.cgi?id=149051 --- Comment #3 from QA Administrators --- Dear Andrew Richardson, 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 99362] Frame and image with no wrapping appearing as if they are floating in 2007 DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=99362 --- Comment #14 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98396] table properties > disabling table split: emulation not working in .doc and .docx format
https://bugs.documentfoundation.org/show_bug.cgi?id=98396 --- Comment #16 from QA Administrators --- Dear synthview, 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 96751] EDITING writer hangs when editing an image in a docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=96751 --- Comment #14 from QA Administrators --- Dear doriano.mag, 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 96629] FILESAVE: equations change positioning after reopening particular DOCX ('To Character' saved 'As Character')
https://bugs.documentfoundation.org/show_bug.cgi?id=96629 --- Comment #9 from QA Administrators --- Dear ale.carrazzoni, 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 137480] Severe screen flickering and misplaced cursor visual while editing with dual window on dual screen
https://bugs.documentfoundation.org/show_bug.cgi?id=137480 --- Comment #3 from QA Administrators --- Dear Dominique, 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 138474] When image is anchored to page in Writer, cannot interact with anchor.
https://bugs.documentfoundation.org/show_bug.cgi?id=138474 --- Comment #3 from QA Administrators --- Dear stefan.m.terry, 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 136695] Footer text in impress is wrapped inside words and does not respect alignment directives
https://bugs.documentfoundation.org/show_bug.cgi?id=136695 --- Comment #5 from QA Administrators --- Dear sergio.callegari, 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 134962] FILESAVE: DOC: Saving ODT with lots of formulas to doc slow
https://bugs.documentfoundation.org/show_bug.cgi?id=134962 --- Comment #8 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 134511] Fontwork favorite 18 (Asphalt) has two values in draw:modifiers, should be only one
https://bugs.documentfoundation.org/show_bug.cgi?id=134511 --- Comment #2 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 134501] _CxxUnregisterExceptionObject VCRUNTIME140 after _RTDynamicCast related to SwViewShell::SetEndActionByVirDev
https://bugs.documentfoundation.org/show_bug.cgi?id=134501 --- 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 125914] Validation with cells referencing themselves always gives error
https://bugs.documentfoundation.org/show_bug.cgi?id=125914 --- Comment #10 from QA Administrators --- Dear Aron Budea, 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 130937] Mouse-hold preview differs from result when changing a connector via dragging
https://bugs.documentfoundation.org/show_bug.cgi?id=130937 --- Comment #3 from QA Administrators --- Dear samufi, 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 112532] Color picker widget is slow to initialize - does not cache color palette data
https://bugs.documentfoundation.org/show_bug.cgi?id=112532 --- Comment #9 from QA Administrators --- Dear Gabor Kelemen, 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 100566] DOCX: multiline bookmarks rendered wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=100566 --- Comment #6 from QA Administrators --- Dear Andrey Skvortsov, 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 109011] Calc: Edit-Paste Only items Text/Number/Formula don't paste content from Excel
https://bugs.documentfoundation.org/show_bug.cgi?id=109011 --- Comment #11 from QA Administrators --- Dear Dan Dascalescu, 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 100524] [FILEOPEN] Spaces between page number/count fields lost on import of specific DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=100524 --- Comment #7 from QA Administrators --- Dear Cor Nouws, 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 146069] Property Let multiple arguments ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=146069 --- Comment #2 from Leslie --- Well its been almost a year since I reported this. I tried tonight to remember how to get code running in Libre and I was not successful. The interface is abysmally unintuitive and after multiple crashes and restarts I could not get the code to recognize the class therefore I cannot reproduce the error for you in a project. All I can suggest is that the version of Libre you are using may have corrected the flaw. I do remember posting this bug to a forum and that can be found here: https://ask.libreoffice.org/t/possible-bug-in-basic-class-setter-implementation/71185 Maybe there is something there that can help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152083] Ligatures are incorrectly reversed opening RTL PDF files
https://bugs.documentfoundation.org/show_bug.cgi?id=152083 --- Comment #5 from Hossein --- Thanks Kevin! This is fixed in Draw and Impress. Could you please also fix the same problem in Writer? I've tested opening the file in writer by choosing "PDF - Portable Document Format (Writer)" as the file type, and the problem was still there. Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 3b0b9fcb80242abcedc01eb388a57b1016916353 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107742] [META] Form control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742 Bug 107742 depends on bug 152145, which changed state. Bug 152145 Summary: Placeholder text for the content control fields should be exported to the output https://bugs.documentfoundation.org/show_bug.cgi?id=152145 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152145] Placeholder text for the content control fields should be exported to the output
https://bugs.documentfoundation.org/show_bug.cgi?id=152145 Hossein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #2 from Hossein --- (In reply to Miklos Vajna from comment #1) > Can you test if you have "create pdf form" enabled in the pdf export > settings dialog? If it's enabled, then you ask the PDF exporter to create > PDF forms instead of plain text for fillable forms. In this case this is > working as expected. > > If it's disabled and the placeholder text is missing, that sounds like a bug. Yes, I have selected "Create PDF Form". By deselecting this option, I see the placeholder text in the output. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit e76b1faa3326e5cffed4472fcd410b5abf273067 Author: Olivier Hallot AuthorDate: Sat Nov 26 02:20:21 2022 +0100 Commit: Gerrit Code Review CommitDate: Sat Nov 26 02:20:21 2022 +0100 Update git submodules * Update helpcontent2 from branch 'master' to e4630d4825d9cf21dad5e8a491402d91ea1e3c1f - Fix path fpr "XML Settings" Change-Id: I5c27abea351d3fe007da9f83fa323e74a7dee9bb Reviewed-on: https://gerrit.libreoffice.org/c/help/+/143165 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 8e7f48e5e03d..e4630d4825d9 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 8e7f48e5e03d5588b00d341c5a82fa1a74b2bdd9 +Subproject commit e4630d4825d9cf21dad5e8a491402d91ea1e3c1f
[Libreoffice-commits] help.git: source/text
source/text/shared/00/0406.xhp |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit e4630d4825d9cf21dad5e8a491402d91ea1e3c1f Author: Olivier Hallot AuthorDate: Thu Nov 24 19:29:37 2022 +0100 Commit: Olivier Hallot CommitDate: Sat Nov 26 02:20:19 2022 +0100 Fix path fpr "XML Settings" Change-Id: I5c27abea351d3fe007da9f83fa323e74a7dee9bb Reviewed-on: https://gerrit.libreoffice.org/c/help/+/143165 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/shared/00/0406.xhp b/source/text/shared/00/0406.xhp index 0520db7192..2168512858 100644 --- a/source/text/shared/00/0406.xhp +++ b/source/text/shared/00/0406.xhp @@ -99,9 +99,9 @@ Choose Tools - Macros - Organize Macros - Basic,click the Organizer button. Choose Tools - Extension Manager. Choose Tools - Extension Manager, click Check for Updates button. -Choose Tools - XML Filter Settings. -Tools - XML Filter Settings, then click New or Edit. -Tools - XML Filter Settings, then click Test XSLTs. +Choose Tools - Macros - XML Filter Settings. +Tools - Macros - XML Filter Settings, then click New or Edit. +Tools - Macros - XML Filter Settings, then click Test XSLTs. Choose Tools - Customize. Choose Tools - Customize - Menus tab. Choose Tools - Customize - Menus tab, click the hamburger Icon Hamburger menu dropdown menu and choose Add.
[Libreoffice-bugs] [Bug 152227] Add support for Zarnegar format
https://bugs.documentfoundation.org/show_bug.cgi?id=152227 Eike Rathke changed: What|Removed |Added Ever confirmed|0 |1 Product|LibreOffice |Document Liberation Project Status|UNCONFIRMED |NEW Component|Writer |General Severity|normal |enhancement Version|7.4.0.3 release |unspecified --- Comment #1 from Eike Rathke --- This could be a candidate for The Document Liberation Project. It's also tracked here, I'm setting its product. See https://www.documentliberation.org/ Note that the Python code is under GPLv3+ and can't be used. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91666] PDF: Broken import of non-BMP characters
https://bugs.documentfoundation.org/show_bug.cgi?id=91666 Rajasekaran Karunanithi changed: What|Removed |Added CC||rajasekara...@gmail.com --- Comment #11 from Rajasekaran Karunanithi --- Still reproducable in LO 7.4.2.3 under Windows 10(x64). Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ta-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151918] LO Default per-language-group language choice must only apply to a document on creation
https://bugs.documentfoundation.org/show_bug.cgi?id=151918 --- Comment #15 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #14) Mike summarized my position correctly. > I support a vision that each and every option that is be stored in > the document, should be removed from the Options dialog; Agree so far. > and wherever it gets finally landed, it may get a "make default" > button, to allow *also* to store this piece of settings into the > profile as a default value for newly created documents. I'm not against this in principle, but: * If you did this everywhere it is possible, you would need to allow every feature of, say, the default page style and default paragraph style to be "made default". That's a lot of buttons... * You may also/instead want to consider the 'mirror' approach to your suggestion, i.e. having the LO options dialog have buttons for "adopt settings in current document as the default for new documents". * Wouldn't some of these "default value" settings actually belong in the template file rather than the app option? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152228] New: Inconsistent "Show Boundaries" behavior based on document creation method
https://bugs.documentfoundation.org/show_bug.cgi?id=152228 Bug ID: 152228 Summary: Inconsistent "Show Boundaries" behavior based on document creation method Product: LibreOffice Version: 7.2.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: altasilvap...@gmail.com Description: If I create a .odt file by right-clicking in a folder and choosing "New->Open Document Text" from the context menu, I'll get the erroneous behavior. If I create a .odt file by first opening LibreOffice, clicking New File, and then Writer, I get the correct behavior. Erroneous Behavior: "Show Table Boundaries" does nothing. "Show Text Boundaries" toggles BOTH table and text boundaries. Correct Behavior: "Show Table Boundaries" toggles table boundaries, while "Show Text Boundaries" toggles text boundaries. Steps to Reproduce: REPRO BUG: 1. Create ODT file from Windows Context menu (New->Open Document Text) 2. Insert Table of any number of rows/columns 3. Set all borders of said table to invisible 4. Toggle "Show Table Boundaries" on/off 5. Toggle "Show Text Boundaries" on/off 6. Observe erroneous behavior of toggles. REPRO UNBUGGED: 7. Create ODT file from LibreOffice New File menu (inside LibreOffice) 8. Repeat steps 2-5 9. Observe expected/correct behavior of toggles. Actual Results: In the bugged file, "Show Table Boundaries" and "Show Text Boundaries" do not properly toggle the appropriate elements. Expected Results: "Show Table Boundaries" and "Show Text Boundaries" should ONLY toggle their respective elements. Reproducible: Always User Profile Reset: Yes Additional Info: I first observed this behavior in April of 2022 and reported it on AskLO, where it appeared to be tied to a partially-corrupted file. Since then, I have coincidentally wiped my hard drive and reinstalled LO at least once, as well as reset my profile at least once, and happened upon the same bug behavior again today. I have not yet had time to download or attempt to reproduce the bug in the 7.4.x line. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152227] New: Add support for Zarnegar format
https://bugs.documentfoundation.org/show_bug.cgi?id=152227 Bug ID: 152227 Summary: Add support for Zarnegar format Product: LibreOffice Version: 7.4.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 183793 --> https://bugs.documentfoundation.org/attachment.cgi?id=183793=edit Sample Zarnegar75 file Description: Zarnegar was a commercial word processor from SinaSoft co. for DOS and later Windows that supported Persian/Arabic languages. It was the prominent word processor in Iran in 1990s. Libraries and elsewhere might have many Zarnegar files as a heritage. Being able to import and use these files can be very helpful to preserve them. More information about this format can be found here: Zarnegar (word processor) https://en.wikipedia.org/wiki/Zarnegar_(word_processor) The original software can be download from here: http://sinasoft.com/Downloads.html Two different versions of the program are available: * Zarnegar 5.2 (Windows): Has problems with Windows 10. The software interface is Persian. * Zarnegar 76 (DOS): Can be used with DOSBox https://www.dosbox.com/ Character encoding and examples: There are 2 common formats for Zarnegar: Zarnegar1 and Zarnegar75. Quoting from the wiki article above: "Zarnegar1 character set Zarnegar used an Iran System-based character encoding system, named Zarnegar1, with text file formats for its early versions, up to the Zarnegar 75 version. The Zarnegar1 character set is a two-form left-to-right (visual) encoding, meaning that every Perso-Arabic letter receives different character codes based on its cursive joining form, but most letters receive only two forms, because of the limited code-points available." A sample from the Python Zarnegar1 convertor: https://github.com/persian-computing/python-zarnegar-converter/blob/e3482740c34cba14e7c372a675c9166d213629be/samples/zar1-sample-text-01.zar Also from the same article: "Zarnegar75 character set With the Zarnegar 75 version, a new character encoding system was introduced, and the file format was changed to a binary format. The Zarnegar75 character set is a four-form bidirectional visual encoding, meaning that every Perso-Arabic letter receives a one, two, or four character code, depending on its cursive joining form, and these letters are stored in the memory in the semantic order." A sample Zarnegar75 binary file format is attached. Convertors: Some convertors available for Zarnegar file format. For example, this one for Zarnegar1 format is in Python, and provides some examples: Converter for Zarnegar Encoding and File Format to Unicode Text https://github.com/persian-computing/python-zarnegar-converter There is another (closed source) convertor that can convert Zarnegar format to RTF: https://www.noorsoft.org/file/downloads/productfile/Zarnegar.To_.RTF_.Converter_[www.noorsoft.org].zip -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152205] Wayland does not allow switching between multiples LibreOffice windows from the Window menu
https://bugs.documentfoundation.org/show_bug.cgi?id=152205 --- Comment #5 from Steve Sibelman --- I'm glad my symptom is reproducible. Wayland is definitely a work in progress. Thunderbird actually works better in Wayland than X11. fwiw, I'm using Ubuntu (Kubuntu) 22.04, KDE Plasma 5.24.7 KDE Frameworks Version 5.92.0 Qt Version 5.15.2 Kernel 5.15.0-53-generic (64-bit) running on a Core i7-7700T with 16GB of RAM. per etymonline.com, an on-line etymology resource I value: bollix (v.) "bungle, make a mess of," 1937, a respelling (perhaps euphemistic) of bollocks, from Old English beallucas "testicles," OK, I guess that's more than enough tangential chatter. Cheers! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136608] Cell borders not announced by screen readers
https://bugs.documentfoundation.org/show_bug.cgi?id=136608 --- Comment #4 from TammyM --- When using the screen reader NVDA, it announces the contents of the cell when tabbing. Also if the cells are empty, it still announces the cell number (A1) when tabbing left, right, up, or down the sheet. I did not hear it announce line left or line right as an example. Is it possible to let us know if you are still experiencing this issue? Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 651658d37bcb3f493942dd5d0b9a0d65c96f105c CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148876] Add Thai hyphenation patterns
https://bugs.documentfoundation.org/show_bug.cgi?id=148876 --- Comment #7 from Commit Notification --- Theppitak Karoonboonyanan committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/dictionaries/commit/2b234ba64f43d16b9393fb0cfdc794814065e838 tdf#148876 Adding Thai hyphenation patterns -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148876] Add Thai hyphenation patterns
https://bugs.documentfoundation.org/show_bug.cgi?id=148876 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: dictionaries
dictionaries |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 3b0b9fcb80242abcedc01eb388a57b1016916353 Author: Theppitak Karoonboonyanan AuthorDate: Sat Nov 26 05:07:30 2022 +0700 Commit: Gerrit Code Review CommitDate: Fri Nov 25 23:07:30 2022 +0100 Update git submodules * Update dictionaries from branch 'master' to 2b234ba64f43d16b9393fb0cfdc794814065e838 - tdf#148876 Adding Thai hyphenation patterns Change-Id: Ib9e6fe6350c6b8a4e9644315717fd744714a271a Reviewed-on: https://gerrit.libreoffice.org/c/dictionaries/+/141961 Reviewed-by: Andras Timar Tested-by: Andras Timar diff --git a/dictionaries b/dictionaries index 43a746e2dcbd..2b234ba64f43 16 --- a/dictionaries +++ b/dictionaries @@ -1 +1 @@ -Subproject commit 43a746e2dcbdea7b89172024a14e6c6f1738c95c +Subproject commit 2b234ba64f43d16b9393fb0cfdc794814065e838
[Libreoffice-commits] dictionaries.git: Dictionary_th.mk th_TH/description.xml th_TH/hyph_th_TH.dic th_TH/README_hyph_th_TH.txt
Dictionary_th.mk|2 th_TH/README_hyph_th_TH.txt | 13 th_TH/description.xml |4 th_TH/hyph_th_TH.dic| 5245 4 files changed, 5262 insertions(+), 2 deletions(-) New commits: commit 2b234ba64f43d16b9393fb0cfdc794814065e838 Author: Theppitak Karoonboonyanan AuthorDate: Fri Oct 28 16:21:38 2022 +0700 Commit: Andras Timar CommitDate: Fri Nov 25 23:07:29 2022 +0100 tdf#148876 Adding Thai hyphenation patterns Change-Id: Ib9e6fe6350c6b8a4e9644315717fd744714a271a Reviewed-on: https://gerrit.libreoffice.org/c/dictionaries/+/141961 Reviewed-by: Andras Timar Tested-by: Andras Timar diff --git a/Dictionary_th.mk b/Dictionary_th.mk index 59c5cb6..86c6f14 100644 --- a/Dictionary_th.mk +++ b/Dictionary_th.mk @@ -13,6 +13,8 @@ $(eval $(call gb_Dictionary_add_root_files,dict-th,\ dictionaries/th_TH/README_th_TH.txt \ dictionaries/th_TH/th_TH.aff \ dictionaries/th_TH/th_TH.dic \ + dictionaries/th_TH/README_hyph_th_TH.txt \ + dictionaries/th_TH/hyph_th_TH.dic \ )) # vim: set noet sw=4 ts=4: diff --git a/th_TH/README_hyph_th_TH.txt b/th_TH/README_hyph_th_TH.txt new file mode 100644 index 000..f435031 --- /dev/null +++ b/th_TH/README_hyph_th_TH.txt @@ -0,0 +1,13 @@ +Thai hyphenation patterns for LibreOffice.org +Version 1.0 (2022-04-30) + +License: LPPL 1.3+ + +Origin: + These Thai hyphenation patterns are based on word list from LibThai project, + manually hyphenated to be processed with patgen, plus additional processing, + by tex-hyphen project, and then converted for libhyphen using its + substrings.pl script. + +Author: + Theppitak Karoonboonyanan diff --git a/th_TH/description.xml b/th_TH/description.xml index b3a5f73..eb3fcd8 100644 --- a/th_TH/description.xml +++ b/th_TH/description.xml @@ -1,9 +1,9 @@ http://openoffice.org/extensions/description/2006; xmlns:d="http://openoffice.org/extensions/description/2006; xmlns:xlink="http://www.w3.org/1999/xlink;> - + -Thai spelling dictionary +Thai spelling dictionary and hyphenation rules diff --git a/th_TH/hyph_th_TH.dic b/th_TH/hyph_th_TH.dic new file mode 100644 index 000..168de23 --- /dev/null +++ b/th_TH/hyph_th_TH.dic @@ -0,0 +1,5245 @@ +UTF-8 +.ก6 +.กัน3 +.1กั2 +.ช6 +.ชี5วั2 +.1ชีว +.ช6ี +.ท6 +.ทัศ1น6ู5 +.1ทั2 +.ที6่3 +.ท6ี +.บ6 +.บ1ท1 +.ร6 +.รง4 +.ราย3 +.ร6า +.ล6 +.ล6ำ7 +.ส6 +.สู3ต +.1ส6ู +.ใบ3 +.7ใ6 +.ไฮ3 +.5ไ6 +2ก1ก +ก4ก1ม +กก4ส +2ก1ข2 +ก4ขค +กข5คณ +ก4ขช +กข5ช6า +ก4ขณ +ก5ข5ณ6ะ +ก5ข5ณ6า +ก4ขบ +กข5บ6ุ +ก4ขภ +กข5ภั2 +ก4ขม +ก5ข1มั2 +กข5ม6า +กข5ม6ู +กข5ร6า +ก4ข5ล6า +กข5ศั2 +ก4ขเ2 +กข5เ6ท +กข5เ6ว +ก4ข6์ +ก1ค +กง5บว +ก1จ +ก1ช +2กซ +กญ5จน +กฎ5หม +กฎห2 +กฎ5เก +กฎเ2 +กฏ5หม +กฏห2 +กณ5ฑั2 +ก5ดิน +กด6ิ +ก1ต +ก4ตด +กต5ด6ิ +ก4ตส +ก4ต1เ2 +ก1ท +ก1น +ก4น1ด +ก4นธ +ก1บ +ก1ป +กป4ร +ก1พ +ก1ฟ +ก1ม +ก4ม1ม +ก4ม1ส +ก4ม1เ2 +กย5ม6ุ +ก3ย6้ +กร5กฎ +ก2รก +ก5ร5ณั2 +กร5ต6๋ +1ก4รร +กร5ร6า +กร5ล6า +ก5รา1ค +กร6า +ก5รินท +กร6ิ +ก4ร6ู +กร5ไฟ +กร5ไ6 +กล5น1ค +กล5มห2 +ก2ว +ก5วัต +ก1วั2 +ก5ษณน +ก3ษ5ณ6ะ +ก5ษ1ณ6า +ก5ษ1ม6า +ก5ษ7ม6ี +กษ5เ6ท +กษเ2 +ก1ส +ก4สต +กส4น +ก4ส1โ6 +ก1ห2 +กอ5อ6ิ +1ก6ะ +กะ5ถั2 +กะ5ผล +1กั2 +1ก6า +กา5ก1บ +กา7น6ี +กา5น6้ +กา5บอ +ก6า5ฝ6า +กา7ฝ +กา5รอ +กา5ร6่ +กา5ส6ะ +กำ5ด6้ +ก6ำ7 +กำ5ทอ +กำ5ผล +1ก6ิ +กิ4ต +กิ5น6ี +ก6ิ5ฮ6ิ +กี5รณ +ก6ี +กี5รต +กี5สถ +1ก6ุ +กุ5งอ +กุ5ช6ิ +ก6ุ5ฎ6ุ +ก6ุ5ม6ุ +กุ5รร +กุ1ร +กุ5ล6ี +กุ5แห2 +กุแ6 +1ก6ู +กู5ปร +กู5รข2 +กู5รม +ก1เ2 +ก1แ6 +ก1โ6 +ก5ไ6 +ก่5กอ +ก6่ +ก่5บ6้ +ก6่5ป6่ +ก์5ท6็ +ก6์ +ข2 +ขม5ห6ิ +ขมห2 +4ขล6า +ขอ5ขม +ขอข2 +ขอ5ง6้ +ขอ5อภ +1ขั2 +1ข6า +ขา5ก6๊ +ขา5ทน +ขา1ท +ขิ5ป1ส +ข6ิ +ขี6้1 +ข6ี +ข่5ม6ุ +ข6่ +ข่ม1 +ข่5หง +ข่ห2 +ข้าว3 +ข6้ +ข้6า +ค1ค +ค1ช +คช5ส6ี +ค4ช1เ2 +ค4ณ6ิ +ค4ทร +ค1ท5ร6ี +คท5วอ +คน5ยอ +4ค1น6ิ +คป7ซ6ู +คป5ผก +3คมน +คม5ฟร +คม5ลอ +2คย +คร5ซอ +คร5นอ +คร5น6ี +คร5ปฐ +คร5ม1เ2 +คร5ร6้ +คร5ล6ิ +คร5ห6า +ครห2 +4ค5รัก +ครั2 +ค5รา1ต +คร6า +คฤ5หบ +คฤห2 +คฤ5ห6า +คฤ5โฆ +คฤโ6 +คล5ค6ู +ค5ลา1ภ +คล6า +ค2ว +คว5ทอ +3ค1ว6า +2คส +คส5ต6ิ +คห5กร +คห2 +ค2ห1ก +คห5น6ิ +คห5บด +คห5สถ +3คอน +1ค6า +คา5ป6ู +คา5พจ +คา5พ2ย +คา5ร1ว +คา5วจ +7ค6ำ7 +คำ5ด6ี +คำ5โอ +คำโ6 +คำ5ไก +คำ5ไ6 +1ค6ุ +คุ5ณ6ู +คุ5ล6ี +4คุ6์ +คู5ปอ +ค6ู +คู5ลอ +2ค1เ2 +ค1โ6 +2ค6์ +ค์7จ6ำ7 +1ฆ6า +ฆา5ณั2 +ง1ก +ง4ก1ห2 +ง4ก1เ2 +ง4ก6์ +ง1ข2 +ง4ขก +ง4ขต +งข5ร6ิ +ง1ค +ง4คจ +ง4ค1ช +ง5คชาต6ิ +งค1ช6า +งคชา2ต +ง4คญ +ง4คธ +ง4คบ +ง4คป +งค5วั2 +งค2ว +ง4คศ +ง4ค1โ6 +งฆ5ปร +งฆ5สภ +งฆ5เ6ถ +งฆเ2 +งฆ5เ6ภ +ง1ง +ง4ง1เ2 +ง1จ +ง1ฉ +ง1ช +ง4ช6ี +ง1ซ +ง1ด +ง1ต +ง1ท +ง1น +งบ5ด6ุ +ง1ป +ง1ผ +ง1พ +ง1ม +ง1ย +ง1ร +ง1ล +ง1ว +ง4ว1เ2 +ง1ส +งส4ก +งส5กล +ง4ส5ก6ุ +ง4สบ +ง4สพ +งส5พ2ย +ง4สภ +ง1ห2 +งห5น6า +ง4หบ +งห5บั2 +งห5ร6า +1ง6า +งา5ช6้ +งา5ร6ำ7 +7ง6ู +งู5ส4ว +ง1เ2 +ง1แ6 +ง1โ6 +ง5ไ6 +ง่5งอ +ง6่ +4จกร +จ1จ +จ4จว +จ1ฉ +จ4ฉท +จ4ฉน +จด5จ6่ +จต7จ6ำ7 +จต5ม6ู +จต5ร6ิ +จป4ก +จฟ5ฟร +จมบ5พ +จม1บ +3จริต +จร6ิ +จอ5งอ +1จั2 +1จ6า +จา5มร +จา5ร1ว +จา5ร6ึ +7จ6ำ7 +จำ5ท4ว +จำ5อว +1จ6ิ +จิ5จ6ู +จิ5ตอ +จ6ี7ด6ี +จ6ี +จุ5ฑ6า +จ6ุ +จุ5ส2ม +จู5ป6ิ +จ6ู +จู7ร6า +จ1เ2 +จ้6า1 +จ6้ +ฉก5ฉว +ฉ4กร +ฉก4ษ +ฉท5ท6ิ +ฉ4บั2 +ฉร5ฉ6ิ +1ฉั2 +1ฉ6า +ฉา5ก6๊
[Libreoffice-bugs] [Bug 148416] FILESAVE: Read-only passwords are not requested by default on save-as
https://bugs.documentfoundation.org/show_bug.cgi?id=148416 --- Comment #8 from Justin L --- While it may not be worth submitting the patch, I decided to try and write it anyway. It seems to work nicely. https://gerrit.libreoffice.org/c/core/+/143312 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140742] Copy/paste of row(s) to external programs omit initial empty columns (X11 clipboard)
https://bugs.documentfoundation.org/show_bug.cgi?id=140742 --- Comment #5 from Eike Rathke --- Things are different for Google Sheets and Gnumeric. Google Sheets (or the browser) requests text/html and text/rtf flavour exports (whatever it may use later when actually pasting). For these we do not export empty leading (and obviously trailing neither) empty columns or rows of the selection. And I'd rather not change that. For the "(415)" to -415 that's a Google thing to interpret data (there are no data types in the HTML output) and at least in an en-US locale parentheses may indicate negative values, same in Calc. And I can't confirm that it would be different for a single cell being copy-pasted. It may be different in other locales. Gnumeric requests an ODF text/xml from the clipboard, that writes the internal clipboard document as if saved as ODF, whatever Gnumeric does with the result it skips leading empty rows and columns and pastes starting from content to the current cell cursor position. Which makes sense, see below. Similar happens when copying between different LO Calc processes, though with a application/x-openoffice-embed-source-xml flavour as known internal format (which in fact is ODF as well). For that I can tell it is on purpose, probably similar in Gnumeric, or rather inevitable as the data read has no indication what the original selection of the other application was, so data is pasted from the first data start in the resulting clipboard import with the encompassing data area. There isn't much we can do, except for the ODF format add a format extension to store the last selection as well and use that when pasting, but I'm not convinced that is a good idea. For example, using Ctrl+A and copy you certainly do not want the target to be entirely cleared except the few pasted content cells. Nor would things work the same if the current cell cursor position was not in the first column/row. So some magic when and how to evaluate that would be required anyway, making things more complicate to understand for people. It's more straight forward and consistent to always paste starting with data content to the current cell cursor position. I tend to close this as won't fix. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/jsdialog
vcl/jsdialog/enabled.cxx |7 +++ 1 file changed, 7 insertions(+) New commits: commit 254e56c0c05015db1cbfd20c1e5a48703d3bd136 Author: Michael Meeks AuthorDate: Fri Nov 25 19:08:38 2022 + Commit: Michael Meeks CommitDate: Fri Nov 25 22:15:13 2022 +0100 jsdialog: white-list calc group/un-group & row/col metric dialogs. They're simple dialogs, and are testd. Change-Id: I5a34314f57e058bc66a718c1e85ed52b265752e2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143262 Tested-by: Jenkins Reviewed-by: Michael Meeks diff --git a/vcl/jsdialog/enabled.cxx b/vcl/jsdialog/enabled.cxx index 47d8e0e08df5..79960d687f14 100644 --- a/vcl/jsdialog/enabled.cxx +++ b/vcl/jsdialog/enabled.cxx @@ -52,6 +52,13 @@ bool isBuilderEnabled(std::u16string_view rUIFile, bool bMobile) || rUIFile == u"modules/scalc/ui/datafieldoptionsdialog.ui" || rUIFile == u"modules/scalc/ui/insertcells.ui" || rUIFile == u"modules/scalc/ui/deletecells.ui" +|| rUIFile == u"modules/scalc/ui/deletecontents.ui" +|| rUIFile == u"modules/scalc/ui/ungroupdialog.ui" +|| rUIFile == u"modules/scalc/ui/groupdialog.ui" +|| rUIFile == u"modules/scalc/ui/rowheightdialog.ui" +|| rUIFile == u"modules/scalc/ui/optimalrowheightdialog.ui" +|| rUIFile == u"modules/scalc/ui/colwidthdialog.ui" +|| rUIFile == u"modules/scalc/ui/optimalcolwidthdialog.ui" || rUIFile == u"svx/ui/fontworkgallerydialog.ui" || rUIFile == u"svx/ui/findreplacedialog.ui" || rUIFile == u"svx/ui/findreplacedialog.ui" || rUIFile == u"cui/ui/macroselectordialog.ui" || rUIFile == u"uui/ui/macrowarnmedium.ui"
[Libreoffice-bugs] [Bug 120348] Copy-paste of line chart to another spreadsheet results in data loss if the data-range of the chart contains cells that have value ERR:502
https://bugs.documentfoundation.org/show_bug.cgi?id=120348 --- Comment #11 from Commit Notification --- Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6e9b99ffe0083060176dc782986d3b441b7e48ec tdf#120348: move UItest to CppUnittest It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120348] Copy-paste of line chart to another spreadsheet results in data loss if the data-range of the chart contains cells that have value ERR:502
https://bugs.documentfoundation.org/show_bug.cgi?id=120348 Commit Notification changed: What|Removed |Added Whiteboard|target:7.2.0 target:7.1.1 |target:7.2.0 target:7.1.1 |target:7.0.5|target:7.0.5 target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: chart2/CppunitTest_chart2_uichart.mk chart2/Module_chart2.mk chart2/qa sc/qa
chart2/CppunitTest_chart2_uichart.mk | 58 ++
chart2/Module_chart2.mk |1
chart2/qa/extras/uichart.cxx | 108 +++
sc/qa/uitest/chart2/tdf120348.py | 61 ---
4 files changed, 167 insertions(+), 61 deletions(-)
New commits:
commit 6e9b99ffe0083060176dc782986d3b441b7e48ec
Author: Xisco Fauli
AuthorDate: Fri Nov 25 14:38:48 2022 +0100
Commit: Xisco Fauli
CommitDate: Fri Nov 25 21:28:10 2022 +0100
tdf#120348: move UItest to CppUnittest
for that, create a new CppunitTest_chart2_uichart
in chart2
Change-Id: Ie4cdaff4a1dd623c7788ed7acdd5ef135f403e84
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143305
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
diff --git a/chart2/CppunitTest_chart2_uichart.mk
b/chart2/CppunitTest_chart2_uichart.mk
new file mode 100644
index ..9e464e0a7c6f
--- /dev/null
+++ b/chart2/CppunitTest_chart2_uichart.mk
@@ -0,0 +1,58 @@
+# -*- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t -*-
+#*
+#
+# This file is part of the LibreOffice project.
+#
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+#
+#*
+
+$(eval $(call gb_CppunitTest_CppunitTest,chart2_uichart))
+
+$(eval $(call gb_CppunitTest_use_externals,chart2_uichart, \
+ boost_headers \
+ libxml2 \
+))
+
+$(eval $(call gb_CppunitTest_add_exception_objects,chart2_uichart, \
+chart2/qa/extras/uichart \
+))
+
+$(eval $(call gb_CppunitTest_use_libraries,chart2_uichart, \
+comphelper \
+cppu \
+cppuhelper \
+i18nlangtag \
+sal \
+sc \
+sfx \
+subsequenttest \
+svl \
+svl \
+svx \
+svxcore \
+test \
+tl \
+unotest \
+utl \
+vcl \
+))
+
+$(eval $(call gb_CppunitTest_set_include,chart2_uichart,\
+ -I$(SRCDIR)/chart2/qa/extras \
+-I$(SRCDIR)/chart2/inc \
+$$(INCLUDE) \
+))
+
+$(eval $(call gb_CppunitTest_use_sdk_api,chart2_uichart))
+
+$(eval $(call gb_CppunitTest_use_ure,chart2_uichart))
+$(eval $(call gb_CppunitTest_use_vcl,chart2_uichart))
+
+$(eval $(call gb_CppunitTest_use_rdb,chart2_uichart,services))
+
+$(eval $(call gb_CppunitTest_use_configuration,chart2_uichart))
+
+# vim: set noet sw=4 ts=4:
diff --git a/chart2/Module_chart2.mk b/chart2/Module_chart2.mk
index 1a26ebd2b959..5f7fd5aee961 100644
--- a/chart2/Module_chart2.mk
+++ b/chart2/Module_chart2.mk
@@ -37,6 +37,7 @@ $(eval $(call gb_Module_add_slowcheck_targets,chart2,\
CppunitTest_chart2_dump \
CppunitTest_chart2_pivot_chart_test \
CppunitTest_chart2_geometry \
+CppunitTest_chart2_uichart \
))
ifeq ($(WITH_FONTS), TRUE)
diff --git a/sc/qa/uitest/data/tdf120348.ods
b/chart2/qa/extras/data/ods/tdf120348.ods
similarity index 100%
rename from sc/qa/uitest/data/tdf120348.ods
rename to chart2/qa/extras/data/ods/tdf120348.ods
diff --git a/chart2/qa/extras/uichart.cxx b/chart2/qa/extras/uichart.cxx
new file mode 100644
index ..b6e2cb417643
--- /dev/null
+++ b/chart2/qa/extras/uichart.cxx
@@ -0,0 +1,108 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+#include "charttest.hxx"
+
+#include
+#include
+
+#include
+
+using namespace ::com::sun::star;
+
+class Chart2UiChartTest : public ChartTest
+{
+public:
+Chart2UiChartTest()
+: ChartTest("/chart2/qa/extras/data/")
+{
+}
+};
+
+CPPUNIT_TEST_FIXTURE(Chart2UiChartTest, testTdf120348)
+{
+loadFromURL(u"ods/tdf120348.ods");
+uno::Reference xChartDoc = getChartDocFromSheet(0,
mxComponent);
+CPPUNIT_ASSERT(xChartDoc.is());
+
+uno::Reference xDocument(mxComponent,
uno::UNO_QUERY_THROW);
+uno::Reference xIndex(xDocument->getSheets(),
uno::UNO_QUERY_THROW);
+uno::Reference xSheet(xIndex->getByIndex(0),
uno::UNO_QUERY_THROW);
+
+std::vector> aExpected;
+
+for (sal_Int32 nRowIdx = 1; nRowIdx < 159; ++nRowIdx)
+{
+std::vector aRow;
+for (sal_Int32 nColIdx = 5; nColIdx < 9; ++nColIdx)
+{
+uno::Reference xCell =
xSheet->getCellByPosition(nColIdx, nRowIdx);
+aRow.push_back(xCell->getValue());
+}
+aExpected.push_back(aRow);
+}
+
+uno::Sequence aPropertyValues = {
+comphelper::makePropertyValue("ToObject", OUString("Object 2")),
+};
+dispatchCommand(mxComponent, ".uno:GoToObject", aPropertyValues);
+
[Libreoffice-commits] core.git: sw/qa test/qa test/source
sw/qa/extras/ooxmlexport/ooxmlexport17.cxx |6 +++---
test/qa/cppunit/test_xpath.cxx |6 ++
test/source/xmltesttools.cxx |6 +-
3 files changed, 6 insertions(+), 12 deletions(-)
New commits:
commit c802c5f390a30a66118f56a01e47772a54743a6a
Author: Mike Kaganski
AuthorDate: Fri Nov 25 19:26:46 2022 +0300
Commit: Mike Kaganski
CommitDate: Fri Nov 25 20:57:39 2022 +0100
Require valid attribute in getXPath
The reason for accepting empty attribute was eliminated in commit
2f91ab025de850fe5af8114565755a8deed55911 (Merge two assertXPath
overloads that both check number of nodes, Nov 25 16:36:57 2022)
Change-Id: I6cd77eb0f73650dfdafd55946b5269ffe3f0bde5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143304
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
index e294a51feabb..87e7d0c68b21 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
@@ -873,7 +873,7 @@ DECLARE_OOXMLEXPORT_TEST(testTdf81507, "tdf81507.docx")
CPPUNIT_ASSERT_EQUAL(OUString("0"), getXPath(pXmlDoc,
"/w:document/w:body/w:p[2]/w:sdt/w:sdtPr/w:text", "multiLine"));
// Ensure that we have
-getXPath(pXmlDoc, "/w:document/w:body/w:p[3]/w:sdt/w:sdtPr/w:text", "");
+assertXPath(pXmlDoc, "/w:document/w:body/w:p[3]/w:sdt/w:sdtPr/w:text");
// Ensure that we have no (not quite correct case, but to ensure
import/export are okay)
xmlXPathObjectPtr pXmlObj = getXPathNode(pXmlDoc,
"/w:document/w:body/w:p[4]/w:sdt/w:sdtPr/w:text");
@@ -974,8 +974,8 @@ DECLARE_OOXMLEXPORT_TEST(testTdf148455_2,
"tdf148455_2.docx")
xmlDocUniquePtr pNumberingDoc = parseExport("word/numbering.xml");
// Ensure we have empty lvlOverride for levels 0 - 1
-getXPath(pNumberingDoc, "/w:numbering/w:num[@w:numId='" +
OString::number(nListId) +"']/w:lvlOverride[@w:ilvl='0']", "");
-getXPath(pNumberingDoc, "/w:numbering/w:num[@w:numId='" +
OString::number(nListId) +"']/w:lvlOverride[@w:ilvl='1']", "");
+assertXPath(pNumberingDoc, "/w:numbering/w:num[@w:numId='" +
OString::number(nListId) +"']/w:lvlOverride[@w:ilvl='0']");
+assertXPath(pNumberingDoc, "/w:numbering/w:num[@w:numId='" +
OString::number(nListId) +"']/w:lvlOverride[@w:ilvl='1']");
// And normal override for level 2
getXPath(pNumberingDoc, "/w:numbering/w:num[@w:numId='" +
OString::number(nListId) +"']/w:lvlOverride[@w:ilvl='2']/w:startOverride",
"val");
}
diff --git a/test/qa/cppunit/test_xpath.cxx b/test/qa/cppunit/test_xpath.cxx
index c622e59617ec..599ae8dbcfc1 100644
--- a/test/qa/cppunit/test_xpath.cxx
+++ b/test/qa/cppunit/test_xpath.cxx
@@ -25,15 +25,13 @@ CPPUNIT_TEST_FIXTURE(TestXPath, test_getXPath)
xmlDocUniquePtr pTable(xmlParseDoc(s_xml));
CPPUNIT_ASSERT(pTable);
// Must get existing element content without errors
-CPPUNIT_ASSERT_ASSERTION_PASS(getXPath(pTable, "/xml/item", ""));
+CPPUNIT_ASSERT_ASSERTION_PASS(assertXPath(pTable, "/xml/item"));
// Must error out when getting non-existing element
-CPPUNIT_ASSERT_ASSERTION_FAIL(getXPath(pTable, "/xml/no_item", ""));
+CPPUNIT_ASSERT_ASSERTION_FAIL(assertXPath(pTable, "/xml/no_item"));
// Must get existing attribute value correctly
CPPUNIT_ASSERT_ASSERTION_PASS(getXPath(pTable, "/xml/item", "attrib"));
// Must fail when requested non-empty attribute doesn't exist
CPPUNIT_ASSERT_ASSERTION_FAIL(getXPath(pTable, "/xml/item", "no_attrib"));
-// Must return empty string if not asking an attribute, regardless what is
its content
-CPPUNIT_ASSERT_EQUAL(OUString(), getXPath(pTable, "/xml/item", ""));
// Must properly return attribute content
CPPUNIT_ASSERT_EQUAL(OUString("val"), getXPath(pTable, "/xml/item",
"attrib"));
// Trying to get position of missing child of a node must fail assertion
diff --git a/test/source/xmltesttools.cxx b/test/source/xmltesttools.cxx
index e329bc968760..7cf4bb53c6d9 100644
--- a/test/source/xmltesttools.cxx
+++ b/test/source/xmltesttools.cxx
@@ -88,11 +88,7 @@ OUString XmlTestTools::getXPath(const xmlDocUniquePtr&
pXmlDoc, const OString& r
xmlNodeSetPtr pXmlNodes = pXmlObj->nodesetval;
CPPUNIT_ASSERT_EQUAL_MESSAGE(OString(OString::Concat("In <") +
pXmlDoc->name + ">, XPath '" + rXPath + "' number of nodes is
incorrect").getStr(),
1, xmlXPathNodeSetGetLength(pXmlNodes));
-if (rAttribute.isEmpty())
-{
-xmlXPathFreeObject(pXmlObj);
-return OUString();
-}
+CPPUNIT_ASSERT(!rAttribute.isEmpty());
xmlNodePtr pXmlNode = pXmlNodes->nodeTab[0];
xmlChar * prop = xmlGetProp(pXmlNode, BAD_CAST(rAttribute.getStr()));
OString sAttAbsent = OString::Concat("In <") + pXmlDoc->name + ">, XPath
'" + rXPath
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - include/test sw/qa sw/source test/source
include/test/xmltesttools.hxx |4 ++
sw/qa/extras/ooxmlexport/data/tdf152200-field+textbox.docx |binary
sw/qa/extras/ooxmlexport/ooxmlexport18.cxx | 23 +
sw/source/filter/ww8/wrtw8nds.cxx |8
test/source/xmltesttools.cxx | 12 +-
5 files changed, 44 insertions(+), 3 deletions(-)
New commits:
commit 4fbdc82cb3afce1f067ae45253b2fe50678cb948
Author: Mike Kaganski
AuthorDate: Fri Nov 25 15:20:48 2022 +0300
Commit: Mike Kaganski
CommitDate: Fri Nov 25 20:56:02 2022 +0100
tdf#152200: Make sure to not write objects into field character runs
Similar how it's done for preceding objects immediately after calculating
'ofs', we also need to make sure to create a separate run for the objects
that may be anchored after the last character; otherwise, the field that
was just processed (and is waiting in the attributes) would be put out of
place, inside an inner run (e.g., in a text box inside the object).
Change-Id: I2702693595acf4befdbd25ef07a9f7c444926aab
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143297
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
(cherry picked from commit ec345c02d8fa5a7c7d4ea4ad08ae7be5303d9b20)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143259
Tested-by: Jenkins CollaboraOffice
diff --git a/include/test/xmltesttools.hxx b/include/test/xmltesttools.hxx
index a4f0ef30d8ba..e37638fa674c 100644
--- a/include/test/xmltesttools.hxx
+++ b/include/test/xmltesttools.hxx
@@ -61,6 +61,10 @@ protected:
* Useful for checking relative order of elements.
*/
int getXPathPosition(const xmlDocUniquePtr& pXmlDoc, const
OString& rXPath, std::string_view rChildName);
+/**
+ * Get the number of the nodes returned by the rXPath.
+ */
+int countXPathNodes(const xmlDocUniquePtr& pXmlDoc, const
OString& rXPath);
/**
* Assert that rXPath exists, and returns exactly one node.
*/
diff --git a/sw/qa/extras/ooxmlexport/data/tdf152200-field+textbox.docx
b/sw/qa/extras/ooxmlexport/data/tdf152200-field+textbox.docx
new file mode 100644
index ..606d1346a27a
Binary files /dev/null and
b/sw/qa/extras/ooxmlexport/data/tdf152200-field+textbox.docx differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
index 2d5cca60eb27..c0d3e7c6d161 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
@@ -92,6 +92,29 @@ CPPUNIT_TEST_FIXTURE(Test, testImageCropping)
CPPUNIT_ASSERT_EQUAL(sal_Int32(0), aGraphicCropStruct.Bottom);
}
+CPPUNIT_TEST_FIXTURE(Test, testTdf152200)
+{
+// Given a document with a fly anchored after a FORMTEXT in the end of the
paragraph:
+// When exporting that back to DOCX:
+loadAndSave("tdf152200-field+textbox.docx");
+
+// Then make sure that fldChar with type 'end' goes prior to the at-char
anchored fly.
+xmlDocUniquePtr pXmlDoc = parseExport("word/document.xml");
+const int nRunsBeforeFldCharEnd = countXPathNodes(pXmlDoc,
"//w:fldChar[@w:fldCharType='end']/preceding::w:r");
+CPPUNIT_ASSERT(nRunsBeforeFldCharEnd);
+const int nRunsBeforeAlternateContent = countXPathNodes(pXmlDoc,
"//mc:AlternateContent/preceding::w:r");
+CPPUNIT_ASSERT(nRunsBeforeAlternateContent);
+// Without the accompanying fix in place, this test would have failed with:
+// - Expected greater than: 6
+// - Actual : 5
+CPPUNIT_ASSERT_GREATER(nRunsBeforeFldCharEnd, nRunsBeforeAlternateContent);
+// Make sure we only have one paragraph in body, and only three field
characters overal,
+// located directly in runs of this paragraph
+assertXPath(pXmlDoc, "/w:document/w:body/w:p");
+assertXPath(pXmlDoc, "/w:document/w:body/w:p/w:r/w:fldChar", 3);
+assertXPath(pXmlDoc, "//w:fldChar", 3); // no field characters elsewhere
+}
+
CPPUNIT_PLUGIN_IMPLEMENT();
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/filter/ww8/wrtw8nds.cxx
b/sw/source/filter/ww8/wrtw8nds.cxx
index 595b700fc663..423b8dc3ee81 100644
--- a/sw/source/filter/ww8/wrtw8nds.cxx
+++ b/sw/source/filter/ww8/wrtw8nds.cxx
@@ -2654,6 +2654,14 @@ void MSWordExportBase::OutputTextNode( SwTextNode& rNode
)
bPostponeWritingText = false ;
AttrOutput().RunText( aSnippet, eChrSet );
}
+
+if (ofs == 1 && nNextAttr == nEnd)
+{
+// tdf#152200: There could be flys anchored after the last
position; make sure
+// to provide a separate run after field character to
write them
+AttrOutput().EndRun(, nCurrentPos, -1, nNextAttr ==
nEnd);
+AttrOutput().StartRun(pRedlineData, nCurrentPos,
bSingleEmptyRun);
+}
[Libreoffice-bugs] [Bug 39937] Missing dc:language metadata element for default language
https://bugs.documentfoundation.org/show_bug.cgi?id=39937 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||3036 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103036] rework document Language Setting into a dedicated dialog (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=103036 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=39 ||937 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103036] rework document Language Setting into a dedicated dialog (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=103036 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1906 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151906] If documents have a "document language", allow viewing and setting it
https://bugs.documentfoundation.org/show_bug.cgi?id=151906 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||3036 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152030] Allow regular deletion of selection containing an entire generated index/table
https://bugs.documentfoundation.org/show_bug.cgi?id=152030 --- Comment #11 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #10) > What I personally would agree on is to delete (protected) ToC if the > selection includes the whole ToC like known from tables. This is exactly what I've asked in the opening comment. And speaking of regular tables, I said in the design meeting the other day that it makes little sense for user-generated table content to have less protection against deletion than auto-generated table content, which can always be regenerated if necessary. So, let's do just this :-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152226] New: Crashed using Base: Create Report in Design View, changing report data type from table to query
https://bugs.documentfoundation.org/show_bug.cgi?id=152226 Bug ID: 152226 Summary: Crashed using Base: Create Report in Design View, changing report data type from table to query Product: LibreOffice Version: 7.3.7.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nigel.bla...@btinternet.com Description: Screen goes black but able to recover by clicking through the report navigator (Functions, Page Header, Groups, Detail, Page Footer) in turn and then clicking on the Page Footer on the left of the screen whereupon normal colours return. I can then work on and save save the report but when I close the report editor an error box appears asking me to close LibreOffice and send a crash report. When I restart LibreOffice the document is recovered and the report is there as I saved it and I can continue working on it - all OK unless I change the report data type again, when the process is repeated. Steps to Reproduce: 1.Open Base Report in Design View 2.Change report data type from table to query or vice versa 3. Actual Results: Screen instantly goes black Expected Results: Screen should remain workable Reproducible: Always User Profile Reset: No Additional Info: If you click through the report navigator (Functions, Page Header, Groups, Detail, Page Footer) in turn and then click on the Page Footer on the left of the screen then normal colours return and its possible to continue working, save and close the report, but then a bug report is generated. That should not happen - I don't know when I last used the report generator but I have not had the problem with earlier releases. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152224] Table Borders bugged by RTL Paragraph Style
https://bugs.documentfoundation.org/show_bug.cgi?id=152224 Naufal Abdulbaasith changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Naufal Abdulbaasith --- Updated to the last version and never see this bug occurs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151549] No UI for manipulating a section other than Format | Sections
https://bugs.documentfoundation.org/show_bug.cgi?id=151549 --- Comment #7 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #5) > Well, the summary is "No UI for manipulating a section...". I'm not against > a command Hide in the context menu but the other functions are > over-engineering. Ok, fair enough about the requests exceeding UI availability - that merits a separate bug. Let's limit this to some/most/all of the functionality currently available via Format | Sections. In that dialog we have: * Hide * Delete * Link to contents of another file <- actually I don't quite understand what kind of link this is, it looks like it just copies the contents and the help page says the same * Protect * Make editable (in a read-only document) * Open "Options" dialog ... and perhaps open the Format | Sections dialog with a focus on the right-clicked section. Hide, Delete, and Options are definitely necessary; and probably also opening the Format | Sections dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152225] FILESAVE PDF PAC tool reports "Possibly inappropriate use of a Div structure element"
https://bugs.documentfoundation.org/show_bug.cgi?id=152225 --- Comment #2 from Gabor Kelemen (allotropia) --- Created attachment 183792 --> https://bugs.documentfoundation.org/attachment.cgi?id=183792=edit Screenshot of the issue in the PAC tool -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152225] FILESAVE PDF PAC tool reports "Possibly inappropriate use of a Div structure element"
https://bugs.documentfoundation.org/show_bug.cgi?id=152225 --- Comment #1 from Gabor Kelemen (allotropia) --- Created attachment 183791 --> https://bugs.documentfoundation.org/attachment.cgi?id=183791=edit The example file exported to PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139007] [META] PDF accessibility
https://bugs.documentfoundation.org/show_bug.cgi?id=139007 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||152225 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152225 [Bug 152225] FILESAVE PDF PAC tool reports "Possibly inappropriate use of a Div structure element" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152225] New: FILESAVE PDF PAC tool reports "Possibly inappropriate use of a Div structure element"
https://bugs.documentfoundation.org/show_bug.cgi?id=152225 Bug ID: 152225 Summary: FILESAVE PDF PAC tool reports "Possibly inappropriate use of a Div structure element" Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com Blocks: 139007 Created attachment 183790 --> https://bugs.documentfoundation.org/attachment.cgi?id=183790=edit Example file with frame When the attached file with a frame is exported to PDF with PDF/UA enabled and the file is checked in the PAC tool, the reported error is "Possibly inappropriate use of a Div structure element" 1, Open attached file 2, Export it as PDF, with enabled PDF/UA option 3, Check with the PAC tool: https://pdfua.foundation/en/pdf-accessibility-checker-pac PAC would report the error on the attached screenshot. VeraPDF https://demo.verapdf.org/ with PDF/UA setting on the second page reports no error. Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5116d6ad85d804e7b7897bc57a4a4bf9d5bed4f1 CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (hu_HU); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139007 [Bug 139007] [META] PDF accessibility -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152224] Table Borders bugged by RTL Paragraph Style
https://bugs.documentfoundation.org/show_bug.cgi?id=152224 Naufal Abdulbaasith changed: What|Removed |Added Severity|minor |normal -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152224] Table Borders bugged by RTL Paragraph Style
https://bugs.documentfoundation.org/show_bug.cgi?id=152224 Naufal Abdulbaasith changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152224] Table Borders bugged by RTL Paragraph Style
https://bugs.documentfoundation.org/show_bug.cgi?id=152224 Naufal Abdulbaasith changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Naufal Abdulbaasith --- Corrections: The bug happens because the text direction property for the troublesome tables is set to `Right-to-Left`. So, any work that leads to that will results in the same bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152224] New: Table Borders bugged by RTL Paragraph Style
https://bugs.documentfoundation.org/show_bug.cgi?id=152224 Bug ID: 152224 Summary: Table Borders bugged by RTL Paragraph Style Product: LibreOffice Version: 7.3.6.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: unkin...@gmail.com Description: It seems that Right-to-Left Paragraph Alignment makes the borders of new-created tables not fill all its borders, specifically the before most left and the before most right. For example, after I set the mentioned style for Default Paragraph Style, and create a new table with more than three columns; then the right border of the left column and the left border of the right column will not be affected by any applied border style for that table. Steps to Reproduce: 1. Open a document or make a new one in LibreOffice Writer. 2. Open `Modify` UI of `Default Paragraph Style`. 3. Go to Tab `Alignment`. 4. In `Properties` section, set the `Text Direction` to `Right-to-Left`. 5. Create a new table with more than three columns. 6. Apply any visible border style to it. &. The bug occurs. Actual Results: Two line borders of the table will not be affected by the style application. To be more specific, these are the right line borders of the left column and the left line borders of the right column. Expected Results: All line borders should be affected by the style application. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.3.6.2 (x64) / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: id-ID (id_ID); UI: en-US Calc: CL 1. It only happens when the RTL style has been applied for `Default Paragraph Style`. If the same application is worked on other styles, no bug will occur. 2. If the work is reset to default, the created table still holds the bug. But new tables after that will behave normally as long as `Default Paragraph Style` is not modified as before again. 3. The bug only occurs if the created tables have more than three columns. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152095] Enhancement request : adding 'Data - Refresh all ranges' command
https://bugs.documentfoundation.org/show_bug.cgi?id=152095 ocleyr2lal...@zaclys.net changed: What|Removed |Added CC||ocleyr2lal...@zaclys.net --- Comment #4 from ocleyr2lal...@zaclys.net --- It would be great if we could refresh all ranges in only one operation. On Stéphane's example, other sheets are not hidden. The subject is why refresh range by range and not sheet by sheet or for the whole workbook, when several ranges (on several sheets) depend on the same data ? I also agree with Heiko's comment. Care must be taken with this type of command. But we could ask for confirmation before refresh all ranges. Of course, the current function would still be relevant, but it would be a really nice improvement. Thanks Claire -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148416] FILESAVE: Read-only passwords are not requested by default on save-as
https://bugs.documentfoundation.org/show_bug.cgi?id=148416 --- Comment #7 from Justin L --- (In reply to Justin L from comment #6) > I think the key to fixing this is to get that dialog to expand and default > to m_xOpenReadonlyCB->set_active(IsLoadReadonly()) Doing so requires adding an entry to -offapi/com/sun/star/task/DocumentPasswordRequest2.idl -offapi/com/sun/star/task/DocumentMSPasswordRequest2.idl It just doesn't seem worth it for this minor annoyance. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144774] Crash when you try to install a Turkish dictionary
https://bugs.documentfoundation.org/show_bug.cgi?id=144774 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #6 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I don't reproduce the crash but perhaps it's Windows only? -- You are receiving this mail because: You are the assignee for the bug.
Re: WollMux adoption proposal for The Document Foundation
Indeed, Tomaž indicated the same and no pb for me if it stays an external extension./ /
[Libreoffice-commits] core.git: sd/qa sw/qa
sd/qa/unit/layout-tests.cxx |4 +-
sw/qa/extras/uiwriter/uiwriter3.cxx | 50 ++--
2 files changed, 22 insertions(+), 32 deletions(-)
New commits:
commit 66e93c7a74af4d7078762ef4f2071e2f8ae15c27
Author: Mike Kaganski
AuthorDate: Fri Nov 25 19:25:23 2022 +0300
Commit: Mike Kaganski
CommitDate: Fri Nov 25 18:59:02 2022 +0100
Simplification
Change-Id: Ib72d4eb95879f94efad3834b133400e76f1b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143303
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sd/qa/unit/layout-tests.cxx b/sd/qa/unit/layout-tests.cxx
index d2bf22622885..36293f2dcfe2 100644
--- a/sd/qa/unit/layout-tests.cxx
+++ b/sd/qa/unit/layout-tests.cxx
@@ -72,8 +72,8 @@ CPPUNIT_TEST_FIXTURE(SdLayoutTest, testTdf146876)
{
const OString xPath = "/metafile/push[1]/push[1]/push[" +
OString::number(i)
+ "]/polyline/point[" + OString::number(j) +
"]";
-const sal_Int32 nX = getXPath(pXmlDoc, xPath.getStr(),
"x").toInt32();
-const sal_Int32 nY = getXPath(pXmlDoc, xPath.getStr(),
"y").toInt32();
+const sal_Int32 nX = getXPath(pXmlDoc, xPath, "x").toInt32();
+const sal_Int32 nY = getXPath(pXmlDoc, xPath, "y").toInt32();
// Without the fix in place, this test would have failed with
// - Expected greater or equal than: 5000
diff --git a/sw/qa/extras/uiwriter/uiwriter3.cxx
b/sw/qa/extras/uiwriter/uiwriter3.cxx
index ebdce194e9cd..f1b50f047234 100644
--- a/sw/qa/extras/uiwriter/uiwriter3.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter3.cxx
@@ -401,35 +401,30 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest3, testTdf147126)
for (auto nFly = 1; nFly < 8; ++nFly)
{
const auto nFlyLeft = getXPath(pLayoutXML1,
-
OString::Concat("/root/page/body/txt[2]/anchored/fly[")
- +
OString::Concat(OString::number(nFly))
- + OString::Concat("]/infos/bounds"),
+ "/root/page/body/txt[2]/anchored/fly["
+ + OString::number(nFly) +
"]/infos/bounds",
"left")
.toInt64();
const auto nFlyRight = getXPath(pLayoutXML1,
-
OString::Concat("/root/page/body/txt[2]/anchored/fly[")
-+
OString::Concat(OString::number(nFly))
-+
OString::Concat("]/infos/bounds"),
+"/root/page/body/txt[2]/anchored/fly["
++ OString::number(nFly) +
"]/infos/bounds",
"width")
.toInt64();
const auto nFlyTop = getXPath(pLayoutXML1,
-
OString::Concat("/root/page/body/txt[2]/anchored/fly[")
- +
OString::Concat(OString::number(nFly))
- + OString::Concat("]/infos/bounds"),
+ "/root/page/body/txt[2]/anchored/fly[" +
OString::number(nFly)
+ + "]/infos/bounds",
"top")
.toInt64();
const auto nFlyBottom = getXPath(pLayoutXML1,
-
OString::Concat("/root/page/body/txt[2]/anchored/fly[")
- +
OString::Concat(OString::number(nFly))
- +
OString::Concat("]/infos/bounds"),
+ "/root/page/body/txt[2]/anchored/fly["
+ + OString::number(nFly) +
"]/infos/bounds",
"height")
.toInt64();
const auto sDrawRect = getXPath(
pLayoutXML1,
-
OString::Concat("/root/page/body/txt[2]/anchored/SwAnchoredDrawObject/SdrObjGroup/"
-"SdrObjList/SdrObject[")
-+ OString::Concat(OString::number(nFly)) +
OString::Concat("]"),
+
"/root/page/body/txt[2]/anchored/SwAnchoredDrawObject/SdrObjGroup/SdrObjList/SdrObject["
++ OString::number(nFly) + "]",
"aOutRect");
const auto nComaPos1 = sDrawRect.indexOf(',', 0);
@@ -465,35 +460,30 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest3, testTdf147126)
for (auto nFly = 1; nFly < 8; ++nFly)
{
const auto nFlyLeft = getXPath(pLayoutXML2,
-
OString::Concat("/root/page/body/txt[6]/anchored/fly[")
-
[Libreoffice-bugs] [Bug 113665] Visual bug with spelling check turned on
https://bugs.documentfoundation.org/show_bug.cgi?id=113665 --- Comment #14 from Buovjaga --- (In reply to horus from comment #13) > I'm using the latest version 7.4.2.1: > > The problem of this bug is resolved. That is, there's no more extra spacing > between the letter s and the letter h when spelling check is ON (with the > sample ODS file). Good! > > PS: But the whole string with "Liberation Sans" font moves horizontally one > or two pixels. But that's another incident and I don't care. That's great to hear. Caolán was working a lot on that topic lately and it is possible that there are even further improvements in upcoming versions. If you like, you can download Win-x86_64@tb77-TDF from https://dev-builds.libreoffice.org/daily/master/current.html to test the very latest. It installs separately and will not mess with your stable version. In case the small movement still exists in the latest build, you could open a new report for it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152149] Can't Open "What's New" video to FULLSCREEN
https://bugs.documentfoundation.org/show_bug.cgi?id=152149 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report! Unfortunately, website issues should be reported on Redmine: https://redmine.documentfoundation.org/ Know that the website should be completely overhauled soon, so you might want to hold off reporting until that new version is available. -- You are receiving this mail because: You are the assignee for the bug.
