it means that you want to use native UTF-8 support in my humble opinion.
Not necessarily. The problem isn't encodings, it's fonts. The two
things are intimately and fundamentally tied together, and that cannot
be escaped.
By switching to native UTF-8, the support in texinfo.tex for characte
> Thanks for preparing the test files. Experimenting, I found it wasn't
> related to the character encoding problem, because removing the
> \directlua code made no difference.
>
> I got it down to the following:
>
[...snip...]
>
> This discussion on the lualatex-dev mailing list suggested the pr
> Date: Thu, 14 Jan 2016 19:12:53 +
> From: Gavin Smith
> Cc: Texinfo , Ken Brown
>
> In ExtUtils::MM_Win32 the static library is passed
> directly as an argument to the linker, but that doesn't work for
> libtool. I'm not sure exactly of the reasons, but it gives a warning
> looking like
>
I'm inclined to add "-L$(PERL_INC) -lperl", with "-lperl" determined
from perl -V:libperl, with a special case for cygwin to change
"cygperl5_22.dll" into -lperl.
If the "-no-undefined" flag causes problems, anywhere else, removing
it would be indicated, as it's only needed for Windows. This likel
> Date: Thu, 14 Jan 2016 12:02:20 +
> From: Gavin Smith
> Cc: Texinfo , Ken Brown
>
> Could -no-undefined be included in PERL_EXT_LDFLAGS or similar when
> configure is run?
It's possible, but it becomes too much, I think. PERL_EXT_LDFLAGS can
be justified as some setting dependent on the
On 1/14/2016 7:02 AM, Gavin Smith wrote:
On 13 January 2016 at 20:09, Eli Zaretskii wrote:
Date: Wed, 13 Jan 2016 19:42:45 +
From: Gavin Smith
Cc: Texinfo
It would appear to be inappropriate to add the -no-undefined flag
unconditionally.
Then we should do so conditionally, I guess. E.
On 13 January 2016 at 20:09, Eli Zaretskii wrote:
>> Date: Wed, 13 Jan 2016 19:42:45 +
>> From: Gavin Smith
>> Cc: Texinfo
>>
>> It would appear to be inappropriate to add the -no-undefined flag
>> unconditionally.
>
> Then we should do so conditionally, I guess. E.g., have a Make
> variabl
