[Libreoffice-bugs] [Bug 148194] slanted cells do not display correctly

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148194

--- Comment #1 from Elmar  ---
Created attachment 179114
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179114=edit
sheet1 displays incorrectly

It would be nice if there were some kind of tool that could "audit" a sheet and
identify cases where the sheet metadata does not conform to the standard so
that this could be corrected

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

[Libreoffice-bugs] [Bug 148194] New: slanted cells do not display correctly

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148194

Bug ID: 148194
   Summary: slanted cells do not display correctly
   Product: LibreOffice
   Version: 7.4.0.0 alpha0+ Master
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rob...@iafrica.com

Description:
I have columns where the data in the body will be a single character. The
heading is 10 or more characters. To conserve space, especially as the sheet
can be many pages I want to slope the heading text at 45 degree angle.

Steps to Reproduce:
1. type text in cells
2.change cell slope 
3.

Actual Results:
displays incorrectly.

Expected Results:
should be correctly positioned and not overlap text from different cells


Reproducible: Always


User Profile Reset: No



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

NOTE:
This seems t  be a problem that previously existed but has since been
corrected.
The original spreadsheet was created in around 2014/6, originally in Excel and
then opened in Calc. See the extracted Sheet1 from that file. It had originally
not had any formatting, just text.
However, when I extracted sheet2 from a file created some years later,
originally created in Calc, it displays correctly.
If I add a new Sheet3, then copy the cells from Sheet1 to Sheet3 as unformatted
text and then format them, it displays correctly.

So, why raise this as a bug?
Mainly to query how a person would resolve a problem like this. 
I have a long history of working with these kind of tools (from Visicalc in
1983).
I was using a file which was already in ODS format and it was through some
experimentation that I found that this might have been a bug in a former
version. 
How does another user of Calc figure this out?
My original file has 36 sheets in if many were still raw and I would have a lot
of work to fix this.
But maybe there are few who would experience this.

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

[Libreoffice-bugs] [Bug 146320] Base Report generator Java error

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146320

Lucas  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #13 from Lucas  ---
Uninstalling previews versions and installing from
https://www.libreoffice.org/download/download/ as suggested in Comment 10
solved this problem.

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

[Libreoffice-bugs] [Bug 144869] Feature Request for export format Similar to SVG

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144869

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 147924] [UI] Missing icon in colibre icon set

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147924

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 147915] Mirroring of page headers not working in one case

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147915

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 147943] Allow numbering formats when sending Master Document

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147943

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 147943] Allow numbering formats when sending Master Document

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147943

--- 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 144726] Programa Libre Office se cierra inesperadamente

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144726

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

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 146320] Base Report generator Java error

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146320

--- Comment #12 from Lucas  ---
I have this problem too. I use OpenSUSE Leap 15.3, LibreOffice 7.2.5.1 and
PostgreSQL. 

Initially I installed OpenOffice from their website but I did not know how to
connect to PostgreSQL using JDBC. So I installed LibreOffice through YaST. I
connected to PostgreSQL by selecting PostgreSQL option when creating the Libre
Office Base database. In Libre Office Base I can open tables and views from
PostgreSQL but I cannot run reports.

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

[Libreoffice-bugs] [Bug 148170] Calc: setting print range not remember

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148170

--- Comment #2 from pornchai_...@hotmail.com ---
I found this when I'm working with my xls file. 
I created this file with Calc and save as xls format.

And I have set filter to some column in the sheet I do print, but I show all
data for that column when print.

I tried set print rage to other sheet (sheet B) in same file but no filter,
then I previewed to check the setting. I closed and reopened the file with
sheet B and check with print preview, the setting pring range is reset.

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

[Libreoffice-bugs] [Bug 148193] New: Reading .ods file created by LibreOffice 7.0.4.2 or newer breaks jOpenDocument

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148193

Bug ID: 148193
   Summary: Reading .ods file created by LibreOffice 7.0.4.2 or
newer breaks jOpenDocument
   Product: LibreOffice
   Version: 7.0.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: l...@heess.me

Could this bug be caused by LibreOffice:
https://bugs.documentfoundation.org/show_bug.cgi?id=139446

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

[Libreoffice-bugs] [Bug 139446] using jOpenDocument-1.3.jar read ods created by LibreOffice 7.0.4.2 has error

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139446

--- Comment #2 from l...@heess.me ---
Hi, I am maintaining a huge software project built with jOpenDocument and
because of this error I can't support any of the newer versions of LibreOffice.
Any chance this will get fixed or do I have to migrate to a new library all
together?

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

[Libreoffice-bugs] [Bug 148192] Create a new option External Firebird file under Create new database

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148192

--- Comment #1 from B. Antonio Fernández  ---
I am of the same opinion, the user should have the option to create a firebird
database to use it as external database

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

[Libreoffice-bugs] [Bug 148192] New: Create a new option External Firebird file under Create new database

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148192

Bug ID: 148192
   Summary: Create a new option External Firebird file under
Create new database
   Product: LibreOffice
   Version: 7.3.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jcs...@libreoffice.org

Currently, in the first step of the database wizard, three options are
available.

When selecting the first option, *Create* a new database, if the experimental
functionalities have been enabled, it proposes two options Firebird embedded
and HSQLDB embedded (but it does not propose to create an external Firebird
archive).

However, if we select the third option, Connect to an *existing* database, in
the next step, we can connect to an existing Firebird file (by selecting the
Browse button) but in addition we have a *Create new* button, which allows us
to create a new external Firebird file.

This behavior can mislead the user, who does not see the way to create a new
Firebird database file in the option that should correspond to it (Create a new
database) while the option to create the database is in Connect to an
*existing* file.

So I believe that adding a new entry under Create new database that allows you
to create an external Firebird database and at the same time removing the
Create new button from Connect to an existing database would improve the user
experience by having the options in the places where they should be expected.

In addition, the user would have the two options for creating Firebird
databases (embedded and external) in the same place, allowing them to decide
which is best option

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

[Libreoffice-bugs] [Bug 148191] New: xlink:href in SVG is deprecated

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148191

Bug ID: 148191
   Summary: xlink:href in SVG is deprecated
   Product: LibreOffice
   Version: 7.3.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: gessos.p...@yahoo.gr

Description:
According to
https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/xlink:href
xlink:href is deprecated for SVG images.
But LibreOffice Writer needs it.

So, instead of:
http://www.w3.org/2000/svg;
xmlns:xlink="http://www.w3.org/1999/xlink;>
...


which is deprecated, anyone must use:

http://www.w3.org/2000/svg;>
...



