[Libreoffice-bugs] [Bug 131664] REPORT-BUILDER: Attribute "Auto Grow" will only be saved if first field of a row is set to "Auto Grow" → 'Yes'

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=131664

Robert Großkopf  changed:

   What|Removed |Added

 CC||lbi...@outlook.com

--- Comment #13 from Robert Großkopf  ---
*** Bug 148582 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 148582] Report Text Box Parameter "Auto Grow" Automatically Changes to "No" After Saving the Document

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148582

Robert Großkopf  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Robert Großkopf  ---
This bug has already been reported:
https://bugs.documentfoundation.org/show_bug.cgi?id=131664

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

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

[Libreoffice-bugs] [Bug 148582] Report Text Box Parameter "Auto Grow" Automatically Changes to "No" After Saving the Document

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148582

Robert Großkopf  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 131664] REPORT-BUILDER: Attribute "Auto Grow" will only be saved if first field of a row is set to "Auto Grow" → 'Yes'

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=131664

Robert Großkopf  changed:

   What|Removed |Added

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

--- Comment #12 from Robert Großkopf  ---
Bug still exists in LO 7.3.3.1 on OpenSUSE 15.3
See also the duplicate, which has just been reported.

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

[Libreoffice-bugs] [Bug 148493] replacement does not work well

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148493

--- Comment #5 from masao-...@jcom.home.ne.jp ---
Created attachment 179603
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179603=edit
a sample document

I tried change word "一昨昨日" to "一昨々日" in all tabs.

And serch and change did not work well. 

I made the file to attach for the test. As you know this file is a sort of a
diary. So I tried to deleate sensitve informations, but could not remove all, I
know. Please take this fle caefully.

When I reported the bug, search and change worked as normal change and
irregular channge both. Irregular change changed not targetted word to not
requeste word.

I tested this attached file, and in this file no word seemedchanged, althoug
target word was recognised.

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

[Libreoffice-bugs] [Bug 144782] LibreOffice_7.2.1_Win_x64.msi (323 MB) not downloading

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144782

Duane Steele  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |FIXED

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

[Libreoffice-bugs] [Bug 148274] AutoText from LO > 7.3 (or maybe > 7.0..?) incompatible with older versions

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148274

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 148311] calc . REQUEST for Copy & Past configurability ......... ( 500 000 asking calc user so far )

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148311

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 148306] ToC column layout does not default to the page style's direction

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148306

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 148305] Multi-column table of contents/index is always LTR

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148305

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 148487] when you try to insert a special character, Libre Office closes

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148487

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 148487] when you try to insert a special character, Libre Office closes

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148487

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

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

[Libreoffice-bugs] [Bug 148479] Support category indicators

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148479

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 148479] Support category indicators

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148479

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

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

[Libreoffice-bugs] [Bug 148299] Master Document: File not found if filename/path has back to back spaces.

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148299

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 148299] Master Document: File not found if filename/path has back to back spaces.

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148299

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

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

[Libreoffice-bugs] [Bug 144507] Unable to save spreadsheets when one of them is a CSV file

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144507

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 144507] Unable to save spreadsheets when one of them is a CSV file

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144507

--- Comment #7 from QA Administrators  ---
Dear Pete Haigh,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 142572] Mendely Plugin: Word to LibreOffice citation compatibility problem

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142572

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 142572] Mendely Plugin: Word to LibreOffice citation compatibility problem

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142572

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 145100] Applying numbered list style after bulleted increases its level

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145100

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

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 144782] LibreOffice_7.2.1_Win_x64.msi (323 MB) not downloading

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144782

--- Comment #2 from QA Administrators  ---
Dear Duane Steele,

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 133092] [META] Crash bugs

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092

Telesto  changed:

   What|Removed |Added

 Depends on||148620


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148620
[Bug 148620] Crash in Draw when using Format > Lists > Move Down
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148620] Crash in Draw when using Format > Lists > Move Down

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148620

Telesto  changed:

   What|Removed |Added

 Blocks||133092


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=133092
[Bug 133092] [META] Crash bugs
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148620] Crash in Draw when using Format > Lists > Move Down

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148620

Telesto  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 CC||tele...@surfxs.nl

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

[Libreoffice-bugs] [Bug 148620] Crash in Draw when using Format > Lists > Move Down

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148620

--- Comment #1 from Telesto  ---
Created attachment 179602
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179602=edit
BT with symbols

Confirm
Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: fbf739198aa7f02975d531521c6525073783c7f1
CPU threads: 8; OS: Mac OS X 12.2.1; UI render: Skia/Metal; VCL: osx
Locale: nl-NL (nl_NL.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 148620] Crash in Draw when using Format > Lists > Move Down

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148620

sdc.bla...@youmail.dk changed:

   What|Removed |Added

Summary|Crash in Draw when using|Crash in Draw when using
   |Format > Lists > Move Up|Format > Lists > Move Down

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

[Libreoffice-bugs] [Bug 148620] New: Crash in Draw when using Format > Lists > Move Up

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148620

Bug ID: 148620
   Summary: Crash in Draw when using Format > Lists > Move Up
   Product: LibreOffice
   Version: 7.4.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sdc.bla...@youmail.dk

Created attachment 179601
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179601=edit
test file for making Draw crash

First crash occurred in a textbox with a six item ordered list and using Format
> Lists > Move Up (and Move Down).

For subsequent crashes, I made a keyboard shortcuts to "Move Chapter Down" and
"Move Chapter Up" (see bug 144493 if you want to know why they have those names
in Customize).  I mention this because it makes testing easier.

