> Date: Thu, 8 Oct 2015 21:08:11 +0100
> From: Gavin Smith
> Cc: Texinfo
>
> There is a new syntax for specifying an explicit sort key that was
> introduced after the Texinfo 6.0 release. It looks like
>
> @cindex @sortas{\ escape sequence} \
Hi. THanks for the mail. I moved to current development code for
texindex and braces are working. I note that hyphens and < signs
also get removed from the key for the index. Is that on purpose?
I can go ahead and add @sortas, but I'm wondering if I need to do
that also for the hyphen and the <
> many manuals have indexed items starting with a backslash that are
> better indexed under a letter following the backslash (an example from
> Texinfo's manual is \mathopsup, better indexed under "M").
I suppose this decision is already made, but I feel compelled to kibitz,
sorry:
On 2 October 2015 at 23:29, Oliver Heimlich wrote:
> On 03.10.2015 00:12, Karl Berry wrote:
>> \DeclareUnicodeCharacter{00A0}{\ }
>>
>> FWIW, A0 is supposed to be a no-break space. That's \tie, not "\ ".
>>
>> \DeclareUnicodeCharacter{03C0}{$\pi$}
>>
>> Can you please
> Date: Fri, 9 Oct 2015 16:39:14 +0100
> From: Gavin Smith
> Cc: Texinfo
>
> On 9 October 2015 at 08:06, Eli Zaretskii wrote:
> > So perhaps we should introduce a facility for such tests, and
> > preferably in a way that is itself
On 9 October 2015 at 08:06, Eli Zaretskii wrote:
> Btw, my usual problem with such new features is that it's impossible
> (AFAIK) to use them in a manual in a backward-compatible way,
> i.e. while making sure older versions of makeinfo will process the
> manual without errors.
On 9 October 2015 at 08:00, Aharon Robbins wrote:
> Hi. THanks for the mail. I moved to current development code for
> texindex and braces are working. I note that hyphens and < signs
> also get removed from the key for the index. Is that on purpose?
>
> I can go ahead and
> Date: Fri, 9 Oct 2015 11:48:44 +0100
> From: Gavin Smith
> Cc: Aharon Robbins , Texinfo
>
> On 9 October 2015 at 08:06, Eli Zaretskii wrote:
> > Btw, my usual problem with such new features is that it's
Update of bug #46083 (project texinfo):
Open/Closed:Open => Closed
Status:None => Wont Fix
___
Reply to this item at:
On 2015-10-09 02:06, Eli Zaretskii wrote:
Btw, my usual problem with such new features is that it's impossible
(AFAIK) to use them in a manual in a backward-compatible way,
i.e. while making sure older versions of makeinfo will process the
manual without errors. That's because there's no way
10 matches
Mail list logo