[Libreoffice-bugs] [Bug 148632] Point Bookmarks are not removed when the Table of Contents are removed. Can't get rid of them

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

Eldar  changed:

   What|Removed |Added

Summary|Point Bookmarks are not |Point Bookmarks are not
   |removed when the Table of   |removed when the Table of
   |Contents are removed|Contents are removed. Can't
   ||get rid of them

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

[Libreoffice-bugs] [Bug 148633] New: LO Help F1 shows contents of a script file, not a doc for help

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

Bug ID: 148633
   Summary: LO Help F1 shows contents of a script file, not a doc
for help
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: robgr...@gmx.com

Version: 7.3.2.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 6; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Ubuntu package version: 1:7.3.2-0ubuntu2
Calc: threaded
Gnome 42
Ubuntu 22.04
windowing X11
cpu amd fx 6core
LO installed from Ubuntu repositories

When clicking "help" or pressing F1, a new window opens and displays...

 window.location.href =
"file:///usr/share/libreoffice/help/index.html?Target=swriter/.uno%3AHelpIndex&Language=en-GB&System=UNIX&Version=7.3";Help
Page Redirection

No help function.

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

[Libreoffice-bugs] [Bug 148632] New: Point Bookmarks are not removed when the Table of Contents are removed

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

Bug ID: 148632
   Summary: Point Bookmarks are not removed when the Table of
Contents are removed
   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: eagala...@gmail.com

Description:
When I insert Table of Contents then LO creates so called "Point Bookmarks" for
all Headings. They looks as vertical gray bar symbol before Heading text. When
I remove Table of Contents these bookmarks remains in the document and cannot
be deleted.

Steps to Reproduce:
1. Type some text like "Title 1" and pick Heading 1 style for it;
2. Insert Table of Contents at new line. Point bookmark should be added before
"Title 1" text;
3. Remove Table of Contents. Point Bookmark will remains.

Actual Results:
After removing ToC, Point Bookmark remains.

Expected Results:
Point Bookmarks should be removed when ToC are removed.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.3.2.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-GB (en_US.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.2-0ubuntu2
Calc: CL

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

[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window

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

Bug 148237 Summary: Wrong field names for cross references to footnotes and 
endnotes (see comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=148237

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

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

[Libreoffice-bugs] [Bug 148237] Wrong field names for cross references to footnotes and endnotes (see comment 3)

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

Jim Raykowski  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #11 from Jim Raykowski  ---
(In reply to sdc.blanco from comment #9)
> I can also see that you make the Statistics Field in Navigator have the
> information requested in bug 45048.
That wasn't done as part of this patch. I didn't know about bug 45048 until you
mentioned it.

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

[Libreoffice-bugs] [Bug 148329] Accept Hebrew Maqaf for '-' in search pattern

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

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 148320] Explicit toggle for ToC/Index title

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

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 148319] EDITING deleting cells with dependency must issue warning

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

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 148317] KDE wayland session: presentation does not display on external screen

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

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 148189] Autocorrect hyphen/minus sign into Hebrew Maqaf when appropriate

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

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 148575] Crash when I tried to change the contents in a formula field of a write table

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

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 148575] Crash when I tried to change the contents in a formula field of a write table

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

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

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

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

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

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 148493] replacement does not work well

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

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

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

[Libreoffice-bugs] [Bug 145202] Non si apre piu i documenti

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

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

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 148237] Wrong field names for cross references to footnotes and endnotes (see comment 3)

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

--- Comment #10 from Commit Notification 
 ---
Jim Raykowski committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/8f27cde891cc925d5ff76a736fb54dd70e53b4ee

tdf#148237 Show 'Footnote' and 'Endnote' as field name for field cross

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 148237] Wrong field names for cross references to footnotes and endnotes (see comment 3)

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

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 131085] SVG cross-hatch pattern appears with spurious mosaic of squares

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

--- Comment #10 from Daniel Neville  ---
The spurious hatch rendering bug (revealed by dragging lo-sad.svg into a
LibreWriter document) persists in Version 7.2.6.2 (the latest normally
available for my fresh install of Ubuntu 21.10)

Adding ppa:libreoffice/ppa and and installing the updates, I now have:

Version: 7.3.2.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: en-NZ (en_AU.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.2~rc2-0ubuntu0.21.10.1~lo1
Calc: threaded

The bug still appears exactly as pictured in the "LibreOffice Writer screenshot
(annotated)" attachment above.

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

[Libreoffice-bugs] [Bug 99084] [META] Impress outline view bugs and enhancements

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

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

   What|Removed |Added

 Depends on||148629


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148629
[Bug 148629] The "Demote" command is always active in Draw (and Impress), but
does not do anything on non-list paragraphs
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148629] The "Demote" command is always active in Draw (and Impress), but does not do anything on non-list paragraphs

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

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

   What|Removed |Added

 Blocks||99084


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 148629] The "Demote" command is always active in Draw (and Impress), but does not do anything on non-list paragraphs

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

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

   What|Removed |Added

Summary|The "Demote" command is |The "Demote" command is
   |always active in Draw, but  |always active in Draw (and
   |does not do anything on |Impress), but does not do
   |non-list paragraphs |anything on non-list
   ||paragraphs

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

[Libreoffice-bugs] [Bug 148630] IVS characters get more space if character spacing is set.

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

--- Comment #1 from Mark Hung  ---
Created attachment 179621
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179621=edit
Sample document

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

