NYCPHP Meetup

[rinaudom at tiscali.it]

I think that a file inclusion based solution for translation is a good
choice (like phpMyAdmin does, for istance), but a more flexible way is a
DB-based solution. In particular (PanamaSuite):

1) The customer who administers his website/application can operate easily
with a secure, DB based control-panel which allows him to easily add new
languages, TRANSPARENTLY modifying page contens WITHOUT dealing with the
code in include files; PanamaSuite was built with usability in mind, so a
PanamaSuite based application can be administered by a non-programmer
person;

2) the customer has got an internal, DB based search engine which allows
him to find quickly what he is searching for thru a transparent DB query;

3) using a database is really better when you need to add a language,
WITHOUT UPLOADING ANYTHING, so you don't need to make a folder writeable
by the user/group of e.g. Apache;

4) I have built several web applications with PanamaSuite: none of them
were slow.

5) when you add a language (a column in the database) and you make it
active, the rest of work is made automatically: the selectboxes are
auto-populated, you need only to fill with static text the object-contents
in database via the USER FRIENDLY control panel.

6) with PanamaSuite you can customize a language as well. Text direction
(`ltr' vs `rtl'), codepages etc. It is more flexible IMHO than a
filesystem based translation.
PLEASE NOTE: PanamaSuite DOES NOT CREATE AUTO-TRANSLATED TEXT. The static
text must be inserted MANUALLY.

Thanks a lot for your time, Matteo Rinaudo