[Libreoffice-bugs] [Bug 103956] RTF table import wrong: cellx issue (minimal testcases)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103956

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:7.6.0|target:7.6.0 target:7.5.0.2

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sw/qa writerfilter/source

[Vasily Melenchuk (via logerrit)]

 sw/qa/extras/rtfexport/data/tdf103956.rtf   |8 +
 sw/qa/extras/rtfexport/rtfexport4.cxx   |   37 
 writerfilter/source/rtftok/rtfdispatchvalue.cxx |   13 ++--
 3 files changed, 55 insertions(+), 3 deletions(-)

New commits:
commit 84aea0a29962cf11a63bdb550f522b3d5574cf64
Author: Vasily Melenchuk 
AuthorDate: Fri Jan 6 17:31:16 2023 +0300
Commit: Xisco Fauli 
CommitDate: Wed Jan 11 07:57:41 2023 +

tdf#103956: RTF import: fix for \cellx0 or no params.

If cell width is not given or zero lets not confuse it with too
narrow cell. Lets keep zero to allow domain mapper define some
width.

This patch does not solves autofit issue completely, but finally
tables with autofit are visible somehow and do not contain cells
with minimal almost invisible width (41).

Change-Id: I640228ed117f1d65dde9753a00b8403dda45dd40
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145148
Tested-by: Jenkins
Reviewed-by: Vasily Melenchuk 
(cherry picked from commit 26d74a57d54327b9fd562065d04d867852ce8e8a)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145227
Reviewed-by: Xisco Fauli 

diff --git a/sw/qa/extras/rtfexport/data/tdf103956.rtf 
b/sw/qa/extras/rtfexport/data/tdf103956.rtf
new file mode 100644
index ..f41be5b54aba
--- /dev/null
+++ b/sw/qa/extras/rtfexport/data/tdf103956.rtf
@@ -0,0 +1,8 @@
+{\rtf\ansi\deff0
+
+\trowd\trautofit0\cellx \cellx \pard \intbl 1 \cell \pard \intbl 2 \cell \row 
+\pard\par
+\trowd\trautofit0\trgaph100\cellx0 \cellx0 \pard \intbl 1 \cell \pard \intbl 2 
\cell \row
+\pard\par
+\trowd\trautofit0\cellx500 \cellx1000 \pard \intbl 1 \cell \pard \intbl 2 
\cell \row
+}
\ No newline at end of file
diff --git a/sw/qa/extras/rtfexport/rtfexport4.cxx 
b/sw/qa/extras/rtfexport/rtfexport4.cxx
index c55c74a4f6b3..6912948c57db 100644
--- a/sw/qa/extras/rtfexport/rtfexport4.cxx
+++ b/sw/qa/extras/rtfexport/rtfexport4.cxx
@@ -784,6 +784,43 @@ DECLARE_RTFEXPORT_TEST(testTdf139948, "tdf139948.rtf")
 sal_uInt32(0), getProperty(getParagraph(5), 
"BottomBorder").LineWidth);
 }
 
+DECLARE_RTFEXPORT_TEST(testTdf103956, "tdf103956.rtf")
+{
+// Ensure that RTF tables without column width (\cellx or \cellx0) are 
displayed with some
+// suitable width. Currently there is no good support for autofit for RTF 
docs, so ensure
+// that table cells are somehow visible. Width for it is not clear, so 
here we will check
+// table & cell widths are more than default minimal value of 41.
+CPPUNIT_ASSERT_MESSAGE(
+"Table #1 is too narrow!",
+82 < parseDump("/root/page/body/tab[1]/row/infos/bounds", 
"width").toInt32());
+CPPUNIT_ASSERT_MESSAGE(
+"Table #1 cell#1 is too narrow!",
+41 < parseDump("/root/page/body/tab[1]/row/cell[1]/infos/bounds", 
"width").toInt32());
+CPPUNIT_ASSERT_MESSAGE(
+"Table #1 cell#2 is too narrow!",
+41 < parseDump("/root/page/body/tab[1]/row/cell[2]/infos/bounds", 
"width").toInt32());
+
+CPPUNIT_ASSERT_MESSAGE(
+"Table #2 is too narrow!",
+82 < parseDump("/root/page/body/tab[2]/row/infos/bounds", 
"width").toInt32());
+CPPUNIT_ASSERT_MESSAGE(
+"Table #2 cell#1 is too narrow!",
+41 < parseDump("/root/page/body/tab[2]/row/cell[1]/infos/bounds", 
"width").toInt32());
+CPPUNIT_ASSERT_MESSAGE(
+"Table #2 cell#2 is too narrow!",
+41 < parseDump("/root/page/body/tab[2]/row/cell[2]/infos/bounds", 
"width").toInt32());
+
+CPPUNIT_ASSERT_MESSAGE(
+"Table #3 is too narrow!",
+82 < parseDump("/root/page/body/tab[3]/row/infos/bounds", 
"width").toInt32());
+CPPUNIT_ASSERT_MESSAGE(
+"Table #3 cell#1 is too narrow!",
+41 < parseDump("/root/page/body/tab[3]/row/cell[1]/infos/bounds", 
"width").toInt32());
+CPPUNIT_ASSERT_MESSAGE(
+"Table #3 cell#2 is too narrow!",
+41 < parseDump("/root/page/body/tab[3]/row/cell[2]/infos/bounds", 
"width").toInt32());
+}
+
 DECLARE_RTFEXPORT_TEST(testTdf148515, "tdf148515.rtf")
 {
 uno::Reference xTable(getParagraphOrTable(1), 
uno::UNO_QUERY);
diff --git a/writerfilter/source/rtftok/rtfdispatchvalue.cxx 
b/writerfilter/source/rtftok/rtfdispatchvalue.cxx
index 2bea9dc9ec8f..a56d8e00d819 100644
--- a/writerfilter/source/rtftok/rtfdispatchvalue.cxx
+++ b/writerfilter/source/rtftok/rtfdispatchvalue.cxx
@@ -393,10 +393,17 @@ bool RTFDocumentImpl::dispatchTableValue(RTFKeyword 
nKeyword, int nParam)
 ? m_nNestedCurrentCellX
 : m_nTopLevelCurrentCellX);
 int nCellX = nParam - rCurrentCellX;
-const int COL_DFLT_WIDTH
-= 41; // sw/source/filter/inc/wrtswtbl.hxx, minimal possible 
width of cells.
-if (!nCellX)
+
+if (!nCellX && nParam > 0)
+{
+// If width of cell is 0, BUT there is a value for \cellxN use 
minimal
+ 

[Libreoffice-ux-advise] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #9 from andreas_k  ---
For 80 % of my documents I have templates and the rest I'm "frustrated" to
rewrite everything all the time. In open 3 documents where the content is
similar and copy paste between the documents.

If I would have a database with all my documents, writer would know, ah you
will write about >>terms of conduct<< and offer me what I have written at other
documents about that toppic. In the sidebar writer can show me content that was
used at x documents and documents that was used at some specific documents. So
I could decide what I will choose.

I can make some mockups, but only if you think it can be a usefull first step
into   writing support (artificial intelligence). As you wrote AutoComplete is
already available I think it need's only an database where you add your files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #9 from andreas_k  ---
For 80 % of my documents I have templates and the rest I'm "frustrated" to
rewrite everything all the time. In open 3 documents where the content is
similar and copy paste between the documents.

If I would have a database with all my documents, writer would know, ah you
will write about >>terms of conduct<< and offer me what I have written at other
documents about that toppic. In the sidebar writer can show me content that was
used at x documents and documents that was used at some specific documents. So
I could decide what I will choose.

I can make some mockups, but only if you think it can be a usefull first step
into   writing support (artificial intelligence). As you wrote AutoComplete is
already available I think it need's only an database where you add your files.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 122802] Check-box is missing from opening menus of For Paragraph, For All Text.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=122802

--- Comment #10 from Dieter  ---
Created attachment 184572
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184572=edit
Screenshot

No checkboxes in

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b4dc43b6d01d85802d5674c3a27789d6354e39a8
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (de_DE); UI: en-GB
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #8 from Heiko Tietze  ---
(In reply to andreas_k from comment #7)
> > Isn't this exactly what AutoComplete does?
> 
> Yes, but it use the text of the used document.

Not if you keep it, see
https://help.libreoffice.org/latest/en-US/text/swriter/guide/word_completion_adjust.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #8 from Heiko Tietze  ---
(In reply to andreas_k from comment #7)
> > Isn't this exactly what AutoComplete does?
> 
> Yes, but it use the text of the used document.

Not if you keep it, see
https://help.libreoffice.org/latest/en-US/text/swriter/guide/word_completion_adjust.html

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 142585] Flashing toolbar for Navigator and Styles (when at least one of them is docked)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=142585

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #14 from Stéphane Guillou (stragu) 
 ---
Adalbert, can you please tell us what this returns in a terminal:

echo "$GTK_IM_MODULE"

If it returns "xim", please have a look at bug 144813 and see if changing that
variable (possibly in the ~/.xinputrc file) solves the flickering issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152624] Numbered Lists in LibreOffice Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152624

Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

--- Comment #6 from Dieter  ---
I confirm behaviour with

Version: 7.5.0.1 (X86_64) / LibreOffice Community
Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded

Steps:
1. Open attachment 184461
2. Select bulleted list
3. In list styles select Numbering 123

Actual and expected result
Bulleted list becomes numbered list ans a part of the following numbered list
with the same style
=> RESOLVED NOTABUG

Additional information
If you want the following list becomes a seperate list, set cursor in first
line of that list -> context menu -> list -> Restart Numbering

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 122802] Check-box is missing from opening menus of For Paragraph, For All Text.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=122802

