Bug 84521 - EDITING: Converting text with spaces to polygon/curve/contour results in duplicated characters
Summary: EDITING: Converting text with spaces to polygon/curve/contour results in dupl...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Drawing (show other bugs)
Version: 4.3.2.2 release
Hardware: Other Mac OS X (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: BSA bibisectRequest
Keywords: regression
Depends on:
Blocks:
 
Reported: 2014-09-30 16:41 UTC by Mikko Ahlroth
Modified: 2014-12-29 07:07 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Two example texts converted to polygon, the lower one having one space added to the end (15.86 KB, image/png)
2014-09-30 16:41 UTC, Mikko Ahlroth 		Details
View All

Description Mikko Ahlroth 2014-09-30 16:41:55 UTC 
Created attachment 107143 [details]
Two example texts converted to polygon, the lower one having one space added to the end

Problem description: 

Steps to reproduce:
1. Open a new drawing
2. Insert a text box with some text but NO spaces (linebreaks are ok it seems)
3. Select text box and choose Convert -> To Polygon, text should be converted to polygon ok
4. Undo and change text content to include spaces (even one will do)
5. Try to convert to polygon again, now duplicated, squished characters are added to the polygon and the result is a mess

Current behavior:
Converted polygon contains duplicate, squished characters

Expected behavior:
Text is converted properly
Operating System: Mac OS X
Version: 4.3.2.2 release
Comment 1 Mikko Ahlroth 2014-09-30 16:43:27 UTC 
Forgot to add in the description (but remembered in the title!) that this also happens when converting text to Curve, Contour and seemingly also 3D.
Comment 2 Alex Thurgood 2014-09-30 17:10:40 UTC 
Confirming on LO 432 and OSX 10.9.5
Comment 3 Alex Thurgood 2014-09-30 17:14:37 UTC 
Also present in master

Version: 4.4.0.0.alpha0+
Build ID: faf99f6f405e076d5c9ab95c876ae1ffb896f8d1
Comment 4 Alex Thurgood 2014-09-30 17:17:02 UTC 
Not present in Version: 4.1.4.2
Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72
regression
Comment 5 Alex Thurgood 2014-09-30 17:22:12 UTC 
Not present in Version: 4.2.4.2
Build ID: 63150712c6d317d27ce2db16eb94c2f3d7b699f8
Comment 6 vilpan 2014-10-01 11:44:23 UTC 
Could not reproduce on Debian "wheezy" 7.6 using LO 4.3.2.2 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d.
Comment 7 Björn Michaelsen 2014-11-28 09:42:17 UTC 
(This is an automated message.)

LibreOffice development currently prioritizes bugs with the so called MAB (most annoying bugs) -- as this bug has not run through that process (including writing a short rationale for this bug being a candidate and other who are watching the tracker bug silently approving that rationale etc.) its priority is set to high. Note this is effectively no change in the urgency assigned to this bug, as we are currently not making a difference between high and highest and severity is untouched.

You can find out more about MABs and how the process works by contacting libreoffice qa on irc:

 http://webchat.freenode.net/?channels=libreoffice-qa

The QA wiki page also gives you hints on how to get in contact with the team (if IRC fails you, your next best choice is the mailing list):

 https://wiki.documentfoundation.org/QA
Comment 8 Joel Madero 2014-12-06 19:18:15 UTC 
This is not a blocker - in 3 years on the project I've seen less than 5 bugs that were legitimate blockers. Reprioriting bug:


Normal - can prevent high quality/professional work.
Medium - default seems appropriate.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.