> On Jul 12, 2021, at 12:36 PM, David Malcolm via Gcc-patches
> wrote:
>
> On Mon, 2021-07-12 at 15:25 +0200, Martin Liška wrote:
>> ...
>
> I think the output formats we need to support are:
> - HTML
> - PDF
> - man page (hardly "modern", but still used)
Also info format (for the Emacs info
> From: Jonathan Wakely
> Date: Mon, 12 Jul 2021 15:54:49 +0100
> Cc: Martin Liška ,
> "g...@gcc.gnu.org" , gcc-patches
> ,
> "Joseph S. Myers"
>
> You like texinfo. We get it.
Would you please drop the attitude?
> Cc: h...@bitrange.com, g...@gcc.gnu.org, gcc-patches@gcc.gnu.org,
> jos...@codesourcery.com
> From: Martin Liška
> Date: Mon, 12 Jul 2021 16:37:00 +0200
>
> > 4) The need to learn yet another markup language.
> > While this is not a problem for simple text, it does require a
> > se
> Cc: g...@gcc.gnu.org, gcc-patches@gcc.gnu.org, jos...@codesourcery.com
> From: Martin Liška
> Date: Mon, 12 Jul 2021 16:34:11 +0200
>
> > "Texinfo must go" is one possible conclusion from your description.
> > But it isn't the only one. An alternative is "the Texinfo source of
> > the GCC manu
On Mon, 2021-07-12 at 15:25 +0200, Martin Liška wrote:
> Hello.
>
> Let's make it a separate sub-thread where we can discuss motivation
> why
> do I want moving to Sphinx format.
>
> Benefits:
> 1) modern looking HTML output (before: [1], after: [2]):
"modern looking" is rather subjective; I'd r
On Mon, 12 Jul 2021 at 17:01, Gavin Smith wrote:
>
> On Mon, Jul 12, 2021 at 4:04 PM Jonathan Wakely via Gcc
> wrote:
> > GNU Hello has the same problem with its docs:
> > https://www.gnu.org/software/hello/manual/hello.html#index-_002dg
> > That URL is garbage because of the URL-encoded %2d char
On Mon, Jul 12, 2021 at 4:04 PM Jonathan Wakely via Gcc
wrote:
> GNU Hello has the same problem with its docs:
> https://www.gnu.org/software/hello/manual/hello.html#index-_002dg
> That URL is garbage because of the URL-encoded %2d character, and the
> fact it links to the wrong place (the descri
On Mon, 12 Jul 2021 at 15:52, Jonathan Wakely wrote:
>
> On Mon, 12 Jul 2021 at 15:13, Eli Zaretskii wrote:
> > I get it that you dislike the HTML produced by Texinfo, but without
> > some examples of such bad HTML it is impossible to know what exactly
> > do you dislike and why.
> >
> > > You ca
On Mon, 12 Jul 2021 at 15:52, Jonathan Wakely wrote:
>
> On Mon, 12 Jul 2021 at 15:13, Eli Zaretskii wrote:
> >
> > > From: Jonathan Wakely
> > > This is a problem with texinfo too.
> >
> > Not for someone who already knows Texinfo. We are talking about
> > switching away of it, so I'm thinking
On Mon, 12 Jul 2021 at 15:13, Eli Zaretskii wrote:
>
> > From: Jonathan Wakely
> > Date: Mon, 12 Jul 2021 14:53:44 +0100
> > Cc: Martin Liška ,
> > "g...@gcc.gnu.org" , gcc-patches
> > ,
> > "Joseph S. Myers"
> >
> > For me, these items are enough justification to switch away from
>
On 7/12/21 3:39 PM, Eli Zaretskii wrote:
Cc: g...@gcc.gnu.org, gcc-patches@gcc.gnu.org, jos...@codesourcery.com
From: Martin Liška
Date: Mon, 12 Jul 2021 15:25:47 +0200
Let's make it a separate sub-thread where we can discuss motivation why
do I want moving to Sphinx format.
Thanks for starti
On 7/12/21 4:16 PM, Eli Zaretskii wrote:
From: Jonathan Wakely
Date: Mon, 12 Jul 2021 15:05:11 +0100
Cc: Martin Liška ,
"g...@gcc.gnu.org" , gcc-patches
,
"Joseph S. Myers"
To be clear, I give links to users frequently (several times a week,
every week, for decades) and prefer
On 7/12/21 4:12 PM, Eli Zaretskii wrote:
From: Jonathan Wakely
Date: Mon, 12 Jul 2021 14:53:44 +0100
Cc: Martin Liška ,
"g...@gcc.gnu.org" , gcc-patches
,
"Joseph S. Myers"
For me, these items are enough justification to switch away from
texinfo, which produces crap HTML pages
> From: Jonathan Wakely
> Date: Mon, 12 Jul 2021 15:05:11 +0100
> Cc: Martin Liška ,
> "g...@gcc.gnu.org" , gcc-patches
> ,
> "Joseph S. Myers"
>
> To be clear, I give links to users frequently (several times a week,
> every week, for decades) and prefer to give them a link to spe
> From: Jonathan Wakely
> Date: Mon, 12 Jul 2021 14:53:44 +0100
> Cc: Martin Liška ,
> "g...@gcc.gnu.org" , gcc-patches
> ,
> "Joseph S. Myers"
>
> For me, these items are enough justification to switch away from
> texinfo, which produces crap HTML pages with crap anchors.
If we
On Mon, 12 Jul 2021 at 14:53, Jonathan Wakely wrote:
> For me, these items are enough justification to switch away from
> texinfo, which produces crap HTML pages with crap anchors. You can't
> find out the anchors without inspecting (and searching) the HTML
> source. That's utterly stupid. And even
On Mon, 12 Jul 2021 at 14:41, Eli Zaretskii via Gcc wrote:
>
> > Cc: g...@gcc.gnu.org, gcc-patches@gcc.gnu.org, jos...@codesourcery.com
> > From: Martin Liška
> > Date: Mon, 12 Jul 2021 15:25:47 +0200
> >
> > Let's make it a separate sub-thread where we can discuss motivation why
> > do I want mo
> Cc: g...@gcc.gnu.org, gcc-patches@gcc.gnu.org, jos...@codesourcery.com
> From: Martin Liška
> Date: Mon, 12 Jul 2021 15:25:47 +0200
>
> Let's make it a separate sub-thread where we can discuss motivation why
> do I want moving to Sphinx format.
Thanks for starting this discussion.
> Benefits:
Hello.
Let's make it a separate sub-thread where we can discuss motivation why
do I want moving to Sphinx format.
Benefits:
1) modern looking HTML output (before: [1], after: [2]):
a) syntax highlighting for examples (code, shell commands, etc.)
b) precise anchors, the current Texinfo anch
19 matches
Mail list logo
