Bug 125127 - FILEOPEN: Support "Wrap Text" Option in Word Text Box
Summary: FILEOPEN: Support "Wrap Text" Option in Word Text Box
Status: RESOLVED DUPLICATE of bug 100693
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks:
 
Reported: 2019-05-05 20:54 UTC by Luke
Modified: 2019-05-06 06:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example DOCX text boxes with wrap disabled (16.27 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-05-05 20:54 UTC, Luke
Details
Impress correctly handles Wrap option in Text Box (31.65 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2019-05-05 20:55 UTC, Luke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luke 2019-05-05 20:54:19 UTC
Created attachment 151190 [details]
Example DOCX text boxes with wrap disabled

In MS Office, Text Boxes expand horizontally (or vertically with vertical text) when "Wrap Text" Option is not checked to fit the text on a single line. The docx importer does not handling the "Wrap Text" option correctly.  

Steps to reproduce:
1. Open TexboxWrap.docx in Writer
2. Open in Word
3. Compare

The first 2 text boxes should be a single line, as there is no wrapping allowed. The 3rd shows how the resize option will automatically expand the shape vertically. 

If you roundtrip the file, the "Wrap Text" Option changed to true.
Comment 1 Luke 2019-05-05 20:55:19 UTC
Created attachment 151191 [details]
Impress correctly handles Wrap option in Text Box

Issue is Writer specific
Comment 2 V Stuart Foote 2019-05-06 03:43:33 UTC
see cmnt 13 of duplicate, Word wrap and frame size is correct for text in Draw shapes. But frames for Draw Text boxes have issues with wrapping, affecting filter import from OOXML.

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