On Tue, Mar 1, 2011 at 02:07, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 2/28/11 1:39 AM, Magnus Hagander wrote:
>> We know from experience that this tends to not work. You'll end up
>> with partial translation and out-of-date translations. We tried it,
>> and failed. Then we tried the separate-site (both the french and the
>> japanese, and I think also the brazilians?) and it has worked really
> To be fair, I don't know that there was ever a serious effort to get the
> website translated. AFAIK, the code to do so was *always* broken. I
Not really. Particularly, translating news and events once worked.
> think it's fairly likely that we'd get partial, out-of-date translations
> anyway, but we don't actually have any history here to speak of.
s/fairly likely/absolutely guaranteed/
We don't even have the resources to keep up with *moderation* all the
time. We don't have anywhere near the resources to do near-real-time
And IMNSHO, an out-of-date translation is *way* worse than no
translation at all.
> Presumably when we move to Django, we can use its built-in multilingual
> stuff, no?
No. And yes.
There is no magic in django. It has a framework, but you hav eto write
the code to actually use it. We decided not to write that code at all
this time, since there has been zero actual demand (from people who
would do the translation) once the potential requestor realized what
the work actually means.
In response to
pgsql-www by date
|Next:||From: Alvaro Herrera||Date: 2011-03-01 19:25:53|
|Subject: Re: .oO - Translation|
|Previous:||From: Alvaro Herrera||Date: 2011-03-01 13:15:46|
|Subject: Re: Top five challenges|