Bug 61387 - FILESAVE: Font size gets lost when saving as pptx file
Summary: FILESAVE: Font size gets lost when saving as pptx file
Status: RESOLVED DUPLICATE of bug 73627
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: Other All
: high major
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-24 09:42 UTC by A (Andy)
Modified: 2014-02-15 14:04 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description A (Andy) 2013-02-24 09:42:11 UTC 
Problem Description: 
If you save an Impress file as a pptx file with LO 4.0.0.3, then the font size of the text gets lost and is not correctly saved.

Steps to Reproduce:
1. Open Impress
2. Type any text in the title and the main text frame (please note that the font size in the title is Arial 44 and in the main text frame is Arial 32)
3. Save it as a pptx file and close it
4. Reopen the pptx file with LibreOffice

Current Behavior:
The font size gots lost.  All the text in the title and main text frame has now the font size Arial 18 and not Arial 44 respectively Arial 32.

Expected Behavior:
The correct font size should be saved.
Operating System: Windows 7
Version: 4.0.0.3 release
Comment 1 Thomas van der Meulen [retired] 2013-02-24 10:37:25 UTC 
Thank you for reporthing this bug,
I can reprofuce this bug running LibreOffice 4.0.1.1 rc on mac osx 10.6.8.
Comment 2 A (Andy) 2013-03-24 20:00:01 UTC 
@Thorsten: Could this issue maybe be something for you?
Comment 3 A (Andy) 2013-12-27 12:15:22 UTC 
still reproducible with LO 4.1.4.2 (Win7 Home, 64bit)
Comment 4 tommy27 2014-02-15 14:04:27 UTC 
this is basically the same issue as Bug 73627.

I mark this one as the duplicate even if it was reported earlier, since the other report has already test cases and more discussion from users

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