[Bug 103429] [META] Split and group buttons in toolbar and sidebar bugs and enhancements

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||160028


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160028
[Bug 160028] Type to select currency in split button dropdown does not work for
gtk3
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160028] Type to select currency in split button dropdown does not work for gtk3

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Summary|Type to select currency |Type to select currency in
   ||split button dropdown does
   ||not work for gtk3
 Whiteboard| QA:needsComment|
Version|24.8.0.0 alpha0+ Master |7.0.0.3 release
   Keywords||bibisected, bisected,
   ||implementationError
   Severity|enhancement |normal
 Status|UNCONFIRMED |NEW
 Blocks||103182, 103429
 CC||caolan.mcnamara@collabora.c
   ||om,
   ||stephane.guillou@libreoffic
   ||e.org

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Reproduced:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 53c5d570cab036b23f4969b858a648c8f0c24f93
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

This is actually a gtk3-specific bug:
- When in the sidebar, typing opens the search/filter overlay but it has no
effect. (Unlike e.g. the Styles deck, where such overlay works to jump to an
item.)
- with gen, kf5 and win VCL plugins, it is possible to jump to an item by
typing (both in sidebar and toolbar)

In 5.2, when the widget was added, and up to 6.4, typing would jump to the
correct item but would apply it directly and close the widget, for both gtk2/3
and gen.

In 7.0, it works as expected for gen but doesn't for gtk3.

Version: 7.0.0.3
Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: x11
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Bibisecting with linux-64-7.0, the sidebar's split button has the
non-functional search field popup since:

commit  b199e335c01f265ba2604c020928b63356b42d15
author  Caolán McNamara Fri Dec 27 17:18:44 2019 +
committer   Caolán McNamara Wed Jan 01 13:19:28 2020 +0100
weld NumberFormatPropertyPanel
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/85873

And the same was added to the toolbar with:

commit  bb362ca226a0089a1b036366e9ffc45ab5c90d8d
author  Caolán McNamara Wed Jan 08 13:15:29 2020 +
committer   Caolán McNamara Thu Jan 09 10:17:34 2020 +0100
use welded CurrencyList dropdown in all toolbars
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/86434

Caolán, could the gtk search be made functional for CurrencyList?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103182
[Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103429
[Bug 103429] [META] Split and group buttons in toolbar and sidebar bugs and
enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103182] [META] GTK3-specific bugs

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||160028


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160028
[Bug 160028] Type to select currency in split button dropdown does not work for
gtk3
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157591] context menu: "add to dictionary" -- no need to deselect word before

[bugzilla-daemon]

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

--- Comment #5 from Shantanu  ---
>> Or maybe we combine context menu #1 and #2 
>> specifically for misspelled words so that the user can correct 
>> misspelled words, add to dictionary, stylize words, etc. 
>> regardless of whether or not the misspelled word is selected/deselected
Yes. That is what being asked. 
It looks like a reasonable feature request.

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

[Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 Depends on||157591


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157591
[Bug 157591] context menu: "add to dictionary" -- no need to deselect word
before
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157591] context menu: "add to dictionary" -- no need to deselect word before

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||103341


Referenced Bugs:

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

[Bug 140752] .uno.DefaultNumbering and .uno:defaultBullet (on Formatting bar) modify a list style -- should it?

[bugzilla-daemon]

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

