[wp-polyglots] translate.wordpress.org

Mon Feb 22 13:05:05 UTC 2010

Hi guys,

I think GlotPress is a very good idea but I agree with Mattias that
it's not quite mature. There's a lot of improvements that might be
introduced. I'd like to help with it, but my help is limited to my
ideas because I'm no developper. Maybe I can help with the interface.
But I think we should give it a try, because it's only when we use it
that it can be improved with the suggestions made by our own
experiences with it.

Back when the project started, José talked to me about it and I wrote
the following suggestions I believe are important:

Glossary - a system to create, integrate and manage a glossary
(add/change/delete terms and mark them when new/changed). This
glossary should be at hand, there should be a way to let the
translator know a term is in the glossary. And links to other
glossaries we should refer to. The translations Google provides are
too poor.

Consistency - a system to keep the translation consistent, in other
words, a system to help make a term always be translated the same way
across the projects, or the projects we chose, as I understand it, it
alows more than one version of the same po. I think it has to do with
Translation Memory, though it differ a little.

Orthography/grammar/style - After the deadline (I know it supports a
few languages yet) should be integrated.

Context - I think the filter 'file name in source' is fine, but it
would be helpful if the file name was shown somewhere in the header of
the page too, or right above the strings of that file.

Proof reading - this has to do with roles and permissions. When a
project is under proof reading it should be unavaillable for
translation for users other than the ones who are performing the proof
reading.

I guess some of these things are on Nikolay's mind already, so I have
great expectations on it!

Cheers
Cátia

> Message: 1
> Date: Sat, 20 Feb 2010 14:14:46 +0200
> From: Stas Su?cov <stas at nerd.ro>
> Subject: Re: [wp-polyglots] translate.wordpress.org
> To: wp-polyglots at lists.automattic.com
> Message-ID: <1266668086.19390.1.camel at rivalry.c7.campus.utcluj.ro>
> Content-Type: text/plain; charset="UTF-8"
>
> ?n data de Sb, 20-02-2010 la 10:41 +0200, Nikolay Bachiyski a scris:
>> On Fri, Feb 19, 2010 at 01:41, Mattias Tengblad <mst at eyesx.com> wrote:
>> > Hi,
>> >
>> > I agree with you Stas.
>> >
>> > I also think that we should leave svn repo's as the final production
>> > location with manual commit by team leaders.
>> >
>> > IMO, GlotPress got really good potential but is not yet quite mature as a
>> > main production location (I rather use poedit<->SVN for now).
>> >
>>
>> All the final translations should be in GlotPress. Of course, this
>> won't happen overnight. At least not before we have good enough tools
>> easy import and export translations.
>>
>> The subversion repository won't die. Currently it keeps not only
>> translations, but the dist/ folder, which will be ineffective to be
>> kept some place else.
>>
>> I understand that for a single developer GlotPress can be more of a
>> burden than help. I, myself, am doing the Bulgarian translation alone,
>> so I am personally interested to have a good way to sync the
>> translations in svn with GlotPress :-) It's neither impossible, not
>> even difficult problem.
>>
>> GlotPress should be the final production location, because it doesn't
>> have any theoretical limitations. If we have all the translations
>> there we can add translation suggestion interface in WordPress admin
>> panel, we can build and easily expose translation memories, we can do
>> incredibly smart validation checks. We can do anything. And we can't
>> do it if only some of the locales use it.
>>
>
> Heh,
> so the time will show.
> In Nikolay we (me) trust. ;)
>
>> Happy translating,
>> Nikolay.
>> _______________________________________________
>> wp-polyglots mailing list
>> wp-polyglots at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>
>
> --
> ()  Campania Panglicii ?n ASCII
> /\  http://stas.nerd.ro/ascii/
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 20 Feb 2010 14:25:18 +0000
> From: Jos? Fontainhas <jfontainhas at gmail.com>
> Subject: Re: [wp-polyglots] wp-polyglots Digest, Vol 61, Issue 10
> To: wp-polyglots at lists.automattic.com
> Message-ID:
>        <7e66c63e1002200625w5946a81apf00534bebeff40b2 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 19 February 2010 07:58, Fernando Tellado <info at fernandotellado.com> wrote:
>> I don't love glotpress a lot, but thanks for the great job
>
> Yes, you do. You just don't know it yet... :D
>
> Z
>
> Message: 5
> Date: Sun, 21 Feb 2010 02:01:58 +0100
> From: Mattias Tengblad <mst at eyesx.com>
> Subject: Re: [wp-polyglots] translate.wordpress.org
> To: wp-polyglots at lists.automattic.com
> Message-ID: <4B808606.2090602 at eyesx.com>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Hi,
>
> That makes it a bit clearer.
>
> The limitation of GlotPress right now, is in my mind the odd work flow.
> Like when you bubble click to translate a string the layout totally
> changes, which some what spoils the work flow. And I'm not to fond of
> the current language overview. (Maybe its just me).
>
> But I'm sure you're gonna make GlotPress as nice to work with as WordPress.

-- 
Cátia Kitahara
www.catiakitahara.com.br
www.wp-brasil.org