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