--- Comment #9 from Heiko Tietze  ---
Created attachment 184571
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184571=edit
Screenshot

The menu does have checkboxes for Selection, Paragraph, and All Text.

Version: 7.4.3.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (en_US.UTF-8); UI: en-US
7.4.3-4
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #7 from andreas_k  ---
(In reply to Heiko Tietze from comment #6)
> (In reply to andreas_k from comment #4)
> > If you look at a smartphone keyboard it will offer you word complete, show
> > you the next word if you rephrase a sentense, ... this help for example my
> > kid a lot and make mobile better than desktop.
> 
> Isn't this exactly what AutoComplete does?

Yes, but it use the text of the used document. And ordinary you don't reuse
phrases that often within one document but if you think on a letter like

dear mr. ...

I'm kindly, ... 

cu 

It should be the same text at a specific letter which will be ordinary an
letter template where you insert the names and finished. But if you don't have
a template, it would be nice when writer can offer you the text phrases cause
writer know, ah this kind of text was used very often, maybe it's usefull also
this time.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #7 from andreas_k  ---
(In reply to Heiko Tietze from comment #6)
> (In reply to andreas_k from comment #4)
> > If you look at a smartphone keyboard it will offer you word complete, show
> > you the next word if you rephrase a sentense, ... this help for example my
> > kid a lot and make mobile better than desktop.
> 
> Isn't this exactly what AutoComplete does?

Yes, but it use the text of the used document. And ordinary you don't reuse
phrases that often within one document but if you think on a letter like

dear mr. ...

I'm kindly, ... 

cu 

It should be the same text at a specific letter which will be ordinary an
letter template where you insert the names and finished. But if you don't have
a template, it would be nice when writer can offer you the text phrases cause
writer know, ah this kind of text was used very often, maybe it's usefull also
this time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 108988] [META] Validity-related bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108988

Heiko Tietze  changed:

   What|Removed |Added

 Depends on||152936


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152936
[Bug 152936] Feature Request: Consider adding autocomplete (with full-text
search) to cell validation
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152936] Feature Request: Consider adding autocomplete (with full-text search) to cell validation

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152936

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |79045_79...@mail.ru,
   |.freedesktop.org|c...@nouenoff.nl,
   ||heiko.tietze@documentfounda
   ||tion.org,
   ||stephane.guillou@libreoffic
   ||e.org
 Blocks||108988
   Keywords|needsUXEval |

--- Comment #6 from Heiko Tietze  ---
My understanding of the STR:

1. Create a validity list with a couple of similar options like "Position 1,
Position 2, Position 3"
2. Type "1" in the cell => expectation is to autocomplete as "Position 1"
(picking the item from a very long list is tedious)

Valid enhancement
See also 
* bug 94513 (autocompletion is based on the sheet content not the validity
list)
* bug 98953 (type to find => DUP)
* bug 113237 (duplicate, Cor?)
* bug 114393 (duplicate, Roman?)
* bug 137113 (DUP of bug 94513)

Stéphane, something to consolidate?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108988
[Bug 108988] [META] Validity-related bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 152936] Feature Request: Consider adding autocomplete (with full-text search) to cell validation

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152936

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |79045_79...@mail.ru,
   |.freedesktop.org|c...@nouenoff.nl,
   ||heiko.tietze@documentfounda
   ||tion.org,
   ||stephane.guillou@libreoffic
   ||e.org
 Blocks||108988
   Keywords|needsUXEval |

--- Comment #6 from Heiko Tietze  ---
My understanding of the STR:

1. Create a validity list with a couple of similar options like "Position 1,
Position 2, Position 3"
2. Type "1" in the cell => expectation is to autocomplete as "Position 1"
(picking the item from a very long list is tedious)

Valid enhancement
See also 
* bug 94513 (autocompletion is based on the sheet content not the validity
list)
* bug 98953 (type to find => DUP)
* bug 113237 (duplicate, Cor?)
* bug 114393 (duplicate, Roman?)
* bug 137113 (DUP of bug 94513)

Stéphane, something to consolidate?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108988
[Bug 108988] [META] Validity-related bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

Re: Fwd: Extension development - Are there any limitations?

[Miklos Vajna]

Hi Giulia,

On Tue, Jan 10, 2023 at 06:12:11PM +0100, Giulia Rossi  
wrote:
> Trivial (?) question here: are there any physical limitations on what a
> LibreOffice extension can contain?

I'm not aware of articial limits, but be aware that by default all
LibreOffice APIs are private and only a subset of those are available on
the UNO API, which is available for extensions.

It's a trade-off: once functionality is exposed on the UNO API, then that
is meant to be unchanged, so improving that feature is more difficult
once it has UNO API. (E.g. this is why extensions can't contain dialogs
that load their content from .ui files.)

On the other hand, sometimes a feature is not exposed on the public API
because nobody felt the need for it; in this case once somebody steps up
to do the work, it can be exposed.

Regards,

Miklos

[Libreoffice-bugs] [Bug 152972] Javamaker fails with "unknown entity"

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152972

Julien Nabet  changed:

   What|Removed |Added

 CC||sberg...@redhat.com,
   ||serval2...@yahoo.fr

--- Comment #1 from Julien Nabet  ---
Stephan: thought you might be interested in this one since it concerns IDL,
Java.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 122802] Check-box is missing from opening menus of For Paragraph, For All Text.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=122802

Dieter  changed:

   What|Removed |Added

 CC||heiko.tietze@documentfounda
   ||tion.org

--- Comment #8 from Dieter  ---
Can't see any checkboxes (but don't use dark mode). And I'm atually not sure,
if chekcboxes are expected or not

=> Heiko, what's or opinion? Feel free to close it as NOTABUG

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152669] Some ruled lines in the table are not set in cases other than "Left-to-Right(Horizontal)".

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152669

Dieter  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Keywords||bibisectRequest, regression
 CC||dgp-m...@gmx.de
 Whiteboard| QA:needsComment|
 Status|UNCONFIRMED |NEW
 Blocks||107701

--- Comment #3 from Dieter  ---
I confirm it with

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b4dc43b6d01d85802d5674c3a27789d6354e39a8
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (de_DE); UI: en-GB
Calc: CL threaded

Reproducible also in Safe Mode

but not in

Version: 7.2.7.2 (x64) / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107701
[Bug 107701] [META] Table border bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107701] [META] Table border bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107701

Dieter  changed:

   What|Removed |Added

 Depends on||152669


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152669
[Bug 152669] Some ruled lines in the table are not set in cases other than
"Left-to-Right(Horizontal)".
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: sw/source

[Miklos Vajna (via logerrit)]

 sw/source/uibase/shells/textfld.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 30f6793baa5529b0594407cd0caaf3a3cde3289c
Author: Miklos Vajna 
AuthorDate: Tue Jan 10 16:01:51 2023 +0100
Commit: Miklos Vajna 
CommitDate: Wed Jan 11 07:32:04 2023 +

sw: fix FN_UPDATE_TEXT_FORMFIELD typo

A single fieldmark should not be plural.

Change-Id: I5fc1d9fd3a19937c312a25e36bada0c5c4e70e7d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145277
Tested-by: Jenkins
Reviewed-by: Miklos Vajna 

