public inbox for [email protected]
help / color / mirror / Atom feedFrom: Guillaume Lelarge <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Cc: Adrian Maier <[email protected]>
Subject: Re: Multi-language to be or not to be
Date: Mon, 12 Feb 2007 14:32:33 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
Magnus Hagander a ecrit le 12/02/2007 10:36:
> On Mon, Feb 12, 2007 at 10:16:10AM +0100, Peter Eisentraut wrote:
>> Am Montag, 12. Februar 2007 09:50 schrieb Magnus Hagander:
>>> Right. But will they rush to do that even if we have easier tools to do
>>> it?
>> I would love to translate some pages, but frankly anything short of a PO file
>> or some equivalent technology isn't going to excite any translators for long.
>
> A .po file is easier than a plaintext file? Well, I'm don't do much
> translating myself, but I can't see how translating a webpage can be
> easier than translating the actual text of the webpage in the file...
>
> (We do have .po files for the strings that come out of the PHP code
> directly)
>
> As for news and such, there's a web interface. Are you saying that's
> also too complex? Frankly, I don't see how a .po would make that better,
> but again I'm not used to working with these things.
>
Honestly, I didn't know there was a way to translate the main website.
Renaud Fortier and I did the translation on pgAdmin's website because
Dave told us it was possible. I think keeping the translation part of
the code is really necessary. I would be glad to provide a french
translation of the www.postgresql.org website. But I don't know how. And
a few days back, I didn't know we could do it. Is there a document
describing how to take care of this ?
Using po files is really easier when you don't have big pages or
documents. They are really useful for apps' translations and websites.
But they could be nightmare for things like manuals, books.
>>> There's also the question of wether it's a good thing to have a say 15%
>>> translated site, vs a 0% translated one. If we have a 15% translation,
>>> that will give a very strange impression for people going there with a
>>> browser set for that language - some pages come up in their language,
>>> the majority comes up in a completely different language.
>> By that theory, no translation of open-source software would ever take place.
>
> Well, I stand by that opinion. I know for examlpe pgAdmin only ships
> translations that are n percent or better (iirc, it's 85% or so), which
> makes it reasonable. Shipping something that only has 15% translation
> rate does the user a disservice, imho.
>
I agree on this. And it's really easy to get the percentage with po files.
Regards.
--
Guillaume.
view thread (52+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Multi-language to be or not to be
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox