asciidoctor / docbookrx

(An early version of) a DocBook to AsciiDoc converter written in Ruby.
MIT License
22 stars 49 forks source link

No support for certain DocBook elements #7

Open pmkovar opened 8 years ago

pmkovar commented 8 years ago

When converting Publican-based DocBook XML docs from the Fedora Doc Project, it turned out some of the often-used elements are unsupported:

pmkovar commented 8 years ago

One more that seems to be missing:

pmkovar commented 8 years ago

Found two more:

mojavelinux commented 8 years ago

It's going to be really helpful if you can cite examples for each missing element. Just point to a DocBook source somewhere. The reason is that there are so many ways to structure a DocBook file, so how the element is used in context actually becomes quite important to the implementation of the converter (at least to hit the 80-90% case).

mojavelinux commented 8 years ago

In my opinion, some of these inline elements should just get erased when converting to AsciiDoc (or mapped to simplified markup such as bold with a role perhaps). The reason is because I feel very strongly that DocBook goes way overboard with markup. It's such a time sync for writers when the reader never sees the distinction anyway. My observation is that writers often overuse markup, wasting time and money and making editing much harder than it has to be.

mojavelinux commented 8 years ago

Something like a gui menu is a great example of something that should be preserved...and we do have support for that in Asciidoctor.

mojavelinux commented 8 years ago

I think I've implemented menuchoice correctly now, which also covers:

If I'm missing a use case, just point me to a sample.

mojavelinux commented 8 years ago

I've handled a whole bunch more. I'm updating the original list as I go.

mojavelinux commented 8 years ago

We now have a test suite to use for providing samples.

mojavelinux commented 8 years ago

part is also missing, but we're handling that as part of #6

pmkovar commented 8 years ago

@mojavelinux Thanks a lot for working on these! Erasing some of the elements works for me and makes sense provided the content itself is preserved.

Do you still need samples for the remaining elements?

mojavelinux commented 8 years ago

I'll always take samples. But now that we have a test suite, there's actually somewhere to put those examples now. Definitely looking for edge cases and things that we aren't currently covering.

mojavelinux commented 8 years ago

I'd like to get this list in the description completed checked off. That's definitely the goal here. Some of the tags I don't yet understand the context, so seeing it "in the wild" definitively helps know how to map it.

tradej commented 8 years ago

Hi, it seems to me that

also aren't supported.