diff --git a/sw/source/uibase/shells/textfld.cxx 
b/sw/source/uibase/shells/textfld.cxx
index 7e10b7a8673d..d4b9e92c5416 100644
--- a/sw/source/uibase/shells/textfld.cxx
+++ b/sw/source/uibase/shells/textfld.cxx
@@ -1069,7 +1069,7 @@ FIELD_INSERT:
 break;
 case FN_UPDATE_TEXT_FORMFIELD:
 {
-// This updates a single fieldmarks under the current cursor.
+// This updates a single fieldmark under the current cursor.
 OUString aFieldType;
 const SfxStringItem* pFieldType = 
rReq.GetArg(FN_PARAM_1);
 if (pFieldType)

[Libreoffice-ux-advise] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #6 from Heiko Tietze  ---
(In reply to andreas_k from comment #4)
> If you look at a smartphone keyboard it will offer you word complete, show
> you the next word if you rephrase a sentense, ... this help for example my
> kid a lot and make mobile better than desktop.

Isn't this exactly what AutoComplete does?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #6 from Heiko Tietze  ---
(In reply to andreas_k from comment #4)
> If you look at a smartphone keyboard it will offer you word complete, show
> you the next word if you rephrase a sentense, ... this help for example my
> kid a lot and make mobile better than desktop.

Isn't this exactly what AutoComplete does?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #5 from Heiko Tietze  ---
Sounds very much like artificial intelligence. AT is just a shortcut to insert
content, like "lorem" +F3 inserts a complete lorem ipsum chapter. If you have a
conditional AT in mind where "lorem" depends on what you wrote before, I think
it would be awesome but barely doable in LibreOffice. For a limited number of
texts it is possible to insert hidden paragraphs / sections and show it
depending on what you enter somewhere else.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #5 from Heiko Tietze  ---
Sounds very much like artificial intelligence. AT is just a shortcut to insert
content, like "lorem" +F3 inserts a complete lorem ipsum chapter. If you have a
conditional AT in mind where "lorem" depends on what you wrote before, I think
it would be awesome but barely doable in LibreOffice. For a limited number of
texts it is possible to insert hidden paragraphs / sections and show it
depending on what you enter somewhere else.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Re: LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

[Stephan Bergmann]

On 10/01/2023 19:57, John Paul Adrian Glaubitz wrote:

(5) Presumably dead:
* gcc3_linux_alpha


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice=alpha


Thanks for those pointers.  Just to make sure, the latest line there being


1:6.4.5-1 (sid) Buildd exposure stats alpha Maybe-Failed
2020-07-03 06:39:28 phys18h 37m 9.48 GB


means that that's a build of LO 6.4.5, right?  Are all those Debian 
Ports builds consistently lagging behind current LO master by N years?

[Libreoffice-ux-advise] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #4 from andreas_k  ---
In general this bug report is:

1. a simple replacement for users how didn't use templates for there regular
work

2. the user document database will be usefull for some kind of write support.
Also when you think on text analysis for whatever (AI) your own documents would
be a good first starting point.

3. for me writer is to produce content, so every function that help users to
produce content (quantity) will help and reuse stuff will increase quality.

If you look at a smartphone keyboard it will offer you word complete, show you
the next word if you rephrase a sentense, ... this help for example my kid a
lot and make mobile better than desktop.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #4 from andreas_k  ---
In general this bug report is:

1. a simple replacement for users how didn't use templates for there regular
work

2. the user document database will be usefull for some kind of write support.
Also when you think on text analysis for whatever (AI) your own documents would
be a good first starting point.

3. for me writer is to produce content, so every function that help users to
produce content (quantity) will help and reuse stuff will increase quality.

If you look at a smartphone keyboard it will offer you word complete, show you
the next word if you rephrase a sentense, ... this help for example my kid a
lot and make mobile better than desktop.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #3 from andreas_k  ---
So Nr. 2 is already available with AutoText. As Ordinary you don't reuse
phrases within the same document (that often), this bug report is to have a
database with all your writer files where LibO will search for AutoText. So how
can I feed AutoText with all my files and would AutoText will "sort" the text
so I can use each paragraph for AutoText?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

--- Comment #3 from andreas_k  ---
So Nr. 2 is already available with AutoText. As Ordinary you don't reuse
phrases within the same document (that often), this bug report is to have a
database with all your writer files where LibO will search for AutoText. So how
can I feed AutoText with all my files and would AutoText will "sort" the text
so I can use each paragraph for AutoText?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 148955] Display the full path name of the .so[cgb] file in the Area dialog

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148955

--- Comment #4 from Heiko Tietze  ---
To comment on your idea: Showing the full name somewhere is not a good solution
as your workflow is very special and most users are not interested in this
information. The position can be defined via Tools > Options > Path.

Note: Next to the combobox to pick a color palette is a direct access to all
color palettes located on our extension site for quick and easy installation on
your system (see
alsohttps://design.blog.documentfoundation.org/2016/11/11/additions-to-libreoffice/).

And for the mentioned export extension see
https://design.blog.documentfoundation.org/2017/03/29/libreoffice-extension-export-custom-palette/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 148955] Display the full path name of the .so[cgb] file in the Area dialog

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148955

--- Comment #4 from Heiko Tietze  ---
To comment on your idea: Showing the full name somewhere is not a good solution
as your workflow is very special and most users are not interested in this
information. The position can be defined via Tools > Options > Path.

Note: Next to the combobox to pick a color palette is a direct access to all
color palettes located on our extension site for quick and easy installation on
your system (see
alsohttps://design.blog.documentfoundation.org/2016/11/11/additions-to-libreoffice/).

And for the mentioned export extension see
https://design.blog.documentfoundation.org/2017/03/29/libreoffice-extension-export-custom-palette/

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 148955] Display the full path name of the .so[cgb] file in the Area dialog

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148955

Heiko Tietze  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Heiko Tietze  ---
Don't mess with internal files :-)

IIRC, the correct position of user-defined content is
/libreoffice/4/gallery. Or is it /libreoffice/4/user/config? 

Anyway, the recommended way to deal with own palettes is the user palette,
meaning you always add colors to this palette called "custom". I created an
extension [1] to export this "custom" palette under a variable name. Load the
extension to make it available as another entry in the list of color palettes.
And don't forget to share.

[1] https://extensions.libreoffice.org/en/extensions/show/custom-palette-eport

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 148955] Display the full path name of the .so[cgb] file in the Area dialog

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148955

Heiko Tietze  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Heiko Tietze  ---
Don't mess with internal files :-)

IIRC, the correct position of user-defined content is
/libreoffice/4/gallery. Or is it /libreoffice/4/user/config? 

Anyway, the recommended way to deal with own palettes is the user palette,
meaning you always add colors to this palette called "custom". I created an
extension [1] to export this "custom" palette under a variable name. Load the
extension to make it available as another entry in the list of color palettes.
And don't forget to share.

[1] https://extensions.libreoffice.org/en/extensions/show/custom-palette-eport

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-commits] core.git: bridges/Library_cpp_uno.mk bridges/source

[wjh-la (via logerrit)]

 bridges/Library_cpp_uno.mk|2 
 bridges/source/cpp_uno/gcc3_linux_loongarch64/abi.cxx |  137 
 bridges/source/cpp_uno/gcc3_linux_loongarch64/abi.hxx |   51 
 bridges/source/cpp_uno/gcc3_linux_loongarch64/call.hxx|6 
 bridges/source/cpp_uno/gcc3_linux_loongarch64/call.s  |   15 +
 bridges/source/cpp_uno/gcc3_linux_loongarch64/cpp2uno.cxx |   97 +++--
 bridges/source/cpp_uno/gcc3_linux_loongarch64/share.hxx   |3 
 bridges/source/cpp_uno/gcc3_linux_loongarch64/uno2cpp.cxx |  150 +++---
 8 files changed, 288 insertions(+), 173 deletions(-)

New commits:
commit d3152ea3ae0d6d1bdbc6379c3505812434da6466
Author: wjh-la 
AuthorDate: Tue Jan 3 17:22:11 2023 +0800
Commit: Stephan Bergmann 
CommitDate: Wed Jan 11 07:09:21 2023 +

bridges:Fixed test fail caused by bridges on the loongarch64

Some failed test are caused by the bridges when testing on the
loongarch64 machine. After adjust the function parameters and return
value processing according to the characteristics of the loongarch64
architercture. I tested in version 7.4.3 on the loongarch64 machine, and
all tests passed.

Change-Id: I9c67287cd7cc89fd79a907afdbffa507bb6052e3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144986
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/bridges/Library_cpp_uno.mk b/bridges/Library_cpp_uno.mk
index 1718202e94d0..5dc92c23cdbb 100644
--- a/bridges/Library_cpp_uno.mk
+++ b/bridges/Library_cpp_uno.mk
@@ -119,7 +119,7 @@ else ifeq ($(CPUNAME),LOONGARCH64)
 ifneq ($(filter LINUX,$(OS)),)
 bridges_SELECTED_BRIDGE := gcc3_linux_loongarch64
 bridge_asm_objects := call
-bridge_noopt_objects := cpp2uno uno2cpp
+bridge_noopt_objects := abi cpp2uno uno2cpp
 bridge_exception_objects := except
 endif
 
diff --git a/bridges/source/cpp_uno/gcc3_linux_loongarch64/abi.cxx 
b/bridges/source/cpp_uno/gcc3_linux_loongarch64/abi.cxx
new file mode 100644
index ..686cbb596317
--- /dev/null
+++ b/bridges/source/cpp_uno/gcc3_linux_loongarch64/abi.cxx
@@ -0,0 +1,137 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4; 
fill-column: 100 -*- */
+/*
+ * 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/.
+ *
+ * This file incorporates work covered by the following license notice:
+ *
+ *   Licensed to the Apache Software Foundation (ASF) under one or more
+ *   contributor license agreements. See the NOTICE file distributed
+ *   with this work for additional information regarding copyright
+ *   ownership. The ASF licenses this file to you under the Apache
+ *   License, Version 2.0 (the "License"); you may not use this file
+ *   except in compliance with the License. You may obtain a copy of
+ *   the License at http://www.apache.org/licenses/LICENSE-2.0 .
+ */
+
+#include 
+
+#include "abi.hxx"
+
+int loongarch64::flatten_struct(typelib_TypeDescription* pTypeDescr, 
Registers& regs)
+{
+const typelib_CompoundTypeDescription* p
+= reinterpret_cast(pTypeDescr);
+int sum = p->nMembers;
+for (sal_Int32 i = 0; i < p->nMembers; ++i)
+{
+typelib_TypeDescriptionReference* pTypeInStruct = p->ppTypeRefs[i];
+
+switch (pTypeInStruct->eTypeClass)
+{
+case typelib_TypeClass_STRUCT:
+{
+typelib_TypeDescription* t = 0;
+TYPELIB_DANGER_GET(, pTypeInStruct);
+sum--;
+sum += flatten_struct(t, regs);
+TYPELIB_DANGER_RELEASE(t);
+}
+break;
+case typelib_TypeClass_CHAR:
+case typelib_TypeClass_BOOLEAN:
+case typelib_TypeClass_BYTE:
+case typelib_TypeClass_SHORT:
+case typelib_TypeClass_UNSIGNED_SHORT:
+case typelib_TypeClass_LONG:
+case typelib_TypeClass_UNSIGNED_LONG:
+case typelib_TypeClass_HYPER:
+case typelib_TypeClass_UNSIGNED_HYPER:
+case typelib_TypeClass_ENUM:
+regs.nr_int++;
+if (!regs.priorInt && !regs.priorFp)
+regs.priorInt = true;
+break;
+case typelib_TypeClass_FLOAT:
+case typelib_TypeClass_DOUBLE:
+regs.nr_fp++;
+if (!regs.priorInt && !regs.priorFp)
+regs.priorFp = true;
+break;
+default:
+break;
+}
+}
+return sum;
+}
+
+loongarch64::ReturnKind 
loongarch64::getReturnKind(typelib_TypeDescriptionReference* pTypeRef)
+{
+switch (pTypeRef->eTypeClass)
+{
+case typelib_TypeClass_CHAR:
+case typelib_TypeClass_BOOLEAN:
+case 

[Libreoffice-bugs] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

Heiko Tietze  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #2 from Heiko Tietze  ---
This is called AutoText and works out of the box. See for example my "Formatted
Dummy Text" which inserts dummy text with a lot of formattings [1] and the
online help [2]. 

[1] https://extensions.libreoffice.org/en/extensions/show/132
[2] https://help.libreoffice.org/latest/en-US/text/swriter/guide/autotext.html

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 152965] AutoComplete word/sentence/paragraph from other files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152965

Heiko Tietze  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #2 from Heiko Tietze  ---
This is called AutoText and works out of the box. See for example my "Formatted
Dummy Text" which inserts dummy text with a lot of formattings [1] and the
online help [2]. 

[1] https://extensions.libreoffice.org/en/extensions/show/132
[2] https://help.libreoffice.org/latest/en-US/text/swriter/guide/autotext.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 108663] [META] AutoText bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108663
Bug 108663 depends on bug 124088, which changed state.

Bug 124088 Summary: Propose AutoText name and shortcut based on selected text
https://bugs.documentfoundation.org/show_bug.cgi?id=124088

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: sw/qa sw/source

[Andreas Heinisch (via logerrit)]

 sw/qa/uitest/writer_tests3/tdf124088.py |   33 
 sw/source/ui/misc/glossary.cxx  |   24 ++-
 2 files changed, 52 insertions(+), 5 deletions(-)

New commits:
commit fbabd959060655a77188447c9fc0112e0ab8474c
Author: Andreas Heinisch 
AuthorDate: Sun Jan 8 12:31:51 2023 +0100
Commit: Andreas Heinisch 
CommitDate: Wed Jan 11 06:58:42 2023 +

tdf#124088 - Propose AutoText and shortcut name based on selected text

Change-Id: I55ab9b41a32d7a4e41465f375179997a5c8dd06a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145175
Tested-by: Jenkins
Reviewed-by: Andreas Heinisch 

diff --git a/sw/qa/uitest/writer_tests3/tdf124088.py 
b/sw/qa/uitest/writer_tests3/tdf124088.py
new file mode 100755
index ..6ff65dad7631
--- /dev/null
+++ b/sw/qa/uitest/writer_tests3/tdf124088.py
@@ -0,0 +1,33 @@
+# -*- tab-width: 4; indent-tabs-mode: nil; py-indent-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/.
+#
+
+from uitest.framework import UITestCase
+from uitest.uihelper.common import type_text, get_state_as_dict
+
+class tdf124088(UITestCase):
+
+def test_tdf124088_propose_autotext(self):
+with self.ui_test.create_doc_in_start_center("writer"):
+# Insert a random text greater than 25 characters and select it
+xWriterDoc = self.xUITest.getTopFocusWindow()
+xWriterEdit = xWriterDoc.getChild("writer_edit")
+type_text(xWriterEdit, "This is a sample paragraph")
+self.xUITest.executeCommand(".uno:SelectAll")
+
+# Open auto text dialog and check proposed text
+with 
self.ui_test.execute_dialog_through_command(".uno:EditGlossary") as 
xEditGlossaryDlg:
+xName = xEditGlossaryDlg.getChild("name")
+self.assertEqual(get_state_as_dict(xName)["Text"], "This is a 
sample")
+# Click on a group entry, proposed auto text should remain
+xCategory = xEditGlossaryDlg.getChild("category")
+xMyAutoText = xCategory.getChild("2")
+xMyAutoText.executeAction("SELECT", tuple())
+self.assertEqual(get_state_as_dict(xName)["Text"], "This is a 
sample")
+
+# vim: set shiftwidth=4 softtabstop=4 expandtab:
diff --git a/sw/source/ui/misc/glossary.cxx b/sw/source/ui/misc/glossary.cxx
index ae3ce4f0..a1e4a60fe883 100644
--- a/sw/source/ui/misc/glossary.cxx
+++ b/sw/source/ui/misc/glossary.cxx
@@ -410,12 +410,7 @@ IMPL_LINK(SwGlossaryDlg, GrpSelect, weld::TreeView&, rBox, 
void)
 ShowAutoText(::GetCurrGlosGroup(), m_xShortNameEdit->get_text());
 }
 else
-{
-m_xNameED->set_text("");
-m_xShortNameEdit->set_text("");
-m_xShortNameEdit->set_sensitive(false);
 ShowAutoText("", "");
-}
 // update controls
 NameModify(*m_xShortNameEdit);
 if( SfxRequest::HasMacroRecorder( m_pShell->GetView().GetViewFrame() ) )
@@ -904,6 +899,25 @@ void SwGlossaryDlg::Init()
 m_xInsertTipCB->set_active( rCfg.IsAutoTextTip() );
 
m_xInsertTipCB->set_sensitive(!officecfg::Office::Writer::AutoFunction::Text::ShowToolTip::isReadOnly());
 m_xInsertTipCB->connect_toggled(LINK(this, SwGlossaryDlg, CheckBoxHdl));
+
+// tdf#124088 - propose autotext and shortcut name based on selected text
+if (m_pShell->HasSelection())
+{
+OUString aSelText;
+m_pShell->GetSelectedText(aSelText, ParaBreakType::ToBlank);
+
+aSelText = aSelText.trim();
+if (aSelText.getLength() > 25)
+{
+aSelText = aSelText.copy(0, 25);
+if (const sal_Int32 nBlankIndex = aSelText.lastIndexOf(' '); 
nBlankIndex != -1)
+aSelText = aSelText.copy(0, nBlankIndex);
+}
+
+m_xNameED->set_text(aSelText);
+m_xNameED->select_region(0, -1);
+m_xShortNameEdit->set_text(lcl_GetValidShortCut(aSelText));
+}
 }
 
 // KeyInput for ShortName - Edits without Spaces

[Libreoffice-ux-advise] [Bug 147656] Presenter console default disable

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147656

Heiko Tietze  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #10 from Heiko Tietze  ---
(In reply to Artem Proskurnev from comment #8)
> I will check if there is a problem in the new version

Back to NEEDINFO

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 147656] Presenter console default disable

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147656

Heiko Tietze  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #10 from Heiko Tietze  ---
(In reply to Artem Proskurnev from comment #8)
> I will check if there is a problem in the new version

Back to NEEDINFO

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152958] Presentation hangs with multiple screens but shows blackscreen

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152958

--- Comment #6 from dani2...@gmx.de ---
I tested it with Safe Mode and reset to factory settings and had no issue
starting the presentation.
I tested again if the problem still appears when i start the presentation
without Safe Mode and it happened again with the issue.
Odd thing is, i didn't personalize anything prior to starting the presentation.
My process was: install LibreOffice 7.4.3.2, open .ppsx file, start
presentation. Nothing more.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: sw/qa sw/source

[Pranam Lashkari (via logerrit)]

 sw/qa/uibase/uno/uno.cxx  |5 +++--
 sw/source/uibase/uno/loktxdoc.cxx |1 +
 2 files changed, 4 insertions(+), 2 deletions(-)

New commits:
commit 5dd5011eabc755d4ea8d282c32dd4854d532849a
Author: Pranam Lashkari 
AuthorDate: Tue Jan 10 11:24:56 2023 +0530
Commit: Pranam Lashkari 
CommitDate: Wed Jan 11 05:48:09 2023 +

sw: return field under cursor inside field node

Having values inside field node makes it easier to detect which commands 
value
is being returned in online. otherwise its impossible to predict the 
command from "type" and "command"
as "command" can be anything and "type" is very generic

this also makes output more consistent with "GetTextFormFields"

Signed-off-by: Pranam Lashkari 
Change-Id: I1b8b39bfd0de6d7b19c2944bd42f7031d60518af
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145295
Tested-by: Jenkins

diff --git a/sw/qa/uibase/uno/uno.cxx b/sw/qa/uibase/uno/uno.cxx
index b9158c44426d..4b21bca0bb0c 100644
--- a/sw/qa/uibase/uno/uno.cxx
+++ b/sw/qa/uibase/uno/uno.cxx
@@ -407,10 +407,11 @@ CPPUNIT_TEST_FIXTURE(SwUibaseUnoTest, 
testGetTextFormField)
 // Without the accompanying fix in place, this test would have failed with:
 // - No such node (type)
 // i.e. the returned JSON was just an empty object.
+auto field = aTree.get_child("field");
 CPPUNIT_ASSERT_EQUAL(std::string("vnd.oasis.opendocument.field.UNHANDLED"),
- aTree.get("type"));
+ field.get("type"));
 CPPUNIT_ASSERT_EQUAL(std::string("ADDIN ZOTERO_ITEM foo bar"),
- aTree.get("command"));
+ field.get("command"));
 }
 
 CPPUNIT_TEST_FIXTURE(SwUibaseUnoTest, testGetSections)
diff --git a/sw/source/uibase/uno/loktxdoc.cxx 
b/sw/source/uibase/uno/loktxdoc.cxx
index 2291cf3f7ab5..a2f5b3cdd131 100644
--- a/sw/source/uibase/uno/loktxdoc.cxx
+++ b/sw/source/uibase/uno/loktxdoc.cxx
@@ -126,6 +126,7 @@ void GetTextFormField(tools::JsonWriter& rJsonWriter, 
SwDocShell* pDocShell,
 SwWrtShell* pWrtShell = pDocShell->GetWrtShell();
 SwPosition& rCursor = *pWrtShell->GetCursor()->GetPoint();
 sw::mark::IFieldmark* pFieldmark = rIDMA.getFieldmarkFor(rCursor);
+auto typeNode = rJsonWriter.startNode("field");
 if (!pFieldmark)
 {
 return;

[Libreoffice-bugs] [Bug 130782] docx alt text for charts not shown if document has been edited in Word

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=130782

--- Comment #8 from qualifiedbabyish  ---
Tested and looks fixed to me.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152972] New: Javamaker fails with "unknown entity"

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152972

Bug ID: 152972
   Summary: Javamaker fails with "unknown entity"
   Product: LibreOffice
   Version: 7.3.6.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: sdk
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dloch...@aussiebb.com.au

Created attachment 184570
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184570=edit
This IDL definition fails JAVAMAKER after running IDLC and REGMERGE
successfully.

I've developed two succesful Calc extensions, both written in Java using the
old method of hand-coding everything.  However a current project using
'javamaker' fails when that utility diagnoses:
ERROR: Unknown entity 'com.sun.star.uno.XComponentContext'

Both 'idlc' and 'regmerge' run successfully.

Similar behaviour is reported on github also at
https://flywire.github.io/lo-p/47-Calc_Add-ins.html - see Chapter 47, section
2.4. "Problems with Office Types".

QUOTE:
"Office's idlc.exe and regmerge.exe tools are happy to process these types, but
javamaker.exe always fails to recognize 'com.sun.star.table.XCellRange' and
'com.sun.star.sheet.XVolatileResult', reporting an "Unknown entity" error. I
tried calling javamaker with the inclusion of extra Office RDB files, such as
services.rdb and offapi.rdb, but with no success.

I was unable to find an add-in example online that uses XCellRange, perhaps
because it's more natural to pass a cell range to a function as an array.
UNQUOTE

Attempting to run idlc / regmerge / javamaker on an earlier hand-coded
extension which has run successfully over several versions of LibreOffice
results in exactly the same problem.  Since this earlier extension works, is
simpler, and shows the same problem it's copied here as an example.  Note, the
directive to "include"  was inserted to
see if it fixed the problem, but isn't in the original IDL definition.

Regards!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152695] Display only permanent printers

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152695

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 147656] Presenter console default disable

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147656

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 152669] Some ruled lines in the table are not set in cases other than "Left-to-Right(Horizontal)".

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152669

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 147656] Presenter console default disable

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147656

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 147656] Presenter console default disable

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147656

