Localization
Matt Read
locale repo similar to -extras, so the loco teams can have a place to
collaborate. I envision a repo structure similar to:
/locale
/habari
habari.pot (the current revision's PO Template)
/lang
/trunk
/LC_MESSAGES
/habari.po
/habari.mo
/files
any static files that need
translating, like manual
etc..
/branches
translations for branches
/tags
packaged translations for releases
and "langs" should be like en-us or en-ca or fr-ca, (lang-country code)
Owen Winkler
> To allow pepole to start translating habari, i think we should create a
> locale repo similar to -extras, so the loco teams can have a place to
> collaborate. I envision a repo structure similar to:
Can we add these directories to extras, or should there be a new repo
altogether?
Owen
Michael C. Harris
Speaking of -extras, what about theme and plugin translations?
--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
Matt Read
> Can we add these directories to extras, or should there be a new repo
> altogether?
we could have a locale folder in -extras, like plugin and themes. That
would be much simpler to maintain/setup than a whole new repo...
Matt Read
> Speaking of -extras, what about theme and plugin translations?
plugin and theme translations should be store in the locale folder for
the plugin or theme. see the Defensio plugin for an example..
also note the load_pluggable_domain call in defensio to load defensios
translations...
Scott Merrill
It looks like the Launchpad translations are well underway!
https://translations.launchpad.net/habari/trunk/+pots/habari
The following languages have translations in progress:
Arabic
Czech
Russian
Simplified Chinese
Traditional Chinese
Turkish
Should we plan to bundle completed translations with the core Habari
download, or should they remain an -extras download? My personal
preference is that we should consider bundling at least major
languages with the core download.
Cheers,
Scott
Michael C. Harris
>
> On Tue, May 6, 2008 at 10:58 PM, Matt Read <matt....@gmail.com> wrote:
> > > Can we add these directories to extras, or should there be a new repo
> > > altogether?
> >
> > we could have a locale folder in -extras, like plugin and themes. That
> > would be much simpler to maintain/setup than a whole new repo...
>
>
> It looks like the Launchpad translations are well underway!
> https://translations.launchpad.net/habari/trunk/+pots/habari
>
> The following languages have translations in progress:
> Arabic
> Czech
> Russian
> Simplified Chinese
> Traditional Chinese
> Turkish
Wow, that's awesome!
> Should we plan to bundle completed translations with the core Habari
> download, or should they remain an -extras download? My personal
> preference is that we should consider bundling at least major
> languages with the core download.
Bundling sounds like the right move to me.
rick c
Rick
On May 7, 8:57 am, "Michael C. Harris" <michael.twof...@gmail.com>
wrote:
>
Chris Starjive
One way to go is that setup tells you "That habari has other
translations" and let you download that specific "language pack" you
want, install it! and then the setup restarts and you install habari
in the correct language from a language-tab in the setup (similar to
how drupal works).
After that if the blog has multi-user etc i think habari should be
able to switch language for the user from the Admin > Options >
Presentation area. There you can now let the user switch languages to
what they prefer native lang or not "the only languages you can see
and switch to is what the admin/supervisor has installed on the \system
\locale\*.*". I think thats the correct way to go or whats make more
seens but thats how i see the big picture we all have other ways to
look at things.
But i prefer to have the habari pack so small as possible and clean.
and make others have the opportunity and choose to do what they want.
So my answer has now changed from 0 to -1
On May 7, 2:34 pm, "Scott Merrill" <ski...@skippy.net> wrote:
> > > Can we add these directories to extras, or should there be a new repo
> > > altogether?
>
> > we could have a locale folder in -extras, like plugin and themes. That
> > would be much simpler to maintain/setup than a whole new repo...
>
Owen Winkler
>
> One way to go is that setup tells you "That habari has other
> translations" and let you download that specific "language pack" you
> want, install it! and then the setup restarts and you install habari
> in the correct language from a language-tab in the setup (similar to
> how drupal works).
I think this is an essential part of our installation process.
Since the installer is in English to start off with, it would be ever so
elegant if it detected your language and used RemoteRequest to grab that
locale (if not already present on the server) from hp.o somewhere (maybe
directly from svn?) to at least display the installer in the correct (or
selectable) language and inform the user that they'll need to download
and install the locale files if they hadn't already.
Owen
Matthias Bauer
+1 on:
a) The installer should check the browser language and fetch the
appropriate translation. It should also offer a language selector for
the user to override the auto-detection.
b) The download could be customized with selectable translations.
c) Adding new languages later should be as easy as possible.
-Matt
Christian Mohn
> appropriate translation. It should also offer a language selector for
> the user to override the auto-detection.
Please don't make this automatic. Let there be a opt-in for this. I really
don't want our installer "phoning home" in any way unless the user wants it
to.
Christian
Graham Christensen
it enabled by default.
Graham Christensen
http://itrebal.com - Customized Web Hosting
Graham.Ch...@iamgraham.net
Owen Winkler
Then we'll need to solve the additional puzzle of localizing a string
("Download a language pack in {your language}") to the detected language
when the locale files for that language aren't installed.
Owen