--- Comment #12 from Mike Kaganski  ---
(In reply to Justin L from comment #11)

Ah - thank you!
But why is this inevitable? Isn't it orthogonal, and can't these commands clear
the list prior to assigning the default?

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

[Bug 103537] [META] High contrast mode bugs and enhancements

[bugzilla-daemon]

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

Bug 126933 Summary: LO Writer shows some Buttons almost Unreadable when using 
High Contrast Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=126933

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

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

[Bug 126933] LO Writer shows some Buttons almost Unreadable when using High Contrast Theme

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #25 from Stéphane Guillou (stragu) 
 ---
(In reply to Adalbert Hanßen from comment #17)
> Created attachment 188022 [details]
> comparison old and new state, one minor item still to be improved
When using Hight Contrast, the Sifr icon theme should be automatically picked
because that is the one designed for High Contrast.
In High Contrast, icons are designed to be understandable in greyscale, and
ideally with only two colours that contrast significantly. So what you see as
an issue with the table toolbar is actually expected.
If anything, the Sifr theme should be improved to avoid using an intermediate
grey, and only have single-shade icons that contrast starkly with the
background.

As the original issue in this report is resolved, and we're getting to a large
number of comments, I am closing as "works for me".

Please open now, focused reports if you still see issues when testing with
version 24.2, starting with a new profile.

Thank you!

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

[Bug 160294] New: Base has strange behavior when setting auto value

[bugzilla-daemon]

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

Bug ID: 160294
   Summary: Base has strange behavior when setting auto value
   Product: LibreOffice
   Version: 7.0 all versions
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: prrv...@gmail.com

Description:
I can change whether a column is autoincremented or not in the jdbcDriverOOo[1]
driver.

When changing this option, by the drop-down list which depends on the column
which is selected, if we validate the changes by the Save button (Ctr + S)
while then did not take care to click again in the list of columns then the
changes are saved but Base will ask you to save again before closing.

If after changing the auto value option, I click in the list of columns (it
doesn't matter which one) and I save using the Save button then when I close
this window, Base does not ask me anything...

Steps to Reproduce:
1. Edit a table in Base.
2. Try to modify the auto value option
3. Save and exit the table editing window
4. When you exit Base asks you to save again.

Actual Results:
Base asks to save the changes even though it has just been done.


Expected Results:
Base don't asks to save the changes.


Reproducible: Always


User Profile Reset: No

Additional Info:
If just before saving using the Save button you make sure to put the cursor
back in the column grid (with a click on one of the columns) then everything
will work correctly.

[1] https://prrvchr.github.io/jdbcDriverOOo/

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

[Bug 157591] context menu: "add to dictionary" -- no need to deselect word before

[bugzilla-daemon]

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

Kira Tubo  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
   Keywords||needsUXEval
Version|unspecified |Inherited From OOo
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org

--- Comment #4 from Kira Tubo  ---
@peter josvai, thanks for clarifying! This makes much more sense now. 

But I wonder if this is by design. Because the way I see it: 

1. Context menu of the unselected misspelled word gives the user the option to
spell check/add to dictionary. 

2. Context menu of selected misspelled word gives the user the option to
stylize the word (rather than correcting/add to dictionary). 

If we were to replace context menu from #2 with #1, the user will no longer be
able to stylize a misspelled word from a context menu. 

If we were to add only 'Add to dictionary' to context menu of #2, I don't know
if it would be right to just add this category without giving the user the
option to also correct misspelled words. 

Or maybe we combine context menu #1 and #2 specifically for misspelled words so
that the user can correct misspelled words, add to dictionary, stylize words,
etc. regardless of whether or not the misspelled word is selected/deselected. 

Adding UX team to advise.

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

[Bug 160287] In Tabbed NotebookBar toolbar, "Print directly (%s)" button label contains the printer name, which is too long (uses 25-30% of available screen width space)

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||heiko.tietze@documentfounda
   ||tion.org
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Heiko, could this be an easyHack?

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

[Bug 160287] In Tabbed NotebookBar toolbar, "Print directly (%s)" button label contains the printer name, which is too long (uses 25-30% of available screen width space)

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Created attachment 193220
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193220=edit
Screenshot on Ubuntu 22.04 + GNOME 42.9, gtk3 VCL plugin

Reproduced in:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 53c5d570cab036b23f4969b858a648c8f0c24f93
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

In my case (Ubuntu 22.04 + GNOME 42.9 + gtk3 VCL plugin), the button is cut off
and looks bad.

Label on button should not show the printer name at all (or at least be
ellipsis'ed).

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

[Bug 159971] Base don't handle description, not null and default value on column

[bugzilla-daemon]

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

--- Comment #5 from prrv...@gmail.com ---
Ok, I just found out why I couldn't get the comments on the columns.

The SupportsColumnDescription option must be present in the Driver.xcu file and
must be under the XML node  and not .

It is a property attached to the driver and not to the connection info. And I
confirm that as soon as this option is in place, Base offers two description
columns to enter comments.

Well, on the other hand, I haven't made any progress on how to assign a default
value or a non-null constraint.

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

[Bug 153293] [META] Dark Mode bugs and enhancements

[bugzilla-daemon]

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

Bug 160288 Summary: Statusbar's icons and some widgets (slider drag handle) do 
not update when switching between light and dark theme, become invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=160288

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

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

[Bug 38305] icons in status bar do not update when icon theme changed (newly opened windows OK)

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||nekoh...@gmail.com

--- Comment #16 from Stéphane Guillou (stragu) 
 ---
*** Bug 160288 has been marked as a duplicate of this bug. ***

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

[Bug 160288] Statusbar's icons and some widgets (slider drag handle) do not update when switching between light and dark theme, become invisible

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thanks for the report.
This is already tracked in bug 38305.

*** This bug has been marked as a duplicate of bug 38305 ***

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

[Bug 38305] icons in status bar do not update when icon theme changed (newly opened windows OK)

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Summary|Symbols in status bar do|icons in status bar do not
   |not follow new Theme in |update when icon theme
   |opened document |changed (newly opened
   ||windows OK)

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

[Bug 160292] With columns formatted to date "xx/xx", still changes 3/4 to small font fraction

[bugzilla-daemon]

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

m_a_riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||miguelangelrv@libreoffice.o
   ||rg
 Resolution|--- |NOTABUG

--- Comment #1 from m_a_riosv  ---
Three options:
- Disable Menu/Tools/Autocorrect options/Options — Use replacement table
- Delete in Menu/Tools/Autocorrect options/Replace those not wanted.
- Use two digits at least for the first number of the date 03/4

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

[Bug 160039] Base does not show SQLException error messages

[bugzilla-daemon]

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

prrv...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |NOTOURBUG
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from prrv...@gmail.com ---
I just fixed this problem. This came from my SQLException which did not have a
SQLState and which apparently was not displayed in Base. Sorry for the
inconvenience, I'm closing.

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

[Bug 107158] [META] Notebookbar Groupedbar

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Depends on||160293


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160293
[Bug 160293] When clicking inside a pivot table, GroupedBar Compact hides all
its groups except "File" and "Edit"
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160293] When clicking inside a pivot table, GroupedBar Compact hides all its groups except "File" and "Edit"

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Blocks||107158, 103381


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103381
[Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107158
[Bug 107158] [META] Notebookbar Groupedbar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Depends on||160293


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160293
[Bug 160293] When clicking inside a pivot table, GroupedBar Compact hides all
its groups except "File" and "Edit"
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160293] New: When clicking inside a pivot table, GroupedBar Compact hides all its groups except "File" and "Edit"

[bugzilla-daemon]

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

Bug ID: 160293
   Summary: When clicking inside a pivot table, GroupedBar Compact
hides all its groups except "File" and "Edit"
   Product: LibreOffice
   Version: 24.2.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nekoh...@gmail.com

1. Create a spreadsheet with a pivot table
2. Set LibreOffice's toolbar UI layout mode to "Groupedbar compact"
3. Click a cell inside the existing pivot table

Result: all the toolbar group sections other than "File" and "Edit" disappear.

Expected result: they should not disappear; or at _least_, the "Data" group
section should remain shown, because it contains various things relevant to
pivot tables, if I am not mistaken.

In comparison, when using the other toolbar modes, such as "Standard"
(traditional toolbars), "Tabbed" (notebookbar), or "Tabbed Compact", the UI
doesn't change at all when clicking inside a pivot table's cells area.



Tested with:

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 8; OS: Linux 6.7; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded

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

[Bug 144488] Master documents: Hyperlink from one subdocument to another should be simplified to be internal when exported to ODT or PDF

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

URL||https://ask.libreoffice.org
   ||/t/cross-references-between
   ||-sub-documents/4574

--- Comment #17 from Stéphane Guillou (stragu) 
 ---
See also related user questions:
- https://ask.libreoffice.org/t/cross-references-between-sub-documents/4574
- https://forum.openoffice.org/en/forum/viewtopic.php?t=13724

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

[Bug 52444] : No one-step export of Master Document as self-sufficient word processing file

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||4488

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

[Bug 144488] Master documents: Hyperlink from one subdocument to another should be simplified to be internal when exported to ODT or PDF

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=52
   ||444

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

[Bug 144488] Master documents: Hyperlink from one subdocument to another should be simplified to be internal when exported to ODT or PDF

[bugzilla-daemon]

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

--- Comment #16 from Stéphane Guillou (stragu) 
 ---
Created attachment 193219
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193219=edit
test kit: two ODT subdocs, one ODM master

Test files as described in previous comment. Created with:

Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

But exports with recent trunk build has same results:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 53c5d570cab036b23f4969b858a648c8f0c24f93
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

See also bug 52444, about having the option to export a "self-contained and
self-sufficient" ODT, which this enhancement could be a part of.

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

[Bug 145676] Enhancement: Insert cross-references to Headings in other subdocuments

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||4488

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

[Bug 144488] Master documents: Hyperlink from one subdocument to another should be simplified to be internal when exported to ODT or PDF

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Severity|normal  |enhancement
 Status|UNCONFIRMED |NEW
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||5676
 Ever confirmed|0   |1
Summary|Hyperlink to target in  |Master documents: Hyperlink
   |external document doesn't   |from one subdocument to
   |work in Master document |another should be
   |exported to ODT or PDF  |simplified to be internal
   ||when exported to ODT or PDF
 Blocks||107805

--- Comment #15 from Stéphane Guillou (stragu) 
 ---
Thank you Harald, I understand.
Please feel free to unsubscribe to the report.

---

I tested with my own files created from scratch:
- sub-document ODT 1 with two headings
- sub-document ODT 2 with two headings + a hyperlink to one of the headings in
sub-document 1

What I see:
* In subdoc 2, the target comes up as "1.Heading 1 of subdoc 1|outline" in the
hyperlink dialog.
* Clicking the hyperlink in the Master document opens subdoc 1 in a new window.
* PDF export:
   * link is "subdoc1.odt#1.Heading%201%20of%20subdoc%201%7Coutline"
   * link does not work in Evince / Firefox / Chromium, but it _does_ in
Okular, leading to opening subdoc 1 at the correct heading
   * using the option "convert to PDF targets" does not help as it converts the
link to "subdoc1.pdf#1.Heading%201%20of%20subdoc%201%7Coutline" (subdoc1.pdf
does not exist)
* ODT export:
   * link does work, opens subdoc 1 at the correct heading
* It is possible to insert into the master document a hyperlink to a heading of
a subdocument, but that has to be done in a text section of the master, after
having included the subdocuments.

My conclusion:
I agree with Harald that hyperlinks to parts of documents should be converted
on export to PDF so they can be used to move inside the PDF (instead of opening
the source subdocument). Or at least have an option of the kind "Simplify
document target links for included files" that would follow the logic "if the
link URI points to a file that is included as a subdocument, simplify it so it
is internal to the exported file".

Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

See also bug 145676.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107805
[Bug 107805] [META] Writer master document issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107805] [META] Writer master document issues

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||144488


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=144488
[Bug 144488] Master documents: Hyperlink from one subdocument to another should
be simplified to be internal when exported to ODT or PDF
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160064] Named ranges created by the Solver should be hidden by default

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160062] We need an API to define solver models that are saved to the sheet

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 77963] FILEOPEN: WPS DOC - Text has wrong font and image not aligned correctly (fixed by round-tripping with Word)

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |INSUFFICIENTDATA

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