First, which is deprecated, works on LibreOffice.
Second, which is current, does not work.


Steps to Reproduce:
1. Follow description
2.
3.

Actual Results:
.

Expected Results:
.


Reproducible: Always


User Profile Reset: No



Additional Info:
.

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

[Libreoffice-bugs] [Bug 130383] Filesave ODS: Row height after Optimal Height still opens as 1 line instead of 2 in cell F5 (not with XLS/X)

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=130383

--- Comment #13 from Gessel  ---
I took a screengrab of your demo spreadsheet when I opened it with "enable very
large spreadsheets" enabled and it looked like this:
https://bug-attachments.documentfoundation.org/attachment.cgi?id=179081

It returned to normal after disabling that option with row heights correct.  I
suppose there might be some other configuration option that triggers the bug I
do not have set and you do, happy to exchange configs for a diff check to see
if something pops out.

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

[Libreoffice-bugs] [Bug 136358] [META] ODF to OOXML shape export related issues

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136358
Bug 136358 depends on bug 100390, which changed state.

Bug 100390 Summary: FILESAVE: OOXML export of cloud shape leaves cloud 
partially unfilled
https://bugs.documentfoundation.org/show_bug.cgi?id=100390

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 108897] [META] XLSX (OOXML) bug tracker

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108897
Bug 108897 depends on bug 100390, which changed state.

Bug 100390 Summary: FILESAVE: OOXML export of cloud shape leaves cloud 
partially unfilled
https://bugs.documentfoundation.org/show_bug.cgi?id=100390

   What|Removed |Added

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

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

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

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108226
Bug 108226 depends on bug 100390, which changed state.

Bug 100390 Summary: FILESAVE: OOXML export of cloud shape leaves cloud 
partially unfilled
https://bugs.documentfoundation.org/show_bug.cgi?id=100390

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 104520] [META] DOCX (OOXML) bug tracker

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104520
Bug 104520 depends on bug 100390, which changed state.

Bug 100390 Summary: FILESAVE: OOXML export of cloud shape leaves cloud 
partially unfilled
https://bugs.documentfoundation.org/show_bug.cgi?id=100390

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 136358] [META] ODF to OOXML shape export related issues

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136358
Bug 136358 depends on bug 147978, which changed state.

Bug 147978 Summary: FILESAVE PPTX Cloud shape loses fill after RT
https://bugs.documentfoundation.org/show_bug.cgi?id=147978

   What|Removed |Added

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

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

--- Comment #8 from Regina Henschel  ---
The shapes "Diamond Bevel" and "Octagon Bevel" are difficult:
(A)
These shapes have neither a counterpart in the OOXML preset shapes nor in
shapes of the binary versions of MS Office. So they need to be exported to an
element "custGeom". That export is done in method WriteCustomGeometry. This
method cannot export equations or handles, but only exports the current state
of the shape outline. Export of equations and handles into "custGeom" is very
hard and will not be implemented in the foreseeable future. So we will loose
the handles.
(B)
Because they have no counterpart in the OOXML preset shapes, it will not be
possible to recreate them, when the pptx file will be reopened by LO. They will
be of type "ooxml-non-primitive". That means the next save to pptx will use
WriteCustomGeometry anyway.
(C)
The export in WriteCustomGeometry is in the meantime (current master!) able to
export the lighten/darken commands of the enhanced-path. But the shapes
"Diamond Bevel" and "Octagon Bevel" are not implement the same way as the
shapes from binary MS Office. "Diamond Bevel" and "Octagon Bevel" shapes are
inserted from private://gallery/hidden/imgppt. That Gallery theme is so old,
that is does not know anything about the lighten/darken commands. Their
lighten/darken is different from the lighten/darken in other shapes. The path
does not contain commands for lighten/darken. The shapes are stored in binary
format in the Gallery theme so there is no way to add the needed commands.
(D)
The export to binary MS Office formats does not export them to a shape but to a
WMF image. That keeps lighten/darken but looses handles same as export by
WriteCustomGeometry. Using WMF image drops the possibility to edit a text in
the shape. 

We could move the two shapes from the list in lcl_IsOnDenylist in
/oox/source/export/shapes.cxx to the list in lcl_IsOnAllowlist. That way they
would be exported by method WriteCustomGeometry. Currently an export as preset
shape is tried and because that fails the default preset shape "rect" is used.

Using WriteCustomGeometry would preserve outline and editable text but looses
darken/lighten. Using WMF image preserves outline and darken/lighten but you
can no longer edit text. Both ways loose handles.

@Gabor: What do you think we should do?

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

[Libreoffice-bugs] [Bug 142447] Cut, copy, paste and drag operations for folded outlines: include folded content

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142447

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

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

tdf#142447 related: SwNavigator: Copy outlines

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 142447] Cut, copy, paste and drag operations for folded outlines: include folded content

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142447

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 142447] Cut, copy, paste and drag operations for folded outlines: include folded content

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142447

--- Comment #23 from Jim Raykowski  ---
(In reply to Gerry from comment #22)
> Hi Jim and Heiko, in case you are not aware: the gerrit patch in comment 19
> seems to got stuck and hasn't yet had any reviewers looking at it. The
> pootle bot started complaining "A polite ping, still working on this patch?"
H Gerry, I've rebased that patch on top of master and will put it after getting
the OK from Jenkins.

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

[Libreoffice-bugs] [Bug 148190] Support cell-level widow/orphan control

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148190

--- Comment #1 from Eyal Rozenberg  ---
The motivation: Similar to paragraph widow-orphan control, but when you have a
table row with many paragraphs, so that intra-paragraph widow-orphan settings
don't prevent the table from having just a small part on the first page, e.g.
one line of contents and the repeating header lines. That looks kind of iffy.

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

[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103100

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||148190


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148190
[Bug 148190] Support cell-level widow/orphan control
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148190] New: Support cell-level widow/orphan control

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148190

Bug ID: 148190
   Summary: Support cell-level widow/orphan control
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com
Blocks: 103100

LO Writer supports paragraph-level widow/orphan control: Not letting a
paragraph have just its first k lines or last k lines separate from all the
rest (on a different page).

I suggest having a similar feature for table rows, w.r.t. lines within them (or
rather, lines within the paragraphs within them): Don't allow a row to break
across pages or columns when its first or last part has no more than k lines.

Paragraphs are inconsequential here, in the sense that it doesn't matter if the
k lines belong to k paragraphs or less-than-k or even a single paragraph.
Naturally, per-paragraph widow-orphan settings would also apply.


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 142447] Cut, copy, paste and drag operations for folded outlines: include folded content

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142447

