Very good point about the plugins.
We know that the plugin information is very scarce and not exactly
detailed or informative. (in fact 'plugins' as a theme is going into
planning as something to really talk about in detail).
I think, demanding that any plugin at least be in english (the summary
of what it is/does) should be in English.
Then, in the plugin information screen we should state what languages
are supported.
Again those languages should be 100% complete for the plugin.
On 29 Jun 2009, at 14:00, Michał Sawicz wrote:
Dnia 2009-06-29, pon o godzinie 13:33 +0200, David McLeod pisze:
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.
Sure, I concur :)
We need then to update translations we have in source ASAP (only pl
and
fr are 100% complete) or take them out.
There's one thing we can have problems with - external plugins. Even
Fluendo-managed external plugins (apple_trailers, grooveshark,
jamendo...) are almost completely untranslated. This will mean that we
have complete translations of core Moovida UI but whenever we'll get
into any of these plugins, we'll be dropped into English.
Cheers
--
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]
