git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation: use "spurious .sp" XSLT if DOCBOOK_SUPPRESS_SP is set

From
Jeff King <peff@peff.net>
Date
Apr 1, 2009, 13:06 UTC
Message-ID
<20090401130636.GA29113@coredump.intra.peff.net>
In-Reply-To
<DDA1F213-D15C-49B3-90CB-557F9A465A6A@pobox.com>
On Wed, Apr 01, 2009 at 07:19:08AM -0500, Chris Johnsen wrote:
Show 11 quoted lines
>> In the course of your SVN research, did you find the fixes between
>> 1.73.1 and 1.74.3 that fixed the spacing issue? If so, I wonder if it's
>> worth backporting that fix to DOCBOOK_FIX_LIST_SPACING.
>
> I guess you are referring to an issue different from the one created by 
> using the "spurious .sp" simpara template, but I am not familiar with 
> another one. If not, then I am confused. The new patch to avoid using the 
> "spurious .sp" template fixes the list spacing in pu's git-cvsimport.1 
> when I generate it here (using docbook-xsl 1.74.0). For example, the extra 
> blank line after "Problems related to timestamps:" goes away and a new 
> blank line is inserted before "Problems related to branches:".

Sorry, I should have been more clear (it seems we have enough docbook problems to cause confusion in referring to them :) ). What I meant is:

  The original issue which caused me to investigate this, namely the
  extra blank line before a list and the missing blank line after the
  list, is present in 1.73 but not in 1.74 (I tested only with 1.74.3,
  but your statement above leads me to believe it is fixed in 1.74.0).
  Is it worth including a fix in our docbook templates to make it look
  right for people on 1.73?
Show 7 quoted lines
> My poking around in the docbook SVN repo was largely limited to the  
> manpages/block.xsl file since that is where the normal simpara template 
> lives. If this other issue is list specific, it seems likely that fixes 
> would be in manpages/lists.xsl. It looks like there have only been around 
> ten commits to that lists.xsl since 1.73.1, but none of them jumped out at 
> me as likely culprits unless the spacing you mean is indentation or 
> "bullet"-to-text spacing (though my brain is tired right now).
Hmm. I think part of the fix is actually in param.xsl, which contains:
    <!-- * squeeze multiple .sp instances into a single .sp-->
    <substitution oldstring=".sp&#10;.sp" newstring=".sp"/>
in 1.74, but not 1.73.

I am torn on whether it makes sense to try backporting this. Debian stable, at least, will be on 1.73 for quite a long time. On the other hand, the problem is relatively minor (it is ugly, but you can still read the text) and I'm not sure we want to get into pulling random fixes from upstream docbook-xsl; it could turn into a huge time sink.

-Peff
Previous: Chris Johnsen
Message 22 of 22 in “Add warning about known issues to documentation of cvsimport”
  1. Add warning about known issues to documentation of cvsimportHeiko Voigt, Mar 23, 2009
  2. Ferry Huberts (Pelagic)Mar 23, 2009
  3. Heiko VoigtMar 30, 2009
  4. Ferry Huberts (Pelagic)Mar 31, 2009
  5. Heiko VoigtMar 31, 2009
  6. cvsimport: Add a note about crlf options to the documentationHeiko Voigt, Mar 31, 2009
  7. Ferry Huberts (Pelagic)Mar 31, 2009
  8. Jeff KingMar 24, 2009
  9. Heiko VoigtMar 30, 2009
  10. Junio C HamanoMar 31, 2009
  11. Cleanup warning about known issues in cvsimport documentationHeiko Voigt, Mar 31, 2009
  12. Jeff KingMar 31, 2009
  13. Cleanup warning about known issues in cvsimport documentationHeiko Voigt, Apr 1, 2009
  14. Jeff KingMar 31, 2009
  15. Jeff KingMar 31, 2009
  16. Junio C HamanoMar 31, 2009
  17. Documentation: use "spurious .sp" XSLT if DOCBOOK_SUPPRESS_SP is setChris Johnsen, Apr 1, 2009
  18. Jeff KingApr 1, 2009
  19. Junio C HamanoApr 2, 2009
  20. Jeff KingApr 1, 2009
  21. Chris JohnsenApr 1, 2009
  22. Jeff KingApr 1, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.