--- Comment #9 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149986] FILEOPEN: Cell formatting / alignment when importing a SYLK file is not supported

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=149986

--- Comment #2 from QA Administrators  ---
Dear Laurent Haas,

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-ux-advise] [Bug 147656] Presenter console default disable

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147656

--- Comment #9 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-bugs] [Bug 149995] Calc: the width of the lines of the graph is forgotten

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=149995

--- Comment #2 from QA Administrators  ---
Dear Daniel Houx,

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 149967] documento de excel se traba cuando lo abro con officelibre

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=149967

--- Comment #2 from QA Administrators  ---
Dear Anderson,

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 92447] sub-cell text style is removed/misapplied during search/replace

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=92447

--- Comment #5 from QA Administrators  ---
Dear localcbug,

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 89829] Updating character style to match selection does not remove direct formatting

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=89829

--- Comment #7 from QA Administrators  ---
Dear mahfiaz,

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 74078] EDITING: Attribute "Page Style" in Find and Replace does not work

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=74078

--- Comment #10 from QA Administrators  ---
Dear John Smith,

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 62995] PRINTING LO doesn't remember pages per page and page size property

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=62995

--- Comment #13 from QA Administrators  ---
Dear Paolo Benvenuto,

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 62542] EDITING: Strange behavior when pasting text from Writer into Impress

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=62542

--- Comment #10 from QA Administrators  ---
Dear Pericle Perazzo,

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 38982] Calc [EDITING, FORMATTING] find & replace causes default formatting to be applied to cells, undo working incorrectly

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=38982

--- Comment #21 from QA Administrators  ---
Dear Adam Voysey,

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 139517] Calc: Date values toggle between date and text when changed

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=139517

--- Comment #5 from QA Administrators  ---
Dear Michael,

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 139507] Find and Replace with wildcard(Calc): Wildcard option uncheck after check does not take away the wildcard functionality.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=139507

--- Comment #3 from QA Administrators  ---
Dear Bala,

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 128541] Direct Formatting plus Style Formatting affects results from Find & Replace with Including Styles

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=128541

--- Comment #8 from QA Administrators  ---
Dear Alex,

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 138811] Crop caused image to expand (increase in size); zoom in effect (for certain images)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=138811

--- Comment #3 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 152910] [LOCALHELP] Add help page for new page entry feature

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152910

--- Comment #4 from Commit Notification 
 ---
Olivier Hallot committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/help/commit/a6bf263e06de175a10e35bd6ba7ca51a1529812c

tdf#152910 Add help page for page numbering wizard

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: helpcontent2

[Olivier Hallot (via logerrit)]

 helpcontent2 |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit d2a27ceece84998c686477ffd2073f3516b568a7
Author: Olivier Hallot 
AuthorDate: Wed Jan 11 00:02:31 2023 -0300
Commit: Gerrit Code Review 
CommitDate: Wed Jan 11 03:02:31 2023 +

Update git submodules

* Update helpcontent2 from branch 'master'
  to a6bf263e06de175a10e35bd6ba7ca51a1529812c
  - tdf#152910 Add help page for page numbering wizard

Change-Id: I467f3e49146c9ee4ec133dfb2360bb1d132f18dd
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145179
Tested-by: Jenkins
Reviewed-by: Olivier Hallot 

diff --git a/helpcontent2 b/helpcontent2
index 20d4c17ca1fb..a6bf263e06de 16
--- a/helpcontent2
+++ b/helpcontent2
@@ -1 +1 @@
-Subproject commit 20d4c17ca1fb161bf5fccf3d94db93b0a4d322f2
+Subproject commit a6bf263e06de175a10e35bd6ba7ca51a1529812c

[Libreoffice-commits] help.git: AllLangHelp_swriter.mk source/text

[Olivier Hallot (via logerrit)]

 AllLangHelp_swriter.mk|1 
 source/text/swriter/01/pagenumbering.xhp  |   41 ++
 source/text/swriter/guide/pagenumbers.xhp |   25 ++
 3 files changed, 57 insertions(+), 10 deletions(-)

New commits:
commit a6bf263e06de175a10e35bd6ba7ca51a1529812c
Author: Olivier Hallot 
AuthorDate: Sun Jan 8 11:51:22 2023 -0300
Commit: Olivier Hallot 
CommitDate: Wed Jan 11 03:02:30 2023 +

tdf#152910 Add help page for page numbering wizard

Change-Id: I467f3e49146c9ee4ec133dfb2360bb1d132f18dd
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145179
Tested-by: Jenkins
Reviewed-by: Olivier Hallot 

