Issue 8855 - Cells in table does no "remember" their vertical alligment
Summary: Cells in table does no "remember" their vertical alligment
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC All
: P3 Trivial with 22 votes (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
Keywords: oooqa
: 28902 31588 65504 (view as issue list)
Depends on:
Reported: 2002-10-30 19:54 UTC by ezh
Modified: 2013-08-07 14:43 UTC (History)
6 users (show)

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

The file (I have many of them) (13.93 KB, text/plain)
2002-10-31 10:04 UTC, ezh
no flags Details
the file, sorry, I just now saw the request... (14.41 KB, application/octet-stream)
2003-02-23 10:49 UTC, ezh
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ezh 2002-10-30 19:54:26 UTC
1. Open the attached file.
2. At first the document opens at the end of it (but that's another bug)
3. Uf you do not click on the doc all is fine.
4. Clink in the main table with prices.
5. The digits in some cell will allign at bottom now.
6. Change it so it's alligned to the top.
7. Save the document and reopen it.
8. Same thing happengs.

OOo 1.0.1, also 643 is affected. Tested on Win 95, win 2000 and win XP.
Comment 1 prgmgr 2002-10-31 00:54:01 UTC
Eugene, thank you for using and supporting OOo.

Please attach the file which reproduces this problem via the "Create 
a new attachment" link.
Comment 2 ezh 2002-10-31 10:04:19 UTC
Created attachment 3439 [details]
The file (I have many of them)
Comment 3 ezh 2002-10-31 10:05:13 UTC
Attached as text file.
Comment 4 prgmgr 2002-11-11 19:23:29 UTC
Eugene, you need to use the "Binary file (application/octet-stream)" 
option as the file type for OOo files.

Could you please reattach the file at your convenience? 
Comment 5 ezh 2003-02-23 10:49:39 UTC
Created attachment 4858 [details]
the file, sorry, I just now saw the request...
Comment 6 ezh 2003-02-24 21:33:37 UTC
I'd very apriciate if this is fixed untill 1.1 (SO6.1) final. Tnx.
Comment 7 ezh 2003-03-28 14:12:38 UTC
Same bug in 644m7 and SO6.1 beta. 

Is someone actually knows about this bug?
Comment 8 alex.thurgood 2003-03-28 15:00:56 UTC
It only seems to occur in cells that display a result from a formula,
so it must be linked to the default style for formula results.

There's a workaround for your problem : if you type in a soft line
break at the end of your figure, using the the Shift-Enter key
combination, you will get the result you want and it will stick when
you save.

Comment 9 ezh 2003-03-28 15:09:48 UTC
I tryed this workaround, but it is not a 100% workaround, since the
second row may be a one liner, then I need to delete the added brakes.
Comment 10 mci 2003-08-19 14:39:03 UTC
I opened the document in OOo1.1rc3 and all looked fine ...

Then I clicked "Print File  Directly" and some cells realligned to 

I set the whole table to "top alligned" and saved the file...
I reopened the file and clicked anywhere in the table and the
realligning began again...

reassigned to
Comment 11 frank.meies 2003-08-21 08:27:16 UTC
FME->DVO: Is the cell alignment attribute saved properly?
Comment 12 openoffice 2003-09-18 13:57:03 UTC
dvo: The current behaviour is, admittedly, rather silly. There appear
to be at least two things going wrong. One was previously reported in
the internal bug #107116#, and an additional aspect was reported here.
I'll mark the internal issue as duplicate to this one, so all
information is kept in a single, public location.

Bug description from #107116#:

--------- #107116# ----------------------------------------
In table cells, the default vertical alignment is 'top' for text, and
'bottom' for numbers. This is implemented as follows:

There are four internal alignent values (none, top, center, bottom),
where 'top' is the default. In the context menu, you can select three
values, top, center, bottom , which set 'none', 'center' and 'bottom',
respectively. If a cell value is cahnged from text to number or from
number to text, the vertical alignment is changed from top to bottom,
and from bottom to top.
(The implementation of this is at the bottom of ChgTextToNum and
ChgNumToText in swtable.cxx.)

1) If you enter text/numbers and change between those at will, text
will be at the top, and numbers wil be at the bottom.
(Reason: The top/bottom fiddling mentioned above.)
2) If you select vertical alignment center or top in the menu, the
content will always remain in the center and top.
(Reason: 'center' and 'none' are never changed, and top in the menu
sets the value 'none'.)
3) If you select 'bottom', the value will be bottom aligned. But if
you change it from number to text, it will jump to the top.
(Reason: The top/bottom fiddling.)

It would be much more logical to use 'none' as a default value, which
will be at whatever position is suitable for the text type, and then
never change top/bottom/center values.

This is a successor bug to #106568#.
--------- #107116# ----------------------------------------

Additionally, there is some problem with loading and saving. 'top'
(internally 'none') is apparently saved as default, but loading uses
'top' (internally 'top') as default. This is why Eugene sees the
problem again after a save/load cycle.
Comment 13 Unknown 2003-09-28 23:33:16 UTC
When importing an Excel file, I see all cells top aligned even if they
are configured to be "standard"-aligned.

Trying to align them to the center vertically does not give the same
"center" as with a new file: it is much lower.

