Issue 14121 - Chapter number incorrectly appears in a Word doc
Summary: Chapter number incorrectly appears in a Word doc
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.3
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 116034 (view as issue list)
Depends on:
Reported: 2003-05-05 12:55 UTC by Unknown
Modified: 2013-08-07 14:38 UTC (History)
2 users (show)

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

Doc showing the problem (57.50 KB, application/octet-stream)
2003-05-05 12:56 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-05-05 12:55:08 UTC
The attached doc has a chapter number ("1") show up in the first sentence 
("1TWO LETTER...") while this number does not show up when the doc is opened 
in Word 2000 ("TWO LETTER..."
Comment 1 Unknown 2003-05-05 12:56:40 UTC
Created attachment 6034 [details]
Doc showing the problem
Comment 2 mci 2003-10-08 09:49:33 UTC
reassigned to mru
Comment 3 michael.ruess 2003-10-09 10:58:06 UTC
Not a problem of the importer. The field is a Number range field (SEQ
in word) and such field do not have the posssibility to be hidden
(which is done by the field switch \h in Word) like Writers variables.
Comment 4 Oliver Specht 2003-10-09 11:20:11 UTC
Implementing a "Hidden" property should be possible for OOo 2.0 ->
target changed.
Comment 5 Oliver Specht 2003-10-10 07:25:34 UTC
Comment 6 Oliver Specht 2003-12-19 14:47:12 UTC
os->cj: The field already has an "IsVisble" property but that is not yet stored
in our file format and there's no control in the dialog to change it. 
How about decreasing the height of the Format ListBox and adding a CheckBox
"Invisible" below the "Numbering by Chapter" controls?
Comment 7 christian.jansen 2004-08-17 13:16:21 UTC
CJ: set to Office later
Comment 8 michael.ruess 2010-12-10 13:32:33 UTC
*** Issue 116034 has been marked as a duplicate of this issue. ***