[Libreoffice-bugs] [Bug 148631] New: Shading in some Ribbon shapes from ppt is missing

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

Bug ID: 148631
   Summary: Shading in some Ribbon shapes from ppt is missing
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de

Created attachment 179620
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179620=edit
Document with ribbon-shapes

Open attached document. It contains some shapes and screenshots how these
shapes look in PowerPoint 97.
Notice, that some parts should be dark, but they are not.

The error is in the segment list in
https://opengrok.libreoffice.org/xref/core/svx/source/customshapes/EnhancedCustomShapeGeometry.cxx

The affected shapes are mso_sptRibbon, mso_sptElllipseRibbon2 and
mso_EllipseRibbon.

The parts which are not dark although they should be dark have erroneously the
command "no fill". That is 0xaa00 in the encoding in the segment list.

To investigate whether the "no fill" command is used in the shape, you can
examine the property "CustomShapeGeometry", therein "Path", therein "Segments".
This has the commands encoded as in
https://api.libreoffice.org/docs/idl/ref/EnhancedCustomShapeSegmentCommand_8idl.html

I think, this can become an easyhack.

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

[Libreoffice-bugs] [Bug 148594] IVS characters get more space if character spacing is set.

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

Mark Hung  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 148630] IVS characters get more space if character spacing is set.

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

Mark Hung  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 148630] New: IVS characters get more space if character spacing is set.

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

Bug ID: 148630
   Summary: IVS characters get more space if character spacing is
set.
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mark...@gmail.com

Description:
When setting character spacing to 10pt, some unicode IVS ( U+4E00U+e01e1 ) get
more space than it should have.

Original issue is reported:
https://github.com/ButTaiwan/bpmfvs/issues/1

The font can be downloaded here:
https://github.com/ButTaiwan/bpmfvs/releases/download/v1.320/Bpmf_Regulars.zip


Steps to Reproduce:
1. Open the document.
2. Check the text inside. The text contains two unicode IVS (U+4e00U+e01e1 in
the first line, U+4e00U+e01e2 in the second line. ).


Actual Results:
Some of the character spacing is larger.

Expected Results:
All character spacing should be equal (i.e. 15pt).


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.3.1.3 (x64) / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 16; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: zh-TW (zh_TW); UI: zh-TW
Calc: CL

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

[Libreoffice-bugs] [Bug 148629] New: The "Demote" command is always active in Draw, but does not do anything on non-list paragraphs

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

Bug ID: 148629
   Summary: The "Demote" command is always active in Draw, but
does not do anything on non-list paragraphs
   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 179619
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179619=edit
simple document to use for testing Demote command

1. Use attached file, which has two textboxes, one with an ordered list and one
with a few lines of text, or make your own version.

2. Place cursor in a non-list paragraph.

3. Format > Lists > Demote

Actual: Command is active, nothing happens.

Expected: ??  maybe it shouldn't be active?


This ticket is filed under Draw, but same problem with Impress (and same
command, .uno:OutlineRight), which is why only one ticket is filed for now.

STR in Impress.

1. Make a textbox with some text lines.
2. View > Toolbars > Outline
3. Click on Demote (right arrow)

Actual: Command is active, but nothing happens.

Also in 7.2.6.2

Additional information:
1. The Demote command in Writer is not active, in non-list paragraphs.

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

[Libreoffice-bugs] [Bug 56959] libvisio: Draw does not import properly MS Visio connectors

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

chuck.pob...@gmail.com changed:

   What|Removed |Added

 CC||chuck.pob...@gmail.com

--- Comment #22 from chuck.pob...@gmail.com ---
Still present with Libreoffice 7.3.2

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

[Libreoffice-bugs] [Bug 146598] Freezing when using cut, copy, or paste on macOS

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

steve  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 148051] Mac: Crashings for unkown reasons, despite reset user profile etc.

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

steve  changed:

   What|Removed |Added

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

--- Comment #35 from steve  ---
Could this be a dupe of
https://bugs.documentfoundation.org/show_bug.cgi?id=146598 ?

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

[Libreoffice-bugs] [Bug 113510] [META] Bugs that cause CPU to run at 100%

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

Bug 76985 Summary: Freeze: Moving graphic frame always freezes Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=76985

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 107656] [META] Frame bugs and enhancements

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

Bug 76985 Summary: Freeze: Moving graphic frame always freezes Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=76985

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements

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

Bug 76985 Summary: Freeze: Moving graphic frame always freezes Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=76985

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 76985] Freeze: Moving graphic frame always freezes Writer

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

Gerry  changed:

   What|Removed |Added

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

--- Comment #27 from Gerry  ---
I cannot reproduce this bug anymore with Version: 7.3.2.2 / LibreOffice
Community
Build ID: 30(Build:2)
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Ubuntu package version: 1:7.3.2~rc2-0ubuntu0.21.10.1~lo1
Calc: threaded

I close it as WORKSFORME

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

[Libreoffice-bugs] [Bug 148622] Calc crashes while opening stored ods-files after Windows 10 update

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

--- Comment #2 from m...@brmweb.de ---
After new Win10 installation problem resolved

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

[Libreoffice-bugs] [Bug 148624] Crash in: GrVkPipelineState::setAndBindInputAttachment(GrVkGpu *,gr_sp

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

Julien Nabet  changed:

   What|Removed |Added

   Hardware|All |x86-64 (AMD64)
 OS|All |Windows (All)

--- Comment #1 from Julien Nabet  ---
Logs show "Skia", perhaps
https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28_Skia_.29
may help.

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

[Libreoffice-bugs] [Bug 148628] New: Problem in layout of Bullet and Numbering dialog after choosing Type

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

Bug ID: 148628
   Summary: Problem in layout of Bullet and Numbering dialog after
choosing Type
   Product: LibreOffice
   Version: 7.4.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sdc.bla...@youmail.dk

Created attachment 179618
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179618=edit
Screenshot after step 3 in STR

1. Open new Presentation document.
2. Right-click in Slide, choose Bullets and Numbering
3. Change type from Bullet to 1,2,3
4. See attachment for actual result, where OK button is covered. Even though it
is highlighted, the button is not active. It is necessary to lengthen the
window to get the Reset, Ok, Cancel buttons.

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 148557] Crash mergedlo!SdrTextObj::GetOutlinerParaObject+0x10mergedlo!SdrTextObj::GetOutlinerParaObject+0x10:

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

Julien Nabet  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   Keywords|wantBacktrace   |haveBacktrace

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

[Libreoffice-bugs] [Bug 148557] Crash mergedlo!SdrTextObj::GetOutlinerParaObject+0x10mergedlo!SdrTextObj::GetOutlinerParaObject+0x10:

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

--- Comment #6 from Julien Nabet  ---
Created attachment 179617
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179617=edit
bt with debug symbols

On pc Debian x86-64 with master sources updated today, I could reproduce this.

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

[Libreoffice-bugs] [Bug 121368] Brochure printing error

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

printerhelp  changed:

   What|Removed |Added

Crash report or||hp printer offline
crash signature||

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

[Libreoffice-bugs] [Bug 121368] Brochure printing error

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

printerhelp  changed:

   What|Removed |Added

URL|https://www.printer.support |https://www.supportprinterh
   |/   |elp.com/hp-printer-offline-
   ||help-support/

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #11 from Regina Henschel  ---
The unit of the Position dialog is not determined by the document but by
your "Locale setting". Go to Tools > Options > Language Settings > Languages.
Look at section "Formats" > Locale setting. In your case it should be
"Hungarian". I use "German". If it is "Default - English(USA)" the dialog will
use inches.

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

[Libreoffice-bugs] [Bug 148622] Calc crashes while opening stored ods-files after Windows 10 update

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

Timur  changed:

   What|Removed |Added

Summary|Calc crashes while opening  |Calc crashes while opening
   |stored ods-files after  |stored ods-files after
   |Windows update  |Windows 10 update
   Severity|normal  |major

--- Comment #1 from Timur  ---
Please confirm you did User Profile Reset, as you wrote. 
Does it start in Safe mode?

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

[Libreoffice-bugs] [Bug 148627] New: operation delayed until newline entered

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

Bug ID: 148627
   Summary: operation delayed until newline entered
   Product: LibreOffice
   Version: 7.3.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tor...@yahoo.com

Created attachment 179616
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179616=edit
text with 1 line

In Weird.odt, cursor at ‘0’, hit key ‘m’: no ‘m’ is inserted, but ‘st’ appears
after ‘est’! Now, put cursor at beginning-of-line and hit Enter: new line is
correct, with ‘m’ before ‘0’. Hit ^z (undo), line returns to its place,
correct.
Reload Weird.odt, select ‘Comme le minimum de uQ se produit à ’ and hit
Del (delete), the selected string is not deleted; instead… well, try it! Now,
put cursor at beginning-of-line and hit Enter: new line is correct, with the
selected string deleted.
Why? All I can say is that I did not program deliberately this crazy
behaviour —just to fool you?

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

[Libreoffice-bugs] [Bug 148626] New: Printing Envelopes

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

Bug ID: 148626
   Summary: Printing Envelopes
   Product: LibreOffice
   Version: 7.3.1.3 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: glo...@comcast.net

Description:
When printing #10 envelopes the program creates a much larger size envelope. 
I have reset the user profile but it did not help. Any suggestions? 

Actual Results:
After selecting #10 envelope and clicking on new document, a much larger
envelope is created by the program. 

Expected Results:
A 4/1/8 by 9/1/2 envelope, standard size #10 envelope should have been created. 


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Generate a 4/1/8 by 9/1/2 envelope, standard size #10 envelope.

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

[Libreoffice-bugs] [Bug 113136] [META] Find & Replace Dialog

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||148625


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148625
[Bug 148625] Can't 'Replace All' when also searching comments
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148625] New: Can't 'Replace All' when also searching comments

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

Bug ID: 148625
   Summary: Can't 'Replace All' when also searching comments
   Product: LibreOffice
   Version: 7.4.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com
Blocks: 113136

In the F dialog, if one checks the 'comment' checkbox, the 'Replace All'
button becomes inactive and cannot be pressed. But - there's no reason one
should not be able to "Replace All" in comments as well.


Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: fb9270b238cba4f36e595c5d7f4d85f6f3f18e1c
CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: en-IL (en_IL); UI: en-US


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=113136
[Bug 113136] [META] Find & Replace Dialog
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148574] LibreOffice Writer instant crash upon opening or creating a (new) document

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

--- Comment #10 from Julien Nabet  ---
Here extra info about Skia pbs:
https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28_Skia_.29

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

[Libreoffice-bugs] [Bug 139734] Drop redundant asserts after MacrosTest::loadFromDesktop

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