STR.

1. Open attached draw document (or make your own list in a textbox).
2. Place cursor in a list item.
3. Press "down" shortcut key several times (rapidly may help).

It crashes reasonably quickly.  

STR 2

1. In attachment, select 4 lines of the list in the textbox.
2. Format > Lists > Move Down  (or use your shortcut key)

Crash.

Also reproduced using Safe Mode.

Have not tried to explore other possibilities, but Up may also produce crashes.

Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: d34d1db55978bdcff082af1e0f75b18fa6fc94f4
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: da-DK (da_DK); UI: en-US
Calc: CL

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

[Libreoffice-bugs] [Bug 148619] Cell reference in formula don't update on all sheets when moving cells on multiple sheets

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148619

--- Comment #1 from Gauthier  ---
Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-39-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

Version: 7.3.2.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Ubuntu package version: 1:7.3.2~rc2-0ubuntu0.20.04.1~lo1
Calc: threaded

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

[Libreoffice-bugs] [Bug 148619] New: Cell reference in formula don't update on all sheets when moving cells on multiple sheets

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148619

Bug ID: 148619
   Summary: Cell reference in formula don't update on all sheets
when moving cells on multiple sheets
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: g.gue...@posteo.net

Created attachment 179600
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179600=edit
broken sheet

I have attached and example spreadsheet but first I am going to describe what I
am trying to do and what the problem is.

Say you have 4 sheets with exactly same content on Sheet 1, 2, 3.

On those 3 sheets the cell A1 contains the formula: =B5*C5

If I select sheet 1,2,3, cut cell C5 and past it say in E7, the content of the
cell does move in all three sheets from C5 to E7 and the formula in A1 becomes
=B5*E7 also in all three sheets and so I get the right result. This is the
expected behaviour and if you open a blank spreadsheet and try that simple case
it just works.

However in the attached spreadsheet (test_broken.ods), this does not work. If I
select the 4 Project sheets (Project 1 to 4) and cut for example the cell W13
anywhere, say in V88, the formula in cell N9 which references W13 only updates
in the Project 1 sheet but does not in the others.
Similarly if you insert a column / row on the four sheets simultaneous, formula
affected by the shift only update on one sheet and not on the others.

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

[Libreoffice-bugs] [Bug 148449] Text style is locked into one definition that no editing can change

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148449

stragu  changed:

   What|Removed |Added

 OS|Windows (All)   |All
 Status|NEEDINFO|NEW

--- Comment #2 from stragu  ---
I have tested with the document supplied by Rory via private email and can
confirm that clearing the direct formatting of a specific paragraph (or
modifying the style) does not restore the font style or the font colour set up
in the style. For the paragraph in question, the font colour and the italics
are "sticky": they can only be changed by using the formatting toolbar.

Waiting for Rory to agree to share the document here for others to test.

Version: 7.2.6.2 / LibreOffice Community
Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754
CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 103866] Formula Vertical Alignment issue

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103866

