Bug 130664 - Bulleted entries with special bullets aren't exported properly to SVG
Summary: Bulleted entries with special bullets aren't exported properly to SVG
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:svg
Depends on:
Blocks: SVG-Save
  Show dependency treegraph
Reported: 2020-02-14 15:12 UTC by Roman Kuznetsov
Modified: 2022-02-28 03:26 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Presentation (455.07 KB, application/vnd.oasis.opendocument.presentation)
2020-02-14 15:12 UTC, Roman Kuznetsov
Screenshot with a problem (94.94 KB, image/jpeg)
2020-02-14 15:12 UTC, Roman Kuznetsov

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Kuznetsov 2020-02-14 15:12:01 UTC
Android (Collabora Office): Wrong layout of bullet list in slide show mode, but in Normal mode it looks good, as in desktop version

Steps to Reproduce:
1. Open a presentation from attach
2. Start a slide show
3. Look at slide 7 => bullet list looks badly (see screenshot in attach)

Actual Results:
bullet list looks badly in slideshow mode

Expected Results:
bullet list looks the same as in Normal mode

Reproducible: Always

User Profile Reset: No

Additional Info:
Comment 1 Roman Kuznetsov 2020-02-14 15:12:27 UTC
Created attachment 157866 [details]
Comment 2 Roman Kuznetsov 2020-02-14 15:12:51 UTC
Created attachment 157867 [details]
Screenshot with a problem
Comment 3 Aron Budea 2020-02-28 03:06:14 UTC
This is an SVG export issue, slideshows are exported SVGs.

In Impress switch to slide 7, choose File -> Export, choose SVG format, then open result SVG.

=> Bullet list entries with special bullets aren't shown correctly.

The SVG is displayed slightly differently than in the screenshot, so an Android-specific aspect can't be ruled out, but first the exported SVG needs to be correct.

Observed using LO (f32a59a52e3ee2a0a8df9bb76bc1ff0ada7c7f1d) / Ubuntu.
Comment 4 QA Administrators 2022-02-28 03:26:04 UTC
Dear Roman Kuznetsov,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team