--- Comment #22 from Gerry  ---
Hi Jim and Heiko, in case you are not aware: the gerrit patch in comment 19
seems to got stuck and hasn't yet had any reviewers looking at it. The pootle
bot started complaining "A polite ping, still working on this patch?"


Btw: Is there a chance that outline folding gets out of experimental mode for
LibreOffice 7.4?

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

[Libreoffice-bugs] [Bug 114637] Autocorrect should fully support Hebrew-specific punctuation marks

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114637

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||148189


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148189
[Bug 148189] Autocorrect hyphen/minus sign into Hebrew Maqaf when appropriate
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148189] New: Autocorrect hyphen/minus sign into Hebrew Maqaf when appropriate

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

Bug ID: 148189
   Summary: Autocorrect hyphen/minus sign into Hebrew Maqaf when
appropriate
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com
Blocks: 114637

The Hebrew language uses a character named Maqaf - essentially a top hyphen -
instead of the latin languages' inter-word hyphen. It is not a dash (neither en
nor em), and is not used as a minus sign. More about this character:

https://codepoints.net/U+05BE

and here's an example:

אבי־סער

the Maqaf separates the two words.

The character does not have its own key on a Hebrew-layout keyboard; and use of
hyphens in its stead is quite popular by now, so it is no longer in wide use by
people typing in text... unfortunately. It can be inserted using Alt+underscore
in a Hebrew-layout keyboard on Linux, and is rendered properly, but that is
still not good enough.

The Auto-correct mechanism, when enabled, should replace a hyphen/minus
character with a Maqaf when one types in a sequence of at least two Hebrew
characters, then a hyphen, then another sequence of at least 2 Hebrew
characters. Typing just one character, or mixing in non-Hebrew characters, or
using spaces, should not result in the replacement, to keep things on the
conservative side.


Note: I've split this off from bug 114637, which now becomes a meta-bug,
because this capability is self-contained enough and important enough to merit
its own bug.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=114637
[Bug 114637] Autocorrect should fully support Hebrew-specific punctuation marks
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148167] Writer does not display SVG file correctly when inserted as image

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148167

--- Comment #5 from Gerry  ---
Created attachment 179112
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179112=edit
SVG-in-Firefox-top_and_LibreOffice73_bottom.png

Thanks Xisco for the Screenshots of the SVG in Firefox and Libreoffice. I
assume that Xisco does not have the font Calibri installed, thus here is
another screenshot from a system that has Calibri installed: 
The SVG in Firefox (top) & in LibreOffice 7.3.1.3 (bottom).

Both screenshots, Xisco's and mine, shows the bug in the right grey box in the
svg drawing.

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

[Libreoffice-bugs] [Bug 148080] UI: Dialog "Rename Slide" should name "Rename Page"

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148080

--- Comment #9 from lol  ---
(In reply to Dave Barton from comment #5)

> Yes it appears to be an error in the procedure/function called from the main
> menu "Page -> Rename Page" option.

Maybe I find the reason why you couldn't reproduce the bug at first. Did you
clicked first on the page in the page pane? See the different steps.

Steps:

1. Open Draw
2. Open the dialog via Page - Rename Page...
3. Dialog appears with the title "Rename Slide"

Steps:

1. Open Draw
1a. Click on the page in the Page Pane
2. Open the dialog via Page - Rename Page...
3. Dialog appears with the title "Rename Page"

If the focus is on the page in the page pane the dialog has a another title.

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

[Libreoffice-bugs] [Bug 108911] Cannot toggle cursor focus between formula and worksheet

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108911

--- Comment #10 from Rick Collins  ---
The problem is still present.  It also interferes with editing or adding a
reference to a cell immediately adjacent to the cell being edited. If the
formula is large enough, the editing field over the cell being edited blocks
viewing the adjacent cells.  This makes it impossible to click on it with the
cursor.  Without being able to use the arrow keys to select the cell, the only
choice remaining is to type the cell reference manually. 

I would have expected this to not take so long to fix.  I'm sure this impacts a
lot of users and is rather a headache.

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

[Libreoffice-bugs] [Bug 148186] Potentially confusing text label on Base Database Wizard when connecting to a Firebird file

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148186

Robert Großkopf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #1 from Robert Großkopf  ---
(In reply to Steve Fanning from comment #0)
> 4. At Step 2 of the Database Wizard, notice the legend positioned above the
> text field. It reads "Datasource URL (e.g. host=$host=$host:$port
> dbname=$database)".

This has been changed from LO 7.2.5 to LO 7.3.2. Now there appears:
"Enter the DBMS/driver-specific connection string here".

This should be better something like:
"Enter or choose the URL to the Firebird file here".

Used version here:
Version: 7.3.2.2 / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 148188] Distribute Selection not working correctly when shadows are enabled

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148188

--- Comment #1 from Rafael Lima  ---
Created attachment 179111
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179111=edit
Sample ODP file

This is the sample ODP file I used in the video.

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

[Libreoffice-bugs] [Bug 148188] New: Distribute Selection not working correctly when shadows are enabled

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148188

Bug ID: 148188
   Summary: Distribute Selection not working correctly when
shadows are enabled
   Product: LibreOffice
   Version: 7.3.1.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rafael.palma.l...@gmail.com

Created attachment 179110
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179110=edit
Video showing the bug

In Impress/Draw, if you select 3 or more objects, right-click them and go to
Distribute Selection > Horizontally Spacing, the objects should be
re-positioned so that the horizontal spacing between them is the same. This
works nicely when objects do not have shadows. However, when shadows are
enabled, the horizontal spacing is calculated incorrectly.

See the attached video where I use 2 sets with three rectangles each. The first
set does not have shadows and horizontal spacing works fine. Enabling shadows
in the second set of rectangles breaks spacing calculations.

Steps to reproduce:
1) Open the attached sample ODP file
2) Select the 3 rectangles without shadows
3) Go to Distribute Selection > Horizontally Spacing
4) Notice the three rectangles are spaced evenly (which is expected)
5) Now select the three rectangles with shadows
6) Go to Distribute Selection > Horizontally Spacing
7) Notice that the spacing between rectangles is not the same

System info:
Version: 7.3.1.3 / LibreOffice Community
Build ID: 30(Build:3)
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.1~rc3-0ubuntu0.21.10.1~lo2
Calc: threaded

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

[Libreoffice-bugs] [Bug 105446] Copying forms not working anymore

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105446

