() Patrice Dumas
() Tue, 12 Feb 2013 01:01:40 +0100
I cannot reproduce that. Using fr_FR.UTF-8 I get something correct.
I attach the result.
> which looks funny and is incorrect -- i don't know what the "proper"
Looks like something doubly encoded.
Hmm, maybe my locales are miscon
Hi Karl, hi all,
we got a bug report concerning (g)info segfaulting in big terminals.
I can reproduce it here with 95 and 96.
I build .96 and run it under the debugger, and got the following
backtrace, the free segfault is in
(maybe_)free (window->log_line_no);
Program received signal S
On Mon, Feb 11, 2013 at 06:04:40PM +0100, Thien-Thi Nguyen wrote:
> With an input file ixin.texi that has the (incorrect) line 545:
>
> @fonttextsize 42
>
> and env var ‘LANG’ having the value ‘it_IT.UTF-8’, the command:
>
> $ /tmp/a/b/c/bin/makeinfo -o ixin.xml --xml --no-split ixin.texi > BA
Follow-up Comment #2, bug #38168 (project texinfo):
It shouldn't be too bad if limited to --where, at least for starters?
Anyway, please hold off on committing anything (just in case), since I think
we're about to make the release.
___
Re
With an input file ixin.texi that has the (incorrect) line 545:
@fonttextsize 42
and env var ‘LANG’ having the value ‘it_IT.UTF-8’, the command:
$ /tmp/a/b/c/bin/makeinfo -o ixin.xml --xml --no-split ixin.texi > BAD-$LANG
2>&1
produces the file BAD-it_IT.UTF-8, attached here:
BAD-it_IT.UT
Update of bug #38168 (project texinfo):
Assigned to:None => gray
Status:None => In Progress
___
Follow-up Comment #1:
Somehow I have miss