Please tell me if this (or part) should be reported in another bug!
Comment 14 michael.ruess 2004-05-04 08:55:19 UTC
Due to time limitations, this has been retargeted to "OO later".
Comment 15 lohmaier 2004-05-07 20:40:09 UTC
*** Issue 28902 has been marked as a duplicate of this issue. ***
Comment 16 michael.ruess 2004-07-21 11:30:03 UTC
*** Issue 31588 has been marked as a duplicate of this issue. ***
Comment 17 stp 2006-05-07 07:02:11 UTC
Is this issue still valid with 2.0.2?
Comment 18 ezh 2006-05-08 06:55:53 UTC
Yes, it is.
Comment 19 michael.ruess 2006-05-17 17:34:35 UTC
*** Issue 65504 has been marked as a duplicate of this issue. ***
Comment 20 canis 2006-08-10 15:02:11 UTC
I have the same problem with tables!
Comment 21 kpalagin 2007-06-13 19:25:53 UTC
Dear developers,
what is the current status of this issue?

Thanks a lot for your attention.
Kirill Palagin.
Comment 22 canis 2007-07-13 14:16:58 UTC
Dear developers,
is it so difficult to solve this problem?
Vertical alignment is basic function for any text editor, which can work with
tables, and it is surprisingly that Writer can't do it without errors.
Thank you!
Comment 23 dudson 2007-08-10 11:32:08 UTC
Have the same problem on Windows Vista machine.
Still in OpenOffice 2.2.1
Comment 24 canis 2007-09-04 16:59:24 UTC
Dear developers!
Can You target this annoying issue to the nearest release?
It realy delivers greater inconveniences during work.
Thank You!
Comment 25 Frank Schönheit 2007-09-11 20:58:51 UTC
re-setting owner - DVO is not working on Writer anymore.
re-setting target for re-consideration (there's a relatively high number of
votes I think).
Comment 26 michael.ruess 2007-09-12 10:14:40 UTC
MRU->OS: it does not matter wether the document is saved in sxw or odt format.
When clicking into table 5, some of the cell's vertical alignment will chage
from "top" to "center".
I will target this to OO 3.0 at first, 'cause the issue has many votes and I
think that the behavior is very annoying for the user.
Comment 27 michael.ruess 2007-09-12 10:15:36 UTC
Making summary a bit more significant.
Comment 28 dudson 2007-09-18 17:15:11 UTC
Tables are being made a lot.
Still not fixed in OOo 2.3
Comment 29 kpalagin 2007-09-18 20:56:53 UTC
version 3.0 is approx 1.5 years away. In addition to that targets are very 
flexible. So can we consider 2.4 as target for this issue?

Thanks a lot for your attention!
Comment 30 canis 2007-09-21 12:40:35 UTC
I agree: version 3.0 is very long-run prospect for such absurd bug in one of the
basic functions of text editor.
Comment 31 canis 2007-12-01 16:15:56 UTC
Dear sirs.
Please, bring forward this issue to ver. 2.4.
Our department can't completely prefer OOo to MSO only because of this issue:
now using OOo we have to waste a lot of time to look through large documents
before printing.
Comment 32 cno 2007-12-01 19:49:50 UTC
Comments from (dvo Sep 18 2003) hold relative simple suggestion, I think
Comment 33 canis 2007-12-02 05:42:23 UTC
Simple suggestion, but not a solution.
Just imagine, what price a examination of document with 30-50 large tables!
DVO didn't have enough time I think, and tried to present this bug as Writer;s
Comment 34 cno 2007-12-02 20:36:53 UTC
Cor-> canis: I meant a relative solution for development. Not for the users.
Sorry for not being clear in this aspect.
Comment 35 cno 2007-12-02 20:37:23 UTC
Cor-> canis: I meant a relative simple suggestion for development. Not for the
Sorry for not being clear in this aspect.
Comment 36 canis 2007-12-03 12:45:11 UTC
canis-> cornouws: Sorry, I didn't understand.

Unfortunatelly this "simple suggestion" can take over 1.5 years.
Comment 37 cno 2007-12-03 13:13:35 UTC
Hi canis, That's indeed inforunate.
If my impression is right, it might be doable for development to pick this one
up rather easily. But that's not in my competence to judge or decide ...

(If it might help you, I can provide a simple macro setting the allignment of
all cells in tables in a document. But if there are complex tables and
differences between various tables and rows, the macro becomes less simple ;-) 
- you can contact me by mail if you so wish.)
Comment 38 canis 2007-12-03 16:46:09 UTC
cornouws, thanks, but such macros won't solve this problem.
Developers are only "sheet anchors" in this situation.
Comment 39 kpalagin 2008-02-27 16:51:50 UTC
are we on track for 3.0 with this issue?
Comment 40 Oliver Specht 2008-02-29 12:20:21 UTC
Fixed in cws os112 in
Comment 41 kpalagin 2008-03-02 15:41:23 UTC
Thanks a ton!
Comment 42 Oliver Specht 2008-04-11 12:11:38 UTC
Reassigned for verification
Comment 43 stefan.baltzer 2008-04-24 16:01:41 UTC
Verified in CWS os112.
Comment 44 michael.ruess 2008-05-08 10:39:19 UTC
Checked fix in DEV300m12.