> Le 28 mai 2019 à 19:59, Bruno Haible a écrit :
>
> Support for a preference list of languages is part of the current web
> standards.
> [1]
Oh wow, weighted languages... It feels like language theory :)
Thanks, I had no idea.
> However, I'm not sure I prefer the web pages that do dynami
Akim Demaille wrote:
> However, such support from the web site itself
> is the surest way to be always up to date, even if you are on some old
> distro with a piece of software that was released many years ago.
Indeed.
> If there's really demand, they could also support this "path" of languages.
> Le 28 mai 2019 à 10:49, Bruno Haible a écrit :
>
> Hi Akim,
>
>> On the other end, it would be nice if the FSF supported something like
>> '?locale=CODE' or '?lang=CODE', as some sites do, as it would relieve us
>> from having to maintain some correspondance by hand.
>
> The only benefit t
s 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.
e 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.
Bruno
Hi Akim,
> On the other end, it would be nice if the FSF supported something like
> '?locale=CODE' or '?lang=CODE', as some sites do, as it would relieve us
> from having to maintain some correspondance by hand.
The only benefit that this syntax would have is that the PATTERN could be
derived fro
Hi Bruno,
> Le 28 mai 2019 à 00:07, Bruno Haible a écrit :
>
> Hi Akim,
> [...]
> Or maybe you have better ideas to solve this dilemma?
I would certainly not claim to have better ideas :)
You are looking for a generic way to deal with URLs that have alternatives for
languages. I was looking
; Aide globale sur les logiciels GNU : <https://www.gnu.org/gethelp/>
Good point. Yes, you are right, gettext or gnulib should provide a way to deal
with localized URLs.
Like with localized strings in PO files, we are merely looking for a
string -> string replacement that is localizable.