--- Comment #32 from Mike Kaganski  ---
(In reply to Hannah Meeks from comment #31)

Only one :-)

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #10 from Scott  ---
Created attachment 179615
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179615=edit
Metric coordinates displayed in inches

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #9 from Scott  ---
I see now that you are totally correct. I can see that I misunderstood and thus
misstated the bug. The coordinates are in fact stored and restored with the
document as they should be. The problem is the display parameters when the
document is reloaded.

Let's say I create a document with certain grid/unit parameters, save and later
reload it. In the newest attachment would you say that the fact that the
"Position and Size" are displayed in inches is a bug? Given that the "Tool |
Options" are only associated with document creation and I want to work with
these parameters in centimeters how should I manage that?

I think that's a bug but not the bug I initially described. This is new to me
so I'm not sure how to proceed. Do you agree there's a bug and if so should
this thread be closed and refiled differently?

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

[Libreoffice-bugs] [Bug 148574] LibreOffice Writer instant crash upon opening or creating a (new) document

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

Telesto  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #9 from Telesto  ---
@Mbstein
You could try to update your videocard driver..

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

[Libreoffice-bugs] [Bug 148272] Cross-reference to numbering wrongly includes separator character

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

--- Comment #6 from Charles Valente  ---
At least in 7.2.6.2, "Number" and "Chapter" do not solve the problem: the
separator character is still inserted with the number of the item.
There is, from what I tested, *no way* to just insert the number, as it was
before 7.2.
Maybe I am doing something wrong given the new way the cross-reference and the
numbering is happening in the new versions of LO Writer.

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

[Libreoffice-bugs] [Bug 148597] FORMATTING request enhancement: create formatted Table of Figures using tabs before and after index

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

Telesto  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||tele...@surfxs.nl

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

[Libreoffice-bugs] [Bug 148603] cannot set Wrap/Top value of Graphics

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

--- Comment #1 from Telesto  ---
*** Bug 148602 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 148602] cannot set Wrap/Top value of Graphics

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

Telesto  changed:

   What|Removed |Added

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

--- Comment #1 from Telesto  ---


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

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

[Libreoffice-bugs] [Bug 148624] New: Crash in: GrVkPipelineState::setAndBindInputAttachment(GrVkGpu *,gr_sp

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

Bug ID: 148624
   Summary: Crash in:
GrVkPipelineState::setAndBindInputAttachment(GrVkGpu
*,gr_sp,GrVkCommandBuffer *)
   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: tex2002ans+libreoff...@gmail.com

This bug was filed from the crash reporting server and is
br-853ade4b-9770-4cbe-9a65-b3af61356690.
=

All I did was:

- Open a new document in Calc
- Clicked in a cell
- Insert > Chart
- Crash

I tried again, but couldn't reproduce crash. Completely random.

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #8 from Regina Henschel  ---
Created attachment 179614
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179614=edit
Screenshot from attachment 179589

The attachment 179589 has grid 1000 (=1cm) for wide gride and 200 (=0.2cm) for
fine grid. That it exactly what is shown in the opened document. The ruler has
30, 40, 50... because scaling is 1:10. From one line to the next is 1cm as it
should be and there are 5 spaces between two grid lines, exactly as it should
be. So for me here the document is rendered correctly.

Again, the values in Tools > Options > Draw > Grid are not designed to reflect
the settings of the active document.

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

[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace

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

Bug 112894 Summary: find search entry has a broken accessibility hierarchy
https://bugs.documentfoundation.org/show_bug.cgi?id=112894

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 36549] [META] ACCESSIBILITY: Tracking bug for issues affecting a11y ATK and GNOME Orca screen reader support

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

Bug 112894 Summary: find search entry has a broken accessibility hierarchy
https://bugs.documentfoundation.org/show_bug.cgi?id=112894

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 112894] find search entry has a broken accessibility hierarchy

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

Michael Weghorn  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||m.wegh...@posteo.de
 Resolution|--- |WORKSFORME

--- Comment #5 from Michael Weghorn  ---
I can reproduce with an old version from the bibisect repo:

Version: 6.0.6.0.0+
Build ID: c6c82096301180cfa7942dd9fb9d1cb66c7ecc04
CPU threads: 4; OS: Linux 5.16; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); Calc: group

but everything looks fine with current git master, Orca speaks the
corresponding character and the attached script prints 0 as index in parent, no
more -1:

> object:text-caret-moved(1, 0, 0)
> source: [text | ]
> host_application: [application | soffice]
> sender: [application | soffice]
> 0
> object:text-caret-moved(2, 0, 0)
> source: [text | ]
> host_application: [application | soffice]
> sender: [application | soffice]
> 0
> object:text-caret-moved(3, 0, 0)
> source: [text | ]
> host_application: [application | soffice]
> sender: [application | soffice]
> 0
> object:text-caret-moved(4, 0, 0)
> source: [text | ]
> host_application: [application | soffice]
> sender: [application | soffice]
> 0
> object:text-caret-moved(3, 0, 0)
> source: [text | ]
> host_application: [application | soffice]
> sender: [application | soffice]
> 0
> object:text-caret-moved(2, 0, 0)
> source: [text | ]
> host_application: [application | soffice]
> sender: [application | soffice]
> 0
> object:text-caret-moved(1, 0, 0)
> source: [text | ]
> host_application: [application | soffice]
> sender: [application | soffice]
> 0
> object:text-caret-moved(0, 0, 0)
> source: [text | ]
> host_application: [application | soffice]
> sender: [application | soffice]
> 0