[Bug 160039] Base does not show SQLException error messages

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 112681] [META] DOC (binary) character-related issues

[bugzilla-daemon]

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

Bug 77963 Summary: FILEOPEN: WPS DOC - Text has wrong font and image not 
aligned correctly (fixed by round-tripping with Word)
https://bugs.documentfoundation.org/show_bug.cgi?id=77963

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |INSUFFICIENTDATA

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

[Bug 112701] [META] DOC (binary) image-related issues

[bugzilla-daemon]

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

Bug 77963 Summary: FILEOPEN: WPS DOC - Text has wrong font and image not 
aligned correctly (fixed by round-tripping with Word)
https://bugs.documentfoundation.org/show_bug.cgi?id=77963

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |INSUFFICIENTDATA

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

[Bug 157380] I am making a passcode list and your spreedsheet wont save as test without err:510

[bugzilla-daemon]

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

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

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.

[Bug 77963] FILEOPEN: WPS DOC - Text has wrong font and image not aligned correctly (fixed by round-tripping with Word)

[bugzilla-daemon]

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

--- Comment #17 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Bug 157372] New Insert Page Number is a PITA

[bugzilla-daemon]

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

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

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.

[Bug 157379] Expanding the data through the lower right corner of the selection corrupts the data

[bugzilla-daemon]

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

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

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.

[Bug 157330] Wrong flag shown for Swedish Page_Translate function

[bugzilla-daemon]

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

--- Comment #2 from QA Administrators  ---
Dear derek.n.e...@gmail.com,

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.

[Bug 60469] : Wrong "formulas formating" from excel 2010

[bugzilla-daemon]

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

--- Comment #13 from QA Administrators  ---
Dear Honza,

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.

[Bug 55846] Comboboxes aren’t displayed when the toolbar is vertical

[bugzilla-daemon]

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

--- Comment #30 from QA Administrators  ---
Dear Al McAusland,

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.

[Bug 141140] GTK3: menubuttons toggled states not visually consistent throughout the toolbars

[bugzilla-daemon]

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

--- Comment #7 from QA Administrators  ---
Dear Jeff Fortin Tam,

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.

[Bug 137840] GTK3 selection is different between Sidebar and Notebookbar

[bugzilla-daemon]

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

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

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.

[Bug 120078] When inserting snap guide lines, the position should be relative to page, not margin

[bugzilla-daemon]

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

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

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.

[Bug 160292] New: With columns formatted to date "xx/xx", still changes 3/4 to small font fraction

[bugzilla-daemon]

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

