Jacqueline Rahemipour wrote:
Hi Oliver, Uwe, *,

Oliver-Rainer Wittmann - Software engineer - Sun Microsystems schrieb:
Uwe Fischer schrieb:

Hi,

Oliver-Rainer Wittmann - Software engineer - Sun Microsystems Inc wrote:

Hi Jacqueline,

Jacqueline Rahemipour schrieb:

Hi Oliver,

Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems schrieb:

Hi Jacqueline,

(...)

Ok, I will discuss it with the iTeam members.
Do you have any idea how the dialog has to be extended in this case? My thoughts are: - There have to be a new list box for the used outline levels in the current document, labeled "Outline". - The user has to decide, if the current document is separated by a chosen style or by a chosen outline level. This could be done by radio buttons in front of the list boxes for the styles and the outline levels. The Save-File-Dialog is used for this function. I have to check, if it can be extended.


may be it is possible to add some information to the contents of the listbox, e.g.:

Paragraph Style: Heading 1
Paragraph Style: Heading 2
Outline Level: Level 1
Outline Level: Level 2

and so on.

This would have the smallest impact on UI while offering the new functionality in an intuitive way.

Uwe


I've also thought about with possibility.
In this case the existing list box should be labeled "Styles/Outline".

I agree, that this is an acceptable solution. I checked up how MSO creates master documents from existing files, but afaik it is totally different to the procedure in OOo.

I
would also propose that the entry "Outline Level: Level 1" is selected by default, if such an outline level exists in the document

Yes, ok.


Ok. Thus, I will adjust the specification accordingly.


Maybe a silly question: Does in this case the selection outline Level 1 include the paragraphs heading 1 (or whatever is assigned to the first list level of the outline numbering)?

Yes, as long as the paragraph style "Heading 1" is assigned to a list level 1 of the outline style (menu Tools - Outline Numbering). Because this will cause, that all paragraphs, which have this paragraph style applied, will have an outline level = 1.


But this question reminds me of one of my general concerns with implementing the new attribute outline level without further steps:

Not many users will really know the difference between a heading (a certain paragraph style) and a paragraph (style) with outline level > 0. That difference is irrelevant as long as the user can achieve with both what he wanted to do. But atm there is a big difference - as you pointed out in your reply to my first mail about this spec.

I think there is a misunderstanding - there isn't a big difference. Probably, I've been somehow not clear enough. A paragraph is a heading, if it belongs to an outline level. After the specification is implemented this can be achieve in three ways - see glossary and chapter 1.5 of the current specification. If you use a paragraph style, which is assigned to a list level of the outline style, to make a paragraph a heading, the paragraph additional is also numbered according the outline style.

In my point of view the possible impact on outline numbering, TOC (e.g. hyperlinks) and pdf-export are the most important ones for users which are working on large documents. But these areas are not touched by this implementation. As long as there is no improvement on this I would prefer not to change too much on UI not to raise false hope.

The new attribute doesn't have any influence on the outline numbering. That's one of the main purpose of these new attribute - to get a heading without using the outline style.

The TOC is influenced by the new attribute, because the TOC will by default contain all headings.

What is the impact on the PDF-export, which you are thinking about?


Regards, Oliver.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  • [sw-disc... Jacqueline Rahemipour
    • Re:... Oliver-Rainer Wittmann - Software engineer - Microsystems Inc
      • ... Jacqueline Rahemipour
        • ... Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems
          • ... Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems
            • ... Jacqueline Rahemipour
              • ... Oliver-Rainer Wittmann - Software engineer - Sun Microsystems Inc
                • ... Oliver-Rainer Wittmann - Software engineer - Sun Microsystems
                • ... Jacqueline Rahemipour
                • ... Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems
                • ... Jacqueline Rahemipour
                • ... Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems
    • Re:... Mathias Bauer
      • ... Jacqueline Rahemipour
        • ... Mathias Bauer

Reply via email to