-> Closing as WORKSFORME

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: de45c09a3b48e8ab3ac995ea72681ec265c24123
CPU threads: 4; OS: Linux 5.16; UI render: default; VCL: gtk3
Locale: en-US (en_GB.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 139734] Drop redundant asserts after MacrosTest::loadFromDesktop

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

--- Comment #31 from Hannah Meeks  ---
Are there any more of these left?

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

[Libreoffice-bugs] [Bug 36549] [META] ACCESSIBILITY: Tracking bug for issues affecting a11y ATK and GNOME Orca screen reader support

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

Bug 55695 Summary: Writer not generating window.activate when focus is returned.
https://bugs.documentfoundation.org/show_bug.cgi?id=55695

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WORKSFORME

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

[Libreoffice-bugs] [Bug 55695] Writer not generating window.activate when focus is returned.

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

Michael Weghorn  changed:

   What|Removed |Added

 CC||m.wegh...@posteo.de
 Status|REOPENED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #10 from Michael Weghorn  ---
(In reply to Alex ARNAUD from comment #9)
> On Debian Sid with LibreOffice 5.4 I can only reproduce this issue with VCL
> GTK2, not with GTK3.
> 
> Best regards.

-> Closing as WORKSFORME

The gtk2 VCL plugin is no more, and when using the gtk3 VCL plugin, the
attached python script prints this when switching either from Writer to Konsole
or the other way round, which looks correct:

> [application | soffice]
> [application | konsole]

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

[Libreoffice-bugs] [Bug 108538] [META] Chart feature enhancements

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

Bug 141625 Summary: Calc Chart x-Axis Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=141625

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

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

[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs

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

Bug 141625 Summary: Calc Chart x-Axis Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=141625

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

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

[Libreoffice-bugs] [Bug 148623] [DOCX] Comments in headers and footers are not saved in DOCX files (in ODT all is OK)

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

--- Comment #3 from Rafael Lima  ---
(In reply to Mike Kaganski from comment #2)
> Word does not allow to have comments in headers/footers. This is simply a
> format limitation. This is not a bug.

Hi Mike. Thanks for the prompt feedback.

Indeed you're right. I tested in MS Office 365 and the option to create
comments in the header/footer is simply not available.

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

[Libreoffice-bugs] [Bug 148621] The horrible state of the BASIC API and documentation

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

--- Comment #4 from Buovjaga  ---
First stab: https://gerrit.libreoffice.org/c/help/+/133096

Very much simplified. The old version had the table headers
Macro Calling parameters and comments

I just skipped them for now.

Maybe Olivier has ideas on how to present the function names to make them stand
out a bit. As headings?

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #7 from Scott  ---
Just thinking about my results it appears one of two things is happening:

1. My settings are not stored in my document (something you can check I
presume).
2. My verion of Draw isn't loading them when I open the file.

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #6 from Scott  ---
Created attachment 179612
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179612=edit
Shows Unit of measurement is not inches

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #5 from Scott  ---
Created attachment 179611
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179611=edit
Showing proper "Load" setting

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #4 from Scott  ---
Created attachment 179610
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179610=edit
Opened document showing wrong settings

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

--- Comment #3 from Scott  ---
This morning I followed the procedure I outlined above and got the results
shown in the attached images. The images show the document and coordinates when
I last saved the document as well as my current settings. As you can see there
are several issues. The Grid H/V=2.54cm not 1.00cm. Also the selected rectangle
Position and Size are shown in inches even though the "General UOM" is
Centimeter (that might be a related but separate bug). The setting you ask
about ( "Load user-specific settings with the document") is set properly.

I performed the following steps with the indicated result:

1. I opened and closed the document several times in a row without changing
anything (and thus without saving anything). Each time the results were
incorrect the same as the images show.

2. After closing Draw I reopened it with no document.
3. I changed the options settings to reflect the desired document settings for
this document.
4. Then I reopened the document from "Recent Documents" and all settings were
correct. The document was fine.

Then I performed the procedure again outlined in my original submission and the
settings were incorrect as indicated.

This is very repeatable for me.

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

[Libreoffice-bugs] [Bug 112916] [META] DOCX (OOXML) comment issues

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

Bug 148623 Summary: [DOCX] Comments in headers and footers are not saved in 
DOCX files (in ODT all is OK)
https://bugs.documentfoundation.org/show_bug.cgi?id=148623

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements

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

Bug 148623 Summary: [DOCX] Comments in headers and footers are not saved in 
DOCX files (in ODT all is OK)
https://bugs.documentfoundation.org/show_bug.cgi?id=148623

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 148623] [DOCX] Comments in headers and footers are not saved in DOCX files (in ODT all is OK)

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

Mike Kaganski  changed:

   What|Removed |Added

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

--- Comment #2 from Mike Kaganski  ---
Word does not allow to have comments in headers/footers. This is simply a
format limitation. This is not a bug.

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

[Libreoffice-bugs] [Bug 148623] [DOCX] Comments in headers and footers are not saved in DOCX files (in ODT all is OK)

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

Rafael Lima  changed:

   What|Removed |Added

 Blocks||106179


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements

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

Rafael Lima  changed:

   What|Removed |Added

 Depends on||148623


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148623
[Bug 148623] [DOCX] Comments in headers and footers are not saved in DOCX files
(in ODT all is OK)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148623] [DOCX] Comments in headers and footers are not saved in DOCX files (in ODT all is OK)

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

Rafael Lima  changed:

   What|Removed |Added

 Blocks||112916


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 112916] [META] DOCX (OOXML) comment issues

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

