The old build system is used when you run build.sh in livedocs. It does a ./configure --with-lang=$lang
I don't know if we will ever get ride of this build system. The use of entities is a good idea, Goba! we may add the entites for livedocs in language-snippets.ent, for example. Moshe: There won't be too many IFs. We need just one if for the array $map and other IF to declare your special functions. No real impact on performance and its much more manageable. Anyway, any more opinions? We need also to decide how to choose the encoding and how to choose if RTL or LTR for each language. Create an array with this info? It's dificult to extract this info from the old (actual) build system because livedocs can be used for more than one language. Nuno > Are you planing to use on the old build system forever? Shouldn't livdocs > replace completely the old system sometime? > > also if the answers to those two questions are yes and no, Imho, the multi > languages support on the old build is realy creak part (specially in the > aspect of not duplication the code and files-structure) and and we sould > reduce the old build system relay as much as possible. It's just looks to me > stupid giving the new build system the pleasure to extract some bash or > whatever old definitions and build new per language php file (keep in mind > we need those definitions on runtime, not on configure time) when we can put > it in ready to use php file. > > --/moshe. > > "Gabor Hojtsy" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > I think that having a file for each language with the strings is OK. > > > > > > But I think we don't need any other file for RTL. We need just an array > > > (sorry Derick :)) with the languages that use RTL. > > > Which languages use RTL? and which charset? > > > > A lot of strings can be extracted from the phpdoc build system (entities > > used for translation). Also the phpdoc build system is aware of what > > language is RTL or LTR, so there is no need to duplicate this. > > > > Goba
