Issue 54577 - Fontwork alignment
Summary: Fontwork alignment
Status: ACCEPTED
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 3.0 Beta
Hardware: PC Windows XP
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
: 56296 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-09-14 00:21 UTC by jonessco
Modified: 2013-08-07 14:44 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Example document (31.07 KB, application/vnd.oasis.opendocument.text)
2005-10-14 19:55 UTC, jonessco
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description jonessco 2005-09-14 00:21:38 UTC
When I create a fontwork object and choose stretch to justify. Then save the
document. Then reopen, the formating of stretch to justify is forgotten, and it
goes to left justify.

Any Ideas?
Comment 1 jonessco 2005-10-13 19:22:06 UTC
This issue is very similer to issue 55330.  I would like to bump this to a P2. 
Maybe the fix for i55330 will fix this?
Comment 2 michael.ruess 2005-10-14 09:02:55 UTC
MRU->OD: when having a fontwork object with Alignment "stretch to justify" (in
the Fontwork-Toolbar) this will not be displayed in the toolbar after save and
reload.
I wasn't able to see any visible impact on the object, so 'i do not think it is
worth P2.
Comment 3 jonessco 2005-10-14 19:55:02 UTC
Created attachment 30453 [details]
Example document
Comment 4 jonessco 2005-10-14 20:00:57 UTC
Let me clarify, See attached doc.  If I click on the words in the oval then
click on the stretch justify on the fontwork toolbar the object looks as i want.
 I then save it and it saves.  Then i close the document and reopen it and the
stretch justify change i made is un-done.  The word on the first line that was
stretch justified now goes back to left.
Comment 5 michael.ruess 2005-10-20 13:45:53 UTC
*** Issue 56296 has been marked as a duplicate of this issue. ***
Comment 6 jonessco 2007-02-13 19:46:18 UTC
When is this slated to be fixed, other than "OOo Later"?
Comment 7 Oliver-Rainer Wittmann 2007-02-14 07:22:45 UTC
OD->SJ: Seems to be a fontwork issue - please take over.
Comment 8 jonessco 2007-02-15 22:17:25 UTC
What do you mean take over?  I don't know how to fix this.  It seems like a
coder issue not user issue.
Comment 9 Oliver-Rainer Wittmann 2007-02-16 07:21:40 UTC
OD->jonessco:
I didn't assign this issue to you. I assigned it to my colleague SJ.
Thus, again reassigning to SJ.

OD->SJ: Seems to be a fontwork issue - please take over.
Comment 10 jonessco 2007-02-18 15:59:01 UTC
Thank you. Sorry.
Comment 11 jonessco 2007-12-04 12:09:15 UTC
Is there any time frame on fixing this issue?
Comment 12 jonessco 2008-05-14 22:21:24 UTC
This still isn't fixed in v3.0 Beta.
Comment 13 sven.jacobi 2008-06-02 15:40:32 UTC
Sorry, I do not have enough time to fix this for OOo.3.0 _> changed target
Comment 14 jonessco 2008-12-22 17:13:29 UTC
Any new time frame on this issue now that 3.0 is released?
Comment 15 jonessco 2010-12-04 14:33:07 UTC
OK.  Is this ever going to get fixed! 3.3 is coming.  This has been around since
2005!
Comment 16 Regina Henschel 2010-12-04 17:43:31 UTC
Stretching works as expected, if the fontwork object has only one line. So there
is an easy workaround, put each line into a separate fontwork object. Setting
back to P3.
Comment 17 jonessco 2010-12-04 19:45:18 UTC
OK.  Now I see when a bug sits out there for the past 5 years it looses 
attention.  The Stretch works, it just doesn't get saved when a doc is saved.  
If it is in the software why wouldn't it just work and take 5 years and still 
not be fixed.  A workaround would be something that wouyld be offered when this 
was first posted.  Plus having multiple fontwork objects to maintain is more 
work when OO has a function for it.  So that said, 5 years later is there an 
ETA on fixing this?
Comment 18 sven.jacobi 2010-12-08 15:14:25 UTC
Sorry, I have to adjust this issue with respect to my other 700 Issues I own. I
think there is no chance before 2011, but I try to get it solved for OOo 3.4.
Comment 19 jonessco 2011-02-28 17:21:51 UTC
Well, just an FYI, whatever it is, LibreOffice has already fixed it.  Maybe it's time to switch.