[geeklog-devel] Look-up Tables in GL2

[Vincent Furia]

Right now I'm leaning toward using the Translation2's gettext for
doing all the translation.  It's pretty smooth, very fast, and will
even work on PHP installs without gettext support (though obviously
not as quickly as with gettext support).  Another advantage is that
we'll be able to modify the translation files online via a web-based
administration tool.

I didn't want to go with database for a couple reasons.  If we went
the database root we'd have to do caching and other tricks for speed
or else performance would be really awful.  Also Translation2 only
supports PEAR::DB, which would mean a hassle since Propel only
supports Creole.  We'd either have to run with two DB abstraction
layers (really, really bad) or else port one or the other library to
the other DB layer (more work then I think any of us want to commit
two).  Besides that I don't see any big advantages to using the DB
over gettext.  If anyone knows of any please speak up now.

Also I encourage people to try out Translation2 if you get the chance.
 Though its not necessary, I think you'll get a kick out of how easy
it will make things.

</$.02>

-Vinny


On Mon, 13 Dec 2004 15:03:51 -0600, Tony Bibbs <tony at tonybibbs.com> wrote:
> Right now we plan on using Translation2 from PEAR.  They support using
> the database and gettext.  I'm not sure which we plan to favor...I was
> leaving that decision until Vinny finishes taking a look at it.   Also I
> think Translation2 will always use the default langauge in the case a
> string was missing but I'd have to double check that.
> 
> Thanks,
> 
> --Tony
> 
> Dirk Haun wrote:
> 
> >Tony,
> >
> >
> >
> >>In GL2 I'm proposing we use a single table to serve all those needs.
> >>
> >>
> >
> >Makes sense.
> >
> >
> >
> >
> >>The issue I really
> >>wanted to discuss was one brought up by someone recently (name escapes
> >>me) on how to handle the translation of text stored in drop downs.   I
> >>have been assuming we would pipe the text in the actual database table
> >>through our translation library...seems simple enough but I wanted to
> >>make sure I wasn't over looking anything.
> >>
> >>
> >
> >Remind me again where GL2 will keep the translated text strings - in
> >language files or in the database?
> >
> >Anyway, I seem to remember that when there's no translation for a string,
> >it would use the english text, so there's no problem with keeping things
> >consistent.
> >
> >That would be okay then (and would get rid of one of the annoyances in
> >the 1.3 design).
> >
> >bye, Dirk
> >
> >
> >
> >
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://lists.geeklog.net/listinfo/geeklog-devel
>