[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: different encodings for input and output file names and command line
From: |
Gavin Smith |
Subject: |
Re: different encodings for input and output file names and command line |
Date: |
Tue, 1 Mar 2022 19:48:14 +0000 |
On Tue, Mar 01, 2022 at 01:42:50AM +0100, Patrice Dumas wrote:
> I commited an implementation. The XS parser part is incomplete, I coded
> passing the informations, but not using the information, for instance in
> encode_file_name(). Also encode_file_name() should be used for CPP file
> directive, as I reported in another mail.
I'm testing a change for #line directives.
I found a possible bug with #line:
$ cat test.texi
\input texinfo
#line 100 "foo.ptexi"
@gggg
aaa
@bye
$ ../texi2any.pl test.texi
test.texi:5: unknown command `gggg'
$ cat test2.texi
\input texinfo
@node Top
@top
#line 100 "foo.ptexi"
@gggg
aaa
@bye
$ ../texi2any.pl test2.texi
foo.ptexi:102: unknown command `gggg'
It looks like it has to be inside a node to work.
- Re: different encodings for input and output file names and command line,
Gavin Smith <=