On Wednesday, July 15, 2015 at 3:16:44 AM UTC-5, Dan Allen wrote: > > > That's not how the *default* output works atm. I agree that it would be > nice if a role could be applied per list item. This was missed in the > original design of AsciiDoc and perhaps something for UniDoc (AsciiDoc 2). > >
That would be nice. I think now i'll try and catch that in the generated DocBook xml, and add something to my transform, to handle that. Should be simple! > >> Adding a role to a table row is another missed requirement in AsciiDoc. > However, we can see that there's actually pretty clear room for it already. > > |=== > |Column A |Column B > > [.row-role-a] > | A1 > | B1 > > [.row-role-b] > | A2 > | B2 > |=== > > I'd certainly consider implementing this in Asciidoctor if you'd like to > file an issue. Until then, unfortunately, there isn't much of a workaround > that I can think of. > I'll do that! Where can i file an issue? A role attribute for a row would be, for us, probably a minimum. I can also handle this, through my xslt, catching the generated DocBook xml and transforming that. Another idea, we had some documents, where the writers had put a role item on the internal colspec element. With a role on this, they were able to have, depending on the role vale, a 2 column table for windows users, for example, and a 3 column table for linux users. This might be something to consider also! Thanks again, sorry for the late reply! Russ > > -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
