Re: [PATCH] wwwdocs: experiments with a Python postprocessing script

2025-01-16 Thread David Malcolm
On Thu, 2025-01-16 at 22:58 +0800, Gerald Pfeifer wrote: > On Wed, 15 Jan 2025, David Malcolm wrote: > > The heading elements in our website contain "id" information, > > but currently to find them you to look at the page source, > > whereas in the generated HTML for the manual we have e.g.: > > >

Re: [PATCH] wwwdocs: experiments with a Python postprocessing script

2025-01-16 Thread David Malcolm
On Thu, 2025-01-16 at 22:58 +0800, Gerald Pfeifer wrote: > On Wed, 15 Jan 2025, David Malcolm wrote: > > The heading elements in our website contain "id" information, > > but currently to find them you to look at the page source, > > whereas in the generated HTML for the manual we have e.g.: > > >

Re: [PATCH] wwwdocs: experiments with a Python postprocessing script

2025-01-16 Thread Gerald Pfeifer
On Wed, 15 Jan 2025, David Malcolm wrote: > The heading elements in our website contain "id" information, > but currently to find them you to look at the page source, > whereas in the generated HTML for the manual we have e.g.: > > ΒΆ > > which shows up nicely in the browser in e.g. > https://

Re: [PATCH] wwwdocs: experiments with a Python postprocessing script

2025-01-15 Thread Joseph Myers
On Wed, 15 Jan 2025, David Malcolm wrote: > I've never managed to build MetaHTML and have always just > crossed my fingers and hoped when making edits to the GCC > website; bin/preprocess just errors out for me immediately > due to not finding mhc. I think that replacing MetaHTML with a Python sc