hello, About the gettext, I agree with you, Alexander, actually I think that a gettext function can be usefull for messages( error, warnig, etc) or labels and all sort of short phrases or words but not for objects. So if we want to internationalize we need to make some changes to the database. I think I will work on version 2 of midgard. I already began to design a first draft for the database so we can have a word about it. I send the model on a jpeg image as an attached file. I used the midgard 2 scheme to begin my work, and I put all the common properties in one table object, which will make it easier if whe need to add properties(fields) to our objects. Then each object has its specific table with its specific properties(fields), now if we add a clang field in the specific tables for the objects that need translations( here page, pageelement and element) , we will only then to have one record for each language, the primary key is then the object id and the language code in the specific table. the object table will only have one record per object and then to fetch an object we only have to add the language code in the url : for instance where we have actually "http://path" we will have "http://LC/path" where LC stand for a two letter iso code for the language( EN for english, FR for french, etc). This way we will be able to cache pages for each language, because if we had the same url (we could using an internal variable) for two different languages, we would not be able to cache pages. We only need then to look in the language table to have the charset for each language to make the formatting.(the language table can be hard coded for performance since it's not a data that is likely to change often). bye, carmelo.
-- This is The Midgard Project's mailing list. For more information, please visit the project's web site at http://www.midgard-project.org To unsubscribe the list, send an empty email message to address [EMAIL PROTECTED]