--- Comment #35 from sdc.bla...@youmail.dk ---
(In reply to Ben from comment #33)
> I do think this is a bug and not a formatting issue. 
You do not need to determine if it is a bug. But, as noted in comment 31, you
need to provide sufficient information. The evaluations here are based on the
concrete information, not on assertions or intuitions about bugs. Without that
information, it is impossible to evaluate the situation.

Cited from:  How to Report Bugs in LibreOffice
https://wiki.documentfoundation.org/QA/BugReport

All bug reports should have at minimum:
your Operating System and version of LibreOffice;
clear reproducible steps;
expected results;
observed results; and
a simple attachment where appropriate.

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

[Libreoffice-bugs] [Bug 148608] Slide has background with 'hairlines' in powerpoint but not in LibO (and get lost on round trip)

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148608

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de
   Severity|normal  |enhancement
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #1 from Regina Henschel  ---
That is the special fill "Slide background fill" of an object. The object is
not transparent but copies the underlying slide background. So it looks as if
the object makes a hole in the shapes between itself and the slide background.
It depends on the position of the shape, which part of the background of the
slide is shown.

It can neither be solved by setting the shape background the same as the slide
background nor by setting the shape background transparent.

LibreOffice is not able to render this special fill and it cannot be expressed
in current ODF. It is the attribute "useBgFill" in OOXML.

I'm quite sure there are already reports about this problem. It might be bug
128150 or bug 147852. It is a missing OOXML feature, so set to enhancement.

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

[Libreoffice-bugs] [Bug 147732] font effect "small caps" does not work in Impress

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147732

--- Comment #10 from sdc.bla...@youmail.dk ---
(In reply to Xisco Faulí from comment #9)
> For me, 'Small capitals' is greyed out in the menu in Impress, so the option
> can't be used
Repro that Format > Text > Small capitals is greyed out.

@Xisco -- did you try:

1. Place cursor in text to be small cap'ed.
2. Right-click, choose Character
3. Choose "Font Effects" tab.
4. In "Case" dropdown box in Effects section, choose "Small capitals".

Does that not work for you?  (aside from the fact that it gives the result of
UPPERCASE letters, which is the OP).

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

[Libreoffice-bugs] [Bug 148513] Poor nomenclature for Manual Break

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148513

--- Comment #20 from sdc.bla...@youmail.dk ---
(In reply to Heiko Tietze from comment #19)
> Keep localization in mind.
Proposal in comment 14 seems translation-friendly in terms of understanding
(i.e., familiar nouns and adjectives, simple prepositions, no special
grammatical demands).

> And the UI scales according to the largest content.
The Spanish translation might be pretty long.

In that connectionto gain some more room in the "to" field ...

Could the Vertical and Horizontal control widths be reduced?
At present, there is a least a cm of white space in the drop down menu.   

Also the "by" field could probably be reduced a little.

And there is already bug 148512 to address the "to" field.

(and ftr, such UI adjustments are beyond my possibilities. Presumably it is
preferred that these changes are achieved before July string freeze.)

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

[Libreoffice-bugs] [Bug 148299] Master Document: File not found if filename/path has back to back spaces.

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148299

--- Comment #2 from John  ---
Hi Dieter, appreciate you looking into this!

For context I was writing specifications, with file names following a standard
format "## ## ## - Title".  Occasionally I'd double-tap the space bar, or an
extra space would sneak in there while renaming.  

The extra space is nearly invisible, so it just appeared to me like the file
was randomly corrupted.  It wasn't until I was looking at the files in windows
explorer that my OCD compelled me to figure out why some of the file names
weren't kerning properly, that I found the root cause.  Multiple spaces in the
filename is not at all a requirement, just a nearly-invisible accident.

Long story short:  a more descriptive error would be a fine solution.

Cheers!

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

[Libreoffice-bugs] [Bug 148559] FILESAVE: RTF: Border lost after RT

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148559

--- Comment #4 from Regina Henschel  ---
Created attachment 179599
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179599=edit
Reduced version of attachment 50625

I have reduced attachment 50625 to the affected object.

The patch will force the object to a default line. But I think, there is a
principle problem:

The object is not a text box (as I thought first) but it is a frame. When Word
exports docx to RFT, it sets the borders as paragraph borders. For such
RTF-document made by Word, LibreOffice renders the borders same as Word. LO
converts the paragraph group to a Frame.

But when LO converts the docx document to RTF it generates a shape and enables
default "stroke" of the shape. It does not consider border color and border
width. So there is a principle shortcoming in exporting such object from docx
to rtf.

Should we nevertheless use the patch?

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

[Libreoffice-bugs] [Bug 123381] FILEOPEN DOCX INT table formula is not working in LO

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=123381

--- Comment #8 from Xisco Faulí  ---
Proposed patch in https://gerrit.libreoffice.org/c/core/+/133091

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

[Libreoffice-bugs] [Bug 148618] Font size in fields is incorrect depending on the zoom level

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148618

Xisco Faulí  changed:

   What|Removed |Added

   Keywords||bibisected, bisected,
   ||regression
 CC||l.lu...@collabora.com
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #2 from Xisco Faulí  ---
Regression introduced by:

author  Luboš Luňák  2022-04-07 12:06:27 +0200
committer   Luboš Luňák  2022-04-08 21:29:19
+0200
commit  3e5863605881c6de6ad130fe06883c176ca1c69f (patch)
tree9e7863107a162eba8952710af00c281b91a12633
parent  53fe4a26c7c4691fcf9d07d022adfd45247d176b (diff)
use just one shared global SalLayoutGlyphsCache

Bisected with: bibisect-linux64-7.4

Adding Cc: to Luboš Luňák

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

[Libreoffice-bugs] [Bug 148618] Font size in fields is incorrect depending on the zoom level

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148618

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org

--- Comment #1 from Xisco Faulí  ---
Created attachment 179598
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179598=edit
wrong vs right

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

[Libreoffice-bugs] [Bug 148618] New: Font size in fields is incorrect depending on the zoom level

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148618

Bug ID: 148618
   Summary: Font size in fields is incorrect depending on the zoom
level
   Product: LibreOffice
   Version: 7.4.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: xiscofa...@libreoffice.org

Created attachment 179597
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179597=edit
sample file

Steps to reproduce:
1. Open attached document
2. Zoom in and out

-> Font size is incorrect

Reproduced in

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: ab8d141967111ca81f4607db3618bb09214e42db
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

and GEN

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

[Libreoffice-bugs] [Bug 109169] [FILESAVE DOCX] Some shapes are not correctly preserved when saved as DOCX

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109169

--- Comment #10 from Regina Henschel  ---
This is a first step. Now the geometry is correct. Still missing are shading
and handle.

Shading cannot be exported identical to LO, because OOXML has only four grades
of shading, whereas shapes of type "col-..." can have up to 14 grades of
shading. But before finding a suitable emulation the rendering in LO needs to
be fixed, see bug 148501.

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

[Libreoffice-bugs] [Bug 103866] Formula Vertical Alignment issue

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103866

--- Comment #34 from Ben  ---
Created attachment 179596
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179596=edit
Formula alignment in odt file

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

[Libreoffice-bugs] [Bug 103866] Formula Vertical Alignment issue

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103866

--- Comment #33 from Ben  ---
This issue can be further investigated by inspecting the attached .odt file.
After trying various changes once again, similar to what people have reported,
I do think this is a bug and not a formatting issue. Please check this in both
Windows and other environments. Unfortunately, this has literally taken me many
days of investigations on the Internet and trying all kinds of workarounds.

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

[Libreoffice-bugs] [Bug 109169] [FILESAVE DOCX] Some shapes are not correctly preserved when saved as DOCX

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109169

--- Comment #9 from Commit Notification 
 ---
Regina Henschel committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/b195cf4db4c21da3cf754689fb22f0b6a904a03e

tdf#109169 use custGeom for Octagon Bevel shape

It will be available in 7.4.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 109169] [FILESAVE DOCX] Some shapes are not correctly preserved when saved as DOCX

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109169

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.4.0

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

[Libreoffice-bugs] [Bug 148274] AutoText from LO > 7.3 (or maybe > 7.0..?) incompatible with older versions

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148274

--- Comment #3 from Cor Nouws  ---
Hi Dieter,

(In reply to Dieter from comment #2)
> I'm not familiar with AutoText, so I couldn't reproduce it without more
> detailed steps,

- Text document with some content
- select
- Ctrl+F3 or Tools>AutoText (dialog AutoText)
- Chose  category to create a category - it will be stored in your user profile
under /user/autotext/
- Choose Autotext > New to create an AutoText, select your category and give a
name
- Close LO
- Copy the /bau to the user profile of an older LO version


> ...  but i would like to ask, why somebody should create AutoText
> in LO 7 and use it in LO 6? So where is the use case for the described
> problem in real life?

Not something you expect indeed. Unless you have a .bau that you share with
someone else who turns out to have that older version :)

HTH & thanks for looking at this,
Cor

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

[Libreoffice-bugs] [Bug 148617] New: LO Calc - Grouped bar compact (GBC) - dropdown menu blocks menu next to it

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148617

Bug ID: 148617
   Summary: LO Calc - Grouped bar compact (GBC) - dropdown menu
blocks menu next to it
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: x86 (IA32)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dajo...@gmail.com

Description:
in the GBC layout I hit the "Review" drop down menu, and the menu appearance
follows the mouse click location. This means that if I click on the click on
the top edge of this menu button, the menu goes over "view" so that I have to
click it away before I can choose "view". If I click on the lower edge of the
"review" button, the menu appears a bit lower down so that "view" button is
available. I think that the menu appearance should not follow the mouse and the
menu buttons should always be available.

Steps to Reproduce:
1.Use Grouped bar compact
2.Click on "review" menu
3.

Actual Results:
See description

Expected Results:
See description


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

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

[Libreoffice-bugs] [Bug 148301] Shortcuts Ctrl+> and Ctrl+< not working

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148301

jr...@hotmail.com changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #2 from jr...@hotmail.com ---
Didn't work with and without profile reset. (Also customised Ctrl+Shift+[ to
check if it was something Ctrl+Shift related, but it worked normally)

Profile reset done as:
1. Start LibreOffice and select Help ▸ Restart in Safe Mode
2. Select Continue in Safe Mode (after restart is done and a modal dialog
appears)

[New version info]
OS: Fedora 35 (5.16.19-200.fc35.x86_64)
GNOME Shell 41.4
Windowing system: Wayland
Version: 7.3.2.2 / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 4; OS: Linux 5.16; UI render: default; VCL: gtk3
Locale: pt-BR (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 108743] [META] Find toolbar bugs and enhancements

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108743
Bug 108743 depends on bug 148349, which changed state.

Bug 148349 Summary: Use attention-attracting cue when pressing Ctrl+F while in 
the find bar
https://bugs.documentfoundation.org/show_bug.cgi?id=148349

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144072

Aron Budea  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #17 from Aron Budea  ---
I'm able to reproduce it in LO 7.4.0.0.alpha0+
(ab612633003c75dfb30664db8cc8924c086a91ee) / Ubuntu.

I have to say, the UX of resizing those widgets is terrible, you try to drag
from the right edge, and it resizes from the left, or from the corner. That's
one of the reasons why the crash is hard to reproduce.

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

[Libreoffice-bugs] [Bug 147237] Dynamic theme gtk switching only partially switches colors

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147237

--- Comment #12 from Commit Notification 
 ---
Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/37fb1cbf7bceac8421741dc55b89146a42a77a22

Related: tdf#147237 change the SalObject background when the settings change

It will be available in 7.4.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 147237] Dynamic theme gtk switching only partially switches colors

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147237

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.4.0

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

