From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 5/8] winsup/doc: Convert utils.xml to using refentry
Date: Tue, 16 Jun 2015 17:33:00 -0000 [thread overview]
Message-ID: <55805DF6.5040004@dronecode.org.uk> (raw)
In-Reply-To: <20150616124934.GD31537@calimero.vinschen.de>
On 16/06/2015 13:49, Corinna Vinschen wrote:
> On Jun 16 12:09, Jon TURNEY wrote:
>> On 16/06/2015 10:45, Corinna Vinschen wrote:
>>> On Jun 16 10:28, Jon TURNEY wrote:
>>>> On 15/06/2015 18:11, Corinna Vinschen wrote:
>>>>> On Jun 15 13:36, Jon TURNEY wrote:
>>>>>> Convert utils.xml from using a sect2 to using a refentry for each utility
>>>>>> program.
>>>>>>
>>>>>> Unfortunately, using refentry seems to tickle a bug in dblatex when generating
>>>>>> pdf, which appears to not escape \ properly in the latex for refentry, so use
>>>>>> fop instead.
>>>>>
>>>>> Uhm... wasn't Yaakov's patch from 2014-11-28 explicitely meant to drop
>>>>> the requirement to use fop andd thus java?
>>>>>
>>>>> Is there really no other way to handle that, rather than reverting to
>>>>> fop?
>>>>
>>>> Now I try again --with-dblatex, it works fine, so that part of the patch can
>>>> be removed.
>>>>
>>>> I can only guess I must have had some other markup error causing me
>>>> problems, which has since been fixed.
>>>
>>> I'm relieved :}
>>
>> Approved with that change?
>
> Yep, thanks.
Done.
Note that the next time you build documentation for the website, you
might need to take some special steps to add new .html files.
and next time you build a package you might need to take some special
steps to exclude /usr/share/man/
Please let me know if there are any problems with these changes.
next prev parent reply other threads:[~2015-06-16 17:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 12:36 [PATCH 0/8] Generate utilities manpages Jon TURNEY
2015-06-15 12:37 ` [PATCH 2/8] winsup/doc: Fix xidepend to handle relative pathnames Jon TURNEY
2015-06-15 17:02 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 5/8] winsup/doc: Convert utils.xml to using refentry Jon TURNEY
2015-06-15 17:11 ` Corinna Vinschen
2015-06-16 9:28 ` Jon TURNEY
2015-06-16 9:45 ` Corinna Vinschen
2015-06-16 11:09 ` Jon TURNEY
2015-06-16 12:49 ` Corinna Vinschen
2015-06-16 17:33 ` Jon TURNEY [this message]
2015-06-16 17:49 ` Corinna Vinschen
2015-06-16 18:50 ` Jon TURNEY
2015-06-16 19:17 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 3/8] winsup/doc: Some preparatory XML fixes Jon TURNEY
2015-06-15 17:04 ` Corinna Vinschen
2015-06-16 9:22 ` Jon TURNEY
2015-06-16 9:35 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 6/8] winsup/doc: Make it easier to extend xidepend to more targets Jon TURNEY
2015-06-15 17:15 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 7/8] winsup/doc: Make and install manpages for utils Jon TURNEY
2015-06-15 18:12 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 8/8] winsup/doc: Fix an issue with parallel make Jon TURNEY
2015-06-15 17:16 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 4/8] winsup/doc: Use fo.xsl to customize PDF generation from DocBook XML Jon TURNEY
2015-06-15 17:05 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 1/8] winsup/doc: Remove tarball target from .PHONY Jon TURNEY
2015-06-15 16:52 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55805DF6.5040004@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).