Re: texinfo macro names don't allow digits

2014-01-31 Thread Karl Berry
Hi Arnold, I admit to not checking, but if this isn't documented, it should be. It is. Along with approximately two zillion other caveats about @macro usage :). Also, I would suggest that makeinfo be modified to enforce this restriction as well. Historically, makeinfo's @macro has

Re: Displaying characters in user's locale

2014-01-31 Thread Gavin Smith
On Fri, Jan 31, 2014 at 8:01 AM, Eli Zaretskii wrote: > > It is true that characters which cannot be encoded in the terminal's > encoding should be replaced with something that still leaves the text > legible. However, many characters _can_ be encoded, and Info should > use libiconv for those. M

Re: docbook conversion issue: nesting of formatting

2014-01-31 Thread Eli Zaretskii
> From: Aharon Robbins > Date: Fri, 31 Jan 2014 15:00:31 +0200 > > The first issue has to do with nesting. Texinfo, like TeX, is quite > general about letting you nest one thing inside another. Docbook, > on the other hand, is quite picky and context sensitive. For example, > something like >

docbook conversion issue: nesting of formatting

2014-01-31 Thread Aharon Robbins
[ PLEASE cc me on all replies, as I'm not subscribed to this group. ] Hello all. It looks like I'm going to need to exercise the conversion of Texinfo to docbook, so you can expect to start hearing from me. :-) The first issue has to do with nesting. Texinfo, like TeX, is quite general about le

texinfo macro names don't allow digits

2014-01-31 Thread Aharon Robbins
Hi All. I recently discovered that texinfo macros should not have digits in their names, since texinfo.tex chokes on them. I admit to not checking, but if this isn't documented, it should be. Also, I would suggest that makeinfo be modified to enforce this restriction as well. Much thanks, Arno

Re: Improving standalone info usability

2014-01-31 Thread Sergey Poznyakoff
Hi. Karl Berry ha escrit: > In general, what you see as a defect ("notation for a computer"), I see > as a positive ("plain and simple text"), i.e., for me it's not broken > and doesn't need to be fixed. I guess I'm just too much of a dinosaur. For what it's worth, that's my feeling too. That

Re: Improving standalone info usability

2014-01-31 Thread Eli Zaretskii
> Date: Fri, 31 Jan 2014 00:25:36 + > From: Gavin Smith > Cc: bug-texinfo@gnu.org > > > P.S. Regarding your other work, on UTF-8 vs. ISO, it still seems to me > > that in principle this should be addressed at the terminal level, > > instead of every single cmdline application having to deal w