[Libreoffice-bugs] [Bug 148616] FILEOPEN PPTX A certain POTX template is slow to open

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148616

Buovjaga  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Severity|normal  |minor
 Status|UNCONFIRMED |NEW

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

[Libreoffice-bugs] [Bug 148616] FILEOPEN PPTX A certain POTX template is slow to open

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148616

--- Comment #1 from Buovjaga  ---
Created attachment 179595
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179595=edit
Perf flamegraph

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

[Libreoffice-bugs] [Bug 148616] New: FILEOPEN PPTX A certain POTX template is slow to open

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148616

Bug ID: 148616
   Summary: FILEOPEN PPTX A certain POTX template is slow to open
   Product: LibreOffice
   Version: 6.3.0.4 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Keywords: haveBacktrace, perf
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ilmari.lauhakan...@libreoffice.org
Blocks: 108226

Created attachment 179594
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179594=edit
Slow template

Originally reported by Dedoimedo:
https://www.dedoimedo.com/computers/libreoffice-7-2-review.html

Template from MS
https://templates.office.com/en-US/Organic-presentation-TM78453729

Takes about 25 secs to open.

Oldest tested version 6.3.

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: b2b821715a3745718a941fa99dda92137c0f0c86
CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108226
[Bug 108226] [META] PPTX (OOXML) bug tracker
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108226] [META] PPTX (OOXML) bug tracker

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108226

Buovjaga  changed:

   What|Removed |Added

 Depends on||148616


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148616
[Bug 148616] FILEOPEN PPTX A certain POTX template is slow to open
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 126087] Hang/processing loop pasting a large table after undo in multipage view

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126087

Buovjaga  changed:

   What|Removed |Added

 Attachment #179590|0   |1
is obsolete||

--- Comment #7 from Buovjaga  ---
Created attachment 179593
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179593=edit
Perf flamegraph

