Re: microtype for texinfo

2022-09-27 Thread Karl Berry
kb> Regarding typewriter: I reiterate the need to turn it off for display kb> environments. On second thought, for the LaTeX backend, I can see how it would be better to simply take the default, that is, \usepackage{microtype}, and let it be as it is. Going along with "make a natural LaTeX docume

Re: microtype for texinfo

2022-09-27 Thread Karl Berry
If the output is better with microtype on, we should try to have it on. If Texinfo has microtype on by default, I agree the LaTeX backend should also have microtype on by default. That's fine. microtypee off if is causes issues in LaTeX output, Are you talking about the typewriter thing

Re: microtype for texinfo

2022-09-27 Thread Karl Berry
There is a new converter in texi2any of Texinfo to LaTeX, I didn't know. Cool! People have long wanted this. Mainly so they can change fonts. So I hope you will support that -- which I think amounts to allowing the user to add stuff to the preamble after your builtings. On my debian Ult

Re: microtype for texinfo

2022-09-27 Thread Gavin Smith
On Tue, Sep 27, 2022 at 09:38:30AM +0200, pertu...@free.fr wrote: > ... but my feeling is > that this is the symptom of something wrong being done with fonts > selection in the LaTeX output, not an issue with microtype as such. It is just a consequence of using T1 encoded fonts, which aren't used

Re: Info reader - issues finding first index entry

2022-09-27 Thread Charles Reilly
On 27/09/2022 6.58 pm, Gavin Smith wrote: On Tue, Sep 27, 2022 at 06:07:08PM +0100, Charles Reilly wrote: Hi, Using info I have had some issues with finding the first entry in the index. For example, try running "info gzip". The first entry in the concept index for gzip is "bugs". Some exampl

Re: leading and trailing spaces in brace commands

2022-09-27 Thread Gavin Smith
On Tue, Sep 27, 2022 at 09:26:15AM +0200, Patrice Dumas wrote: > > I'm not sure if it would be correct to ignore spaces for other commands: > > @math, @value, @verb... Almost every command could be different. It > > seems quite simple to say that these spaces are ignored for BRACE_arguments > > c

Re: Info reader - issues finding first index entry

2022-09-27 Thread Gavin Smith
On Tue, Sep 27, 2022 at 06:07:08PM +0100, Charles Reilly wrote: > Hi, > > Using info I have had some issues with finding the first entry in the index. > For example, try running "info gzip". The first entry in the concept index > for gzip is "bugs". Some example searches: > > ibugs - Succ

Info reader - issues finding first index entry

2022-09-27 Thread Charles Reilly
Hi, Using info I have had some issues with finding the first entry in the index. For example, try running "info gzip". The first entry in the concept index for gzip is "bugs". Some example searches: ibugs - Succeeds ibu - No entries containing 'bu'. Ibugs - No entries c

Re: leading and trailing spaces in brace commands

2022-09-27 Thread Patrice Dumas
On Mon, Sep 26, 2022 at 08:40:46PM +0100, Gavin Smith wrote: > On Sun, Sep 25, 2022 at 04:11:13PM +0200, Patrice Dumas wrote: > > I suggest, for texi2any > > * not to ignore spaces for indicating brace @-commands and @w (nothing > > changes for those commands) and also for the following list of @

Re: microtype for texinfo

2022-09-27 Thread pertusus
On Tue, Sep 27, 2022 at 06:59:10AM +0100, Gavin Smith wrote: > > As I said above, for the LaTeX output converted from Texinfo we use > > quite a few packages to be able to output LaTeX that can express the > > Texinfo formatting. > > It's not necessary to obey any of the formatting command for LaT