[Foresight-i18n] Restarting localisation team

[Thilo Pfennig]

Hi,
on the last developer meeting we also have decided on creation of a
new localization team. Tjios doesnt mean that anybody from the old
list in the wiki cant be on board, buit it was just me and Og Maciel
who volunteered to do some work. We do not yet have a team leader. But
maybe we can live without.

Here is my suggestion of what we do now:

Lets define the worst internationalisation and localisation issues in
Foresight and create issues in the JIRA issue tracker.

I also suggest that we try to define the current core languages.

Currently these could be: DE, PT/pt_BR, ES

Also we need to define which parts need localization. Maybe lets start
with a session. Iam am tagging witth MUST and SHOULD:

* So the computer boots and there is GRUB. Does GRUB need localization
or better the new boot system (whats that called again?) (SHOULD)

* I think the status messages during boot up do get translated (SHOULD)

* Login/GDM - Maybe we can make this more obvious. Whats the default
GDM theme now? (SHOULD)

* After logging in many things depend on GNOME. FF and TB shall be
translated in FL:2 doniphon said. OO.org is a big issue and is
something he is working on also. (SHOULD)

* Foresight help: There are a few localized chat channels channel -
question is if we should suggest people to use that instead of
#foresight. (SHOULD)
* Manuals: yes, manuals are there in english. Current manuals are
based on fl:1.4 - pcutler needs to start writing new docs for fl:2 so
here we are waiting on docs team. The FAQ also needs major reworks.
This is a SHOULD

* Anaconda Installer: I see this as a MUST for fl:2 stable - this
surely needs toi be localized in at least the 4 languages. We should
grab the needed sources as soon as possible and write down how
localization is handled.

* Core Foresight applications: I wish all major  applications for
listening to music, browsing the web,... have as much localization as
possible. For this I recommend to work closely with upstream. But this
is rather a SHOULD and a continuous process. I encourage everybody to
grab the POT files for the default applications and help upstream
projects to get them translated.

Please add you thoughts to this thread.

Also I invite everybody who reads this to state how you are going to
contribute. So that we know if we should depend/wait on you for a
specific language or if you just like to help here and there.

I think what we need is documentation for every possible localization.
Inside and outside of Foresight. So that people grab a HOWTO and can
start from scratch. I dont think we need big coordination - people
just need to know the deadlines for contribution - and then we just
can hope that most of what we want in will be there on time of the
release. So personally I think helping people to contribute is much
more important than forcing everybody into an organisation just to
make it more easy. We should, though give regular feedback on
progress. I would like to limit official supported languages at the
beginning so that we rather can say we have good support for 4
languages as if we have poor support for 30.

If somebody now steps up and says: I request this language to be added
and I will do it for sure I will be happy - if not I consider all
other contributions as a NICE TO HAVE. Which should make it easier for
us to move on.

I think everybody who wants to contribute to localization should
(rather must) read this list and we use this as our primary
coordination channel. Which is especially a good thing as on
localization we tend to live on different time zones.

So please reply to this list with your ideas and thoughts. I just
wanted to start this off in order to get a focus and agree on where we
start or what we need. We are a small distro and so we need to live
with reduced localization. If we get some things translated we are
good! ;-)

One other thing: I think the GNOME manuals are also a good way to
contribute to documentation and the fl 1.4 manual in that sense uses
less than possible. So in that sense I would encourage the docs team
to use more localized GNOME help so the localization team has less
work. I mean many aspects are covered already. And also its nice if
like I did with Epiphany handbook its then just part not only on
Foresight but on every distro using GNOME. Also we then get help from
other distros taht fix our docs. But there we need to communicate with
docs team.


Regards,

Thilo



-- 
Thilo Pfennig
http://issues.foresightlinux.org/confluence/x/R