> On 9 Sep 2022, at 02:53, Sam James wrote:
>
>
>
>> On 7 Sep 2022, at 04:50, Sam James wrote:
>>
>> * info/filesys.c: Ditto.
>> ---
>
> The GNU Emacs side of this change has landed:
> https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=6b7dc132afe99e1b12d32371b06021f64e95.
>
Ping
> This would lead to variant output between (dvi)-TeX, pdfTeX
> and possibly LuaTeX
>
> pdftex and luatex would normally have the same output. Any dvi engine,
> including xetex, would differ.
According to the table on page 6 in the current microtype package,
XeTeX *does* support characte
I am mainly unsure about if/how this should be turned on in Texinfo
files.
Just make it an option, say, @microtype on|off. Off by default. (And
forced to "off" when output is dvi.) That way it doesn't disturb
anyone. I would not advocate for it to be on by default.
This would lead
On Sat, Sep 17, 2022 at 02:28:08PM -0600, Karl Berry wrote:
> Hi Gavin. I've found that the microtype package for LaTeX
> (https://ctan.org/pkg/microtype) helps significantly in eliminating
> overfull lines without the need for rewriting text. (It also improves
> the esthetic appearance of the type
On Sat, 2022-09-24 at 13:48 +0100, Gavin Smith wrote:
> On Sat, Sep 24, 2022 at 01:39:47AM +, Tommy Nguyen wrote:
> > I am using texinfo-6.8-4.fc37.
> >
> > Hardened malloc[1] is a security focused malloc implementation.
> > According to them, crashes are usually bugs in the application
> > be
On Sat, Sep 24, 2022 at 01:39:47AM +, Tommy Nguyen wrote:
> I am using texinfo-6.8-4.fc37.
>
> Hardened malloc[1] is a security focused malloc implementation.
> According to them, crashes are usually bugs in the application because
> they are more strict than the glibc malloc. When running inf
