After discussing this with Phillipe, I am of the opinion we take
translations and the efforts for them seriously and professionally.
So every translation to be labelled complete, means... it is 100%
translated.
Then, only when an language is 100% translated do we ship it with
Moovida.
This looks way more professional and might help drive some community
support to find out about their language and get involved (for
languages that are missing).
Jutta here at Fluendo is going to be doing some work on promoting or
setting up an initiative to help with this area.
This is purely my opinion and I am giving it out for discussion along
with your comments of course.
I am very much behind doing things professionally and making sure the
end product is of high quality.
Shipping half complete languages make us look 'half assed' :p
David
On 29 Jun 2009, at 13:17, Michał Sawicz wrote:
Hi
For some time now I've worked on making Moovida work well with Rosetta
(Launchpad Translations) [1] to simplify and speed up i18n efforts. We
now have a working tree that gets automagically imported into
https://translations.launchpad.net/elisa/1.0 for easy translation.
There are some questions to be asked, though.
a) how should a release process look in regards to i18n - what about
string freeze
b) should we use (display) incomplete translations
- the general consensus is that we should not
c) when (what percentage) a translation is recognized as incomplete
d) should we keep incomplete translations in-source or wait for them
to
be completed in Rosetta
e) should we change translation permissions to 'Structured' as was
suggested on IRC - read [2] for more info
f) should we ask some launchpad translation group to take care of
translations - we can't do all of them
- I've sent a question to Ubuntu Translation Coordinators group [3],
it was forwarded to Launchpad Translators group [4] which has quite a
smaller language base and I'm not completely sure what's the workflow
there...
g) should we upload and handle translation templates for external
plugins (apple_trailers, grooveshark, jamendo etc.) in the Elisa
translation project
h) should we work out a way to use fallback locales on a per-string
basis, only falling back from, say, 'de_CH' to 'de' for strings that
are
not translated for 'de_CH'
- that would mess up determining 'complete' from 'incomplete'
translations, though
i) how should we migrate translations ready in 0.5 [5]
- depending on what we decide in d) we could either import them and
commit in-source so that they would be picked up in Rosetta or upload
them by hand into 1.0 [1] and wait for them to be complete before
committing
I think I've run out of questions for now.
[1] https://translations.launchpad.net/elisa/1.0
[2] https://translations.launchpad.net/elisa/+changetranslators
[3] https://launchpad.net/~ubuntu-translation-coordinator
[4] https://translations.launchpad.net/+groups/launchpad-translators
[5] https://translations.launchpad.net/elisa/0.5
--
Michał Sawicz <[email protected]>
David McLeod
Senior Designer & UI Lead
Fluendo S.A.
World Trade Center Edificio Norte Pl.2
08039 BARCELONA SPAIN
Tel: +34 936 002 323
Skype: Daiode
Jabber/GMail: [email protected]
Email: [email protected]
