Bug 47997 - FILESAVE PPT Indent of paragraph is wrong
Summary: FILESAVE PPT Indent of paragraph is wrong
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.3.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:ppt
Depends on:
Blocks: PPT
  Show dependency treegraph
 
Reported: 2012-03-28 04:17 UTC by sasha.libreoffice
Modified: 2024-12-16 03:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
test case to demonstrate exporting problem (18.57 KB, application/vnd.oasis.opendocument.presentation)
2012-03-28 04:17 UTC, sasha.libreoffice
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sasha.libreoffice 2012-03-28 04:17:19 UTC
Created attachment 59153 [details]
test case to demonstrate exporting problem

To reproduce this problem:
0. Open attached file
1. Place cursor after § 43 and do Format->Paragraph, see Indent "Before text" and "First line". Both are 0.
2. Save as ppt file
3. Format->Reload
4. repeat step 1 : this time 1,2 cm and -0,9 cm

I have changed color of characters beneath of paragraph mark (§) to demonstrate where it should be
Reproduced in 3.3.4 and 3.5.1 on Fedora 64 bit

In produced ppt file msWord 2007 indicates also Indent "Before text" and "First line"  1,2 cm and -0,9 cm (exporting to ppt problem)
Comment 1 bfoman (inactive) 2012-07-03 05:01:36 UTC
Confirmed with:
LO 3.5.4.2 
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit
Comment 2 A (Andy) 2013-04-26 20:46:55 UTC
reproducible with LO 4.0.2.2 (Win7 Home, 64bit)

in addition, the font type is changed
Comment 3 QA Administrators 2015-03-04 02:22:20 UTC Comment hidden (obsolete)
Comment 4 Buovjaga 2015-03-24 13:30:25 UTC
Still reproduced.

Win 7 Pro 64-bit, LibO Version: 4.4.1.2
Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Locale: fi_FI
Comment 5 tommy27 2016-04-16 07:25:23 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2017-05-22 13:26:56 UTC Comment hidden (obsolete)
Comment 7 Thomas Lendo 2018-10-17 20:28:46 UTC
Still reproducible.

Version: 6.2.0.0.alpha0+
Build ID: d92319d2ffeaa65e31f923e0e9c7328b8d7c97bf
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: de-DE (de_DE.UTF-8); Calc: threaded
Comment 8 Buovjaga 2019-08-23 11:35:05 UTC
Still repro.

Version: 6.4.0.0.alpha0+ (x64)
Build ID: 3e64065612acec2eb29aa21e2b515953422256d7
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-08-15_22:57:26
Locale: fi-FI (fi_FI); UI-Language: en-US
Calc: threaded
Comment 9 QA Administrators 2021-08-23 03:51:52 UTC Comment hidden (obsolete)
Comment 10 Stéphane Guillou (stragu) 2022-12-16 19:29:05 UTC
Repro in:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 4e4a31ac7d920c71e26ca4acd18c11ec2bd015bb
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
Comment 11 QA Administrators 2024-12-16 03:17:22 UTC
Dear sasha.libreoffice,

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

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

If you have time, please do the following:

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug