> According to the table on page 6 in the current microtype
> package, XeTeX *does* support character protrusion!
>
> I said that in my first mail. XeTeX supports protrusion,
I missed that, sorry.
> but (unfortunately) not expansion. In my experience, protrusion has
> little effect;
Hi Gavin,
I've committed the code and set it on by default. It is controlled
by @microtype on|off.
Thanks!!
makes me suspect that special treatment of @example and @verbatim
may not be required,
I'm pretty sure it is.
as these environments are not filled and lines
Hi Werner,
According to the table on page 6 in the current microtype package,
XeTeX *does* support character protrusion!
I said that in my first mail. XeTeX supports protrusion, but
(unfortunately) not expansion. In my experience, protrusion has little
effect; expansion is where the
On Sun, Sep 25, 2022 at 11:36:02AM +0100, Gavin Smith wrote:
> Still to do:
> * Documentation
> * Stub implementation in texi2any (doesn't need to do anything for
> any other output format).
Patrice has taken care of texi2any and I've added some documentation,
so all that is left now is XeTeX and
Hello,
I have noticed that there are inconsistencies between texi2any and
Texinfo TeX for leading spaces in some brace commands. It is not such a
big deal, we avoid being too detailed on formatting expectations, but it
would be better if the best option and maybe something more consistent
was
On Sat, Sep 24, 2022 at 03:18:07PM -0600, Karl Berry wrote:
> 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
>
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,10 @@
> +2022-09-07 Sam James
> +
> + * install-info/install-info.c: Recognize .zst file
> + extension from the zstd compression tool.
> +
> + * info/filesys.c: Ditto.
> +
> 2022-09-05 Gavin Smith
>
I've commited the change