--- Comment #10 from Kevin Geller  ---
I am a tech blogger. I write tech articles that solve problems related to
software  and hardware. The site https://enhau.com/ has many articles that help
people solve their problems. Just visit this site it might help solve th bug

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

[Libreoffice-bugs] [Bug 132106] CELL() function "format" should include more date formats to return "D1" (or a new "D0")

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132106

--- Comment #15 from peter.hy...@gmail.com ---
I'm not entirely sure if its related, but when I open a Excel document that
dropped in `[$-en-US]` prefixes to the number values, especially date formats,
it doesn't get read properly by Calc.  Is this issue close enough? Or should I
open a new issue about the problems with using the format prefixes in Calc?

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

[Libreoffice-bugs] [Bug 148187] page numbering does not work when setting a start value

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148187

--- Comment #2 from auch.wich...@posteo.de ---
Created attachment 179109
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179109=edit
page numbers are not ok with offset

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

[Libreoffice-bugs] [Bug 148187] page numbering does not work when setting a start value

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148187

--- Comment #1 from auch.wich...@posteo.de ---
Created attachment 179108
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179108=edit
page numbers are ok without offset

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

[Libreoffice-bugs] [Bug 148187] New: page numbering does not work when setting a start value

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148187

Bug ID: 148187
   Summary: page numbering does not work when setting a start
value
   Product: LibreOffice
   Version: 7.2.6.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: auch.wich...@posteo.de

Description:
In a multi-page document the page numbering in the header or footer does not
work if a start value n is given.
No page number is displayed for the last n pages.

Steps to Reproduce:
1. Create a new multi-page document.
2. Set a page header or footer (Insert - Header and Footer - ...) and insert a
page number (Insert - Page Count)
3. Change the start number (Edit - Fields, Page number - Offsets)

Actual Results:
If you set an offset of e.g. 3 the last 3 pages will not show any page numbers

Expected Results:
The last pages should show a page number


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.2.6.2 / LibreOffice Community
Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754
CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

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

[Libreoffice-bugs] [Bug 148186] New: Potentially confusing text label on Base Database Wizard when connecting to a Firebird file

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148186

Bug ID: 148186
   Summary: Potentially confusing text label on Base Database
Wizard when connecting to a Firebird file
   Product: LibreOffice
   Version: 7.2.5.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: stevemfanning...@gmail.com

Description:
When connecting to a Firebird file via the Database Wizard, there is a text
field for entry of the file's location. The legend adjacent to this field is
"Datasource URL (e.g. host=$host=$host:$port dbname=$database)". The text of
this legend may have been copied/pasted from a similar field for creating a
JDBC connection but is very likely to confuse users in this context. Consider
replacing this text when connecting to a Firebird file with something simpler
and more relevant, such as "File location".

Steps to Reproduce:
1. In any LO component, select File > New > Database on Menu bar.
2. At Step 1 of the Database Wizard, click the "Connect to an existing
database" option and select the "Firebird File" entry in the adjacent drop-down
menu.
3. Click the "Next" button.
4. At Step 2 of the Database Wizard, notice the legend positioned above the
text field. It reads "Datasource URL (e.g. host=$host=$host:$port
dbname=$database)".

Actual Results:
Not applicable

Expected Results:
Not applicable


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.5.2 (x64) / LibreOffice Community
Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5
CPU threads: 6; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_GB); UI: en-US
Calc: CL

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

[Libreoffice-bugs] [Bug 143192] 'Format' Basic function doesn't handle Null values

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143192

--- Comment #2 from Paris Oplopoios  ---
I am trying to work on tdf#143193. Is Null supposed to be a correct data type?
It doesn't seem to recognize it as one.

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

[Libreoffice-bugs] [Bug 147809] Updating a paragraph style's associated list style has no effect on other paragraphs with the style

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147809

