[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
branch master updated: Use L<Locale::Messages> in POD instead of L<libin
From: |
Patrice Dumas |
Subject: |
branch master updated: Use L<Locale::Messages> in POD instead of L<libintl-perl> that does not exist |
Date: |
Sun, 27 Oct 2024 11:39:19 -0400 |
This is an automated email from the git hooks/post-receive script.
pertusus pushed a commit to branch master
in repository texinfo.
The following commit(s) were added to refs/heads/master by this push:
new 33977c7f1e Use L<Locale::Messages> in POD instead of L<libintl-perl>
that does not exist
33977c7f1e is described below
commit 33977c7f1e96aea090ac0bdd0b785c45ee08a254
Author: Patrice Dumas <pertusus@free.fr>
AuthorDate: Sun Oct 27 17:38:38 2024 +0100
Use L<Locale::Messages> in POD instead of L<libintl-perl> that does not
exist
---
doc/tp_api/api_includes/Texinfo-Common.texi | 2 +-
tp/Texinfo/Common.pm | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/tp_api/api_includes/Texinfo-Common.texi
b/doc/tp_api/api_includes/Texinfo-Common.texi
index 484305e05d..9d82a04139 100644
--- a/doc/tp_api/api_includes/Texinfo-Common.texi
+++ b/doc/tp_api/api_includes/Texinfo-Common.texi
@@ -188,7 +188,7 @@ only be used in user-defined code with translatable strings
already present in
the domain anyway. In fact, these functions are documented mainly because they
are automatically exported.
-See @url{https://metacpan.org/pod/libintl-perl, libintl-perl},
+See @url{https://metacpan.org/pod/Locale::Messages, Locale::Messages},
@url{https://www.gnu.org/software/gettext/manual/html_node/gettext.html,
@code{gettext} C interface},
@url{https://www.gnu.org/software/gettext/manual/html_node/Perl.html, Perl in
GNU Gettext}.
For translation of strings in output, see @ref{Texinfo@asis{::}Translations
NAME,, Texinfo::Translations}.
diff --git a/tp/Texinfo/Common.pm b/tp/Texinfo/Common.pm
index 8574b61399..e11b304943 100644
--- a/tp/Texinfo/Common.pm
+++ b/tp/Texinfo/Common.pm
@@ -2166,7 +2166,7 @@ only be used in user-defined code with translatable
strings already present in
the domain anyway. In fact, these functions are documented mainly because they
are automatically exported.
-See L<libintl-perl>,
+See L<Locale::Messages>,
L<C<gettext> C
interface|https://www.gnu.org/software/gettext/manual/html_node/gettext.html>,
L<Perl in GNU
Gettext|https://www.gnu.org/software/gettext/manual/html_node/Perl.html>.
For translation of strings in output, see L<Texinfo::Translations>.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- branch master updated: Use L<Locale::Messages> in POD instead of L<libintl-perl> that does not exist,
Patrice Dumas <=