Re: cvs: phpdoc / Makefile.in

> > > move to xsl build > > > > Wow! Have you tested this with foreign languages? > > I am not sure it will work. Especially I am sure > > that it won't work for languages whose encodings > > are not compatible with iso-8859-1 (due to the > > translated entities, getting used in iso-8859-1 > > files). I had experienced this problem with 'he' > > files. > > You've a few days to fix it then ;) I just tested a build here for 'en' > which worked fine (and it took only 29 minutes on my 1.1ghz box). Well, yes the problem is not with the EN build. Is with the HE build for example. They have translated snippets in some specific encoding. When the manual is build English and Hebrew files are mixed, and Hebrew entities get into English files. There xsltproc has serious problems with putting Hebrew content into iso-8859-1 files, as they don't match that encoding. Therefore you get 'character out of range' or something like this for every Hebrew char in every file which uses some translated entity. My first idea was to modify the XMLs on the fly for building (adding ".he" to all entity names and entity usage in translated XML files). But this can also be done once and stick to this that translators need to add .LANGCODE to the end of entity names for their XMLs to build. Neither of these two solutions is nice but they will probably solve this problem, and so we would be able to use XSL sheets finally. Jade does not check encoding [properly], so this was not a problem for that tool... Goba