Re: [bug #46083] DeclareUnicodeCharacter breaks if used twice for same character

2015-10-03 Thread Karl Berry
come up with for a tick was the radical sign. The lineless radical looks surprisingly ok to my eyes. I hadn't thought of that. Sounds fine. The complication is that we're not currently loading cmex at different sizes at all, so that will take some tweaking a la cmmi to do it right. Althoug

Re: @heading unaffected by @lowersections

2015-10-03 Thread Gavin Smith
On 30 September 2015 at 23:32, Quinn Grier wrote: > @heading and friends are unaffected by @lowersections. One would expect > the following to output Foo and Bar at the same sectioning level, as is > the case without the @lowersections command: > > \input texinfo > @setfilename test.in

Re: [bug #46083] DeclareUnicodeCharacter breaks if used twice for same character

2015-10-03 Thread Gavin Smith
On 2 October 2015 at 23:29, Oliver Heimlich wrote: > Please note that my definition of 2713 is wrong, because I couldn't > figure out how to produce a check mark in Tex. It depends on what glyphs are available in the fonts. The best I could come up with for a tick was the radical sign. test.dvi

Re: The defaults for Info

2015-10-03 Thread Gavin Smith
On 2 October 2015 at 07:35, Eli Zaretskii wrote: >> Date: Thu, 1 Oct 2015 21:14:17 GMT >> From: Karl Berry >> >> I find the File: and Node: parts of the hdr line the most useful. >> At least Node:, for sure, much more than the pointers. Go figure ... > > Actually, the "File:" and "Node:" parts a