Better layout of lists in output formats #10132
Conversation
In different output format the layout of some listing was not correct (especially in the RTF output): - missing space after the word "directory" (whilst present after the word "file") - missing separators in lists (the big dots), due to missing initial initial parts, i.e. strange concatenation of items (when brief was missing).
| @@ -946,7 +946,7 @@ void GroupDefImpl::writeDirs(OutputList &ol,const QCString &title) | |||
| if (!dd->hasDocumentation()) continue; | |||
| ol.startMemberDeclaration(); | |||
| ol.startMemberItem(dd->getOutputFileBase(),OutputGenerator::MemberItemType::Normal); | |||
| ol.parseText(theTranslator->trDir(FALSE,TRUE)); | |||
| ol.docify(theTranslator->trDir(FALSE,TRUE)+" "); | |||
There was a problem hiding this comment.
wouldn't it be better to move adding the space inside insertMemberAlign() for those formats that require it?
There was a problem hiding this comment.
I made it so that it is analogous to the code in void GroupDefImpl::writeFiles(OutputList &ol,const QCString &title) where we already have: ol.docify(theTranslator->trFile(FALSE,TRUE)+" ");
The change is required for LaTeX, RTF, Docbook (I didn't test it for man). For the HTML output it doesn't really hurt.
When looking where insertMemberAlign() is used we see that this is in:
- classdef.cpp
- conceptdef.cpp
- dirdef.cpp
- groupdef.cpp
- namespacedef.cpp
- vhdldocgen.cpp
With dirdef.cpp there is currently no space either and I don't know what the effect would be , though the fact that there is a <span... line a little above it I think it is here only used in HTML or tag file.
The situation in vhdldocgen.cpp is a bit more complicated as here we see that there is here sometimes a space before or (often) after the call to insertMemberAlign.
In different output format the layout of some listing was not correct (especially in the RTF output):
Example: example.tar.gz