Issue 55923 - Alignment of numbers not saved in reports
Summary: Alignment of numbers not saved in reports
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0
Hardware: All All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
Depends on:
Reported: 2005-10-13 15:08 UTC by xxtobi
Modified: 2013-08-07 15:45 UTC (History)
4 users (show)

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

The final report, with number-field aligned bottom-right (67.78 KB, image/jpeg)
2005-10-13 15:29 UTC, xxtobi
no flags Details
The design view of the report - number field aligned top-left (41.83 KB, image/jpeg)
2005-10-13 15:30 UTC, xxtobi
no flags Details
Test .odb-file with an report demonstrating the problem. (11.71 KB, application/vnd.sun.xml.base)
2005-12-02 21:41 UTC, xxtobi
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description xxtobi 2005-10-13 15:08:05 UTC
I encountered a problem in the Base module of the OOo2.0RC2 (WinXP) release but
am quite sure it also affects other OS's:
1. I create a report using report wizard, some of the data fields contain
numbers (e.g. integer or date/time fields)
2. The corresponding table cells in the report are automatically aligned
3. I change their alignment to top-left in the design-mode of the report,
everything looks o.k. now
4. I create the report and all number fields are aligned *bottom-right* again!
=> My report looks horrible and I am a bit pissed now...;-)

I am attaching two screenshot, one is the "should be" (design mode), the other
one the "way it is" in the resulting report.
Comment 1 xxtobi 2005-10-13 15:29:15 UTC
Created attachment 30402 [details]
The final report, with number-field aligned bottom-right
Comment 2 xxtobi 2005-10-13 15:30:02 UTC
Created attachment 30403 [details]
The design view of the report - number field aligned top-left
Comment 3 roweezy 2005-10-23 15:20:18 UTC
Win XP Pro SP2
OOo 2.0.0 final
Comment 4 roweezy 2005-10-26 13:51:47 UTC
Reassigned to component owner
Comment 5 lars 2005-12-02 16:30:57 UTC
could you also attach the document in which this defect occurs?
Comment 6 xxtobi 2005-12-02 21:40:33 UTC
Hi Lars! As the original document contains confidential data, I have prepared a 
new one for you (this time on OOo2.0 final on Suse10.0). I am sure you can 
reproduce it, too, if you follow the steps in my original description. 
As for the attachment, please check out the report "Zahlungen" that contains 
two number fields showing the issue. 
Comment 7 xxtobi 2005-12-02 21:41:43 UTC
Created attachment 31992 [details]
Test .odb-file with an report demonstrating the problem.
Comment 8 lars 2005-12-03 11:06:48 UTC
this issue is still present in OOo 2.0.1 RC1

explaining step 3 a little more detailed: (use the attached db) in the last 
step of the report generation choose "modify report layout". Increase the 
hight of the second row to make the alignment attributes more visible. Align 
the data in A2 top left. Save. Close and Open the report: the data is aligned 
bottom right.
Comment 9 marc.neumann 2005-12-05 08:37:27 UTC

I can reproduce this, reassign it to the right developer and set target.

Bye Marc
Comment 10 berend.cornelius 2005-12-16 15:23:03 UTC

*** This issue has been marked as a duplicate of 56325 ***
Comment 11 berend.cornelius 2006-05-19 18:28:31 UTC
bc: Still could reproduce the issue
Comment 12 berend.cornelius 2006-05-19 18:30:14 UTC
Comment 13 berend.cornelius 2006-06-27 14:28:46 UTC
bc: I discussed the issue with fme: It looks like the Numberformatter always
changes the alignment of a style as soon as it recognizes it as a number, when
Number recognition is enabled. After consulting cj we came to the conclusion,
that this behaviour should be changed following this direction: When the
alignment attribute of a style is set by the user (PropertyState = the Numberformatter must not
change this attribute. Only if it inherits the attribute value (PropertyState = or if the attribute value is
ambigous ((PropertyState = it may
change the value of the alignment.
bc->fme: As discussed I send the bug to you to implement this change. After that
you have to send the issue to va so that he can reset the alignment attributes
in all user defined paragraph styles of the document templates,,,,, in the share
directory /template/lang/wizard/report
Comment 14 berend.cornelius 2006-06-27 14:30:38 UTC
bc: Adding cj as cc
Comment 15 berend.cornelius 2006-06-27 14:31:21 UTC
Adding va as cc
Comment 16 berend.cornelius 2006-06-27 14:37:01 UTC
*** Issue 56325 has been marked as a duplicate of this issue. ***
Comment 17 frank.meies 2006-07-04 15:33:11 UTC
Comment 18 frank.meies 2008-01-10 11:31:33 UTC
Cannot be fixed until code freeze. Adjust target to 3.x.