Rafael Lima  changed:

   What|Removed |Added

 Depends on||148623


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148623
[Bug 148623] [DOCX] Comments in headers and footers are not saved in DOCX files
(in ODT all is OK)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148623] [DOCX] Comments in headers and footers are not saved in DOCX files (in ODT all is OK)

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

--- Comment #1 from Rafael Lima  ---
Created attachment 179609
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179609=edit
DOCX file used in the screenshots

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

[Libreoffice-bugs] [Bug 148623] New: [DOCX] Comments in headers and footers are not saved in DOCX files (in ODT all is OK)

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

Bug ID: 148623
   Summary: [DOCX] Comments in headers and footers are not saved
in DOCX files (in ODT all is OK)
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rafael.palma.l...@gmail.com

Created attachment 179608
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179608=edit
Screenshots showing the problem

When I edit DOCX files and create comments in the Header / Footer areas, the
comments are not saved. So when I save the DOCX file and reopen it, the comment
is lost.

See the attached ODG file with screenshots detailing the problem.

If the DOCX file is saved as ODT, then comments are saved as expected.
Therefore, it seems to be a problem in the DOCX export filter.

System info:
Version: 7.3.2.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR
Ubuntu package version: 1:7.3.2~rc2-0ubuntu0.21.10.1~lo1
Calc: threaded

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

[Libreoffice-bugs] [Bug 148621] The horrible state of the BASIC API and documentation

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

--- Comment #3 from Olivier Hallot  ---
1) Recent discussions in the ESC (Engineering Steering Commt'ee) lead to a
phase-out of JavaBeans and JavaScript in the future.
https://lists.freedesktop.org/archives/libreoffice/2022-January/088371.html

Nevertheless, our documentation guides have some starting point for Javascript:
https://books.libreoffice.org/en/GS73/GS7313-GettingStartedWithMacros.html#toc39

2) The poor layout is likely consequence of the update of prism.js and
prism.css in master branch. Some tweak to set because the previous releases are
not affected.
https://gerrit.libreoffice.org/c/help/+/132570

3) It has been a long time like that and fixing it depends on volunteer
effort or business investment on the issue. To give an example, we submitted
(but were not picked for funding) a project on illustrating the API:
https://wiki.documentfoundation.org/Documentation/GSoDOC/2022
And this project is an easy hack, actually.

4) These "Advanced" libraries are in the code since the birth of OpenOffice.org
(StarOffice?) and were never documented. Excluding the current formatting
issue, the Help page was an effort to give a minimum visibility of the macros.
It worked since you got there (and your comments are appreciated) :-).

5) Exactly because reading the code is a time consuming task and the script
signature has already a minimal useful information. The build of the Help page
was done with a script and no human intervention.  Feel free to propose a
better, perhaps more professional description. 
Note 
a) the library is static from ages and is likely to stay like that unless you
want to add contents and 
b) the script signatures are not translated.
c) Have a look at the Scriptforge libraries under development at the moment.
Documentation is coming along with the forge development.

6) Correct. These are 2 different entities. The Help targets the end user and
the API targets developers and advanced script coders. Besides, the Help is
translated into +70 languages while the API is not. Pushing for more contents
to translation is something we consider with special care.

The API website (which is an online version of the LibreOffice SDK) is
generated by Doxygen. Of course, volunteers are welcome to improve the page
layout and usability, as well as contents. Doxygen experts are welcome.

Finally, the documentation is left historically to the community. We advise
volunteers but we won't prevent them from using their pet tool for their own
use. That said, some communities prefer wiki, others books, some Ask, other
mailing list or Telegram groups, and so on...

PS. we are aware of readthedocs and other tools in github.

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148615

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de

--- Comment #2 from Regina Henschel  ---
Not sure whether I understand you correctly. If I open a document it always
uses the grid stored in the document. The grid settings in Tools > Options are
used, when generating a new document. They do not reflect the grid settings of
the current active document. Only if you change the settings, then the changed
values are used for the active document.
Grid settings are stored in hundredths of a millimeter in the file.

If the document does not show the grid as it was when last saved, then perhaps
the settings are not load? Please have a look whether the option "Load
user-specific settings with the document" is checked in section 'Load' in Tools
> Options > Load/Save > General.

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

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

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

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de

--- Comment #22 from Regina Henschel  ---
In RTL there is currently bug 148291 and in CTL bug 148289.

Eyal, do you know an application with a similar feature which works for RTL?
Then please add the observed behavior there to bug 148291.

-- 
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, or lanugage-group, of a piece of text

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