--- Comment #7 from Dieter  ---
(In reply to Eyal Rozenberg from comment #6)
> Shall I try to run it from a terminal and see if I get
> some interesting output?

Don't know, sorry.

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

[Libreoffice-bugs] [Bug 147899] Borders: Allow Shadow Style Distance to be less than than 0.1 cm (current default) or change Default to Point

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

--- Comment #9 from Luke  ---
(In reply to Heiko Tietze from comment #8)
> (In reply to Heiko Tietze from comment #3)
> Don't see why this needs to be an extra ticket.

Only if you fix this by a overly complex workaround. Following the industry
standard of using a point, like Word and Word Prefect would eliminate the need
for the user to manually manage the complexity of changing units. 

Why shift this burden to the User? Why not use the industry standard unit here?
We are doing it wrong. As a result it creates problems for the user that don't
exist in other productivity suites. Change the unit to point. Don't force the
user to juggle units that don't make sense for the measurement.

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

[Libreoffice-bugs] [Bug 147809] Updating a paragraph style's associated list style has no effect on other paragraphs with the style

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147809

--- Comment #6 from Eyal Rozenberg  ---
(In reply to Dieter from comment #5)
> Correct, so I don't understand, why "Update Selected Style" doesn't work for
> you, if cursor is in second paragraph.

I don't know either... it just doesn't work. Maybe it's something with the
nightly I'm using? Shall I try to run it from a terminal and see if I get some
interesting output?

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

[Libreoffice-bugs] [Bug 147582] PostgreSQL JDBC: Form with Subform and SubSubform gives Parameter Error for SubSubForm

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147582

Alex Thurgood  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #6 from Alex Thurgood  ---
This is the error I get on opening the JDBC connected form:

Statut SQL: 42883

ERROR: operator does not exist: integer = character varying
  Indice : No operator matches the given name and argument type(s). You might
need to add explicit type casts.
  Position : 79

and then indeed, there is no connection to the subsubform if no subform data is
provided beforehand.

Confirming.

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

[Libreoffice-bugs] [Bug 148185] New: German translation - little issue

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148185

Bug ID: 148185
   Summary: German translation - little issue
   Product: LibreOffice
   Version: 7.3.1.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Installation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: klaus.lupp...@gmail.com

Created attachment 179107
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179107=edit
screenshot

German translation for installation needs a little fix.
I found it during 7.3.2.2 installation, but I couldn't select it here for this
bug, since it is not listed.
Anyway, I uploaded a screenshot -> the two blue and the two green marked words
match, but the two red marked which is german for "Cancel" needs to be matched.

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

[Libreoffice-bugs] [Bug 147304] UI: Find and replace dialog position to parent is off (dialog doesn't open centered to main screen)

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147304

--- Comment #5 from Dieter  ---
(In reply to Dieter from comment #3)
> I suppose, that there is an underlying problem: The dialog position to
> parent is off (dialog doesn't open centered to main screen); same with Table
> of Content dialog (see bug 146562)

Looks good now in

Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: e8c95b796626cb9db163f5d563fa67f38a5e92b0
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

HTK300, could you please retest?

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

[Libreoffice-bugs] [Bug 147899] Borders: Allow Shadow Style Distance to be less than than 0.1 cm (current default) or change Default to Point

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org
   Keywords|needsUXEval |

--- Comment #8 from Heiko Tietze  ---
(In reply to Heiko Tietze from comment #3)
> Smallest number that can be entered manually is 0.01cm...
> ... The solution is to me to allow different units per control, as requested 
> at bug 72662.

Don't see why this needs to be an extra ticket.

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

[Libreoffice-bugs] [Bug 147809] Updating a paragraph style's associated list style has no effect on other paragraphs with the style

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147809

--- Comment #5 from Dieter  ---
(In reply to Eyal Rozenberg from comment #4)
> After step 4,
> 
> * Format -> Paragraph -> Outline & List while in the second paragraph -
> "Bullet -" is the applied list style.
> * Format -> Paragraph -> Outline & List while in the first paragraph -
> "Numbering 123" is the applied list style.
> * Right-click -> Outline & List on the "foo" style - "Numbering 123" is the
> applied list style.

Correct, so I don't understand, why "Update Selected Style" doesn't work for
you, if cursor is in second paragraph.

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

[Libreoffice-bugs] [Bug 147899] Borders: Allow Shadow Style Distance to be less than than 0.1 cm (current default) or change Default to Point

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

Luke  changed:

   What|Removed |Added

Summary|Borders: Allow Shadow Style |Borders: Allow Shadow Style
   |Distance to be less than|Distance to be less than
   |than 0.1 cm (current|than 0.1 cm (current
   |default)|default) or change Default
   ||to Point

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

[Libreoffice-bugs] [Bug 147899] Borders: Allow Shadow Style Distance to be less than than 0.1 cm (current default)

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

--- Comment #7 from Luke  ---
Created attachment 179106
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179106=edit
MS Word Shadow Distance in Points

This is another case of using the wrong units. Both Word and Word Perfect use
the natural unit of point for Shadow Distance. In typography, the traditional
unit is the point.

Switching to that not only makes sense for all professional users, but also
would follow the industry standard. Finally it would fix this issue of forcing
a user to switch to mm as it's the only other unit (although non-standard) that
makes sense in this use case.

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

[Libreoffice-bugs] [Bug 147809] Updating a paragraph style's associated list style has no effect on other paragraphs with the style

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147809

--- Comment #4 from Eyal Rozenberg  ---
(In reply to Dieter from comment #3)
> (In reply to Eyal Rozenberg from comment #2)
> > Expected results:
> > After step 1.5, the paragraphs begin with "1." and "2." respectively.
> > After step 5, both paragraphs have an en-dash-like bullet.
> 
> Yes, and this is my result.
> 
> After step 4, please open Format -> Paragraph -> Outline & List
> List St[y]le "Bullet -" is the applied list style. Do you get the same result?

After step 4,

* Format -> Paragraph -> Outline & List while in the second paragraph - "Bullet
-" is the applied list style.
* Format -> Paragraph -> Outline & List while in the first paragraph -
"Numbering 123" is the applied list style.
* Right-click -> Outline & List on the "foo" style - "Numbering 123" is the
applied list style.

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

[Libreoffice-bugs] [Bug 147809] Updating a paragraph style's associated list style has no effect on other paragraphs with the style

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147809

Dieter  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #3 from Dieter  ---
(In reply to Eyal Rozenberg from comment #2)
> Expected results:
> After step 1.5, the paragraphs begin with "1." and "2." respectively.
> After step 5, both paragraphs have an en-dash-like bullet.

Yes, and this is my result.

After step 4, please open Format -> Paragraph -> Outline & List
List Stle "Bullet -" is the applied list style. Do you get the same result?

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

[Libreoffice-bugs] [Bug 147809] Updating a paragraph style's associated list style has no effect on other paragraphs with the style

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147809

Eyal Rozenberg  changed:

   What|Removed |Added

Summary|Updating a list style to|Updating a paragraph
   |reflect a change to bullets |style's associated list
   |has no effect   |style has no effect on
   ||other paragraphs with the
   ||style

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

[Libreoffice-bugs] [Bug 147809] Updating a list style to reflect a change to bullets has no effect

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147809

--- Comment #2 from Eyal Rozenberg  ---
Created attachment 179105
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179105=edit
Document for reproducing the bug

Here are reproduction instructions, without even using a custom list style,
just a custom paragraph style:

1.
1.1 Type in two paragraphs, with text "first" and "second" respectively (and
type Enter after the end of each paragraph)
1.2 Create a new style based on the default paragraph style, named foo
1.3 Apply style "foo" to the first paragraph
1.4 Apply numbering style "Numbering 123" to the first paragraph
1.5 In the Styles Sidebar, switch to paragraph styles, right-click "foo" and
from the top-right menubutton choose "Updated Selected Style"
1.6 Apply style foo to the second paragraph

(or alternatively: 
1. Open 147809.odt
)

2. Place cursor on one of the foo paragraphs
3. On the Styles Sidebar, choose List Styles
4. Apply the "Bullet -" style
5. In the Styles Sidebar, switch to paragraph styles, right-click "foo" and
from the top-right menubutton choose "Updated Selected Style"

Expected results:
After step 1.5, the paragraphs begin with "1." and "2." respectively.
After step 5, both paragraphs have an en-dash-like bullet.

Actual result:
After step 1.5, the paragraphs begin with "1." and "2." respectively.
After step 5, only the paragraph chosen in step (2.) now exhibits an
en-dash-like bullet, the other one is still preceded by a number.

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

[Libreoffice-bugs] [Bug 147899] Borders: Allow Shadow Style Distance to be less than than 0.1 cm (current default)

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

Dieter  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #6 from Dieter  ---
Heiko, waht Info do you need?

I've tested with master and got the same result

Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 51fb84829afbc1c0957fd1a489085613ad199f1a
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

@R. Green, could you please also test?

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

[Libreoffice-bugs] [Bug 147943] Allow numbering formats when sending Master Document

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147943

--- Comment #4 from L Duperval  ---
In the attached zip file, there is:

mybook.odm with mybook.odt. Those are the generated files.

mybook.odt (without a number) contains a single file that can be used to run
the process again (it will create about 20 subdocuments and a master document).

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

[Libreoffice-bugs] [Bug 147943] Allow numbering formats when sending Master Document

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147943

--- Comment #3 from L Duperval  ---
Created attachment 179104
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179104=edit
Sample output from a document

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

[Libreoffice-bugs] [Bug 147943] Allow numbering formats when sending Master Document

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147943

--- Comment #2 from L Duperval  ---
No, not quite.

The "Send to Master Document" process works like this:

You have a document with 20 "Heading 1" paragraphs in it.

Choose "File > Send > Create Master Document"

A window opens, asking you to give a name to your master document. So, let's
say I call it "mybook.odm"

Then Writer will create files called

mybook.odm
mybook1.odt
mybook2.odt
mybook3.odt
.
.
.
mybook10.odt
mybook11.odt
..
.


What I'm asking is for the ability to have some control over the naming of the
files, without needing to do them by hand after the fact.

In my case, it would be:

mybook.odm
mybook-01.odt
mybook-02.odt
.
.
.
mybook-10.odt
mybook-11.odt
.
.
.

I'm attaching a file so you can test out the process.

P.S. this particular file also caused problems witht eh Master document
creation process. Although all the ODT files were created, they did not appear
in the structure. I had to add them by hand.

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

[Libreoffice-bugs] [Bug 147899] Borders: Allow Shadow Style Distance to be less than than 0.1 cm (current default)

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

Heiko Tietze  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

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

[Libreoffice-bugs] [Bug 147899] Borders: Allow Shadow Style Distance to be less than than 0.1 cm (current default)

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

--- Comment #5 from Heiko Tietze  ---
Created attachment 179103
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179103=edit
Screencast

(In reply to Dieter from comment #4)
> ... but shadow has always width of 0,1 cm and if you reopen dialog...

Cannot confirm

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

[Libreoffice-bugs] [Bug 107838] [META] Character-level bugs and enhancements

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107838

Dieter  changed:

   What|Removed |Added

 Depends on||147869


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=147869
[Bug 147869] Problem with border around characters at beginning of list entry
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108382] [META] Borders bugs and enhancements

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108382

Dieter  changed:

   What|Removed |Added

 Depends on||147869


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=147869
[Bug 147869] Problem with border around characters at beginning of list entry
-- 
You are receiving this mail because:
You are the assignee for the bug.

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

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103369

Dieter  changed:

   What|Removed |Added

 Depends on||147869


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=147869
[Bug 147869] Problem with border around characters at beginning of list entry
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 147869] Problem with border around characters at beginning of list entry

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147869

Dieter  changed:

   What|Removed |Added

 Blocks||107838, 108382, 103369
Summary|Border in character style   |Problem with border around
   |disrupts list style |characters at beginning of
   ||list entry
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

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

Version: 7.3.1.3 (x64) / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

But it's not only in character style but also if you add boder to a characer at
the beginning of a list.

Additional observation:
Doesn't happen with paragraph border.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103369
[Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107838
[Bug 107838] [META] Character-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108382
[Bug 108382] [META] Borders bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113200] [META] DOC (binary) field bugs and enhancements

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113200
Bug 113200 depends on bug 147861, which changed state.

Bug 147861 Summary: FILEOPEN DOC: Custom DocProperty field shows only one 
value, not the changed value
https://bugs.documentfoundation.org/show_bug.cgi?id=147861

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 72662] Use Different Measurement Units for Line vs Page Properties (e.g. point vs inch)

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=72662

Dieter  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 108014] [META] Writer character style bugs and enhancements

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108014
Bug 108014 depends on bug 147899, which changed state.

Bug 147899 Summary: Borders: Allow Shadow Style Distance to be less than than 
0.1 cm (current default)
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 147899] Borders: Allow Shadow Style Distance to be less than than 0.1 cm (current default)

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147899

Dieter  changed:

   What|Removed |Added

 Status|RESOLVED|NEW
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=72
   ||662
 Resolution|DUPLICATE   |---

--- Comment #4 from Dieter  ---
(In reply to Heiko Tietze from comment #3)
> Smallest number that can be entered manually is 0.01cm if Tools > Options >
> Writer > Units is set to centimetre.

That's true (Tools -> Options -> LibreOffice Writer -> General -> Settings) ,
but shadow has always width of 0,1 cm and if you reopen dialog it shows 0,1cm.
So a value less than 0,1 cm is not accepted. 
=> Status back to NEW

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

[Libreoffice-bugs] [Bug 69795] Macros: Copying a cell form one table to another looks different on Windows

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=69795

Andreas Heinisch  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |andreas.heini...@yahoo.de
   |desktop.org |

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

[Libreoffice-bugs] [Bug 144869] Feature Request for export format Similar to SVG

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144869

--- Comment #2 from 1820204_1@ebbinghaus.world ---
Hi Andy and Thank you for answering. I am sorry, I do not know what the
different export methods are. I do not remember to have any basic macro
installed.

What I did was always under "File -> Export ... " (The one above "Export as"
where you can create PDFs.

What is tha macro-thing?

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

[Libreoffice-bugs] [Bug 148184] New: FORMATTING create a means to represent an integer as an IP Address

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148184

Bug ID: 148184
   Summary: FORMATTING create a means to represent an integer as
an IP Address
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: umine...@gmail.com

An IP address, be it an IPv4 or IPv6 is an integer number, being a 32bit
integer if IPv4 or a 128bit if IPv6. 

Since Calc is well suited to perform number operations, it would be nice to add
a formatting option to represent an integer as an Human readable IP Address and
to accept a valid IP address and stora in the cell as an integer, as it is done
with the DATE and TIME formats.

There is an excelent set of Libreoffice Basic functions from Thomas
Rohmer-Kretz in  http://trk.free.fr/ipcalc/ to perform this task among various
other IP related functions, but it would be better to have a native conversion
in place, since going the Basic functions way is slow and cumbersome.

Alternatively, a means to create a personalized format representation with a
module function would be also be a way to enhance the personalized format
feature.

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

[Libreoffice-bugs] [Bug 138147] [EMF] Shapes/Annotations on DOCX files drawn with Microsoft Surface Pen are lighter due to missing SETPOLYFILLMODE implementation

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138147

Bartosz  changed:

   What|Removed |Added

 Attachment #167218|0   |1
is obsolete||
 Attachment #167219|0   |1
is obsolete||
 Attachment #167220|0   |1
is obsolete||
 Attachment #167221|0   |1
is obsolete||

--- Comment #11 from Bartosz  ---
Created attachment 179102
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179102=edit
Minimal EMF image where issue is visible (needs to be zoomed in)

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

[Libreoffice-bugs] [Bug 147668] Writer crashes shortly after loading document with LanguageTool extension active

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147668

Stephan Bergmann  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 142021] [EMF] SetPolyfilMode Mode = 2 ("winding") is ignored

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142021

Bartosz  changed:

   What|Removed |Added

 Blocks||138147


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=138147
[Bug 138147] [EMF] Shapes/Annotations on DOCX files drawn with Microsoft
Surface Pen are lighter due to missing SETPOLYFILLMODE implementation
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103859] [META] EMF/WMF (Enhanced/Windows Metafile) bugs and enhancements

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103859

Bartosz  changed:

   What|Removed |Added

 Depends on||138147


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=138147
[Bug 138147] [EMF] Shapes/Annotations on DOCX files drawn with Microsoft
Surface Pen are lighter due to missing SETPOLYFILLMODE implementation
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 138147] [EMF] Shapes/Annotations on DOCX files drawn with Microsoft Surface Pen are lighter due to missing SETPOLYFILLMODE implementation

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138147

Bartosz  changed:

   What|Removed |Added

 Depends on||142021, 84199


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=84199
[Bug 84199] [EMF] FILEOPEN Wrong Bezier curve display
https://bugs.documentfoundation.org/show_bug.cgi?id=142021
[Bug 142021] [EMF] SetPolyfilMode Mode = 2 ("winding") is ignored
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 138147] [EMF] Shapes/Annotations on DOCX files drawn with Microsoft Surface Pen are lighter due to missing SETPOLYFILLMODE implementation

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138147

Bartosz  changed:

   What|Removed |Added

Summary|Shapes/Annotations on DOCX  |[EMF] Shapes/Annotations on
   |files drawn with Microsoft  |DOCX files drawn with
   |Surface Pen are lighter in  |Microsoft Surface Pen are
   |color when opening with |lighter due to missing
   |Libre   |SETPOLYFILLMODE
   ||implementation

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

[Libreoffice-bugs] [Bug 138147] [EMF] Shapes/Annotations on DOCX files drawn with Microsoft Surface Pen are lighter due to missing SETPOLYFILLMODE implementation

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138147

Bartosz  changed:

   What|Removed |Added

 Blocks||103859


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103859
[Bug 103859] [META] EMF/WMF (Enhanced/Windows Metafile) bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 96389] Default tab size wrong on pptx import

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96389

--- Comment #8 from Commit Notification 
 ---
Gülşah Köse committed a patch related to this issue.
It has been pushed to "libreoffice-7-3":

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

tdf#96389 Use default tab stop value of MSO for pptx import.

It will be available in 7.3.3.

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 96389] Default tab size wrong on pptx import

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96389

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:7.4.0|target:7.4.0 target:7.3.3

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

[Libreoffice-bugs] [Bug 148183] Dragging widgets in the Dialog Editor should preview the full widget size

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148183

Rafael Lima  changed:

   What|Removed |Added

 Blocks||97233


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 97233] [META] Dialog Designer bugs and enhancements

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=97233

Rafael Lima  changed:

   What|Removed |Added

 Depends on||148183


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148183
[Bug 148183] Dragging widgets in the Dialog Editor should preview the full
widget size
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148183] Dragging widgets in the Dialog Editor should preview the full widget size

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148183

--- Comment #1 from Rafael Lima  ---
Minor typo in the original message:

The preview should have the same size as the widget, so that when the user
drags the widget to some other place, it will be possible to know exactly the
AREA that it will occupy.

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

[Libreoffice-bugs] [Bug 148183] New: Dragging widgets in the Dialog Editor should preview the full widget size

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148183

Bug ID: 148183
   Summary: Dragging widgets in the Dialog Editor should preview
the full widget size
   Product: LibreOffice
   Version: 7.3.1.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: BASIC
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rafael.palma.l...@gmail.com

Created attachment 179101
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179101=edit
Video showing the bug

Suppose you add a widget to a Basic dialog using the Dialog Editor (in the
Basic IDE). If you drag this widget to another place in the dialog, a preview
of the widget is drawn, however with a much smaller size. See the attached
video for a better explanation.

The preview should have the same size as the widget, so that when the user
drags the widget to some other place, it will be possible to know exactly the
are that it will occupy. This issue has been a big problem for me while
designing Basic dialogs.

This bug seems to be around for a long time, at least since 6.4, but I cannot
tell if it is inherited from OO.

System info:
Version: 7.3.1.3 / LibreOffice Community
Build ID: 30(Build:3)
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.1~rc3-0ubuntu0.21.10.1~lo2
Calc: threaded

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

[Libreoffice-bugs] [Bug 120052] Pen annotations are not shown in documents created with Microsoft Word

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120052

Timur  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 138147] Shapes/Annotations on DOCX files drawn with Microsoft Surface Pen are lighter in color when opening with Libre

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138147

Timur  changed:

   What|Removed |Added

 CC||gan...@poczta.onet.pl
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||0052
   Keywords|bibisectRequest |

--- Comment #10 from Timur  ---
Annotations appear from LO 7.0 source
sha:1c399bb1dc9af8d591258e936508200d38d3bb5a
Bartosz, you fixed this, please see if you can why these are lighter than in
MSO.

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

[Libreoffice-bugs] [Bug 97233] [META] Dialog Designer bugs and enhancements

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=97233

Rafael Lima  changed:

   What|Removed |Added

 Depends on||147097


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=147097
[Bug 147097] Text boxes in Basic dialogs are being rendered without borders
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 147097] Text boxes in Basic dialogs are being rendered without borders

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147097