I might have absentmindedly used some incorrect version for testing, so
uploading a trace taken with an --enable-symbols build

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: b2b821715a3745718a941fa99dda92137c0f0c86
CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 135703] EDITING Inserting paragraph before multi page table causes CPU spike

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135703

Buovjaga  changed:

   What|Removed |Added

 Attachment #179538|0   |1
is obsolete||

--- Comment #4 from Buovjaga  ---
Created attachment 179592
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179592=edit
Perf flamegraph

I might have absentmindedly used some incorrect version for testing, so
uploading a trace taken with an --enable-symbols build

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: b2b821715a3745718a941fa99dda92137c0f0c86
CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 143441] FILEOPEN TABLE: Writer process stops responding when opening MS Office doc with vertical text center aligned on merged table cells that cross pages

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143441

--- Comment #5 from Buovjaga  ---
Created attachment 179591
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179591=edit
Perf flamegraph

I might have absentmindedly used some incorrect version for testing, so
uploading a trace taken with an --enable-symbols build

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: b2b821715a3745718a941fa99dda92137c0f0c86
CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 126087] Hang/processing loop pasting a large table after undo in multipage view

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126087

Buovjaga  changed:

   What|Removed |Added

 Attachment #179537|0   |1
is obsolete||

--- Comment #6 from Buovjaga  ---
Created attachment 179590
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179590=edit
Perf flamegraph

I might have absentmindedly used some incorrect version for testing, so
uploading a trace taken with an --enable-symbols build

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: b2b821715a3745718a941fa99dda92137c0f0c86
CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 112969] [META] DOCX (OOXML) field-related issues

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112969
Bug 112969 depends on bug 148494, which changed state.

Bug 148494 Summary: FILESAVE DOCX Field MacroButton saved incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=148494

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 131751] Character emphasis is not rendered correctly in print and export

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=131751

--- Comment #9 from Kenneth Hanson  ---
Bug still present in v7.2.6.2.

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

[Libreoffice-bugs] [Bug 148599] Frame style issue

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148599

--- Comment #2 from la...@hotmail.com ---
Hi,
  It seems that when a frame property is changed on a frame instance, style are
not influencing that property anymore.
  Is it the correct behavior ?
  Then, how do we reset the override ?

Regards

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

[Libreoffice-bugs] [Bug 148615] Grid settings in Draw not properly set upon loading file

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

Scott  changed:

   What|Removed |Added

 CC||salex...@gmail.com

--- Comment #1 from Scott  ---
Created attachment 179589
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179589=edit
Draw file with specific grid settings

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

[Libreoffice-bugs] [Bug 148479] Support category indicators

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148479

--- Comment #2 from Eyal Rozenberg  ---
(In reply to Heiko Tietze from comment #1)
> Likely not possible without changing the ODF spec.

Oh, yes, certainly. I should have mentioned that. Definitely asking for this to
be directly representable in ODF files and part of the spec.

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

[Libreoffice-bugs] [Bug 148615] New: Grid settings in Draw not properly set upon loading file

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

Bug ID: 148615
   Summary: Grid settings in Draw not properly set upon loading
file
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: salex...@gmail.com

Description:
I have various Drawings generated with Draw with different grid settings. I
noticed when I load a Drawing to work on it items would be off grid and a mess.
Figured out it was because the Grid settings are not properly set for each
drawing when the drawing is loaded.

Steps to Reproduce:
1. Open Draw
2. Set Tools | Options | General | UOM : Inch
3. Set Tools | Options | Grid : Snap to Grid:on + Visible Grid:on + H/V= 1.00"
+ H/V Spaces=5
4. Apply
5. Close Draw
6. Open Draw
7. Verify the previous settings
8. Open grid1.odg
9. Check the Options to see if they agree with file settings



Actual Results:
When I perform these steps and check the grid settings I find the Grid H/V
settings are 2.54 cm.

Expected Results:
The Grid H/V settings should be 1.00 cm.


Reproducible: Always


User Profile Reset: No



Additional Info:
I can reproduce this on two different windows 11 computers.
I can reproduce many variations of this problem opening and closing files with
different grid settings.
OpenGL doesn't seem to make a difference.

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

[Libreoffice-bugs] [Bug 148494] FILESAVE DOCX Field MacroButton saved incorrectly

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148494

Xisco Faulí  changed:

   What|Removed |Added

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

--- Comment #4 from Xisco Faulí  ---
Proposed fixed in https://gerrit.libreoffice.org/c/core/+/133077

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

[Libreoffice-bugs] [Bug 147237] Dynamic theme gtk switching only partially switches colors

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147237

--- Comment #11 from Caolán McNamara  ---
https://gerrit.libreoffice.org/c/core/+/133076 should at least fix comment #10
and the "speckles" that can be seen at the corner of the comboboxes in that
image.

Comment #9 however I can't reproduce and I'm not sure I'm looking at the right
thing. "Default Paragraph Style" and "Clear formatting" looks a bit like the
top of the style dropdown from the standard toolbar, but in 7.3 those entries
are the other way around and don't have that wide bevel around them

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

[Libreoffice-bugs] [Bug 147237] Dynamic theme gtk switching only partially switches colors

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147237

Caolán McNamara  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

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

[Libreoffice-bugs] [Bug 148612] Bug in a macro that cannot read cells

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148612

Mike Kaganski  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

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

[Libreoffice-bugs] [Bug 148612] Bug in a macro that cannot read cells

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148612

--- Comment #2 from Mike Kaganski  ---
Created attachment 179588
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179588=edit
Minimal bugdoc

Repro using Version: 7.3.3.1 (x64) / LibreOffice Community
Build ID: 1688991ca59a3ca1c74bc2176b274fba1b034928
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: default; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: 

The attachment has minimal macro needed to reproduce the bug. Looks like having
something named "cells" referenced from a sub, affects use of an object's
member having the same name in another function. Renaming "cells" to anything
else in "test3" makes "test_bug" function properly copy data from A1 to A2.

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

[Libreoffice-bugs] [Bug 148494] FILESAVE DOCX Field MacroButton saved incorrectly

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148494

Xisco Faulí  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 CC||xiscofa...@libreoffice.org

--- Comment #3 from Xisco Faulí  ---
Reproduced in

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: ab8d141967111ca81f4607db3618bb09214e42db
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

and Word 2016

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

[Libreoffice-bugs] [Bug 147732] font effect "small caps" does not work in Impress

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147732

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org

--- Comment #9 from Xisco Faulí  ---
For me, 'Small capitals' is greyed out in the menu in Impress, so the option
can't be used

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

[Libreoffice-bugs] [Bug 148493] replacement does not work well

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148493

Xisco Faulí  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #4 from Xisco Faulí  ---
Please attach a sample document, as this makes it easier for us to verify the
bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive
information before attaching it. 
See
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
for help on how to do so.)

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

