On Sat, Nov 02, 2024 at 11:43:44AM +, Werner LEMBERG wrote:
>
> [texinfo.tex 2024-11-01.22]
>
>
> > Thanks for the quick fix!
>
> Unfortunately, your fix is buggy; it swallows the space after the
> quotation mark.
>
> ```
> \input texinfo
>
> c’’ a
>
> @bye
> ```
I belive it is because
[texinfo.tex 2024-11-01.22]
> Thanks for the quick fix!
Unfortunately, your fix is buggy; it swallows the space after the
quotation mark.
```
\input texinfo
c’’ a
@bye
```
Werner
> I found the following in the LuaTeX manual:
>
> See chapter 5 for many small changes related to paragraph
> building, language handling and hyphenation. The most important
> change is that adding a brace group in the middle of a word (like
> in of{}fice) does not prevent ligature creatio
On Fri, Nov 01, 2024 at 06:55:56AM +, Werner LEMBERG wrote:
>
> Consider this input file (the second line uses U+2019).
>
> ```
> \input texinfo
>
> c
>
> c
>
> @bye
> ```
>
> If processed with pdftex (or xetex), everything's fine. In the first
> line, gets resolved into two
>> So we now encourage not to use @documentencoding at all if it's UTF-8?
>
> Indeed.
It doesn't sound to my ears that the manual 'encourages' to not tag a
file with `@documentencoding`. However, it is no longer necessary
since more than five years.
Werner
On Fri, Nov 01, 2024 at 03:45:43PM +0200, Eli Zaretskii wrote:
> So we now encourage not to use @documentencoding at all if it's UTF-8?
Indeed.
https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#g_t_0040documentencoding
"In the default case, the input and output document encoding a
> Date: Fri, 1 Nov 2024 13:19:20 +0100
> From: Patrice Dumas
> Cc: Werner LEMBERG , bug-texinfo@gnu.org
>
> On Fri, Nov 01, 2024 at 02:03:13PM +0200, Eli Zaretskii wrote:
> > > Date: Fri, 01 Nov 2024 08:42:50 + (UTC)
> > > Cc: bug-texinfo@gnu.org
> > > From: Werner LEMBERG
> > >
> > > > Sho
On Fri, Nov 01, 2024 at 02:03:13PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 01 Nov 2024 08:42:50 + (UTC)
> > Cc: bug-texinfo@gnu.org
> > From: Werner LEMBERG
> >
> > > Shouldn't you use @documentencoding if you include UTF-8 encoded
> > > characters verbatim? (I have no idea if that affect
> Date: Fri, 01 Nov 2024 08:42:50 + (UTC)
> Cc: bug-texinfo@gnu.org
> From: Werner LEMBERG
>
> > Shouldn't you use @documentencoding if you include UTF-8 encoded
> > characters verbatim? (I have no idea if that affects the problem.)
>
> UTF-8 is meanwhile the default encoding.
In what vers
> Shouldn't you use @documentencoding if you include UTF-8 encoded
> characters verbatim? (I have no idea if that affects the problem.)
UTF-8 is meanwhile the default encoding.
Werner
> Date: Fri, 01 Nov 2024 06:55:56 + (UTC)
> From: Werner LEMBERG
>
> Consider this input file (the second line uses U+2019).
>
> ```
> \input texinfo
>
> c
>
> c
>
> @bye
> ```
>
> If processed with pdftex (or xetex), everything's fine. In the first
> line, gets resolved in
11 matches
Mail list logo
