From: Alex B. <en...@tu...> - 2001-06-08 17:08:21
|
> Hi all, > > I am the one of the poor Turkish guy have to fight with > bloody localization issues and i believe there are too many > non English citizens of the world have the same pain in the ass. > > Directory based language structure is very good for now to the homo > sapiens high level technology :=) Very useful for images and files. > > i'd like to follow > <img src="/resources/fr/images/foo/foo.gif"> > > It is clear and not affects the flow. > > CSS idea is good. It helps to solve most of the problems but what > about a stuff like OK, Cancel, next, preview buttons etc.? If we don't > use images there is a big trouble waiting. > In Phpnuke, fellows used the translate method and separate language > files. Seems okay but make it slow the all code and site. > I am still looking the right solution on it. The above is exactly what we do: resources/images/foo.fr.gif and foo.de.gif in the source tree are: resources/fr/images/foo.gif and resources/de/images/foo.gif in the make tree. > I want to talk about two other major problems. > > 1. Sorting tables in specific language. > 2. Date time trouble. > > I know that we should deal with OS and software specific issues about them. > But i strongly prefer to stay in cross platform as could as i do. 1: sorting, as I think the only way to deal with charsets properly is to put everything in utf-8, that means sorting would be a function of char order in utf, which I have admittedly little experience with. date/time is much easier, as you can standardize the dates you store in the DB, and use simple routines to display dates differently. i.e. you use "date/time" format in presentation only, all data storage is homogenous. > Note: Of course i am ready to translate parts to Turkish :=) cool! :) _alex |