> From: Nikolay Kudryavtsev
> Date: Tue, 21 Dec 2021 02:12:14 +0300
> Cc: Eli Zaretskii , Texinfo
>
> Looked at c0c07af5f1, seems like it only touches texi2any, I think the
> same should be done for makeinfo.
Yes, as I said, the patch should be applied both to texi2any and to
makeinfo. Did yo
Gavin Smith wrote:
[...]
The width specifications seem to be the most appropriate for printed
output. Often when specifying a @multitable the user wouldn't care
about the column widths. Maybe the browser can do a good job at the
layout without them. However, it could matter in some cases. I woul
Looked at c0c07af5f1, seems like it only touches texi2any, I think the
same should be done for makeinfo.
Eli, I was able to apply your patch and confirm it works.
On Mon, Dec 20, 2021 at 10:06:26PM +, Gavin Smith wrote:
> It would help to know which Texinfo commands were generating the
> non-standard HTML, and then it would be easier to understand if it was
> really needed.
h* align are for @centerchap, @settitle and @subtitle (@settitle
and @subtitle
It would help to know which Texinfo commands were generating the
non-standard HTML, and then it would be easier to understand if it was
really needed.
I haven't done research into any of the output for this mail.
On Mon, Dec 20, 2021 at 8:38 PM Patrice Dumas wrote:
>
> Hello,
>
> I think that it
Hello,
I think that it would make sense to do stricter HTML4 that is also
relevant for HTML5, and should also improve validity as XHTML 1.*.
For attributes that are deprecated and were not readded in HTML5, here
is what I propose. I know very little about CSS, so do not hesitate to
criticize. T
Patrice Dumas wrote:
However it looks like HTML5 cannot be validated...
In the sense of validating using an old-style DTD validator.
However, that has limited usefulness regardless.
HTML5 is defined in terms of a very specific parsing algorithm, meant
to avoid the incompatible extensions and wo
On Mon, Dec 20, 2021 at 05:17:46PM +0100, Jean Abou Samra wrote:
> Le 20/12/2021 à 17:01, Patrice Dumas a écrit :
> > On Wed, Nov 24, 2021 at 03:17:22PM +, Werner LEMBERG wrote:
> > > Hello Gavin,
> > >
> > >
> > > For the LilyPond documentation we are going to use `pygments` to do
> > > auto
Le 20/12/2021 à 19:54, Patrice Dumas a écrit :
On Mon, Dec 20, 2021 at 05:17:46PM +0100, Jean Abou Samra wrote:
Le 20/12/2021 à 17:01, Patrice Dumas a écrit :
On Wed, Nov 24, 2021 at 03:17:22PM +, Werner LEMBERG wrote:
Hello Gavin,
For the LilyPond documentation we are going to use `p
On Mon, Dec 20, 2021 at 01:05:29AM +0100, Patrice Dumas wrote:
> It is not the only change. There are actually quite a bit of changes,
> the validation as HTML5 with the new DOCTYPE is not very good.
Could we (you) use the HTML4 DTD to validate texi2any's output? Is that
what you did before?
Pl
> Patrice Dumas writes:
> On Thu, Dec 16, 2021 at 06:20:34PM +0100, Kurt Hornik wrote:
>> > Jacob Bachmeyer writes:
>>
>> What I ended up doing is set up a local W3C service. On Debian, after
>>
>> apt-get install w3c-markup-validator
>>
>> https://github.com/ysangkok/w3c-validator-run
On Wed, Nov 24, 2021 at 03:17:22PM +, Werner LEMBERG wrote:
>
> Hello Gavin,
>
>
> For the LilyPond documentation we are going to use `pygments` to do
> automatic colour highlighting of LilyPond snippets. We also want to
> support this feature in the PDF manuals. To do so I ask you to appl
Le 20/12/2021 à 17:01, Patrice Dumas a écrit :
On Wed, Nov 24, 2021 at 03:17:22PM +, Werner LEMBERG wrote:
Hello Gavin,
For the LilyPond documentation we are going to use `pygments` to do
automatic colour highlighting of LilyPond snippets. We also want to
support this feature in the PDF m
> Patrice Dumas writes:
Great, thanks.
I just tried the current development version on my test case
(R-intro.texi in R). This now gives
$ python3 validator-runner.py R-intro-7.html
error: line 148: there is no attribute "align"
error: line 4363: there is no attribute "compact"
error: line 4
On Sun, Dec 19, 2021 at 04:39:04PM -0800, Per Bothner wrote:
> On 12/19/21 16:02, Patrice Dumas wrote:
> > It was much easier in the HTML converter. It is actually a bit
> > cumbersome, but it works. To use XML compatible syntax, it is possible
> > to use -c 'USE_XML_SYNTAX 1'. It is also possib
On Mon, Dec 20, 2021 at 07:24:01AM +, Gavin Smith wrote:
> On Mon, Dec 20, 2021 at 01:05:29AM +0100, Patrice Dumas wrote:
> > It is not the only change. There are actually quite a bit of changes,
> > the validation as HTML5 with the new DOCTYPE is not very good.
>
> Could we (you) use the HTM
> With your patch, the following produces a malformed PDF file:
>
> @example
> aaa
> @setcolor{0.7 0.7 0.2}bbb
> @setcolor{0 0 0}ccc
> ddd @r{@setcolor{0.2 0.7 0.7}comment@setcolor{0 0 0}}
> eee
> @end example
>
> due to the nesting of @setcolor inside @r.
Thanks.
> Admittedly, putting any comm
18 matches
Mail list logo
