From: Akim Demaille <akim@lrde.epita.fr>
To: Bruno Haible <bruno@clisp.org>
Cc: Gnulib bugs <bug-gnulib@gnu.org>, John Darrington <jmd@gnu.org>
Subject: Re: localized URLs
Date: Tue, 28 May 2019 18:30:43 +0200 [thread overview]
Message-ID: <32089E84-3495-441C-873D-5324CEB0F9ED@lrde.epita.fr> (raw)
In-Reply-To: <3127494.Aj9ckBhTiW@omega>
Hi Bruno,
> Le 28 mai 2019 à 10:55, Bruno Haible <bruno@clisp.org> a écrit :
>
> Akim Demaille wrote:
>> I don't think errors in URL translations are more serious that plain errors
>> in the translations (I fixed some of them in my own language that were even
>> conveying incorrect semantics), or delicate pieces of text such as the GPL
>> disclaimer excerpt.
>
> That's not the point. The point is:
>
> 1) When translators are requested to translate an URL, they would manually
> do something that an automated script can do just as well.
I'm not sure a script can cover all the cases, but I'm fine with this approach,
of course.
> The linguistic
> expertise of the translators is not exploited.
If all the pages we want to map to strictly follow some unique pattern,
yep.
> 2) It is perfectly normal for translators to not update a PO file in 3 years.
> But a translated URL can appear (or disappear); the translator would not
> be made aware of it.
>
> In summary, localized URLs require another workflow than localized text.
Yes, indeed.
prev parent reply other threads:[~2019-05-28 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 8:05 version-etc.c: about "Do not include URLS in translatable strings" Akim Demaille
2019-05-26 8:19 ` Akim Demaille
2019-05-27 22:07 ` localized URLs Bruno Haible
2019-05-28 6:44 ` Akim Demaille
2019-05-28 8:49 ` Bruno Haible
2019-05-28 16:37 ` Akim Demaille
2019-05-28 17:59 ` Bruno Haible
2019-05-28 18:41 ` Akim Demaille
2019-05-28 8:55 ` Bruno Haible
2019-05-28 16:30 ` Akim Demaille [this message]
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32089E84-3495-441C-873D-5324CEB0F9ED@lrde.epita.fr \
--to=akim@lrde.epita.fr \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=jmd@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).