--- Comment #18 from Eyal Rozenberg  ---
(In reply to Mike Kaganski from comment #17)
> What I would agree would be "assigning a language does not pick the right
> font" bug.

But we can't assign a language, so that bug can't exist yet...

I've rephrased the title to indicate that being able to assign a language is
just as desirable (perhaps more so).

-- 
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, or lanugage-group, of a piece of text

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

Eyal Rozenberg  changed:

   What|Removed |Added

Summary|Missing/unexposed ability   |Missing/unexposed ability
   |to explicitly set the   |to explicitly set the
   |"language group" of a piece |language, or
   |of text |lanugage-group, of a piece
   ||of text

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

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

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

--- Comment #4 from sdc.bla...@youmail.dk ---
FTR -- do not need to use ordered lists.

1. In Draw textbox, put 4 lines of text.
2. Select two lines (e.g., first two).
3. Format > Lists > Move Down

Crash.

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

[Libreoffice-bugs] [Bug 148197] LibreOffice crashes when I try to dock floating Navigator window (GTK3)

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

Caolán McNamara  changed:

   What|Removed |Added

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

--- Comment #17 from Caolán McNamara  ---
perfect, that gives me what I need to know.

#0  0x7f37e8625e2a in gtk_tree_model_get_iter () from
/lib/x86_64-linux-gnu/libgtk-3.so.0
#1  0x7f37e8626091 in gtk_tree_model_get_iter_first () from
/lib/x86_64-linux-gnu/libgtk-3.so.0
#2  0x7f37e8bf3eb3 in virtual thunk to (anonymous
namespace)::GtkInstanceTreeView::get_iter_first(weld::TreeIter&) const () at
./vcl/unx/gtk3/gtkinst.cxx:12846
#3  0x7f37c56c7eee in SwContentTree::CommandHdl (this=0x55b6c3e5a5e0,
rCEvt=...) at /usr/include/c++/11/bits/unique_ptr.h:173
#4  0x7f37e8c14cc7 in (anonymous
namespace)::GtkInstanceWidget::signalPopupMenu (pWidget=0x7ffe668b3590,
widget=0x55b6c3e67a50) at ./vcl/unx/gtk3/gtkinst.cxx:2639
...
#19 0x7f37e8682a5b in gtk_window_propagate_key_event () from
/lib/x86_64-linux-gnu/libgtk-3.so.0

so this suggests that the context menu is triggered by the keystroke and the
problem is with the context menu when nothing is selected in the treeview, but
focus is in there.

And I can reproduce by launching the navigator, click a row in the treeview,
click the row again to unselect it (but focus is still in there) and press (on
my keyboard) the dedicated "menu" button.

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

[Libreoffice-bugs] [Bug 148621] The horrible state of the BASIC API and documentation

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

