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

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

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


Subject: Re: DOCBOOK: XHTML tables


Sorry, Norm wanted to see hundreds jump in here. I'll just try it with 
my own two feet.

I see major usability, compatibility and support issues turning up with 
this discussion. What Tobias sees as trivial with respect to scripting 
and regular expression search and replace is simply a non-starter when 
it comes to a (somewhat recalcitrant) team of tech writers who are 
hanging on by both their toe and finger nails to the rocket-science of 
structured editing. It's hard enough to convince some folks that looking 
at element/tag names in the editor is not a major incovenience, 
complexification.

I've followed this discussion off and on and I'm running out of time, 
energy and patience. If we could have one or two detailed, concrete and 
preferably practicable alternative solutions to the dual-Table-model 
question, perhaps we could cut to the chase and begin some sort of 
definitive decision process going forward to the TC?

Thanks.                 ...edN

Tobias Reif wrote:
> Jirka Kosek wrote:
> 
>  > Well you have proposed using HTML tables in their own namespaces.
> 
> This could be one way to incorporate the table model; each of the 
> various ways has it's own pro/con balance. I'd be OK with several 
> different ways.
> 
>  > You will either need to prefix all HTML table elements and you
>  > wouldn't be then able to cut'n'paste from HTML.
> 
> It's trivial to cut and paste, then add the prefix via search and 
> replace, eg
> 
>   :%s/<\(\/\?\)tr\(\_s*\)/<\1h:tr\2/g
> 
> etc, then cut and paste into DocBook (or do via some tiny script you can 
> run each time). But c'n'p is not the most important reason for inclusion 
> anyways, from my POV.
> 
>  > <html:table xmlns:html="http://www.w3.org/1999/xhtml">
>  >   <html:tr>
>  >     <html:td>Cell with <emphasis>emphasized words</emphasis></html:td>
>  >   </html:tr>
>  > </html:table>
> 
>   xmlns:h="http://www.w3.org/1999/xhtml"
> can be set on the root element and/or be set (via "fixed") from the DTD. 
> (see the SVG DTD)
> 
> Then write:
> 
> <h:table>
>   <h:tr>
>     <h:td>Cell with <emphasis>emphasized words</emphasis></html:td>
>   </h:tr>
> </h:table>
> 
> [... default ns example ...]
> 
>  > Which style from these two did you preffer?  Or do you have any other
>  > solution which won't be as complex?
> 
> Prefixing each element might be one way offering most control from the 
> DTD, but I'd be OK with any of the ways you showed.
> 
> Tobi
> 






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