[Libreoffice-bugs] [Bug 148528] FILEOPEN RTF User name field updated on opening

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148528

Xisco Faulí  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||xiscofa...@libreoffice.org
 Status|UNCONFIRMED |NEW

--- Comment #2 from Xisco Faulí  ---
Reproduced in

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: ab8d141967111ca81f4607db3618bb09214e42db
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 148487] when you try to insert a special character, Libre Office closes

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148487

--- Comment #4 from Kenou  ---
I work with CPU.
On my Mac desk, I have the same Monterey and I have no problem but the version
of LibreOffice is not the same, it is a previous one 7.0.3.1.

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

[Libreoffice-bugs] [Bug 148541] Crash in: google_breakpad::ExceptionHandler::HandlePureVirtualCall()

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148541

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org

--- Comment #4 from Xisco Faulí  ---
I can't reproduce it in

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: ab8d141967111ca81f4607db3618bb09214e42db
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: x11
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 148578] FILEOPEN RTF Table left indent incorrect

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148578

Xisco Faulí  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 CC||xiscofa...@libreoffice.org

--- Comment #3 from Xisco Faulí  ---
Reproduced in

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: ab8d141967111ca81f4607db3618bb09214e42db
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 148575] Crash when I tried to change the contents in a formula field of a write table

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148575

Xisco Faulí  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||xiscofa...@libreoffice.org
 Ever confirmed|0   |1

--- Comment #4 from Xisco Faulí  ---
(In reply to special from comment #2)
> Roman,
> 
> unfortunately this file contains confidential tax reports, so I can't send
> it.
> 
> Regards --  HGJ

Hello,
would you mind sharing the file with me via email ? I can test it locally and
the file won't be available to anyone else.

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

[Libreoffice-bugs] [Bug 108905] UI: Imported Page Area Bitmap background resets to default after having applied Transparency or other page property

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108905
Bug 108905 depends on bug 132048, which changed state.

Bug 132048 Summary: CROSS-REFERENCE: Cutting a referenced title breaks 
the cross-reference to that title
https://bugs.documentfoundation.org/show_bug.cgi?id=132048

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 132048] CROSS-REFERENCE: Cutting a referenced title breaks the cross-reference to that title

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132048

Roberto Cantù  changed:

   What|Removed |Added

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

--- Comment #7 from Roberto Cantù  ---
Hello QA Team,

tested just now, now it works.

Thank you very much & happy Easter
Roberto

Version: 7.2.6.2 (x64) / LibreOffice Community
Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: it-IT (it_IT); UI: it-IT
Calc: threaded

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

[Libreoffice-bugs] [Bug 139962] Creating a new .odt file from Win Explorer does not use default template

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139962

--- Comment #5 from Mike Kaganski  ---
FTR: This is *not* "skillCpp"; I do not see a matching "skillAny" in the
possible values ;) - so I'll keep what is set now :-D

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

[Libreoffice-bugs] [Bug 139962] Creating a new .odt file from Win Explorer does not use default template

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139962

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 CC||sdc.bla...@youmail.dk
   Keywords||skillCpp

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

[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143344
Bug 143344 depends on bug 148448, which changed state.

Bug 148448 Summary: Warning is unreadable in Mail Merge Wizard in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=148448

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 148448] Warning is unreadable in Mail Merge Wizard in dark mode

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148448

Caolán McNamara  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
   Assignee|libreoffice-b...@lists.free |caol...@redhat.com
   |desktop.org |

--- Comment #5 from Caolán McNamara  ---
couldn't see anything good to take a warning color from, so in the end just
picked a color I could read it with as a background

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

[Libreoffice-bugs] [Bug 148448] Warning is unreadable in Mail Merge Wizard in dark mode

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148448

--- Comment #4 from Commit Notification 
 ---
Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/a0f9f8ddaaa4ca14c9cc37259e2ac5dce63b3c77

tdf#148448 pick a warning color more likely to be readable in dark theme

It will be available in 7.4.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 148448] Warning is unreadable in Mail Merge Wizard in dark mode

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148448

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.4.0

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

[Libreoffice-bugs] [Bug 148614] Date fields not printed

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148614

