This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: list items HTML formating with XSL



>| Would it be very difficult to condition the emission of these styling
>| attributes to a stylesheet parameter, say emit.style.attribs ? We can
then
>
>There's already css.decoration. I've changed the list generation
>templates to output type on ul only if css.decoration != 0.
>
>| produce a suitable default CSS to serve as a initial point for styling.
>| Most of these attributs occur only in tables.
>
> I think you can turn all of those off by setting table.borders.with.css=0
>
>(But the resulting tables are probably going to be a lot uglier because
>there's so much that HTML can't do.)

Thank you. But now I can see why I got confused. The parameter names appear
inconsistent to me. Isn't it strange that a parameter called
'css.decoration' would produce the type attribute when set to true? You
see, type is defined entirely by HTML, not by CSS. The equivalent CSS code
for type="disc" would be to use style="list-style-type: disc;". (Yes, it is
very verbose. However, it was not intended to be used primarily inline, but
rather in a separate CSS file.) The same applies to the table attributes:
color, background, border, etc. are all HTML, not CSS (although there are
CSS equivalents for them).

All these HTML styling attributes are deprecated, and are going away
forever in XHTML 2.0. Only the style attribute, which is where all CSS code
may reside, will remain.

To avoid confusion without changing the parameter semantics, it would be
nice to rename them. Or better still, to use separate attributes to
segregate the desired effects: the list- and table-bound attributes turn
decoration on and off for them, and a separate general attribute selects a
language for the styling (transitional HTML or CSS). Would that involve too
much
coding? I can help.

(BTW: Some entries in pt_br.xml have not been translated/localized. How
should I proceed to post the corrections? Should I send you the
modifications? I wasn't able to reach the address stamped in the file
header, do I need special access for that?)

Cheers.

=============================================
Marcelo Jaccoud Amaral
Petrobrás (http://www.petrobras.com.br)
mailto:jaccoud@petrobras.com.br
voice: +55 21 2534-3485
fax: +55 21 2534-1809
=============================================




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]