[Phpwiki-talk] Re: Patch: internationalisation with php3 fallback [Was: ...]

[Jan N. <ja...@gn...>]

On Sunday, 1 October 2000, Arno Hollosi writes:

> So I installed the gettext package and your script runs ok now.
> Ok, maybe we should use gettext to automatically produce files
> for the translators. But I would still use hash-tables for phpwiki
> (generated automatically from those .po files if you like).
>
> Apart from avoiding duplicate information (.mo and .php3 files) and being 

Ok, that's a valid reason.  A reason to use gettext tools would be
that you could have them translated by the GNU translation project.
However, maybe that's all a bit overdone, because there are so few
strings in php code...

> How can you have per-visitor localization?

 [snip -- would be real cool]

> Or is this feature too far off the mark?

Yes, I pondered about that too, esp. wrt to the RecentChanges page.
I don't think it would be worth the effor: you'd get 'EditText'
instead of 'VeranderText' when you visit a dutch wiki, but all
pages would still be in dutch.  I think localisation on a per-wiki
basis would be ok.

> On a side note: I think all files for translators should be moved into
> a "translator" directory: currently that is translate.sh and the files in the
    +  
> po directory. That way one can easily delete stuff unnecessary for running 
> the wiki.

Otoh, it's non standard, so people might wonder how it all works.

> And I don't understand why we need wiki_linguas.php3. Either the pagename 

Duh.  I think that I goofed on that one.  It's probably that I kept
seeing things like EditText, before I translated the templates.
It would be good if the templates were gettextised too, so that there'd
only be the .po's and the pgsrc's.

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <ja...@gn...> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org