> On Dec 20, 2021, at 10:43, Jacob Bachmeyer wrote:
>
> Is there even a reason to move to HTML5 at all? Texinfo produces documents,
> not Web apps. What does HTML5 bring to the proverbial table that HTML4 lacks?
I don't understand your focus on "web apps". "Web apps" predate HTML5. The
Gavin Smith wrote:
[...]
It's questionable how useful it is to have a version number in a file
format if reading software is not going to use it (apparently just
"" is needed to turn off "quirks mode" but browsers
pay no attention to the DTD beyond that). I doubt that a doctype
declaration
Patrice Dumas wrote:
On Sat, Dec 18, 2021 at 08:01:50PM -0600, Jacob Bachmeyer wrote:
I would suggest staying with HTML4; it is upwards compatible in that an
HTML5 parser should generally be able to read it, and the HTML4 DOCTYPE
actually declares a version, instead of the "eternal now"
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 possible to use only numeric
entities, with -c 'USE_NUMERIC_ENTITY 1', to add
On Wed, Dec 15, 2021 at 07:06:37PM +0100, Kurt Hornik wrote:
> Friends,
>
> In the discussions in the bug report for R, someone wrote
>
> calibre does not guarantee that an EPUB produced by it is valid. The
> only guarantee it makes is that if you feed it valid XHTML 1.1 + CSS
> 2.1 it
On Sat, Dec 18, 2021 at 08:01:50PM -0600, Jacob Bachmeyer wrote:
>
> I would suggest staying with HTML4; it is upwards compatible in that an
> HTML5 parser should generally be able to read it, and the HTML4 DOCTYPE
> actually declares a version, instead of the "eternal now" HTML5 uses. That
>
On Sat, Dec 18, 2021 at 03:46:20PM +, Gavin Smith wrote:
> On Fri, Dec 17, 2021 at 09:08:24AM +0900, Jean-Christophe Helary wrote:
> > Is there a place *now* where HTML4 is a requirement ? HTML5 is the only
> > *current* standard and does not specifically target web applications.
> >
>
> We
On Sat, Dec 18, 2021 at 10:01:53PM +0100, Patrice Dumas wrote:
>
> I'll do the code to generate XML, though I am still unsure whether it
> should be in the HTML converter directly or as an init file.
It was much easier in the HTML converter. It is actually a bit
cumbersome, but it works. To
On Sat, Dec 18, 2021 at 03:30:26PM -0800, Per Bothner wrote:
>
>
> On 12/18/21 14:20, Patrice Dumas wrote:
> > I tried that with the https://validator.w3.org/, also using .xhtml as
> > extension as it seems that it is what makes the w3c validator consider
> > that it is XML, with and without ,
On Sun, Dec 19, 2021 at 11:25:00AM +0900, Jean-Christophe Helary wrote:
>
>
> Sure, but Patrick is not (if I understand correctly) trying to have exported
> documents validate properly in general, but to have some kind of internal
> validation now while he develops the new output.
>
> Once
> "AMS" == Alfred M Szmidt writes:
AMS>On
AMS>(info "(texinfo) Footnote Styles")
AMS>(info "(texinfo) @paragraphindent")
AMS>mention how to unindent footnotes.
AMS>$ makeinfo --plaintext --set-customization-variable paragraphindent=0
AMS>doesn't work.
AMS> Your
> "GS" == Gavin Smith writes:
GS> On Sun, Dec 05, 2021 at 03:10:41AM +0800, 積丹尼 Dan Jacobson wrote:
>> Add a note to (info "(texinfo) @noindent")
>> mentioning why
>>
>> $ echo -e @indent\\n\\n|makeinfo --plaintext
>>
>>
>> $ echo -e @noindent\\n\\n|makeinfo --plaintext
>>
>>
On Sun, Dec 05, 2021 at 03:10:41AM +0800, 積丹尼 Dan Jacobson wrote:
> Add a note to (info "(texinfo) @noindent")
> mentioning why
>
> $ echo -e @indent\\n\\n|makeinfo --plaintext
>
>
> $ echo -e @noindent\\n\\n|makeinfo --plaintext
>
>
>
> give the same output. (Don't
On Sun, Dec 05, 2021 at 12:50:52AM +0800, 積丹尼 Dan Jacobson wrote:
> (info "(texinfo) Invoking texi2any") says
> '--no-number-footnotes'
> '--number-footnotes'
> Suppress automatic footnote numbering. By default, footnotes are
> numbered sequentially within a node, i.e., the current
On Sun, Dec 05, 2021 at 12:38:57AM +0800, 積丹尼 Dan Jacobson wrote:
> $ man makeinfo
>--fill-column=NUM
> break Info lines at NUM characters (default 72).
>
> Say columns, not characters. E.g., there will be less characters if they
> are fullwidth characters.
>
> $ makeinfo
On Sun, Dec 05, 2021 at 04:38:37AM -0500, Alfred M. Szmidt wrote:
> This should probobly fix it, untested.
>
> 2021-12-05 Alfred M. Szmidt
>
> * tp/texi2any.pl (makeinfo_help) <--output>: Fix indentation.
>
> diff --git a/tp/texi2any.pl b/tp/texi2any.pl
> index fa7cc7a42a..391d5f8fe4
On Sun, Dec 05, 2021 at 12:13:49AM +0800, 積丹尼 Dan Jacobson wrote:
> Here we see a second run of makeinfo --html has only updated the first file:
> $ ls -ogt
> -rw-r--r-- 1 1714 12-04 23:59 index.html
> -rw-r--r-- 1 2757 12-04 23:49 First-Chapter.html
> -rw-r--r-- 1 2327 12-04 23:49
> From: Gavin Smith
> Date: Sun, 19 Dec 2021 11:20:00 +
> Cc: Eli Zaretskii , Texinfo
>
> On Sun, Dec 19, 2021 at 10:56 AM Gavin Smith wrote:
> > I can try to make this work (it may be as simple as reinstating the
> > above lines) but can't promise anything as this is an extra
> >
> From: Gavin Smith
> Date: Sun, 19 Dec 2021 10:56:36 +
> Cc: Eli Zaretskii , Texinfo
>
> Do other programs from ezwinports not have the same issue with finding
> installed files?
Most of them don't. Some do, but support an environment variable that
can be sent to indicate that the tree
On Sun, Dec 19, 2021 at 10:56 AM Gavin Smith wrote:
> I can try to make this work (it may be as simple as reinstating the
> above lines) but can't promise anything as this is an extra
> complication above what is normally done with installed programs.
Done in commit c0c07af5f1. It appears to
On Sun, Dec 19, 2021 at 2:17 AM Nikolay Kudryavtsev
wrote:
>
> Yes "Can't locate Texinfo/ModulePath.pm" is the error message.
>
> Sorry, maybe I should have joined in and corrected immediately, but the
> latest working version is actually 6.5, not 6.6, I do not have a 6.6
> binary in my
On Sun, Dec 19, 2021 at 01:34:12AM +0100, Patrice Dumas wrote:
> Hello,
>
> Right now, USE_NUMERIC_ENTITY means
> For HTML and XML. If set, use numeric entities instead of ASCII
> characters when there is no named entity. By default, set to true
> for HTML.
>
> I think that it
On Sun, Dec 19, 2021 at 11:25:00AM +0900, Jean-Christophe Helary wrote:
> > HTML validation requires a DOCTYPE that specifies a DTD. XML validation
> > requires the "xmlns" declarations linking XML namespaces to schemas. HTML5
> > eschews any schema declaration at all because WHATWG (if I
On Sun, Dec 19, 2021 at 11:17:43AM +0900, Jean-Christophe Helary wrote:
> > I would suggest staying with HTML4; it is upwards compatible in that an
> > HTML5 parser should generally be able to read it, and the HTML4 DOCTYPE
> > actually declares a version, instead of the "eternal now" HTML5
24 matches
Mail list logo
