From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
Cc: emacs-devel@gnu.org, vincent.b.1@hotmail.fr, stefankangas@gmail.com
Subject: Re: Where to contribute manual translations ? (Re: Emacs-devel Digest, Vol 238, Issue 29)
Date: Fri, 29 Dec 2023 08:48:51 +0200 [thread overview]
Message-ID: <838r5d7bcc.fsf@gnu.org> (raw)
In-Reply-To: <AFA2B042-1B5F-4601-96ED-74BBF0621CED@traductaire-libre.org> (message from Jean-Christophe Helary on Fri, 29 Dec 2023 01:23:40 +0000)
> Date: Fri, 29 Dec 2023 01:23:40 +0000
> From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
> Cc: vincent.b.1@hotmail.fr, stefankangas@gmail.com, eliz@gnu.org
>
> >> Another question : how to internationalize docstrings ? IMHO it would be great if the docstring could have some info manual anchor in it, and one could display it from the currently selected language manual. Besides, reading docstring from manual via some anchor is basically what Calc does with some kitchen tricks.
> >
> > Eli answered that.
>
> There is also a different issue, that comes before translation, it is fixing user facing strings, so that they can eventually be translated one day. I also made a presentation on that at EmacsConf 2022:
> https://emacsconf.org/2022/talks/localizing/
I believe this issue was also raised in the discussions whose pointers
I provided. AFAIR, this issue is a much harder one, since
manipulating such strings is pervasive in Emacs, and mostly in Lisp,
not in C.
next prev parent reply other threads:[~2023-12-29 6:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.35.1703782806.25325.emacs-devel@gnu.org>
2023-12-29 0:24 ` Where to contribute manual translations ? (Re: Emacs-devel Digest, Vol 238, Issue 29) Jean-Christophe Helary
2023-12-31 3:15 ` Richard Stallman
2023-12-31 3:29 ` Jean-Christophe Helary
2024-01-02 3:20 ` Richard Stallman
2024-01-02 3:24 ` Stefan Kangas
2024-01-02 3:32 ` Eli Zaretskii
2023-12-31 7:38 ` Eli Zaretskii
2023-12-29 1:23 ` Jean-Christophe Helary
2023-12-29 6:48 ` Eli Zaretskii [this message]
2023-12-29 14:21 ` Jean-Christophe Helary
2023-12-29 22:58 ` Vincent Belaïche
2023-12-30 1:33 ` Jean-Christophe Helary
2023-12-29 7:10 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838r5d7bcc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traductaire-libre.org \
--cc=stefankangas@gmail.com \
--cc=vincent.b.1@hotmail.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.