diff --git a/AllLangHelp_swriter.mk b/AllLangHelp_swriter.mk
index 11cd361484..18f6511f1f 100644
--- a/AllLangHelp_swriter.mk
+++ b/AllLangHelp_swriter.mk
@@ -201,6 +201,7 @@ $(eval $(call gb_AllLangHelp_add_helpfiles,swriter,\
 helpcontent2/source/text/swriter/01/mm_seladdlis \
 helpcontent2/source/text/swriter/01/mm_seltab \
 helpcontent2/source/text/swriter/01/outlinecontent_visibility \
+helpcontent2/source/text/swriter/01/pagenumbering \
 helpcontent2/source/text/swriter/01/protectdocument \
 helpcontent2/source/text/swriter/01/selection_mode \
 helpcontent2/source/text/swriter/01/show_whitespace \
diff --git a/source/text/swriter/01/pagenumbering.xhp 
b/source/text/swriter/01/pagenumbering.xhp
new file mode 100644
index 00..674d37b7fb
--- /dev/null
+++ b/source/text/swriter/01/pagenumbering.xhp
@@ -0,0 +1,41 @@
+
+
+
+
+
+Page Number Wizard
+/text/swriter/01/pagenumbering.xhp
+
+
+
+
+
+
+page number;insert quickly
+
+
+Page Number 
Wizard
+Use this command to quickly insert a page number in the header 
or footer of the current page style.
+
+
+Choose 
Insert - Page Number.
+
+
+Position
+Select the position of 
the page number: options are header or footer.
+The Page Number command enables 
the header or footer of the current page style.
+
+Alignment
+Select the alignment of 
the page number in the header or footer. Options are Left, Center and 
Right.
+
+
+
+
+
diff --git a/source/text/swriter/guide/pagenumbers.xhp 
b/source/text/swriter/guide/pagenumbers.xhp
index f1d7e0458f..969b65bbf4 100644
--- a/source/text/swriter/guide/pagenumbers.xhp
+++ b/source/text/swriter/guide/pagenumbers.xhp
@@ -35,15 +35,18 @@
   inserting;page numbers
   styles;page numbers
 mw inserted six index entriesmw added 
"styles;"
-Page Numbers
-
+Page Numbers
+
   In 
Writer, a page number is a field that you can insert into your text.
-  To Insert Page Numbers
-  Choose 
Insert - Page Number to insert a page number at the 
current cursor position.
+  To Quickly Insert a Page Number in Header 
or Footer of Page Style
+  Choose Insert - Page 
Numbers to open a dialog to guide you in inserting a page 
number in the current page style header or footer and setting the page number 
alignment.
+
+  To Insert Page Numbers
+  Choose 
Insert - Field - Page Number to insert a page number at 
the current cursor position.
   If you see the text "Page 
number" instead of the number, choose View - Field Names 
(Command+F9Ctrl+F9).
   However, 
these fields will change position when you add or remove text. So it is best to 
insert the page number field into a header or footer that has the same position 
and that is repeated on every page.
   Choose 
Insert - Header and Footer - Header - (name of page 
style) or Insert - Header and Footer - Footer - 
(name of page style) to add a header or footer to all pages with the 
current page style.
-  To Start With a Defined Page Number
+  To Start With a Defined Page Number
   Now you 
want some more control on page numbers. You are writing a text document that 
should start with page number 12.
   
  
@@ -56,7 +59,7 @@
 In 
the Breaks area, enable Insert. Enable With Page 
Style just to be able to set the new Page number. Click 
OK.
  
   
-  The new page 
number is an attribute of the first paragraph of the page.
+  The new page number is an attribute of the 
first paragraph of the page.
   To Select the Page Number 
Format
   You want 
roman page numbers running i, ii, iii, iv, and so on.
   
@@ -83,7 +86,7 @@
  
   
   It 
depends on your document what is best: to use a manually inserted page break 
between page styles, or to use an automatic change. If you just need one title 
page with a different style than the other pages, you can use the automatic 
method:
-  To Apply a Different Page Style to the First Page
+  To Apply a Different Page Style to the First 
Page
   
  
 Click into the first page of your document.
@@ -100,7 +103,7 @@
   
   Now your 
title page has the style "First Page", and the next pages automatically have 
the "Default Page Style".
   You can 

[Libreoffice-commits] core.git: sw/uiconfig

[Olivier Hallot (via logerrit)]

 sw/uiconfig/swriter/ui/pagenumberdlg.ui |   38 ++--
 1 file changed, 32 insertions(+), 6 deletions(-)

New commits:
commit 0afde4cca4046c9478a1c9751ee104495ef18688
Author: Olivier Hallot 
AuthorDate: Sun Jan 8 10:23:43 2023 -0300
Commit: Olivier Hallot 
CommitDate: Wed Jan 11 03:02:03 2023 +

tdf#152910 (part) add Help button to pagenumberdlg.ui

Core part
+ Added extended tips
+ need HIG review

Change-Id: I15363041041cc771db3ffe89540cfd6c0321bd85
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145178
Tested-by: Jenkins
Reviewed-by: Olivier Hallot 

diff --git a/sw/uiconfig/swriter/ui/pagenumberdlg.ui 
b/sw/uiconfig/swriter/ui/pagenumberdlg.ui
index 4f46767d9491..5a81099c5898 100644
--- a/sw/uiconfig/swriter/ui/pagenumberdlg.ui
+++ b/sw/uiconfig/swriter/ui/pagenumberdlg.ui
@@ -5,20 +5,34 @@
   
 False
 Page Number Wizard
-False
 0
 0
 dialog
-north-east
 
   
 False
 vertical
-2
+12
 
   
 False
 end
+
+  
+_Help
+True
+True
+True
+start
+True
+  
+  
+False
+True
+0
+True
+  
+
 
   
 _OK
@@ -30,7 +44,7 @@
   
 True
 True
-0
+1
   
 
 
@@ -44,13 +58,14 @@
   
 True
 True
-1
+2
   
 
   
   
 False
-False
+True
+end
 1
   
 
@@ -102,6 +117,11 @@
 
   
 
+
+  
+Insert 
page number in footer.
+  
+
   
   
 False
@@ -145,6 +165,11 @@
 
   
 
+
+  
+Align 
page number in page footer or header.
+  
+
   
   
 False
@@ -215,6 +240,7 @@
   
 
 
+  help
   ok
   cancel
 

[Libreoffice-bugs] [Bug 152910] [LOCALHELP] Add help page for new page entry feature

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152910

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.6.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152910] [LOCALHELP] Add help page for new page entry feature

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152910

--- Comment #3 from Commit Notification 
 ---
Olivier Hallot committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/0afde4cca4046c9478a1c9751ee104495ef18688

tdf#152910 (part) add Help button to pagenumberdlg.ui

It will be available in 7.6.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 150429] FILEOPEN PPTX: line in "chevron + textboxes" SmartArt renders quite thinner than in PowerPoint

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150429

Aron Budea  changed:

   What|Removed |Added

 Attachment #181792|application/vnd.ms-powerpoi |application/vnd.openxmlform
  mime type|nt  |ats-officedocument.presenta
   ||tionml.presentation

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 150429] FILEOPEN PPTX: line in "chevron + textboxes" SmartArt renders quite thinner than in PowerPoint

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150429

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
Version|7.5.0.0 alpha0+ |4.0.0.3 release
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 Whiteboard| QA:needsComment|

--- Comment #3 from Aron Budea  ---
Confirmed using LO 7.6.0.0.alpha0+ (d993327eab0a2c9c8820c6528075b01de68b0ec6)
and 4.0.0.3 / Ubuntu. Display is not HiDPI.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - sw/qa sw/source

[Miklos Vajna (via logerrit)]

 sw/qa/uibase/shells/shells.cxx  |9 +++--
 sw/source/uibase/shells/textsh1.cxx |2 +-
 2 files changed, 8 insertions(+), 3 deletions(-)

New commits:
commit 1f0d6c660c799900cfda070f7319c8e0cdde41f5
Author: Miklos Vajna 
AuthorDate: Mon Jan 9 16:27:15 2023 +0100
Commit: Pranam Lashkari 
CommitDate: Wed Jan 11 01:11:19 2023 +

sw, UpdateBookmarks: support renaming bookmarks

The problem was that the LOK API client wanted to change the name of the
bookmark, but nothing happened, because we had a sanity check that made
sure the provided vs existing bookmark names match.

The intention was that the bookmark name is just an ID (you can store
additional properties in per-doc custom properties, those can change),
so we can require that bookmarks never get renamed when using this
command.

Fix the problem by dropping this requirement and rather use renameMark()
to adjust the in-doc bookmark name if needed.

This also handles undo/redo for us.

(cherry picked from commit d2318503d559c3797965da777627e4ee45143043)

Change-Id: I7a426c865ddf24f13741c0369fb3991da2e881b2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145280
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Pranam Lashkari 

