[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Stage 1 proposal: outputclass for DITAVAL properties
Would this replace all the style attributes currently available? Or simply be in addition to? Speaking from the point of view of working with clients on their stylesheets, it gives certainly more robust formatting and I know Iâve wished we had such capability. But on the other had I would immediate try to limit my client to deciding
on only a few things like a ânew or changed contentâ style or otherwise I can envision having to constantly make adjustments to stylesheets every time they added a new value to an flagging attribute and therefore wanted a new outputclass. Often my clients
at least understand how to create a DITAVAL file with those attributes, but they donât know how to update their stylesheet to define outputclasses. It could make a difference of what they can do on their own and what they need someone else to do.
I know itâs not really the committeeâs problem to worry about the âjust because you can doesnât mean you shouldâ side of things, but itâs something to consider.
Dawn From: dita <dita@lists.oasis-open.org> on behalf of Robert D Anderson <robander@us.ibm.com> Today, DITAVAL lets you slap a lot of specific styles on a metadata property. (I say a lot, but it's a relatively small set of specific styles, compared to something like CSS). You can have this: |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]