public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH v2] winsup/doc/posix.xml: add note for getrlimit, setrlimit, xrefs to notes
Date: Tue, 16 Feb 2021 09:51:08 -0700	[thread overview]
Message-ID: <39425336-2abc-793e-f2fd-ac6ade12d55c@SystematicSw.ab.ca> (raw)
In-Reply-To: <YCus7LynfyqkvjWl@calimero.vinschen.de>

On 2021-02-16 04:30, Corinna Vinschen via Cygwin-patches wrote:
> On Feb 15 15:35, Brian Inglis wrote:
>> change notes to see "Implementation Notes" to xref to std-notes;
>> add xref to std-notes to getrlimit, setrlimit;
>> add note to document limitations of getrlimit, setrlimit resources support
>> ---
>>   winsup/doc/posix.xml | 101 ++++++++++++++++++++++++-------------------
>>   1 file changed, 57 insertions(+), 44 deletions(-)

> Pushed with a change:
>    <xref linkend="std-notes">(see chapter "Implementation Notes")</xref>
> -->
>    (see <xref linkend="std-notes">chapter "Implementation Notes"</xref>)
> The reason is how xref is handled when creating html docs.  The result
> of an xref is always 'the section called "..."'.  With the above change,
> the text works (albeit differently) in html and info file.

Cheers, thanks, I'll bear that in mind in future, and read the generated output 
more carefully.

I'm not seeing .info generated with Note:... links, is that okay?

Also ...api.pdf is not being regenerated, so what have I lost or am missing?

I have the following doc tools (and others):

$ apt l asciidoc dblatex poppler\$ xmlto
asciidoc 8.6.9-1 x86_64 [installed, manual]
dblatex 0.3.10-1 x86_64 [installed, automatic]
poppler 21.01.0-1 x86_64 [installed, manual]
xmlto 0.0.28-1 x86_64 [installed, automatic]

What else is needed?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-02-16 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 22:35 Brian Inglis
2021-02-16 11:30 ` Corinna Vinschen
2021-02-16 16:51   ` Brian Inglis [this message]
2021-02-16 17:00     ` Brian Inglis
2021-02-17  9:29       ` Corinna Vinschen
2021-02-17 15:51         ` Brian Inglis

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=39425336-2abc-793e-f2fd-ac6ade12d55c@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).