diff --git a/sw/qa/uibase/shells/shells.cxx b/sw/qa/uibase/shells/shells.cxx
index 794932e8cf25..33f0d615b250 100644
--- a/sw/qa/uibase/shells/shells.cxx
+++ b/sw/qa/uibase/shells/shells.cxx
@@ -405,7 +405,7 @@ CPPUNIT_TEST_FIXTURE(SwUibaseShellsTest, 
testUpdateBookmarks)
 {
 "Bookmark": {
 "type": "string",
-"value": "ZOTERO_BREF_GiQ7DAWQYWLy"
+"value": "ZOTERO_BREF_new1"
 },
 "BookmarkText": {
 "type": "string",
@@ -415,7 +415,7 @@ CPPUNIT_TEST_FIXTURE(SwUibaseShellsTest, 
testUpdateBookmarks)
 {
 "Bookmark": {
 "type": "string",
-"value": "ZOTERO_BREF_PRxDGUb4SWXF"
+"value": "ZOTERO_BREF_new2"
 },
 "BookmarkText": {
 "type": "string",
@@ -437,6 +437,11 @@ CPPUNIT_TEST_FIXTURE(SwUibaseShellsTest, 
testUpdateBookmarks)
 // - Actual  : ABCDE
 // i.e. the content was not updated.
 CPPUNIT_ASSERT_EQUAL(OUString("Anew result 1Cnew result 2E"), aActual);
+
+// Without the accompanying fix in place, this test would have failed, 
ZOTERO_BREF_GiQ7DAWQYWLy
+// was not renamed to ZOTERO_BREF_new1.
+auto it = pDoc->getIDocumentMarkAccess()->findMark("ZOTERO_BREF_new1");
+CPPUNIT_ASSERT(it != pDoc->getIDocumentMarkAccess()->getAllMarksEnd());
 }
 
 CPPUNIT_TEST_FIXTURE(SwUibaseShellsTest, testInsertFieldmarkReadonly)
diff --git a/sw/source/uibase/shells/textsh1.cxx 
b/sw/source/uibase/shells/textsh1.cxx
index 4641aede858f..2acf9b037602 100644
--- a/sw/source/uibase/shells/textsh1.cxx
+++ b/sw/source/uibase/shells/textsh1.cxx
@@ -425,7 +425,7 @@ void UpdateBookmarks(SfxRequest& rReq, SwWrtShell& rWrtSh)
 comphelper::SequenceAsHashMap aMap(aBookmarks[nBookmarkIndex++]);
 if (aMap["Bookmark"].get() != pMark->GetName())
 {
-continue;
+rIDMA.renameMark(pMark, aMap["Bookmark"].get());
 }
 
 OUString aBookmarkText = aMap["BookmarkText"].get();

[Libreoffice-bugs] [Bug 108804] [META] Print preview bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108804

Aron Budea  changed:

   What|Removed |Added

 Depends on||151107


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151107
[Bug 151107] Print Preview in Print dialog: page orientation depends on moving
forward or backwards through print previews
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103309] [META] Print dialog bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103309

Aron Budea  changed:

   What|Removed |Added

 Depends on||151107


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151107
[Bug 151107] Print Preview in Print dialog: page orientation depends on moving
forward or backwards through print previews
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108804] [META] Print preview bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108804

Aron Budea  changed:

   What|Removed |Added

 Depends on||146213


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=146213
[Bug 146213] Printer preview will show preview in all sorts of page sizes
(letter/A2) for paper size B5
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103309] [META] Print dialog bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103309

Aron Budea  changed:

   What|Removed |Added

 Depends on||146213


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=146213
[Bug 146213] Printer preview will show preview in all sorts of page sizes
(letter/A2) for paper size B5
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 146213] Printer preview will show preview in all sorts of page sizes (letter/A2) for paper size B5

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=146213

Aron Budea  changed:

   What|Removed |Added

 Blocks||103309, 108804


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103309
[Bug 103309] [META] Print dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108804
[Bug 108804] [META] Print preview bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 127182] [META] MS Visio bugs and Improvements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=127182
Bug 127182 depends on bug 95928, which changed state.

Bug 95928 Summary: print preview upside down in case of Visio object
https://bugs.documentfoundation.org/show_bug.cgi?id=95928

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108804] [META] Print preview bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108804
Bug 108804 depends on bug 95928, which changed state.

Bug 95928 Summary: print preview upside down in case of Visio object
https://bugs.documentfoundation.org/show_bug.cgi?id=95928

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107810] [META] OLE/Embedded object bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107810
Bug 107810 depends on bug 95928, which changed state.

Bug 95928 Summary: print preview upside down in case of Visio object
https://bugs.documentfoundation.org/show_bug.cgi?id=95928

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 95928] print preview upside down in case of Visio object

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=95928

Aron Budea  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED
 CC||aron.bu...@gmail.com

--- Comment #10 from Aron Budea  ---
This is OK now in LO 7.6, and has been OK since the following revert in
6.3.4/6.4. Haven't checked what the actual fixing commit was before that.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=1560adf9cfd1d4ef076561b1c48e80c9936c940d

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152594] Tab does not increase outline level for PS registered in Chapter Numbering

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152594

--- Comment #3 from sdc.bla...@youmail.dk ---
(In reply to Heiko Tietze from comment #2)
> Any relation to bug 146762?
Assuming that my verification was valid (bug 146762, comment 28), and comment 1
here is accurate, then I would deduce that a more likely explanation is a
regression sometime between 7.4 and 7.5.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 120917] Tab key at the beginning of heading has strange and inconsistent effects

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=120917

--- Comment #11 from sdc.bla...@youmail.dk ---
(In reply to Kenneth Hanson from comment #9)
> Behavior is somewhat different in v7.4.2.3, but still mysterious.
> - Tab at the beginning of line inserts a tab stop
See bug 152594

> - Shift+Tab decreases the heading level for the current paragraph only
> - Ctrl+Tab increases the indent (different from both the above) for every
> heading in the document
Appears to correspond to expected design (per bug 146762)
see:
https://help.libreoffice.org/7.4/en-US/text/swriter/04/0102.html#bm_id3150396

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: helpcontent2

[Rafael Lima (via logerrit)]

 helpcontent2 |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 5b3fd1af1247d4096451e5a768c3438fbccec2b2
Author: Rafael Lima 
AuthorDate: Wed Jan 11 00:09:58 2023 +
Commit: Gerrit Code Review 
CommitDate: Wed Jan 11 00:09:58 2023 +

Update git submodules

* Update helpcontent2 from branch 'master'
  to 20d4c17ca1fb161bf5fccf3d94db93b0a4d322f2
  - tdf#152412 Improve the STYLE function help page

This patch creates a separate help page for the STYLE function and 
improves its text and examples.

Change-Id: I3630fbc99ac822ea138f08283e92d88ffa4acaf8
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145299
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 
Reviewed-by: Olivier Hallot 

diff --git a/helpcontent2 b/helpcontent2
index 08418f863745..20d4c17ca1fb 16
--- a/helpcontent2
+++ b/helpcontent2
@@ -1 +1 @@
-Subproject commit 08418f863745757cc8074db7addf4812170dc21b
+Subproject commit 20d4c17ca1fb161bf5fccf3d94db93b0a4d322f2

[Libreoffice-commits] help.git: AllLangHelp_scalc.mk source/text

[Rafael Lima (via logerrit)]

 AllLangHelp_scalc.mk|1 
 source/text/scalc/01/04060104.xhp   |2 
 source/text/scalc/01/04060109.xhp   |   36 ++---
 source/text/scalc/01/func_style.xhp |   73 
 4 files changed, 82 insertions(+), 30 deletions(-)

New commits:
commit 20d4c17ca1fb161bf5fccf3d94db93b0a4d322f2
Author: Rafael Lima 
AuthorDate: Tue Jan 10 19:42:50 2023 +
Commit: Olivier Hallot 
CommitDate: Wed Jan 11 00:09:58 2023 +

tdf#152412 Improve the STYLE function help page

This patch creates a separate help page for the STYLE function and improves 
its text and examples.

Change-Id: I3630fbc99ac822ea138f08283e92d88ffa4acaf8
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145299
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 
Reviewed-by: Olivier Hallot 

diff --git a/AllLangHelp_scalc.mk b/AllLangHelp_scalc.mk
index e7ab38d663..452e16fd57 100644
--- a/AllLangHelp_scalc.mk
+++ b/AllLangHelp_scalc.mk
@@ -264,6 +264,7 @@ $(eval $(call gb_AllLangHelp_add_helpfiles,scalc,\
 helpcontent2/source/text/scalc/01/func_second \
 helpcontent2/source/text/scalc/01/func_skewp \
 helpcontent2/source/text/scalc/01/func_searchb \
+helpcontent2/source/text/scalc/01/func_style \
 helpcontent2/source/text/scalc/01/func_sum \
 helpcontent2/source/text/scalc/01/func_sumifs \
 helpcontent2/source/text/scalc/01/func_switch \
diff --git a/source/text/scalc/01/04060104.xhp 
b/source/text/scalc/01/04060104.xhp
index d2b2f01014..65e0076dab 100644
--- a/source/text/scalc/01/04060104.xhp
+++ b/source/text/scalc/01/04060104.xhp
@@ -207,8 +207,10 @@
   CURRENT function
 
 
+
 CURRENT
 This function returns the result to date of evaluating 
the formula of which it is a part (in other words the result as far as that 
evaluation has got). Its main use is together with the STYLE() function to 
apply selected styles to a cell depending on the cell 
contents.
+
 
 CURRENT()
 
diff --git a/source/text/scalc/01/04060109.xhp 
b/source/text/scalc/01/04060109.xhp
index e1ab74ace9..1e6d28d8e0 100644
--- a/source/text/scalc/01/04060109.xhp
+++ b/source/text/scalc/01/04060109.xhp
@@ -410,36 +410,12 @@
  
 =LOOKUP(A1;D1:D100;F1:F100) searches the 
corresponding cell in range D1:D100 for the number you entered in A1. For the 
instance found, the index is determined, for example, the 12th cell in this 
range. Then, the contents of the 12th cell are returned as the value of the 
function (in the result vector).
   
-  
-STYLE function
-
-
-STYLE
- Applies a style to the cell 
containing the formula. After a set amount of time, another style can 
be applied. This function always returns the value 0, allowing you to add it to 
another function without changing the value. Together with the CURRENT function 
you can apply a color to a cell depending on the value. For example: 
=...+STYLE(IF(CURRENT()3;"red";"green")) applies the style "red" to the 
cell if the value is greater than 3, otherwise the style "green" is applied. 
Both cell formats, "red" and "green" have to be defined beforehand.
- The STYLE function should not be used 
without a compelling reason. Its purpose is the use with asynchronous Add-In 
functions to visually notify about the availability of a result. In almost all 
other cases, using conditional formatting instead is a better choice.
- 
- STYLE("Style" [; Time [; "Style2"]])
- 
-Style is the name of a cell style assigned to the 
cell. Style names must be entered in quotation marks.
- 
-Time is an optional time range in seconds. If this 
parameter is missing the style will not be changed after a certain amount of 
time has passed.
- 
-Style2 is the optional name of a cell style assigned 
to the cell after a certain amount of time has passed. If this parameter is 
missing "Default" is assumed.
- 
-
- 
- 
- 
-=STYLE("Invisible";60;"Default") formats 
the cell in transparent format for 60 seconds after the document was 
recalculated or loaded, then the Default format is assigned. Both cell formats 
have to be defined beforehand.
- Since 
STYLE() has a numeric return value of zero, this return value gets appended to 
a string. This can be avoided using T() as in the following example:
- 
-="Text"T(STYLE("myStyle"))
- 
- See 
also CURRENT() for another example.
- 
-
-ORG.OPENOFFICE.STYLE
-  
+
+
+  
+  
+
+
   
 CHOOSE function
 
diff --git a/source/text/scalc/01/func_style.xhp 
b/source/text/scalc/01/func_style.xhp
new file mode 100644
index 00..7e1c168450
--- /dev/null
+++ b/source/text/scalc/01/func_style.xhp
@@ -0,0 +1,73 @@
+
+
+
+
+
+  
+STYLE function
+/text/scalc/01/func_style.xhp
+  
+
+
+
+  
+
+
+  STYLE function
+
+STYLE 

[Libreoffice-bugs] [Bug 152412] STYLE spreadsheet function help: a phrase that refers to unknown context

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152412

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.6.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152412] STYLE spreadsheet function help: a phrase that refers to unknown context

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152412

--- Comment #3 from Commit Notification 
 ---
Rafael Lima committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/help/commit/20d4c17ca1fb161bf5fccf3d94db93b0a4d322f2

tdf#152412 Improve the STYLE function help page

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152964] Crash on undo deletion of table with track changes enabled

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152964

Telesto  changed:

   What|Removed |Added

 CC||nem...@numbertext.org

--- Comment #4 from Telesto  ---
@László
You might be interested in this one

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152971] Table row stays visible after redo of deletion (track changes enabled)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152971

