On Thu, Feb 24, 2022 at 11:50:51PM +0100, Patrice Dumas wrote:
> Hello,
>
> I have some differences between the perl Parser and the XS parser for
> non ascii strings for extra values. The perl Parser seems to be ok.
>
> My feeling is that the strings are not properly decoded. An analysis,
> tha
Hello,
I have some differences between the perl Parser and the XS parser for
non ascii strings for extra values. The perl Parser seems to be ok.
My feeling is that the strings are not properly decoded. An analysis,
that may be completly off, is that SvUTF8_on should be called on
something, mayb
On Thu, Feb 24, 2022 at 07:40:21PM +, Gavin Smith wrote:
> >
> > To do something similar to the NonXS parser, one would need, maybe
> > in Texinfo/XS/parsetexi/end_line.c in end_line_misc_line around line
> > 1428, instead of fullpath = locate_include_file (text); text should be
> > converted
On Thu, Feb 24, 2022 at 07:40:21PM +, Gavin Smith wrote:
> > To do something similar to the NonXS parser, one would need, maybe
> > in Texinfo/XS/parsetexi/end_line.c in end_line_misc_line around line
> > 1428, instead of fullpath = locate_include_file (text); text should be
> > converted to th
On Fri, Feb 04, 2022 at 08:19:24AM +, Reißner Ernst wrote:
> Hello all,
> I know that texinfo offers some commands to document a function which can be
> used for various computing languages.
> One can document the signature: specify name of function, return variable and
> input parameters.
>
On Thu, Feb 24, 2022 at 02:33:11PM +0100, Patrice Dumas wrote:
> It fixes the NonXS parser (I modified where it is done, such as to do it
> it before locate_include_file but kept your code), but not for the XS
> parser. In the XS parser, the @include file name is converted to utf-8
> upon reading.
On Thu, Feb 24, 2022 at 05:14:22PM +, Gavin Smith wrote:
> > I am not sure about the best way to fix this, maybe move the relevant
> > parts of Texinfo::XSLoader in Texinfo/XS/TestXS.pm, or have fallback
> > values for $Texinfo::ModulePath::texinfo_uninstalled and
> > $Texinfo::ModulePath::buil
On Thu, Feb 24, 2022 at 01:50:15PM +0100, Patrice Dumas wrote:
> Hello,
>
> A ./configure in a devel pristine source shows
>
> Can't locate Texinfo/ModulePath.pm in @INC (you may need to install the
> Texinfo::ModulePath module) (@INC contains: . ../..
> /home/dumas/perl5/lib/perl5//x86_64-linu
On Wed, Feb 23, 2022 at 07:31:52PM +, Gavin Smith wrote:
>
> I think there is some misunderstanding here. The filenames are decoded
> when read from the file according to the document encoding, and when the
> error messages are printed, the locale encoding is used. All this is
> separate to
Hello,
A ./configure in a devel pristine source shows
Can't locate Texinfo/ModulePath.pm in @INC (you may need to install the
Texinfo::ModulePath module) (@INC contains: . ../..
/home/dumas/perl5/lib/perl5//x86_64-linux-gnu-thread-multi
/home/dumas/perl5/lib/perl5/
/home/dumas/src/mini_ker_in
Hello Jacob,
Reißner Ernst wrote:
[...]
All of these markup is not presentational like @table, it is content
markup, descriptive or even procedural. It allows other tools not
only to render, but to analyze and to verify.
I also strongly disagree that this kind of markup is really language
spe
11 matches
Mail list logo