Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
No support for certain DocBook elements #7
Comments
pmkovar
commented
Nov 2, 2015
|
One more that seems to be missing:
|
pmkovar
commented
Nov 5, 2015
|
Found two more:
|
|
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). |
|
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. |
|
Something like a gui menu is a great example of something that should be preserved...and we do have support for that in Asciidoctor. |
|
I think I've implemented
If I'm missing a use case, just point me to a sample. |
|
I've handled a whole bunch more. I'm updating the original list as I go. |
mojavelinux
added
the
bug
label
Dec 6, 2015
|
We now have a test suite to use for providing samples. |
|
|
pmkovar
commented
Jan 7, 2016
|
@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? |
|
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. |
|
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
Jun 28, 2016
•
|
Hi, it seems to me that
also aren't supported. |
pmkovar commentedOct 27, 2015
When converting Publican-based DocBook XML docs from the Fedora Doc Project, it turned out some of the often-used elements are unsupported:
menuchoiceguimenuguisubmenuguimenuitemuserinputcomputeroutputoptionsystemitemremarkreplaceableguiiconcitetitlepackageforeignphrasepropertytypeattributiondatabaseexceptionnamequotecitationfunction