Issue 7717 - RTF - add '\levellegalN' control word
Summary: RTF - add '\levellegalN' control word
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Windows 98
: P5 (lowest) Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL: http://www.biblioscape.com/rtf15_spec...
Keywords: ms_interoperability
Depends on:
Blocks:
 
Reported: 2002-09-13 16:17 UTC by Unknown
Modified: 2017-05-20 10:12 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-09-13 16:17:31 UTC
'\levellegalN' is a small rtf feature supported by word that:
"1 if any list numbers from previous levels should be converted to arabic 
numbers; 0 if they should be left with the format specified by their own 
level's definition."
This allows the following numbering:
I. bla bla
  1.1 bla bla
  1.2 bla bla
II. bla bla
  2.1 bla bla
III. bla bla

Revolutionary product, guys.  Keep up the great effort.
Comment 1 dankegel 2003-05-02 04:43:05 UTC
Seems like you could rephrase this as a DEFECT.
Can you give examples of real-world docuents that can't be imported
properly because of this issue, and a minimal test case
showing the problem?
Comment 2 stefan.baltzer 2003-06-04 14:16:39 UTC
Reassigned to Bettina.
Comment 3 Rainer Bielefeld 2003-07-24 19:02:38 UTC
Hm, I do not miss any feature concerning numbered lists like in the
example, but might be a document with more explications and examples
and VOTES might teach me to miss ie ;-)

Actually:
No reporter-activity for 10 months
No votes
No other one who sie a problem

I think we should close that issue as "WFM",  if someone still sees
the problem, the issue can be reopened.

If I will not see any further action as votes, attachments or
confirmations in this issue, I will have to close this issue
2003-08-31 as WFM.

Rainer


Comment 4 Rainer Bielefeld 2003-07-24 19:03:50 UTC
I am not sure concerning "ms_interoperability"

Rainer
Comment 5 Rainer Bielefeld 2003-09-16 07:44:50 UTC
I will not close this issue, only leave it in the actual "enhancements
black hole" and remove oooqa and myself from CC.

We must improve our "enhancement request handling", it is frustrating
for engaged OOo users if they must believe that there is no reaction
from OOo to their proposals

Rainer
Comment 6 ace_dent 2008-05-16 02:11:04 UTC
OpenOffice.org Issue Tracker - Feedback Request.

The Issue you raised is currently 'Unconfirmed' pending review, but has not been
updated within the last 3 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version: http://download.openoffice.org/index.html
or consider trying the new OOo 3 BETA (still in testing):
http://download.openoffice.org/3.0beta/
 
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
http://www.openoffice.org/issues/query.cgi
 
Many thanks,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 7 bettina.haberer 2010-05-21 14:44:29 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements". 
Comment 8 Edwin Sharp 2014-03-14 08:27:22 UTC
No info from author.