Internationalisation

[Florent Aide]

Hi all,

in our documentation we imply that TurboGears2 comes fully
internationalized. Either we should remove this info or we should make
sure it indeed is before the final release.

I'm not sure which road to follow here. Providing i18n'ized quickstart
is quite easy but will also mean making sure we don't change the
textual content of the quickstart pages and I'm not sure we're here
yet.

Mark? Others?

If/when we are ready to being the translations I'm ok to provide the
fr_FR po/mo files.

Florent.

[Jorge Vargas]

On Tue, Dec 16, 2008 at 2:07 AM, Florent Aide <floren...@gmail.com> wrote:
>
> Hi all,
>
> in our documentation we imply that TurboGears2 comes fully
> internationalized. Either we should remove this info or we should make
> sure it indeed is before the final release.
>

good point, even if everything is supported the quickstart should too.

> I'm not sure which road to follow here. Providing i18n'ized quickstart
> is quite easy but will also mean making sure we don't change the
> textual content of the quickstart pages and I'm not sure we're here
> yet.
>

Maybe we should just set a date after no more changes to the text are
done, like real translation teams and stuff :)

> Mark? Others?
>
> If/when we are ready to being the translations I'm ok to provide the
> fr_FR po/mo files.
>

I guess I could do the ES one.

> Florent.
>
> >
>

[Lukasz Szybalski]

Which files would need to be modified. I once looked at that and I
noticed that tg1 had more languages. I wonder if we can copy that over
to tg2 if not what would need to be changed.

I can do PL.

Thanks,
Lucas

[Mark Ramm]

On Tue, Dec 16, 2008 at 9:03 AM, Jorge Vargas <jorge....@gmail.com> wrote:
>
> On Tue, Dec 16, 2008 at 2:07 AM, Florent Aide <floren...@gmail.com> wrote:
>>
>> Hi all,
>>
>> in our documentation we imply that TurboGears2 comes fully
>> internationalized. Either we should remove this info or we should make
>> sure it indeed is before the final release.
>>
> good point, even if everything is supported the quickstart should too.
>

Well, fully internationalized is different that fully translated, but
that's quibbling. What I think it critical is that we make it clear
that it's ready to go for internatinalization, not that everything is
already translated into multiple languages.

I think it's fair to say that most apps end up with a single language
interface, so while supporting internationalization is critical, I
don't know if we should delay the release for translation stuff.

On the other hand, we could set a text freeze date for the template
(end of next week?) and do some translations before 2.0 final. And I
don't think that would delay us too much.

--Mark

[Florent Aide]

On Tue, Dec 16, 2008 at 4:32 PM, Mark Ramm <mark.mch...@gmail.com> wrote:
>
> I think it's fair to say that most apps end up with a single language
> interface, so while supporting internationalization is critical, I
> don't know if we should delay the release for translation stuff.
>
> On the other hand, we could set a text freeze date for the template
> (end of next week?) and do some translations before 2.0 final. And I
> don't think that would delay us too much.

Agreed.

I still need someone to review the authentication page I created in
the quickstart templates...

Florent.

[Jorge Vargas]

Oh I forgot to mention that I check it out and it seems good to me. I
also tried a non-auth project and the page is gone.
I followed the instructions as a total noob and it works, I didn't
proof read it I'll do it now. Ok it seems good except one detail, it
still uses _require instead of allow_only I have fixed that in trunk.

> Florent.
>
> >
>

[Jorge Godoy]

We also have to be sure to distinguish that it is ready to have the Python parts internationalized and localized.

The dynamic JavaScript libraries that we use do not provide easy means for I18N and L10N (e.g. number support or gettext support).

--
Jorge Godoy     <jgo...@gmail.com>