Rafael Lima  changed:

   What|Removed |Added

 Blocks||97233


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 143193] Clean up Basic 'Format' implementation

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143193

Paris Oplopoios  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 148182] New: Page number and page count mess up in exported SVG

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148182

Bug ID: 148182
   Summary: Page number and page count mess up in exported SVG
   Product: LibreOffice
   Version: 7.2.5.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: andygp...@gmail.com

Description:
The page number and page count fields really screw up export to SVG of a
LibreOffice Draw page, especially the page count field. 

Steps to Reproduce:
Create a new LibreOffice Draw document. Do not insert any elements or text
fields. Instead, directly insert a page count field (menu: Insert > Field >
Page Count). Click somewhere in the page to deselect the inserted item, and
insert a page number field (menu: Insert > Page Number). Add a page (menu: Page
> New Page). Insert a text box, and in the text box type: "Some words, page ",
then insert the page number (menu: Insert > Page Number), then type " of total
" and insert the page count (menu: Insert > Field > Page Count). Make sure the
text box is wide enough that everything fits on one line. Add a third page. On
this page, create two text boxes. In the first, type "Page " and then insert
the page number field. In the second text box, type "Page count " and the
insert the page count field. Export all three pages to SVG. Open them in a text
editor to verify that they're saved as SVG 1.2 (search for '3
It gets worse. In LibreOffice, go to the master page (menu: View > Master Page)
and insert a text box. In it, type "Page ", insert the page number field (it
will show as ), then type " of " and insert the page count field (it
will show as ). Close the master view. The text shows as it should, for
example "Page 2 of 3" on the second page. Now export to SVG. Open the SVG with
a text editor and search for class="BackgroundObjects". The exported text box
looks like this (skipping TextParagraph and TextPosition):
Page 
number
 of 
