From: "Martin Liška" <mliska@suse.cz>
To: Gaius Mulley <gaiusmod2@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Modula-2: merge followup (brief update on the progress of the new linking implementation)
Date: Wed, 31 Aug 2022 15:25:49 +0200 [thread overview]
Message-ID: <dad07bea-b095-35a3-32e0-357ea89568d8@suse.cz> (raw)
In-Reply-To: <87fshc360m.fsf@debian>
On 8/31/22 15:19, Gaius Mulley wrote:
> Martin Liška <mliska@suse.cz> writes:
>
>> How do you mean that? You should ideally generate .rst (Sphinx markup)
>> instead of the *.texi files. These will be then included in the converted
>> Sphinx manual similarly to how you include it now to the Texinfo manual.
>>
>> Does it make sense?
>>
>> Cheers,
>> Martin
>
> ah right - yes this makes sense.
Goo!
> I mistakenly thought the .rst files
> could be automatically generated from texinfo sources. In any case
> generating .rst directly will likely contain advantages,
Yes, that's what I'm doing for the existing documentation, but the conversion
is not perfect and I had to make some manual changes to the emitted .rst content.
So please fix the crash I reported and I can convert GM2 texi manual.
Cheers,
Martin
>
> regards,
> Gaius
next prev parent reply other threads:[~2022-08-31 13:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 10:31 Gaius Mulley
2022-07-11 8:21 ` Rainer Orth
2022-07-11 11:14 ` Rainer Orth
2022-07-11 15:06 ` Gaius Mulley
2022-07-11 20:36 ` Rainer Orth
2022-07-12 12:32 ` Gaius Mulley
2022-07-12 14:16 ` Rainer Orth
2022-07-25 9:42 ` Gaius Mulley
2022-07-26 7:45 ` Rainer Orth
2022-08-30 11:03 ` Gaius Mulley
2022-08-30 12:44 ` Martin Liška
2022-08-30 15:36 ` Gaius Mulley
2022-08-31 9:54 ` Martin Liška
2022-08-31 13:19 ` Gaius Mulley
2022-08-31 13:25 ` Martin Liška [this message]
2022-09-01 12:22 ` Gaius Mulley
2022-09-07 12:29 ` Martin Liška
2022-09-08 15:52 ` Gaius Mulley
2022-09-09 12:16 ` Martin Liška
2022-09-09 15:40 ` Gaius Mulley
-- strict thread matches above, loose matches on Subject: below --
2022-06-11 19:15 Gaius Mulley
2022-06-17 17:08 ` Gaius Mulley
2022-06-17 19:02 ` Richard Biener
2022-06-27 7:24 ` Gaius Mulley
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=dad07bea-b095-35a3-32e0-357ea89568d8@suse.cz \
--to=mliska@suse.cz \
--cc=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).