Bug ID: 160292
   Summary: With columns formatted to date "xx/xx", still changes
3/4 to small font fraction
   Product: LibreOffice
   Version: 6.4.7.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: alba...@hotmail.com

Description:
Columns formatted to Date, short form:  xx/xx enter date on March 4th and it
turns into the fraction 3/4 in small characters..


Steps to Reproduce:
1.type "3" "/" "4"
2.
3.

Actual Results:
3/4

Expected Results:
3/4
Can't change the font size here...


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 6.4.7.2
Build ID: 1:6.4.7-0ubuntu0.20.04.9
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

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

[Bug 159379] Writer crashes when multiple images are drag-and-dropped "As Character" (steps in comment 8)

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

  Regression By||Miklos Vajna
Summary|Writer crashes when |Writer crashes when
   |multiple images are |multiple images are
   |drag-and-dropped "As|drag-and-dropped "As
   |Character"  |Character" (steps in
   ||comment 8)
 OS|Linux (All) |All

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
Good spotting, Matt.

Updated steps:
0. Open Writer
1. In Options > LibreOffice Writer > Formatting Aids, change Image > Anchor to
"As Character" > OK
2. Select two copies of attachment 193103 in a file manager, and drag-and-drop
them onto the document

I checked the bibisection, it still applies.

Also crashed on Windows 11 (froze then a click crashed it) with signature
"GetFrameOfModify(SwRootFrame const *,sw::BroadcastingModify const
&,SwFrameType,SwPosition const *,std::pair const *)":
https://crashreport.libreoffice.org/stats/crash_details/d7eeb699-208b-44fb-b482-47eaa509f0ee
(not enough space in crash signature field to include it).

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

[Bug 156089] When the dialog customizes the Numbering type to "None", it still keeps the prefix/suffix, which need to be removed separately

[bugzilla-daemon]

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

