Please have a look at
https://bugs.ghostscript.com/show_bug.cgi?id=708234
and the thread on the 'luatex' mailing list starting with
https://tug.org/pipermail/luatex/2025-January/008035.html
which discusses the problem that luatex creates invalid PDF outlines.
While some PDF viewers like `e
On Tue, Jan 07, 2025 at 10:55:31PM +0100, Patrice Dumas wrote:
> Actually, after more thinking, the case where translations would not be
> wanted by the user is too much of a special case to balance against
> warning that there won't be translations. I will implement a warning.
This is done.
> S
On Tue, Jan 07, 2025 at 10:37:27PM +0100, Patrice Dumas wrote:
> > If we can detect that the locale is stuck at C/POSIX and that therefore
> > translations are disabled, we could output a warning message.
>
> This could be done at the end of _switch_messages_locale. But do we want
> to do that un
On Tue, Jan 07, 2025 at 09:17:10PM +, Gavin Smith wrote:
> On Tue, Jan 07, 2025 at 09:30:16PM +0100, Patrice Dumas wrote:
> > As far as I can say, it is never possible to distinguish a lack of
> > translation and some kind of error in the gettext framework.
> >
> > In that precise case, if "lo
Hello,
An implementation of the texi2any main program in C is almost done. To
have the same features as the main program in Perl, a Perl interpreter
is embedded. I wanted to be able to control if an embedded Perl
interpreter is actually loaded with a command-line option. If
--no-embed-interpret
On Tue, Jan 07, 2025 at 09:30:16PM +0100, Patrice Dumas wrote:
> As far as I can say, it is never possible to distinguish a lack of
> translation and some kind of error in the gettext framework.
>
> In that precise case, if "locales -a" did not output a message, I also
> think that we should not o
On Tue, Jan 07, 2025 at 08:18:48PM +0100, Patrice Dumas wrote:
> On Tue, Jan 07, 2025 at 06:32:23PM +, Gavin Smith wrote:
> > Some comments are below:
> >
> > > First block:
> > >
> > >
> > > The defaults for the @if... conditionals depend on the output format:
> > > if generating Docboo
On Tue, Jan 07, 2025 at 07:46:29PM +, Gavin Smith wrote:
> On Tue, Jan 07, 2025 at 08:21:48PM +0100, Patrice Dumas wrote:
> > On Tue, Jan 07, 2025 at 06:55:33PM +, Gavin Smith wrote:
> > > That would succeed in suppressing the error messages from "locale", but
> > > it wouldn't make the str
On Tue, Jan 07, 2025 at 07:17:37PM +, Gavin Smith wrote:
> If I understand correctly the issue is with the "Index" link that
> is generated in the HTML output and that there is no way to configure
> which index this refers to.
>
> This could be allowed with two options:
> * One to suppress the
On Tue, Jan 07, 2025 at 08:21:48PM +0100, Patrice Dumas wrote:
> On Tue, Jan 07, 2025 at 06:55:33PM +, Gavin Smith wrote:
> > That would succeed in suppressing the error messages from "locale", but
> > it wouldn't make the strings be translated properly. In fact, the
> > error messages from "l
On Tue, Jan 07, 2025 at 06:55:33PM +, Gavin Smith wrote:
> That would succeed in suppressing the error messages from "locale", but
> it wouldn't make the strings be translated properly. In fact, the
> error messages from "locale" were useful in this case for investigating
> why the strings wer
On Tue, Jan 07, 2025 at 06:32:23PM +, Gavin Smith wrote:
> Some comments are below:
>
> > First block:
> >
> >
> > The defaults for the @if... conditionals depend on the output format:
> > if generating Docbook, --ifdocbook is on and the others are off;
> > if generating HTML, --ifhtml
On Tue, Jan 07, 2025 at 03:08:38AM +0100, Patrice Dumas wrote:
> On Mon, Jan 06, 2025 at 07:33:45AM +, Werner LEMBERG wrote:
> >
> > [texinfo 7.2]
> >
> >
> > The documentation in the 'Direction' section of 'texi2any_api' says
> >
> > _Index_
> >The first output unit with ‘@printi
On Tue, Jan 07, 2025 at 06:51:56PM +0100, Patrice Dumas wrote:
> On Tue, Jan 07, 2025 at 06:37:51PM +0100, Andreas Schwab wrote:
> > On Jan 07 2025, Patrice Dumas wrote:
> >
> > > I do not think that it can be fixed in texi2any, though, so it is
> > > probably best to leave the issue unresolved, s
On Tue, Jan 07, 2025 at 01:36:38PM +0100, Patrice Dumas wrote:
> Hello,
>
> As I reuse texi2any.pl help message parts in the C main program, I also
> resolve the pending reorganization of the messages to avoid \n in
> translated strings and split each line in a translatable string as far
> as poss
> Date: Tue, 7 Jan 2025 18:51:56 +0100
> From: Patrice Dumas
> Cc: Preuße, Hilmar , bug-texinfo@gnu.org
>
> > The message are coming from the locale program:
> >
> > $ LC_ALL=foo locale
> > locale: Cannot set LC_CTYPE to default locale: No such file or directory
> > locale: Cannot set LC_MESSAGE
On Tue, Jan 07, 2025 at 06:37:51PM +0100, Andreas Schwab wrote:
> On Jan 07 2025, Patrice Dumas wrote:
>
> > I do not think that it can be fixed in texi2any, though, so it is
> > probably best to leave the issue unresolved, since this is not a message
> > that texi2any output (unless I missed some
On Jan 07 2025, Patrice Dumas wrote:
> I do not think that it can be fixed in texi2any, though, so it is
> probably best to leave the issue unresolved, since this is not a message
> that texi2any output (unless I missed something).
The message are coming from the locale program:
$ LC_ALL=foo loc
Hello,
As I reuse texi2any.pl help message parts in the C main program, I also
resolve the pending reorganization of the messages to avoid \n in
translated strings and split each line in a translatable string as far
as possible as reported by Benno Schulenberg:
https://lists.gnu.org/archive/html
19 matches
Mail list logo