3

Whereas the page count is exported correctly, the page number is exported as
"number"

Actual Results:
The SVG contains numbers that are meaningless, or not representative of the
element

Expected Results:
(1) The  element that holds the page number field should always be
exported with the attribute class="PageNumber".
(2) In a text box that has a line with multiple fields, each field should be
identified correctly, and they should not be overwritten with the page count.
Certainly, parts of text should not be overwritten by the page count.
(3) The page number field, in master view, should not be exported as
number
but as
0

Why it matters: Correct export will make a document look good in SVG editors,
and will also make it possible to re-import in other drawing editors, such as
Visio. (I'll make Visio import macros available for interested parties).


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
xxx

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

[Libreoffice-bugs] [Bug 148181] New: Libreoffice dosn't work with JAWS

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148181

Bug ID: 148181
   Summary: Libreoffice dosn't work with JAWS
   Product: LibreOffice
   Version: 7.3.0.3 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: bakfitt...@gmail.com

Description:
I have JAWS 2022 screenreader and Libreoffice 7.3.0 on my PC (under Windows 10
system). I can't use Libreoffice with JAWS, because Libreoffice crashes. What
is the probleme?

Steps to Reproduce:
1. Start JAWS
2. Start Libreoffice
3. Start Writer or Calc

Actual Results:
1. Start JAWS
2. Start Libreoffice
3. Start Writer or Calc

Expected Results:
Libreoffice crashed.


Reproducible: Always


User Profile Reset: No



Additional Info:
Microsot Office 20XX

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

[Libreoffice-bugs] [Bug 148170] Calc: setting print range not remember

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148170

--- Comment #1 from Timur  ---
I don't reproduce. Do you reproduce in any file or just some, which file type?
Or you maybe have filtered rows there?

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

[Libreoffice-bugs] [Bug 148180] New: Overline text decoration misses in exported SVG

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148180

Bug ID: 148180
   Summary: Overline text decoration misses in exported SVG
   Product: LibreOffice
   Version: 7.2.5.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: andygp...@gmail.com

Description:
Although LibreOffice correctly exports two of the three text decorations
(underline and strike-through), overlines are missing. There are two places
(that I know of) where text decoration attributes may occur, dependent on
whether a whole paragraph line is decorated, or just part of a paragraph line.

Steps to Reproduce:
On a blank LibreOffice Draw page, insert a text box. In the text box, enter the
following sentences:
First full line, underlined
Second full line, struck through
Third full line, overlined
First partial line, underlined
Second partial line, struck through
Third partial line, overlined
Fully underline, strike through, and overline the first through third
sentences, respectively.
In the second set, underline, strike through, and overline the respective
"partial line" phrases. Manually export to SVG (File > Export… with Save as
type: SVG) to get an SVG 1.2 file. Open the file in (for example) Inkscape to
quickly see that underlining and strike-through are correct, but overlining is
missing.

Actual Results:
Overlines are missing

Expected Results:
Open the SVG file in a text editor, and verify that you exported . Skip the embedded definitions and any Master_Slide, or
search for the element . That element contains the following
section, where details of x, y placement and font may be different:







First full line, underlined




Second full line, struck through




Third full line, overlined




First 
partial line
, underlined




Second 
partial line
, struck through




Third 
partial line
, overlined






The third TextParagraph tspan should read:

The middle tspan in the TextPosition element in the sixth TextParagraph should
read:
partial line

Why it matters: In circuit diagrams of digital systems, inverted signals are
sometimes denoted by overlines. A missing overline makes a circuit or system
diagram faulty and meaningless.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
It seems that both the SVG standard and LibreOffice Draw internally handle
overlines similar to underlining and strike-through. Both systems call them
"text decorations". So it is remarkable that the overlines are missing from
exported SVGs. 

Draw has quite a few options: single line, double line, bold, etc. But SVG has
only one option, so it would be correct to channel any option of overlining
into the same SVG result (same as is done for underlines and strikethrough).

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

[Libreoffice-bugs] [Bug 148166] Chart is empty when using data ranges from another document and the current document is empty

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148166

Timur  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #3 from Timur  ---
I tried in Windows and chart was always empty, regardless if there was some
data or if 2nd file was new or saved. I guess it's new. 
I enabled links after saving and message: "Automatic update of external links
has been disabled".

I noticed that help
https://help.libreoffice.org/latest/he/text/schart/01/wiz_data_range.html
doesn't contain instructions how to use range from other file. So people ask:
https://ask.libreoffice.org/t/how-to-refer-range-of-cells-from-other-libreoffice-excelsheet/21066/8

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

[Libreoffice-bugs] [Bug 148179] New: Dashed boxes, lines and polygons appear solid in exported SVG

2022-03-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148179

Bug ID: 148179
   Summary: Dashed boxes, lines and polygons appear solid in
exported SVG
   Product: LibreOffice
   Version: 7.2.5.2 release
  Hardware: x86-64 (AMD64)
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: andygp...@gmail.com

Description:
Dashed boxes, lines, and polygons appear as solid if their line width is
anything but 0.0pt.

Steps to Reproduce:
On a blank LibreOffice Draw page, draw two dashed boxes, two lines, and two
polygons. Give one set a line width of 0.0 points and the other set any line
width bigger than 0.0 points. Export the page to SVG. Open the SVG page in
Inkscape, or even in a text editor, and see that the set with the non-zero line
widths now has solid lines.

Actual Results:
Solid lines, etc.

Expected Results:
In the exported SVG v1.2 file, dashed lines etc. should be dashed regardless of
their width. 
Why it matters: Currently, SVG files are not a true representation of the
exported drawing.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Currently, if the line width is specified as 0.0pt, the dashed line, polygon,
etc. is exported as a whole bunch of short lines (the dashes). 

If the line width is more, it is exported as a single line, polygon, curve,
rectangle, etc.

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

  1   2   >