Issue 54397 - Changing numbers in tables drops number format
Summary: Changing numbers in tables drops number format
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: 680m124
Hardware: All All
: P3 Trivial with 13 votes (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
: 57434 58897 73823 75150 87908 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-09-09 12:58 UTC by bjoern.milcke
Modified: 2013-08-07 14:43 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description bjoern.milcke 2005-09-09 12:58:24 UTC 
1. create a table in writer
2. enter some numbers
3. format the cells with number format "Number"
4. Change a number in a cell to another number
=> The number format switches back to Text (which is visible by changing the
alignment from right to left)

->TL: If you are not the responsible developer for this, please forward accordingly.
Comment 1 thomas.lange 2005-09-12 13:06:16 UTC 
.
Comment 2 thomas.lange 2005-09-26 12:18:43 UTC 
The code were this effect happens is

#			if( !bSetNumFmt && !bIsEmptyTxtNd && pNumFmtItem )
#			{
#				// JP 15.01.99: Nur Attribute zuruecksetzen reicht nicht.
#				//        Sorge dafuer, das der Text auch #entsprechend
#				//	  formatiert wird!
#				pBoxFmt->SetAttr( *GetDfltAttr( RES_BOXATR_FORMAT ));
#			}

in ndtbl.cxx.

It is currently not yet clear why this code was added...

TL->OS: please have a look. Thanks!
Comment 3 michael.ruess 2005-09-30 13:51:24 UTC 
MRU->OS: looks like TL wanted to assign this to you...
Comment 4 michael.ruess 2005-11-06 19:01:13 UTC 
*** Issue 57434 has been marked as a duplicate of this issue. ***
Comment 5 Oliver Specht 2006-06-20 13:49:48 UTC 
Target adjusted
Comment 6 Oliver Specht 2006-06-20 13:57:36 UTC 
*** Issue 58897 has been marked as a duplicate of this issue. ***
Comment 7 michael.ruess 2007-03-06 11:49:06 UTC 
*** Issue 75150 has been marked as a duplicate of this issue. ***
Comment 8 oreg 2007-09-15 01:51:54 UTC 
This bug has a billion duplicates (just search for "table number format"). The
oldest report is from June 2003! Isn't it time that someone fix this?
Comment 9 oreg 2007-11-08 19:58:50 UTC 
Some of the duplicates:
* Issue 15769
* Issue 25874
* Issue 41125
* Issue 46076
* Issue 48913
* Issue 63127
Comment 10 cno 2007-12-01 19:47:17 UTC 
Another candidate for dupl.: issue 73823
With some useful comments (FME)
Comment 11 Mathias_Bauer 2007-12-04 13:30:29 UTC 
target 3.0
Comment 12 michael.ruess 2008-04-10 10:50:58 UTC 
*** Issue 87908 has been marked as a duplicate of this issue. ***
Comment 13 Oliver Specht 2008-04-29 09:51:07 UTC 
The problem is the number recognition setting. 
According to the spec at 
http://specs.openoffice.org/writer/compatibility/tabstop_compatibility.sxw
the default has been set to off. 
The spec states: 
"The automatic Number Recognition in Writer tables (and the automatic alignment
of numbers caused by it) interferes with the handling of decimal tab stops in
Writer tables. Therefore the default for Number Recognition will be changed to
'disabled'."

->fme: I don't understand (anymore) why the recognition has been disabled
instead of disabling the automatic alignment only?
Comment 14 Oliver Specht 2008-04-29 09:51:34 UTC 
*** Issue 73823 has been marked as a duplicate of this issue. ***
Comment 15 Oliver Specht 2008-05-08 12:55:05 UTC 
A discussion with fme brought no reason not to switch on number recognition and
switch off alignment by default. 

Fixed in cws os113 in officecfg/registry/schema/org/openoffice/Office/Writer.xcs
and WriterWeb.xcs
Comment 16 cno 2008-05-08 13:50:06 UTC 
Hi *,
Good solution, IMO. Thanks.
Comment 17 Oliver Specht 2008-05-22 11:41:43 UTC 
Reassigned for verification
Comment 18 michael.ruess 2008-05-26 18:15:37 UTC 
Verified in CWS os113. The default is correctly hanged now. 
However, the bug, that the number format is changed when the number in a cell is
changed while "number recognition" is still active, remains - I added a comment
to issue 73823.
Comment 19 michael.ruess 2008-07-15 10:17:33 UTC 
Closed.
Comment 20 Dotan Cohen 2009-11-30 13:08:14 UTC 
Why is this marked as fixed? I can reproduce in OOo 3.1.1. See bug #106923.