[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Website translation

From: Ludovic Courtès
Subject: Re: Website translation
Date: Fri, 23 Aug 2019 14:18:27 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)


"pelzflorian (Florian Pelz)" <address@hidden> skribis:

> On Thu, Aug 22, 2019 at 11:13:53PM +0200, Ludovic Courtès wrote:
>> > If this internationalization is to be deployed, the NGINX server
>> > offering would need to redirect according to
>> > Accept-Language headers.  I do not know if nginx alone can do this
>> > properly by now, otherwise there are Lua programs for nginx to handle
>> > Accept-Language or a custom Guile webserver could be written.
>> The nginx config is in guix-maintenance.git, but yeah, and I suspect
>> nginx alone can handle it.  We’ll see!
>> I haven’t reviewed in detail but the approach LGTM, so I’d be willing to
>> move forward on this.  Julien, sirgazil, Ricardo: WDYT?
> Then I will look at .guix.scm you mentioned (I did not notice that it
> exists) and continue adding translations to the other files.
> It would be nice if my code were simpler, but I do not know how and at
> least it works.

That’s OK.

>> We should make sure existing URLs are preserved.  Do you know if that’s
>> the case?
> Preserving URLs requires the above redirects based on the
> Accept-Language HTTP headers.

So /(.*) should be redirected to /en/\1, right?

>> Also, I suppose we don’t translate URI paths themselves, right?  That’s
>> probably OK, at least as a first version.
> I do not understand.

I mean “” could map to “”, for
instance.  That’s not the case, right?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]