--- Comment #3 from Telesto  ---
For an assert 

1. Open the attached file
2. Put cursor in the bottom row of the table
3. Press delete table row button (2x)
4. CTRL+Z (2x)
5. CTRL+Y (2)
6. Press delete table
7. CTRL-Z
8. CTRL-Y

frame #4: 0x0001746b237c
libswlo.dylib`sw::UpdateFramesForAddDeleteRedline(rDoc=0x00010dcab450,
rPam=0x00010dcec460) at DocumentRedlineManager.cxx:209:17
   206  if (frames.empty())
   207  {
   208  auto const& layouts(rDoc.GetAllLayouts());
-> 209  assert(std::none_of(layouts.begin(), layouts.end(),
   210  [](SwRootFrame const*const pLayout) { return
pLayout->IsHideRedlines(); }));
   211  (void) layouts;
   212  break;

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148713] Unexpected table visible after redo table delete (and freezes when pressing delete column (track changes involved)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148713

Telesto  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 152799] Crash with ungroup shapes and also gets some warning in console with debug LO

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152799

Telesto  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr
 OS|Linux (All) |All
   Keywords||wantBacktrace

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 146248] Crash at undo header swlo!sw::XTextRangeToSwPaM+0x5f9:

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=146248

László Németh  changed:

   What|Removed |Added

   Assignee|nem...@numbertext.org   |libreoffice-b...@lists.free
   ||desktop.org
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #12 from László Németh  ---
@Telesto: many thanks for the bug report (and the newest one)!

@All: thanks for handling the issue!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151869] Freeze deleting an image with Track Changes Record ON

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151869

László Németh  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |nem...@numbertext.org
   |desktop.org |

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152963] newzealande

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152963

Eike Rathke  changed:

   What|Removed |Added

  Component|UI  |deletionRequest

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 56903] Moz-free Outlook Address Book driver

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=56903

Hossein  changed:

   What|Removed |Added

   Keywords|skillSql|
 Whiteboard||reviewed:2022
 CC||hoss...@libreoffice.org

--- Comment #8 from Hossein  ---
Re-evaluating the EasyHack in 2022

This enhancement is still relevant. But things have changed since 2012. I think
using Microsoft Jet Database Engine is not the best approach now, as it is
currently called a deprecated technology and it does not support 64 bit
applications.

(In reply to DavidO from comment #3)
> So what is the current name for the API?
> "Windows Address Book (WAB) API" or "Windows Contacts API"
> apparently they make a new one with every windows release?
As can be read here, "Windows Contacts" is the new application, and API:

"Windows Contacts is a contact manager that is included in Windows Vista,
Windows 7, Windows 8, Windows 10, and Windows 11. It replaced but retains most
of the functionality of Windows Address Book and worked with Windows Live Mail
and the Vista version of Windows Mail."
https://en.wikipedia.org/wiki/Windows_Contacts

Also, Microsoft explicitly says that WAB should not be used, and Windows
Contacts API should be used instead, for the new applications:

"New applications should not use this set of interfaces. These interfaces exist
for backward compatibility with legacy applications. These interfaces will be
unavailable in the future.
In Windows Vista, Windows Contacts replaces Windows Address Book (WAB). For
more information about this new mechanism for storing and retrieving contact
information, see Windows Contacts."
https://learn.microsoft.com/en-us/previous-versions/windows/desktop/wab/-wab-entry

Here, "Programming Windows Contacts" is discussed with many examples:

Programming Windows Contacts
https://learn.microsoft.com/en-us/previous-versions/windows/desktop/wincontacts/-wincontacts-example-entry

-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

[John Paul Adrian Glaubitz]

Hi Stephan!


There are currently 27 different, per-platform C++ UNO bridge implementations at
bridges/source/cpp_uno/, some of which are presumably dead by now. And my recent

"Rudimentary support for dynamic_cast on UNO proxy objects" (which had to touch
each of them individually) was the latest example how even presumably dead ones
have ongoing maintenance cost. Therefore, I would like to remove (on master,
towards LO 7.6) the ones that can clearly be identified as being dead.

Below, I sorted those 27 implementations into 5 categories: Ideally, each active
implementation would be built regularly by Jenkins; those 9 that are go into 
category
1. Next, there are 2 additional implementations that I know are built for Fedora
releases; they go into category 2. Next, there are 2 additional implementations
that I presume are built for Debian releases (Rene, correct me if I'm wrong);
they go into category 3. And then there are 3 implementations that are 
presumably
in active use elsewhere (Tor, wjh-la, Sakura286, correct me if I'm wrong); which
go into category 4. That leaves 11 implementations that are presumably dead, in
category 5.



(5) Presumably dead:
* gcc3_linux_alpha


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice=alpha


* gcc3_linux_hppa


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice=hppa


* gcc3_linux_ia64


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice=ia64


* gcc3_linux_m68k


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice=m68k


* gcc3_linux_powerpc


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice=powerpc


* gcc3_linux_sparc64


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice=sparc64

We're still maintaining these in Debian Ports. I have added the build logs for 
the latest builds above.

New builds will be triggered soonish when I have worked through the queue of 
package
dependencies that need to be fixed.


* gcc3_solaris_intel
* gcc3_solaris_sparc


Oracle is still maintaining Solaris until at least 2035 and OpenIndiana is 
still maintained, too.

According to this article, LibreOffice 7.2.7 was shipped with OpenIndiana 
2022.10:


https://www.theregister.com/2022/12/07/new_version_of_openindiana/


So, I'm not sure dropping Solaris support is a good idea either.


* gcc3_linux_sparc


32-bit SPARC is still supported by Gentoo, see:


https://www.gentoo.org/downloads/


Let me know if I can be of any help.

PS: I'm subscribed to this list, but I don't receive any mail.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

[Libreoffice-bugs] [Bug 147161] [LODE] Consider cloning core/ repo with less history

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147161

Hossein  changed:

   What|Removed |Added

   Keywords||difficultyMedium,
   ||skillScript

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 60909] Out of space warning ...

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=60909

Hossein  changed:

   What|Removed |Added

 Whiteboard||reviewed:2022

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 60909] Out of space warning ...

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=60909

--- Comment #10 from Hossein  ---
Created attachment 184569
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184569=edit
Error message when no disk space is available

Re-evaluating the EasyHack in 2022

This issue is still relevant. I ran Michael's instructions, then invoked the
below command after filling the disk space. As a result, I got an error message
that is provided here as an attachment. But, no warning message is shown when I
have some small disk space which is < 1 MB.

$ instdir/program/soffice -env:SAL_USE_VCLPLUGIN=gen
-env:UserInstallation=file:///tmp/small /tmp/small/1.pptx

While having < 1 MB disk space, I get this warning in the terminal, but not
when the space is between 1 and 2 MBs.

warn:configmgr:57868:58063:configmgr/source/components.cxx:190: error writing
modifications com.sun.star.uno.RuntimeException message: "cannot write to
file:///tmp/small/user/nnePqE at
~/Projects/libreoffice/core/configmgr/source/writemodfile.cxx:109"

Please note that both the profile and the opened file were inside /tmp/small.

-- 
You are receiving this mail because:
You are the assignee for the bug.