freew...@free.fr changed:

   What|Removed |Added

 CC||freew...@free.fr

--- Comment #1 from freew...@free.fr ---
Created attachment 179587
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179587=edit
document with date fields

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

[Libreoffice-bugs] [Bug 139962] Creating a new .odt file from Win Explorer does not use default template

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139962

Mike Kaganski  changed:

   What|Removed |Added

   Keywords||difficultyBeginner,
   ||easyHack

--- Comment #4 from Mike Kaganski  ---
So now, after tdf#139991 is implemented, it allows to fix this trivially: make
the shell's New command to create an *empty* (0-byte) file. LibreOffice would
open such a file as a new document of type detected from extension only, using
default template (if any) set for respective component.

For Windows, it implies:
1. Search for all occurrences of "shellnew" in the codebase;
2. In the SCP files found, replace respective "Name" from "FileName" to
"NullFile", and "Value" from "\share\template\shellnew\soffice.*" to
"" (empty string);
3. Drop extras/source/shellnew/*.

There should be some similar way for Linux integrations (or, if unavailable, we
would need to still provide 0-byte files under extras/source/shellnew/, instead
of dropping them at #3 above).

As maybe simple solution, just making all those files under
extras/source/shellnew/ 0-byte would be enough, without a need to modify
anything else. That would automatically work for any Linux integration making
use of the files, too.

The caveat is that the new way relies on special-processing the 0-based files,
which are *not* proper ODF packages. MS Office uses the same technique; but if
you open those files using a different application before editing and saving in
LibreOffice, the results would be unexpected (just the same way as they were in
LibreOffice before implementation of tdf#123476).

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

[Libreoffice-bugs] [Bug 148614] New: Date fields not printed

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148614

Bug ID: 148614
   Summary: Date fields not printed
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: freew...@free.fr

Description:
I have multiboot W7 W10 Ubuntu 20.04, MATE 20.04 and Mint cinnamon 20.3. Epson
StylusPhoto R800.
I have no problem with a document with date fields with Windows 7 and 10
Libreoffice 7.2.6.2 (x64)
I think there was no problem with Ubuntu 18.04 (I don't remember there was a
problem),
but since I upgrade to Ubuntu 20.04, (and also with the last version of MATE
and Mint cinnamon), the date fields are not printed, (and not visible on the
preview).
The option is cheked when printing.
I tested deb 6.4.7.2, and 7.3.2.2  (snap and flatpak) it is the same...
Thank you

Steps to Reproduce:
1.Open document
2.Print
3.

Actual Results:
The date fields are not printed, and not seen on preview

Expected Results:
The fields with the date should be printed!


Reproducible: Always


User Profile Reset: No



Additional Info:
I tested deb 6.4.7.2, and 7.3.2.2  (snap and flatpak):same behaviour

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

[Libreoffice-bugs] [Bug 148613] New: Setting hotkey via macro only works after a restart.

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148613

Bug ID: 148613
   Summary: Setting hotkey via macro only works after a restart.
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: so...@comec92.ru

Execute a macro that sets the Alt+F1 hotkey. Alt+F1 combination starts to be
processed only after LO restart.

Sub TestAccSetKey
   Dim oACC, keyEvent As New com.sun.star.awt.KeyEvent 
  
oACC=com.sun.star.ui.ModuleAcceleratorConfiguration.createWithModuleIdentifier("com.sun.star.sheet.SpreadsheetDocument")
 
   With keyEvent
 .KeyCode=com.sun.star.awt.Key.F1
 .Modifiers=4   ' Alt
   End With   
   oAcc.setKeyEvent KeyEvent,
"vnd.sun.star.script:Standard.Module1.MyMacro?language=Basic=application"
   oAcc.store  ' save
End Sub

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

[Libreoffice-bugs] [Bug 113604] Optimal column width of table in Writer is not persistent (see comment #2 about unused style:use-optimal-column-width")

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113604

--- Comment #18 from Christian Lehmann  ---
Created attachment 179586
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179586=edit
Demonstration of the effect of 'optimal column width' for different tables

Please try 'optimal column width' on the example tables and assess the
acceptability of the result.

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

[Libreoffice-bugs] [Bug 113604] Optimal column width of table in Writer is not persistent (see comment #2 about unused style:use-optimal-column-width")

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113604

--- Comment #17 from Christian Lehmann  ---
Heiko's mockup solves a number of problems. However, it does not contribute
much to the problem of optimal column width. We require a definition of this
concept to begin with. The idea behind it appears to be this: The columns of a
table have optimal width if, for a given table width, the table height is the
smallest possible and no column is wider than necessary.

The table width may be "given" because the user defined it or set it to the
page width. It is, however, also possible that the user had produced an interim
width just for the while that he fills the cells and afterwards wants it to be
set automatically to the minimum necessary width.

There are, then, at the moment that the user triggers 'optimal column width',
two possible start situations depending on whether or not the user has set and
locked the table width. In the former case, the procedure producing optimal
column width does have to get by on the given table width. In the latter case,
the procedure first determines the minimum height for the maximal table width
and then shrinks the table and column width down to the point where it leads to
a heightened table height.

This presupposes that there be, on the table configuration mockup and under
'Position/Size', an additional line for the table width (which in the mockup
misleadingly is under 'Columns') and which the user may or may not 'lock'. If
he does, he limits his freedom to set the column widths. If he does not,
triggering 'optimal column width' will set it to the possible minimum.

I attach an example file which illustrates what is meant and also a bug.

Moreover, all of this does not yet solve the problem of making 'optimal column
width' persistent. This could be an option in the box presented for 'Insert
table', side by side, and of equal status, with 'Don't split table over pages.'

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

[Libreoffice-bugs] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148257

--- Comment #16 from Mike Kaganski  ---
(In reply to Eyal Rozenberg from comment #15)
> > This one should be WF
> 
> Do you mean you're suggesting this issue be marked WFM?

WFM stands for "WORKSFORME", a resolution that means "there was a reproducible
problem that OP described, in some version; later, it was obviously fixed, so
it is not reproducible anymore in newer versions, but we don't know which
commit was that - so instead of marking FIXED (reserved for cases where we know
exact commit), we use WORKSFORME".

WF stands for WONTFIX, which is for "there is an acknowledged problem around
this issue, but this proposal should not be implemented" (there may be
different reasons why).

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

[Libreoffice-bugs] [Bug 42673] With disconnected network printers, Calc hangs opening some files waiting on the Windows print spooler

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42673

--- Comment #46 from Peter Mandrella  ---
SAL_DISABLE_DEFAULTPRINTER=1 solves the issue for Calc, Draw, Impress and
Writer.

Math additionally needs SAL_DISABLE_PRINTERLIST=1.

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

[Libreoffice-bugs] [Bug 42673] With disconnected network printers, Calc hangs opening some files waiting on the Windows print spooler

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42673

--- Comment #45 from Peter Mandrella  ---
I tried the workaround, and - yes, this environment setting solves the issue
for me:

SAL_DISABLE_DEFAULTPRINTER=1

LibreOffice apps do no longer hang on startup, but only when I actually try to
print a document. And before each print, the message "No default printer found"
(translated from German by me) must be confirmed, and a printer must be
selected.

Then, I alternatively tried to set the default printer in the Windows control
printer to a local printer (the Print-to-PDF device included with Windows 11).
That did not work for LibreOffice, but for Pegasus Mail. Nice, now all fine.

Thanks!

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

[Libreoffice-bugs] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148257

--- Comment #15 from Eyal Rozenberg  ---
(In reply to Mike Kaganski from comment #14)
> setting the language, ... should be enough.

I would be fine with the ability to set the language independently of the
direction, but - what will map this setting to a change of font?

> or explicitly setting direction and font, 

Neither of these are relevant in themselves. The entanglement with the
direction setting is part of my problem here - I need to change the language
regardless of the direction.

> The problem that the "language group" tries to solve comes from not
> all fonts having all glyphs etc.

Yes, I assumed as much in comment #10.

> This one should be WF

Do you mean you're suggesting this issue be marked WFM?

> and overall, we definitely need better *concept* for
> handling of this complex issue - but the current state is based on (1) state
> of the art - fonts have imperfect coverage;

I wouldn't characterize it as "state of the art", because it's not something
that is expected to change, or progress, in a different direction. It's
perfectly ok for fonts to have partial coverage. (More on that below)


>  IMO, this could
> only improve *much later*, when (1) is improved greatly

You are proposing a paradigm change for distribution and design of fonts in
general, that is way beyond the scope of LO. Its merits can be debated - I
personally don't agree with your paradigm change - but it cannot be a factor in
short-to-medium-term engineering decisions. If there was 100% consensus that
this is where the world of fonts were going, then maybe you could argue against
addressing issues such as this one. But - with due respect - it's just your
opinion, or the opinion of some people (I've not heard this from others). So I
don't believe it should have bearing on this issue.

For now, LO should be able to let us force the use of any of fonts in the three
language-groups which contain our glyphs of interest (e.g. the digits of a
number). I agree that the language group is an artificial construct, but it is
what LO associates a font right now, so either we allow setting a language
group, or allow setting a language and have that auto-mapped to one of the
groups (and thus also group fonts).


---

Sidenote:

My idea for a long term alternative to the "language group" is one of two, both
involving multiple fonts:

1. A font preference list: To decide which font is used for a glyph, one
searches a list of decreasing preference, and the first font with that glyph
available is chosen.
2. A glyph set map: The Unicode plane / set of all characters is subdivided
into sets (e.g. represented as a list of ranges), each mapped to a font. Simple
division templates would be "all from font F1", "strongly-language-L glyhps
from F1, the rest from F2" and a few others.

In both of these, advanced users would be offered a dialog (pane) for
arbitrarily modifying the list/map.

This does not cover the issue of skewing the preferences for characters which
may be part of different Unicode text runs, and thus perceived as part of
sequences in different languages - like numbers, or punctuation marks. But the
specifics would take more thinking and are even farther beyond the scope of
this bug.

---

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

[Libreoffice-bugs] [Bug 148612] Bug in a macro that cannot read cells

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148612

--- Comment #1 from Frederic Parrenin 
 ---
Note that in the test_bug macro, if I write:

sheets("Feuil1").cells(2,1) = "test"

it works. So LO is able to write something, but not to read.

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

[Libreoffice-bugs] [Bug 148612] New: Bug in a macro that cannot read cells

2022-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148612

Bug ID: 148612
   Summary: Bug in a macro that cannot read cells
   Product: LibreOffice
   Version: 7.3.1.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: frederic.parre...@univ-grenoble-alpes.fr

Created attachment 179584
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179584=edit
.ods file to reproduce the problem

Steps to reproduce:
- open the attached .ods file
- edit macros
- go to macro "test_bug" and execute
=> the macro does nothing
- now remove all other macros in the module
- execute again "test_bug"
=> the macro now produces something

Do I miss something obvious or is this a bug?

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

  1   2   >