--- Comment #16 from Justin L  ---
(In reply to Justin L from comment #12)
> This document really confused me: changeNumbering1.docx
solved by bug 159054

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

[Bug 159683] Crash on closing LibreOffice with certain content on the clipboard

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

  Regression By||Miklos Vajna
Version|7.6.5.2 release |7.6.0.0 alpha0+

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

[Bug 160208] Crash in: cppu::UnoType::get() when changing chart element's corner style in sidebar

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Summary|Crash in:   |Crash in:
   |cppu::UnoType::get() |ception>::get() when
   ||changing chart element's
   ||corner style in sidebar
 CC||fit...@ubuntu.com

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
(In reply to Julien Nabet from comment #8)
> even when
> double-clicking the blue line, I don't see "Corner Style" and "Cap Style".
I also noticed that it was missing. I just checked, it wasn't available either
in the dialog at Adolfo's e960180092a30738655e7e091b51f690914461ce, nor in OOo
3.3.
I think it would be good to have those options in the dialogs for chart
elements, but that's for a separate enhancement request.
There might be some limitation in how chart elements can be customised.
c1b96424b65aed2401a3e86d53a48cc12284de7c for bug 133630 might inspire a fix?

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

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

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

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #3 from m_a_riosv  ---
Maybe in relation with
https://bugs.documentfoundation.org/show_bug.cgi?id=150714
default encoded is UTF-8-encoded
So is needed to put the encoded if it is different. CSV files are plain text
with no encoded definition.

>>To work around the issue, specifying the ANSI encoding with the flag 
>>--infilter="CSV:44,34,ANSI" in the command line enables successful conversion 
>>of ANSI-encoded files to PDF.
It is not a workaround, it is part of command line options.

I think, not a bug.

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

[Bug 160286] Slow Calc FILEOPEN, EDITING, FILESAVE version 24.2.

[bugzilla-daemon]

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

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m_a_riosv  ---
Please test in safe mode, Menu/Help/Restart in Safe Mode

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

[Bug 160291] Sampling dialog should be able to run without closing the dialog

[bugzilla-daemon]

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

Rafael Lima  changed:

   What|Removed |Added

 Blocks||111310


Referenced Bugs:

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

[Bug 111310] [META] Data statistics bugs and enhancements

[bugzilla-daemon]

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

Rafael Lima  changed:

   What|Removed |Added

 Depends on||160291


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160291
[Bug 160291] Sampling dialog should be able to run without closing the dialog
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160291] New: Sampling dialog should be able to run without closing the dialog

[bugzilla-daemon]

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

Bug ID: 160291
   Summary: Sampling dialog should be able to run without closing
the dialog
   Product: LibreOffice
   Version: 24.8.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rafael.palma.l...@gmail.com

Currently, to perform sampling (Data - Statistics - Sampling), the user needs
to open the dialog, fill out all the options and then press OK. As soon as OK
is pressed, the dialog closes.

The problem with this is that all options are lost. So if the user wants to
perform a new "run" of the same settings, they need to reopen the dialog and
fill in all the options again.

It would be better to have a checkbox in the dialog with something like "Close
on OK". If this checkbox is unchecked, the dialog would remain open after OK is
pressed, allowing the user to run the sampling again if needed.

This would be similar to "Run immediately" option from the "Paste special"
dialog.

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

[Bug 142993] Sampling with replacement should still allow "keep order"

[bugzilla-daemon]

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

--- Comment #6 from Rafael Lima  ---
Apparently this issue is "intentional".

The method ScSamplingDialog::PerformRandomSamplingKeepOrder [1] assumes that
when "Keep Order" is checked, the sampling must be "without replacement". The
implementation does not consider the possibility of replacement.

To fix this issue, we would have to implement a new method to perform sampling
with replacement while keeping the original order. This is doable, but not
trivial. I'll add this to my to-do list, hopefully in time for 24.8.

[1]
https://opengrok.libreoffice.org/xref/core/sc/source/ui/StatisticsDialogs/SamplingDialog.cxx

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

[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

--- Comment #7 from Jeff Fortin Tam  ---
> That is all a one-time occurrence, or none at all.
> Once you know how it works, it is always only 2 clicks.

Nope. I've known about this issue for 10+ years and I _still_ keep hitting it,
as the behavior is counter to every other app, and even to other objects in
LOo.
I cannot "remember" it because it is inconsistent with everything else,
and feels unnatural even on its own.

It is not two clicks, it is four clicks every time you hit this bug:

1. Right-click: "Oh no, it clicked through the object I tried clicking on"
2. Left-click: the menu gets dismissed, but nothing gets selected.
3. Left click _again_ to select the object
4. Right-click _again_, and _then_ you finally get the menu.

…and that's the case of "no-hesitation correction, without trial-and-error".


There is also another flaw in your logic defending the current behavior:
right-clicking a shown comment object clicks through to select the cell,
but left-clicking does not "click through" the comment. Yet, by your logic,
one could argue someone could want to select "the cell behind" using left
click,
without a menu appearing, for whatever reason.

Z-order interaction behavior should be consistent whether it's right- or
left-click.
If you want alternate behavior, you use Alt.


> You are "polluting" unnecessary changes in a lot of reports [...]

Cross-linking topically related issues in a bug tracker has value.

If you are rather talking about c.c. addition notifications, you can go to
https://bugs.documentfoundation.org/userprefs.cgi?tab=email
and untick "The CC field changes". Or use email filters.

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

[Bug 159379] Writer crashes when multiple images are drag-and-dropped "As Character"

[bugzilla-daemon]

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

--- Comment #7 from Matt K  ---
(In reply to Stéphane Guillou (stragu) from comment #6)
> Thanks.
> Still reproduce with two copies of the attached picture and:

Confirmed crash using the attached images with following debug build:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 53c5d570cab036b23f4969b858a648c8f0c24f93
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-US (C.UTF-8); UI: en-US
Calc: threaded

The problem is that the repro instructions in comment 0 are wrong.  It says
"Anchor to "To Character".", but it should be "Anchor to "As Character"." like
the title of the bug says.

Output on command line is:
soffice.bin: /home/kali/libreoffice/core/sw/source/core/layout/atrfrm.cxx:1615:
void SwFormatAnchor::SetAnchor(const SwPosition *): Assertion
`(RndStdIds::FLY_AT_FLY == m_eAnchorId && pPos->GetNode().GetStartNode()) ||
(RndStdIds::FLY_AT_PARA == m_eAnchorId && pPos->GetNode().GetTableNode()) ||
pPos->GetNode().GetTextNode()' failed.

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

[Bug 133536] Links to external files in a Calc table integrated in a Writer document can no longer be updated (steps in comment 11)

[bugzilla-daemon]

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

--- Comment #17 from Arundel  ---
I have a very similar problem, but with the linking of cells from a main sheet
to cells in an embedded OLE sheet. I use the terms "source cell" as the source
cell in the main sheet, and "destination cell" as the destination cell in the
embedded OLE sheet.

I used two methods to set up the link: the GUI, and the Paste Special > Link. 
1) With the GUI method, I enter the equals sign in the inputbar for the
destination cell, then select a source from the main sheet with some text, and
press enter. Some file URL syntax is generated in the inputbar.
2) With Paste Special method, I select the source cell in the main sheet, copy,
then Paste Special > Link for the destination cell. Some file URL syntax is
generated in the inputbar.

On freshly inserted OLE's with only one destination cell set up with method 1: 
1) the destination cell's value is correct.
2) Edit > Links to external files... > Update can update the destination cell's
value indefinitely.

After a reload: I encounter different destination values, all conveying the
same outcome (the links not working); when I redirect the link to another
source cell through method 1 or 2, the destination cell's value becomes 0; and
when I press Edit > Links to external files... > Update, no update happens to
the destination cell's value.

I even witnessed after I linked, the destination cell's value becoming an old
version of the source cell's. But I haven't had the time to find the
reproduction steps for this.

Also, as my understanding of what is supposed to happen when entering the OLE
edit mode comes from OpenOffice, there is a major step missing that I never
witness in LibreOffice: the prompt for updating the links. OpenOffice always
shows such prompt. So even if there would not be the mentioned bug, the prompt
missing is also very annoying as you would need to manually update them.

My GUI is in Dutch so I have translated some terms. Both OpenOffice and
LibreOffice have this problem, and it seems to me that you need very similar
steps to reproduce the bug in both. I used OpenOffice v4.1.15 and LibreOffice
v7.6.5.2. The main sheet has been saved, with both programs at these versions. 

Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: nl-NL
Calc: threaded

This bug is critical as embedded modularity is non-existent for my sheets. I
was so happy to break free from the main grid by embedding another grid (OLE),
but then I discovered this.. Please fix it!

OP, does your bug still occur? Who can reproduce mine?

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

[Bug 133092] [META] Crash bugs

[bugzilla-daemon]

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

Bug 154863 Summary: Crash when moving images around in a multipage table
https://bugs.documentfoundation.org/show_bug.cgi?id=154863

   What|Removed |Added

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

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

[Bug 159683] Crash on closing LibreOffice with certain content on the clipboard

[bugzilla-daemon]

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

Matt K  changed:

   What|Removed |Added

 CC||vmik...@collabora.com
   Keywords|bibisectRequest |bibisected

--- Comment #12 from Matt K  ---
(In reply to Stéphane Guillou (stragu) from comment #11)
> It seems we can only crash it on Linux with a debug build (comment 3,
> comment 7, I assume comment 10 too, Matt?).

Yes, that's correct.

> On Windows 11, no crash in 7.5.0.3 -> regression.

I bibisected this using win64-7.6 repo and got the following result:

bad commit is c804c5354855188b5a37219cfe11dc079dc235f4

which is:

Author: Miklos Vajna 
Date:   Fri Mar 10 13:36:37 2023 +0100

sw content control: fix lost properties on copy

Adding Miklos to CC

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

[Bug 160172] A big ODT document still takes too long to open or save

[bugzilla-daemon]

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

--- Comment #7 from David García  ---
The problem also affects the 7.6 branch. These are my results on 7.6.6.2:

- Time to open the file: 5m57.
- Time to save the file: 16s.

Version: 7.6.6.2 (X86_64) / LibreOffice Community
Build ID: 036e73768e828796af6f3a43aa3296f3df77bb1d
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: es-ES
Calc: CL threaded

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

[Bug 101155] FILEOPEN PDF text overlaps because text is split to many boxes, with duplicated characters

[bugzilla-daemon]

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

--- Comment #11 from Eyal Rozenberg  ---
Can reproduce this with:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ffccbf4762a9ae810bcdd21c41fccdd436e7bfc9
CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3
Locale: he-IL (en_IL); UI: en-US
Calc: threaded

and I _do_ have Garamond - although with Garamond, the effect is much more
subtle.

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

[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

--- Comment #6 from ady  ---
(In reply to Jeff Fortin Tam from comment #5)
> You gain some clicks, you lose some. It's a net zero at the end.

That's a stretch, to put it mildly. It is in no way a zero net balance.

Generally speaking, less steps / clicks is usually better than requiring more
steps, unless the same UI gets cluttered and/or "moving interactively".

Every change has pros and cons.

As with other procedures in LO/Calc, there are surely better ways to interact
with the tool than the current ones.

> 
> For instance, your workflow requires users to do two clicks (or more) to
> intuitively get to the contextual menu of a comment (first a left click on
> the comment, then a right click on the comment; or first a right click, then
> realizing it doesn't work, then a left click, then a right-click).

That is all a one-time occurrence, or none at all. Once you know how it works,
it is always only 2 clicks. First select, then apply whichever action on the
selected object(s). I wished other procedures in Calc were so simple. If the UX
Team can make it better and consistent...


> 
> > as a side note, you don't need to add yourself to every single report 
> > related to Calc comments; just add yourself to the relevant meta 
> > (tdf#101216 for example) and you will receive emails for all those reports.)
> 
> Yup, I'm well acquainted with Bugzilla's features set :) however, doing so
> would not get me individual comment notifications from the sub-issues I care
> most about (that is why I subscribe to them), and I would get all the
> comments from SEO spammers that are posted onto the meta issue.

That is (by far) not accurate, while you are "polluting" unnecessary changes in
a lot of reports (some of them with no relevant interaction for years). Oh
well.

Please let's patiently wait for the UX Team comments now.

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

[Bug 160224] Rename "built-in help"

[bugzilla-daemon]

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

--- Comment #5 from Tuomas Hietala  ---
BTW, in the vast majority of cases Help is treated as a proper name,
"%PRODCUTNAME Help". "Built-in help" is the exception, used only in a
comparatively small number of strings. So what exactly makes this exception
absolutely untouchable is beyond my comprehension...

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

[Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements

[bugzilla-daemon]

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

Bug 159054 Summary: Ordered List toggle button is toggled even without numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=159054

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

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

[Bug 160224] Rename "built-in help"

[bugzilla-daemon]

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

--- Comment #4 from Tuomas Hietala  ---
(In reply to Adolfo Jayme Barrientos from comment #2)
> In several languages, “built-in” is translated as “integrated”; maybe you
> can use the equivalent term in your language to convey the idea.

Sure, but I also try to contribute to the quality of the English strings in the
hope that I can spare future users and translators from some confusion.

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

[Bug 160224] Rename "built-in help"

[bugzilla-daemon]

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

--- Comment #3 from Tuomas Hietala  ---
(In reply to V Stuart Foote from comment #1)
> This is distinct from other project documentation: e.g. Wiki delivery,
> published guides, etc. [1]

No, it's not distinct at all. In the Help menu in LO there are also links to
guides, Ask LibreOffice, feedback page, contribution page, and donation page.
Should all of these be called "built-in" because there's a link in the UI?

> 
> A whimsical change of legacy nomenclature would not improve delivery. 
> 
> =-ref-=
> [1] https://wiki.documentfoundation.org/Documentation

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

[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

--- Comment #5 from Jeff Fortin Tam  ---
You gain some clicks, you lose some. It's a net zero at the end.

For instance, your workflow requires users to do two clicks (or more) to
intuitively get to the contextual menu of a comment (first a left click on the
comment, then a right click on the comment; or first a right click, then
realizing it doesn't work, then a left click, then a right-click).

Otherwise, needing to know (and remember) that you must somehow right-click the
comment's *cell* itself is not as intuitively discoverable/expected for
changing the properties of a shown comment that is "right there in front of
you"). Force-shown comments are like "physical" objects, they should behave as
such. And it would be consistent with the rest of the application.

Need proof of this principle being already applied even within LibreOffice?
"Direct right-click" on an image or chart object selects & opens its context
menu.
It does not select the cells behind the chart/image.

Yes, the more "standard expectation" / "consistent UX" I'm proposing here would
require more clicks to accomplish your "select a cell behind a comment whose
contents you cannot see" scenario; but do people actually (want to) do that in
practice in the day-to-day? If moving/hiding the physical object out the way is
"too many clicks", and you really want to still offer the ability to
click-through while ignoring the visual z-ordering principle, then I believe it
would make more sense for this behavior to be behind the `Alt` keyboard
modifier, i.e. Alt+RightClick (which currently doesn't do anything on comments,
and presumably would be a better choice than Ctrl+(Right-)Click or
Shift+(Right-)Click). You could even apply that principle to images and charts
too, if you want.

> as a side note, you don't need to add yourself to every single report related 
> to Calc comments; just add yourself to the relevant meta (tdf#101216 for 
> example) and you will receive emails for all those reports.)

Yup, I'm well acquainted with Bugzilla's features set :) however, doing so
would not get me individual comment notifications from the sub-issues I care
most about (that is why I subscribe to them), and I would get all the comments
from SEO spammers that are posted onto the meta issue.

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

[Bug 149090] Excel kind hyperlink as cell-property produces invalid ODF

[bugzilla-daemon]

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #2 from BogdanB  ---
Still here
Version: 24.2.1.1 (X86_64) / LibreOffice Community
Build ID: 359ef544e625d2ffbfced462ab37bd593ca85fa7
CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
http://www.google.com/;
xlink:type="simple"/>http://www.google.com/;
xlink:type="simple"/>

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

[Bug 101546] Add a button to open the Tools-Options-Libreoffice-Paths-Edit Templates dialog directly from the Template Manager

[bugzilla-daemon]

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

Amos Aidoo  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |aidooamo...@gmail.com
   |desktop.org |

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

[Bug 101216] [META] Calc comment bugs and enhancements

[bugzilla-daemon]

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

Bug 160290 Summary: Right-clicking to select an always-shown comment in Calc 
"clicks through" and selects the cell behind it
https://bugs.documentfoundation.org/show_bug.cgi?id=160290

   What|Removed |Added

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

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

[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

ady  changed:

   What|Removed |Added

 Resolution|NOTABUG |---
   Severity|normal  |enhancement
 CC||heiko.tietze@documentfounda
   ||tion.org
 Status|RESOLVED|UNCONFIRMED

--- Comment #4 from ady  ---
(In reply to Jeff Fortin Tam from comment #3)
> I would like this to be given deeper UX consideration.

I am re-opening this report then. I will convert it from normal bug report to
an enhancement request. I am also CC'ing Heiko.


(In reply to Jeff Fortin Tam from comment #3)
> if I
> wanted to select the cells behind the comment, I would hide the comment
> first

While I understand your point, in practice such procedure would require more
(unrelated, or not really needed) steps.

With the current behavior, it is just 2 clicks (first left, then right), and
there is no need to hide (and then display again) the comment (or any other
object for that matter). It is a matter of practicality, and it is not _that_
strange nor unique either.

(@Jeff, as a side note, you don't need to add yourself to every single report
related to Calc comments; just add yourself to the relevant meta (tdf#101216
for example) and you will receive emails for all those reports.)

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

[Bug 86349] [META] Context menu bugs and enhancements

[bugzilla-daemon]

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

Bug 160290 Summary: Right-clicking to select an always-shown comment in Calc 
"clicks through" and selects the cell behind it
https://bugs.documentfoundation.org/show_bug.cgi?id=160290

   What|Removed |Added

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

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

[Bug 90577] Calc: Context menu of the visible comment itself should give option to remove & hide comment

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0290

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

[Bug 86349] [META] Context menu bugs and enhancements

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Depends on||160290


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160290
[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks
through" and selects the cell behind it
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Blocks||86349
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=90
   ||577

--- Comment #3 from Jeff Fortin Tam  ---
I would like this to be given deeper UX consideration. As a user, if I wanted
to select the cells behind the comment, I would hide the comment first (and in
that sense, this is related to bug #90577). It does not make sense to select
individual cells that I cannot see, because I cannot see what I am acting on.

I believe Z-ordering should be respected, and that manipulating objects should
behave predictably with qualities similar to how things work in the physical
world, and like in other UIs everywhere else (you don't expect right-clicking a
popover or window to "click through" in any window manager, for example).

The current behavior is contradicting many established UX principles throughout
operating systems and applications.


Referenced Bugs:

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

[Bug 159802] Writer Document does not print with Form detail in 24.2 release

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||hoelsc...@sikon-gmbh.eu

--- Comment #12 from V Stuart Foote  ---
*** Bug 160280 has been marked as a duplicate of this bug. ***

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

[Bug 108800] [META] Print related issues

[bugzilla-daemon]

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

Bug 160280 Summary: Writer Form Check-box controls are no longer being printed, 
form export (FDF, PDF) not affected
https://bugs.documentfoundation.org/show_bug.cgi?id=160280

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |DUPLICATE

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

[Bug 160280] Writer Form Check-box controls are no longer being printed, form export (FDF, PDF) not affected

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEEDINFO|RESOLVED

--- Comment #13 from V Stuart Foote  ---
Going to dupe to bug 159802 pretty clearly the same issue, resolved with the
24.2.2.1 build and 10346f5ff6f0ab6e3b2deb709e4f3e9cc49bf80c commit.

*** This bug has been marked as a duplicate of bug 159802 ***

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

[Bug 67219] [VIEWING] Ability to insert Comments for cell ranges / blocks of selected cells in spreadsheets

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

Summary|[VIEWING] Comment cell  |[VIEWING] Ability to insert
   |block selection |Comments for cell ranges /
   ||blocks of selected cells in
   ||spreadsheets
 CC||nekoh...@gmail.com

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

[Bug 101216] [META] Calc comment bugs and enhancements

[bugzilla-daemon]

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

Bug 160290 Summary: Right-clicking to select an always-shown comment in Calc 
"clicks through" and selects the cell behind it
https://bugs.documentfoundation.org/show_bug.cgi?id=160290

   What|Removed |Added

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

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

[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

ady  changed:

   What|Removed |Added

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

--- Comment #2 from ady  ---
Imagine that you actually want to select one of the cells that are covered by
the presence of the comment. With the current behavior, you can select any
cell, including those "behind" the comment. That is, either by right-click, or
by keyboard.

So, you would probably ask... How would you select the comment instead? The
answer is with the normal mouse button (i.e left-click).

And that is how we end up with your question... How to right-click on the
comment? The answer is:

1. left-click on the comment, so it is shown as "selected"; and then,
2. right-click on the same comment.

The context menu for the select comment will show up.

Other tools might use other methods, but ATM this is how it works for all LO
modules.

I am setting this report as NAB. Feel free to add relevant information that
would modify the status.

I would suggest for the next time to use .

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

[Bug 159802] Writer Document does not print with Form detail in 24.2 release

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0280

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

[Bug 160280] Writer Form Check-box controls are no longer being printed, form export (FDF, PDF) not affected

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||9802

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

[Bug 160280] Writer Form Check-box controls are no longer being printed, form export (FDF, PDF) not affected

[bugzilla-daemon]

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

--- Comment #12 from V Stuart Foote  ---
(In reply to V Stuart Foote from comment #11)
> Was it for work on bug 159452 to revert 9bad5be with this patch? Added btwn
> 24.2.1 and 24.2.2
> 
> https://gerrit.libreoffice.org/c/core/+/162729

But, maybe fix for bug 159817 and bug 159802 is the better choice:

https://gerrit.libreoffice.org/c/core/+/164328

to revert https://gerrit.libreoffice.org/c/core/+/153966 affecting positioning
of check boxes, but also radio buttons, combo boxes, and tab pages.

I did notice in my testing attempts against a different simpler two check box
form ODT, at 24.2.1 that the Check box's were present but misplaced to center
line and below the printed form fields.

But the check boxes were simply missing on printing from the Writer file.odt in
attachment 193201

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

[Bug 160280] Writer Form Check-box controls are no longer being printed, form export (FDF, PDF) not affected

[bugzilla-daemon]

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

--- Comment #11 from V Stuart Foote  ---
Was it for work on bug 159452 to revert 9bad5be with this patch? Added btwn
24.2.1 and 24.2.2

https://gerrit.libreoffice.org/c/core/+/162729

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

[Bug 101216] [META] Calc comment bugs and enhancements

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Depends on||160290


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160290
[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks
through" and selects the cell behind it
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Blocks||101216


Referenced Bugs:

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

[Bug 160290] Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

--- Comment #1 from Jeff Fortin Tam  ---
Created attachment 193218
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193218=edit
Demonstration video

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

[Bug 160290] New: Right-clicking to select an always-shown comment in Calc "clicks through" and selects the cell behind it

[bugzilla-daemon]

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

Bug ID: 160290
   Summary: Right-clicking to select an always-shown comment in
Calc "clicks through" and selects the cell behind it
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nekoh...@gmail.com

Created attachment 193217
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193217=edit
Sample spreadsheet

1. In a spreadsheet, Insert a comment in a cell
2. Right-click the cell, enable "Show comment" so that it remains shown at all
times, not only on hover.
3. Deselect the cell
4. Try to right-click anywhere on the shown comment

Result: it selects the cell underneath the comment, instead of selecting the
comment for right-click operations.

See attached sample, and attached demonstration video.

-

Tested with:

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 8; OS: Linux 6.7; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded

This was tested primarily under Wayland, but I believe this was happening with
Xorg too, in every previous LibreOffice release.

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

[Bug 160280] Writer Form Check-box controls are no longer being printed, form export (FDF, PDF) not affected

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #10 from V Stuart Foote  ---
(In reply to Mike Kaganski from comment #9)
> Can't repro using Version: 24.2.2.1 (X86_64) / LibreOffice Community
> Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882
> CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL:
> win
> Locale: ru-RU (ru_RU); UI: en-US
> Calc: CL threaded

Yep, now me either with
Version: 24.2.2.1 (X86_64) / LibreOffice Community
Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

@Rüdiger, Needinfo to you. Please install the "prerelease" 24.2.2.1 build and
retest. And if resolved, guess this can go WFM at 24.2.2

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

[Bug 55004] backup copy fails when using share / samba (if nobrl cifs mount option not used)

[bugzilla-daemon]

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

--- Comment #61 from Matthias Wilde  ---
Hi, 

struggled also on this issue (backup file on samba share fails) even having
newest version installed in Linux Mint:

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Ubuntu package version: 4:24.2.1~rc2-0ubuntu0.22.04.1~lo1
Calc: threaded

waiting now on fixed Version 24.2.2.

greets
Matthias

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

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

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

--- Comment #2 from Yaroslav Moiko  ---
Created attachment 193216
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193216=edit
Result PDF file that shows the problem with replaced special symbols

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

[Bug 160289] Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

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

--- Comment #1 from Yaroslav Moiko  ---
Created attachment 193215
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193215=edit
CSV File in ANSI encoding that contains a special characters. Use it as a
source

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

[Bug 160289] New: Converting ANSI encoded CSV file to PDF via command line results in replacing special characters (trademark:™,®) with the special question mark symbol:�

[bugzilla-daemon]

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

Bug ID: 160289
   Summary: Converting ANSI encoded CSV file to PDF via command
line results in replacing special characters
(trademark:™,®) with the special question mark
symbol:�
   Product: LibreOffice
   Version: 7.5.0.1 rc
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Printing and PDF export
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: yaroslav.mo...@gmail.com

Description:
When attempting to convert an ANSI-encoded CSV file to PDF via the command line
using LibreOffice, special characters such as ™ and ® are replaced with
question marks � in the resulting PDF file. The command used for conversion is
as follows:
'soffice.exe --headless --convert-to pdf "D:\MyCsvFile.csv" --outdir
"D:\conversionResults"'
This issue does not occur when opening the same file using the LibreOffice GUI
and subsequently exporting it to PDF via Calc. Furthermore, saving the CSV file
in UTF-8 encoding using Notepad++ allows for successful conversion via the
command line, preserving all original content.

To work around the issue, specifying the ANSI encoding with the flag
--infilter="CSV:44,34,ANSI" in the command line enables successful conversion
of ANSI-encoded files to PDF.

>From these observations, it appears that there may be a problem with
identifying the encoding of the source file when it is loaded for conversion
using the command line interface.

Additionally, it's worth noting that this issue is reproducible in all stable
releases following version 7.4.7.2.

Steps to Reproduce:
1. Create a .csv file that contains special characters such as ™ and ® and save
it using ANSI encoding. Or take the .csv file from the attachments.
2. Install any of the affected versions of LibreOffice (any starting from
7.5.0.1 to 7.6.6).
3. Convert the csv file to PDF using the following command line, replacing
paths as necessary: 'soffice.exe --headless --convert-to pdf "D:\MyCsvFile.csv"
--outdir "D:\conversionResults"'.
4. Inspect the result PDF document.

Actual Results:
Special characters such as ™ and ® from the source file are replaced with
question marks � in the result PDF file.

Expected Results:
All the content from the original file is preserved in the resulting PDF
document without any unwanted replacements. All special characters should be
kept.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

[Bug 153293] [META] Dark Mode bugs and enhancements

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Depends on||160288


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160288
[Bug 160288] Statusbar's icons and some widgets (slider drag handle) do not
update when switching between light and dark theme, become invisible
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160288] Statusbar's icons and some widgets (slider drag handle) do not update when switching between light and dark theme, become invisible

[bugzilla-daemon]

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

Jeff Fortin Tam  changed:

   What|Removed |Added

 Blocks||153293
   Keywords||accessibility


Referenced Bugs:

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