#29: Remove whitespace trigger ugly PDF formatting ---------------------+------------------------------------------------------ Reporter: quaid | Owner: quaid Type: task | Status: new Priority: major | Milestone: RC-ready Component: Content | Version: 10 Keywords: | ---------------------+------------------------------------------------------ Just in case we cannot get this fixed in the PDF toolchain, we need to remove all the leading whitespace for tags that display CDATA or other content verbatim.
This could be done as part of a general run of a tool such as docbook-lint or xmlformat. Before doing that, we need to assess the risk of the tool chaining line numbers and causing translation stats to go fuzzy.
#29: Remove whitespace trigger ugly PDF formatting ----------------------+----------------------------------------------------- Reporter: quaid | Owner: quaid Type: task | Status: new Priority: major | Milestone: RC-ready Component: Content | Version: 10 Resolution: | Keywords: ----------------------+----------------------------------------------------- Comment (by pfrields):
CDATA shouldn't generate any translation strings, so we're OK there. I completely disagree with certain parties who think CDATA is a hack -- on the contrary, it's been part of the XML standard since day one.
Are we back to this problem of flush-left content again? That just seems like a stupid bug to me and I can't believe we as writers and editors still have to use this kind of manual workaround. Argh!
#29: Remove whitespace trigger ugly PDF formatting ----------------------+----------------------------------------------------- Reporter: quaid | Owner: quaid Type: task | Status: new Priority: major | Milestone: RC-ready Component: Content | Version: 10 Resolution: | Keywords: ----------------------+----------------------------------------------------- Comment (by pfrields):
Ah, I think I recall that it was extra markup inside <screen> that made this occur. This markup would be problematic:
<screen> <computeroutput>too much spacing</computeroutput> </screen>
This might work better:
<screen><![CDATA[spacing OK but maybe not so syntactically correct]]></screen>
Perhaps standardizing on this usage in the markup howto would help?
#29: Remove whitespace trigger ugly PDF formatting ----------------------+----------------------------------------------------- Reporter: quaid | Owner: quaid Type: task | Status: new Priority: major | Milestone: RC-ready Component: Content | Version: 10 Resolution: | Keywords: ----------------------+----------------------------------------------------- Comment (by quaid):
I'd rather munge our XML formatting than lose the contextual markup.
Markup inside of <screen> is explicitly allowed. If <screen> also explicitly displays all whitespace as-is, then our having the whitespace there is a formatting mistake. Just because Emacs indents by default :) ...
#29: Remove whitespace trigger ugly PDF formatting ----------------------+----------------------------------------------------- Reporter: quaid | Owner: quaid Type: task | Status: closed Priority: major | Milestone: RC-ready Component: Content | Version: 10.0.0 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by pfrields):
* status: new => closed * resolution: => fixed
-
Fedora Release Notes -
fedora-badges