OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [office] User-defined character and paragraph styles

On Wed, Apr 2, 2008 at 7:09 AM, David Faure <faure@kde.org> wrote:
> Hello,
>  We can't seem to find a way to refer to a user-defined character style (family=text)
>  from a user-defined paragraph style (family=paragraph)...
>  I am surprised, because I thought this was an obvious use case for user-defined character styles;
>  you would define "arial 20 bold" as character style "big" and then use it in the paragraph style
>  "big heading".
>  Is there a reason for not allowing this? (I am asking from a user-experience point of view
>  as well as from a file-format point of view)
>  If not, what about adding a style:text-style-name attribute to style:style with family=paragraph?
>  I guess it would mean replacing the current style-style-content for family=paragraph with something like this (untested) :
>  <define name="style-style-content" combine="choice">
>     <group>
>         <attribute name="style:family">
>             <value>paragraph</value>
>         </attribute>
>         <optional>
>             <ref name="style-paragraph-properties"/>
>         </optional>
>         <optional>
>             <attribute name="style:text-style-name">
>                 <ref name="styleNameRef"/>
>             </attribute>
>         </optional>
>         <optional>
>             <ref name="style-text-properties"/>
>         </optional>
>     </group>
>  </define>
>  I was wondering about forcing to either refer to a named character style or define text properties in the paragraph style,
>  but I guess that being able to do both at the same time could be useful too.

For ODF 2.0+, it might make sense to only allow character properties
in a paragraph style by referring to a named character style. For 1.x,
where x>=2, we should allow both for backward compatibility, though.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]