Buovjaga  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #2 from Buovjaga  ---
(In reply to Dan Dascalescu from comment #0)
> 2. The documentation web page template at
> https://help.libreoffice.org/7.4/en-US/text/sbasic/shared/03/lib_tools.html
> has a pointlessly narrow column width, which truncates the visible text and
> makes it impossible to clearly see an entry at once (see screenshot). That
> text column also scrolls through the search bar at the top.

The template is fine. It seems here the content creators have been a bit
absentminded. A table was used to create additional layout, which wrecks
mobile-friendliness. Also, the code blocks have pointless indentation that make
the layout fail even on desktop.

I can simplify the page and any others like it.

Olivier can comment on the other stuff.

I am pleased to say we have finally imported the old UNO API developer's guide
into TDF wiki: https://wiki.documentfoundation.org/Documentation/DevGuide
It is being updated.

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

[Libreoffice-bugs] [Bug 148622] Calc crashes while opening stored ods-files after Windows update

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

m...@brmweb.de changed:

   What|Removed |Added

Crash report or||https://crashreport.libreof
crash signature||fice.org/stats/crash_detail
   ||s/936dacdf-34fd-4e2d-9bc5-c
   ||761b1db91ca

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

[Libreoffice-bugs] [Bug 148622] New: Calc crashes while opening stored ods-files after Windows update

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

Bug ID: 148622
   Summary: Calc crashes while opening stored ods-files after
Windows update
   Product: LibreOffice
   Version: 7.3.1.3 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: m...@brmweb.de

Description:
After the update installion of "Servicing Stack 10.0.19041.1613", KB5012117 and
KB5012599 and the correspondent reboot the opening of stored ods-files results
in a Calc-crash. Creating new ods-files is posibble, even storing and
reopening. Writer is working normally.
Deinstalling KB5012117 and KB5012599 had no effect, the servicing stack can't
be deinstalled.

Steps to Reproduce:
1. Open Calc
2. Open a recently stored ods-file (before the mentioned Win10-update)


Actual Results:
Calc chrashes and shuts down

Expected Results:
Open the stored ods-file


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
https://crashreport.libreoffice.org/stats/crash_details/936dacdf-34fd-4e2d-9bc5-c761b1db91ca

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

[Libreoffice-bugs] [Bug 148621] The horrible state of the BASIC API and documentation

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

Buovjaga  changed:

   What|Removed |Added

  Component|BASIC   |Documentation
 CC||ilmari.lauhakangas@libreoff
   ||ice.org,
   ||olivier.hallot@libreoffice.
   ||org

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

[Libreoffice-bugs] [Bug 131192] Comprehensive support for "start" / "end" text alignment

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Whiteboard||needDevComment

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

[Libreoffice-bugs] [Bug 131192] Comprehensive support for "start" / "end" text alignment

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

Eyal Rozenberg  changed:

   What|Removed |Added

Version|3.3.0 release   |Inherited From OOo

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148257

--- Comment #17 from Mike Kaganski  ---
(In reply to Eyal Rozenberg from comment #15)
> 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).

Assigning a *language* (not "language group"!) with any run of the text must be
enough to associate that text with the "language group", and thus to force
picking of glyphs from the respective font associated with that group.

What I would agree would be "assigning a language does not pick the right font"
bug.

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

[Libreoffice-bugs] [Bug 148621] The horrible state of the BASIC API and documentation

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

--- Comment #1 from Dan Dascalescu  ---
Re. 6 - some more documentation is split at documentation.libreoffice.org,

such as this useful cheat sheet -
https://documentation.libreoffice.org/assets/Uploads/Documentation/en/MACROS/RefCards/LibOBasic-3-Calc-Flat-A4-EN-v111.pdf

Centralizing and cross-linking these disparate places would be a step forward,
but a clean solution would be to bring all the documentation in *one* place, in
an easily editable format *stored on GitHub*, using a modern documentation
publishing framework like https://readthedocs.org/ or https://docusaurus.io/,
or at least a Wiki like MediaWiki.

I suspect a chunk of documentation might be in code comments and needs to be
extracted out, so I'm not making specific recommendations for a documentation
platform.

But I do want to urge using GitHub (or at least GitLab) as the VCS, because
whether you like it or not, GitHub does make it easy to edit documentation in a
browser, and has the highest number of registered developers familiar with its
interface and with an account already set up. This is key for encouraging
"drive-by" documentation fixes and contributions.

Note that MDN, one of the largest and most often accessed open-source
documentation platforms ever, has also switched to GitHub for hosting the
content and accepting contributions -
https://hacks.mozilla.org/2020/10/mdn-web-docs-evolves-lowdown-on-the-upcoming-new-platform/

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

[Libreoffice-bugs] [Bug 148621] New: The horrible state of the BASIC API and documentation

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

Bug ID: 148621
   Summary: The horrible state of the BASIC API and documentation
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: BASIC
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ddascalescu+freedesk...@gmail.com

Created attachment 179607
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179607=edit
Poor documentation layout

Preface: I've been a web developer for over 15 years. I've read API docs from
hundreds, possibly over a thousand of libraries and projects. LibreOffice is
the most horribly organized API that I've seen, with the worst documentation
that I've encountered. I'm really sorry to say this, but it's my honest
opinion.

To make this bug more concrete and actionable, I'll give some examples.

1. Five years since I've asked, there is still no clear reference documentation
for the JavaScript macro API
(https://ask.libreoffice.org/t/javascript-macro-reference/25851). Why does it
even exist?

2. The documentation web page template at
https://help.libreoffice.org/7.4/en-US/text/sbasic/shared/03/lib_tools.html has
a pointlessly narrow column width, which truncates the visible text and makes
it impossible to clearly see an entry at once (see screenshot). That text
column also scrolls through the search bar at the top.

3. Searching through the macros documentation returns a jumble of results,
mixing user-facing functions and Calc formulas. Try searching for "regular
expression" in hopes of finding a BASIC macro function that does regular
expression search and replace. Apparently there isn't one. 臘

To use regular expressions, you need to import some cryptic service, and the
code looks like this mess: 濫

yourString = 'Some string with a cell reference like A123 and other stuff'
oTextSearch = CreateUnoService("com.sun.star.util.TextSearch")
oOptions = CreateUnoStruct("com.sun.star.util.SearchOptions")
oOptions.algorithmType = com.sun.star.util.SearchAlgorithms.REGEXP
oOptions.searchString = "([A-Z0-9]+)"
oTextSearch.setOptions(oOptions)
oFound = oTextSearch.searchForward(yourString, 0, Len(yourString))
sFound = mid(yourString, oFound.startOffset(0) + 1, oFound.endOffset(0) -
oFound.startOffset(0))
MsgBox(sFound)

(By the way, I found this on StackOverflow, not anywhere in the documentation.
For 20+ years, the vast majority of programming languages have had built-in
functions for regular expression search.)

4. The BASIC **Strings** module
(https://help.libreoffice.org/7.4/en-US/text/sbasic/shared/03/lib_tools.html?=BASIC=UNIX#strings_module)
lacks such basic functions as finding or replacing based on regular
expressions. 臘‍♂️ Instead, it provides a **Power** function, which has 
absolutely
nothing to do with strings, or a "CheckDouble" one, without documentation.

5. Apparently nobody has edited the documentation for comprehensible English.
>From the same page: "Retrieves the second value for a next to 'SearchString' in
a two-dimensional string-Array" - what?

6. The documentation is apparently split up with some parts at
help.libreoffice.org, and others at api.libreoffice.org (e.g.
https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1util_1_1SearchDescriptor.html,
which again is devoid of examples and context)

I know there are probably historical arguments for why things are the way they
are, but please understand that A NEW DEVELOPER DOESN'T CARE about this, and
they will be turned off by the current state of the API and documentation. (I'm
weird and have stuck with it for 5+ years, but for every person like me, 100
have just left without bothering to leave any feedback - see
https://en.wikipedia.org/wiki/1%25_rule).

So if we want to stop scaring away users and macro developers, we'd better fix
this.

-- 
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-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148575

--- Comment #5 from spec...@joepgen.com ---
The original document can't be sent, since it contains confident tax reports.
But I'll try to create a similar document with bogus data. But this will
require some time - many days. It's very large with many write tables, which
reference each other.

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

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

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

--- Comment #21 from Eyal Rozenberg  ---
As an "RTL/CTL guy", I'd like to remind everyone to make sure and distinguish
between the left edge of a line, and the start of line. In LTR direction they
are the same, while in RTL they're the opposite of each other, with lines
starting on the right.

(LO in general doesn't properly support Start/End vs Left/Right, see
https://bugs.documentfoundation.org/show_bug.cgi?id=131192)

So, ideally, there would be separate Start, End, Left and Right options; but at
the very least - please decide whether you really mean Start and End rather
than Left and Right, i.e. think of what these breaks are supposed to do in an
RTL paragraph.

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

  1   2   >