Re: Change the recommended first line? (was: texinfo should support Emacs coding specifier)

2015-12-29 Thread Gavin Smith
On 28 December 2015 at 23:42, Karl Berry wrote: > Gavin: the idea is that the stuff between **{start,end} of header are > copied to a temp file, followed by the region, and then the texinfo > formatter (texinfmt/makeinfo/whatever) is called on the temp file. > > This was invented by Chassell and/o

Re: Change the recommended first line? (was: texinfo should support Emacs coding specifier)

2015-12-28 Thread Karl Berry
These lines are still useful if ... Maybe the Texinfo "header" concept is still used with makeinfo-region, which is presumably still usable? Not that I've tried it in many years. Gavin: the idea is that the stuff between **{start,end} of header are copied to a temp file, followed by the regi

Re: Change the recommended first line? (was: texinfo should support Emacs coding specifier)

2015-12-27 Thread Eli Zaretskii
> Date: Sun, 27 Dec 2015 13:07:56 + > From: Gavin Smith > Cc: Mathieu Lirzin , Texinfo > > Do you know whether the lines > > @c %**start of header > > and > > @c %**end of header > > are still useful for anyone? The manual says > > The @code{@@c ...header} lines above which surround the

Re: Change the recommended first line? (was: texinfo should support Emacs coding specifier)

2015-12-27 Thread Gavin Smith
On 27 December 2015 at 03:38, Eli Zaretskii wrote: >> Date: Sat, 26 Dec 2015 20:56:37 + >> From: Gavin Smith >> Cc: Texinfo > Emacs automatically enters Texinfo mode for *.texinfo, *.texi, and > *.txi files, so it's okay to omit the mode cookie for those. But any > other Texinfo file still

Re: Change the recommended first line? (was: texinfo should support Emacs coding specifier)

2015-12-26 Thread Eli Zaretskii
> Date: Sat, 26 Dec 2015 20:56:37 + > From: Gavin Smith > Cc: Texinfo > > On 26 December 2015 at 18:58, Mathieu Lirzin wrote: > > Hi, > > > > In the texinfo manual we can read this: > > > > --8<---cut here---start->8--- > > Every Texinfo file that is to b

Re: Change the recommended first line? (was: texinfo should support Emacs coding specifier)

2015-12-26 Thread Gavin Smith
On 26 December 2015 at 18:58, Mathieu Lirzin wrote: > Hi, > > In the texinfo manual we can read this: > > --8<---cut here---start->8--- > Every Texinfo file that is to be the top-level input to TeX must begin > with a line that looks like this: > > \input t

Change the recommended first line? (was: texinfo should support Emacs coding specifier)

2015-12-26 Thread Mathieu Lirzin
Hi, In the texinfo manual we can read this: --8<---cut here---start->8--- Every Texinfo file that is to be the top-level input to TeX must begin with a line that looks like this: \input texinfo @c -*-texinfo-*- --8<---cut here---

Re: texinfo should support Emacs coding specifier

2015-12-26 Thread Eli Zaretskii
> Date: Sat, 26 Dec 2015 12:00:53 + > From: Gavin Smith > Cc: Per Bothner , Texinfo > > >> "The '@documentencoding' command declares the input document encoding, > >> and can also affect the encoding of the output." > > > > A plain-ASCII document could produce a UTF-8 encoded Info manual, no

Re: texinfo should support Emacs coding specifier

2015-12-26 Thread Gavin Smith
On 26 December 2015 at 11:49, Eli Zaretskii wrote: >> Date: Sat, 26 Dec 2015 11:01:15 + >> From: Gavin Smith >> Cc: Per Bothner , Texinfo >> >> On 26 December 2015 at 10:58, Eli Zaretskii wrote: >> >> If the duplication of the encoding information is a problem, maybe the >> >> Emacs mode fo

Re: texinfo should support Emacs coding specifier

2015-12-26 Thread Eli Zaretskii
> Date: Sat, 26 Dec 2015 11:01:15 + > From: Gavin Smith > Cc: Per Bothner , Texinfo > > On 26 December 2015 at 10:58, Eli Zaretskii wrote: > >> If the duplication of the encoding information is a problem, maybe the > >> Emacs mode for Texinfo could recognize a "@documentencoding" command. >

Re: texinfo should support Emacs coding specifier

2015-12-26 Thread Gavin Smith
On 26 December 2015 at 10:58, Eli Zaretskii wrote: >> If the duplication of the encoding information is a problem, maybe the >> Emacs mode for Texinfo could recognize a "@documentencoding" command. > > But @documentencoding doesn't necessarily mean the file is in that > encoding, does it? I thoug

Re: texinfo should support Emacs coding specifier

2015-12-26 Thread Eli Zaretskii
> Date: Sat, 26 Dec 2015 10:38:45 + > From: Gavin Smith > Cc: Texinfo > > If the duplication of the encoding information is a problem, maybe the > Emacs mode for Texinfo could recognize a "@documentencoding" command. But @documentencoding doesn't necessarily mean the file is in that encodin

Re: texinfo should support Emacs coding specifier

2015-12-26 Thread Gavin Smith
On 25 December 2015 at 23:22, Per Bothner wrote: > There is an Emacs standard for specifying the character encoding of a file, > by putting 'coding: ENCODING' in the mode specifier. > The texinfo specification should follow this standard; it is extra > weird to not do so when the texinfo specifica

texinfo should support Emacs coding specifier

2015-12-25 Thread Per Bothner
There is an Emacs standard for specifying the character encoding of a file, by putting 'coding: ENCODING' in the mode specifier. The texinfo specification should follow this standard; it is extra weird to not do so when the texinfo specification does require a mode declaration. I.e. following fi