Re: The defaults for Info

> 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 are redundant: they also appear in the mode line.

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

Karl, Gavin, thanks for your hints and suggestions. I understand that the DeclareUnicodeCharacter command is an internal command and I shouldn't have messed with it. However, without it I'd have waived PDF output. I believe the most simple (and sane) thing for me to do is this: @tex @ifcommandn

Re: The defaults for Info

I notice that the second line usually doesn't reach the start of the "Next:" text on the first line, so if the "File:" and "Node:" parts are hidden, it will usually fit on one line. I find the File: and Node: parts of the hdr line the most useful. At least Node:, for sure, much more th

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

To reiterate Gavin's reply ... 1. Any definitions for Unicode characters that you have that we don't have, and are supported in the CM fonts, we want to add. 2. I added the error check because it is too easy to make incorrect duplicate definitions within texinfo.tex itself. I did it more than on

Re: The defaults for Info

Hi Gavin, Hi Karl! Karl Berry ha escrit: > Personally, I detest all forms of terminal manipulation, be it reverse > video, underlining, fake bold, colorization, or what have you. For me, > all such things merely distract from reading the content, which is what > I'm interested in. (For me, thi

Re: @heading unaffected by @lowersections

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

@heading unaffected by @lowersections

@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.info @settitle test @lowersections @section Fo

Re: The defaults for Info

On 30 September 2015 at 22:40, Karl Berry wrote: > Personally, I detest all forms of terminal manipulation, be it reverse > video, underlining, fake bold, colorization, or what have you. For me, > all such things merely distract from reading the content, which is what > I'm interested in. (For m

[bug #46018] texi2any makes inconsistent EOL style

Update of bug #46018 (project texinfo): Open/Closed:Open => Closed ___ Reply to this item at: ___ Mes

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

On 30 September 2015 at 20:19, Oliver Heimlich wrote: > I have a manual for a free software package, which is written in utf-8 > encoding. Export to text/info/html works as expected, but I have to add the > following to be able to export it to pdf: > > > @tex > \DeclareUnicodeCharacter{00A0}{\ } >

[bug #45862] Texinfo manual does not compile with texi2pdf

Update of bug #45862 (project texinfo): Open/Closed:Open => Closed Status:None => Fixed ___ Reply to this item at:

[bug #46018] texi2any makes inconsistent EOL style

Update of bug #46018 (project texinfo): Status:None => Wont Fix ___ Follow-up Comment #6: As Eli said, there could be ways to handle it automatically, but we don't want the inconvenience

[bug #46007] texi2dvi Msys support

Update of bug #46007 (project texinfo): Open/Closed:Open => Closed Status:None => Fixed ___ Reply to this item at:

Re: The defaults for Info

Since you ask ... Personally, I detest all forms of terminal manipulation, be it reverse video, underlining, fake bold, colorization, or what have you. For me, all such things merely distract from reading the content, which is what I'm interested in. (For me, this is the case for everything, not

DeclareUnicodeCharacter breaks if called twice for same character

I have a manual for a free software package, which is written in utf-8. Export to text/info/html works as expected, but I have to add the following to be able to export it to pdf: @tex \DeclareUnicodeCharacter{00A0}{\ } … several other characters … @end tex This has worked for me for a while, but

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

URL: Summary: DeclareUnicodeCharacter breaks if used twice for same character Project: texinfo - GNU documentation system Submitted by: oheim Submitted on: Mi 30 Sep 2015 21:19:46 CEST