|Thread title||Replies||Last modified|
|Docbook conversion||5||08:21, 11 May 2019|
Hi, I'm not sure the ugly hack, that I found: <span class="menuchoice"></span> works for the docbook conversion.
What ugly hack? Your solution works beautifully!
I suspect you are right about the docbook conversion, but then I suspect that using → instead of -> will also create problems. Still I prefer the templated approach as it spares authors and translators a lot of unnecessary typing and makes the source much more easy to read.
I am currently looking into these problems, but don't expect a solution just yet :-)
→ works great in the docbook conversion. See for example: https://docs.kde.org/trunk5/en/kdemultimedia/kdenlive/quick-start.html#creating-a-new-project
Probably just adding a new rule CSS in docs.kde.org and in khelpcenter should be enough, to solve this problem.
Please... avoid unusual formatting. Today it breaks my Kdenlive export. Do whatever you want on other pages (it's ugly, but someone got to break it from time to time to update at least cosmetically), but leave Amarok and Kdenlive alone.
It's not the → character as such, I worry about. But the program converting our manual pages to docbook format probably can't handle it. Generally, we should be very conservative with the manual pages - any new formatting could potentially mess with the docbook conversion, even if it is just a new template encapsulating existing formatting.
I do welcome the use of → between <menuchoice> tags in all other userbase pages, since the old style of marking up menu choices can lead to very long lines, that can not be split. When that happens, the page looks quite ugly and it does no good for readability, either.
My comment on long lines not being split was wrong. I thought I remembered such problems, but they must have had different causes. When using the → character, however, it must appear outside of the < menuchoice> tags to be displayed properly. That also looks better and is more readable imho, so I am still happy with using it.
I had also observed some problems when using the template in a bulleted list, which led to some misleading statements in comment on the template page. Those problems were due to line terminating characters being introduced in the wrong places in the template code and they are fixed now.
I also found a "more regular" wiki-syntax to achieve what you did with < span> tags. I don't think it makes much of a difference, but decided to use it just in case.
I have added a short description of this template as well as the Path themplate on the Typographical Guidelines page