Gabor Hojtsy wrote: > Using entities in install.xml is completely against our > automatic translation handling system (chapters ent > generation). If one deletes an entity or forget to add > one, that particular part won't be addded to the doc. > This is wht the automatic translation handling system > exixts, and this is why we store all these file entity > references in manual.xml only.
> > So I am also against the current architectural structure > of the install part, as it can easily lead to translation > breaks, and outdated install parts again :(( this is not entirely true, the entities used in install.xml are still defined in entities/chapters.ent which is auto generated by configure, using translated files where possible with a fallback to english originals the only thing that might lead to outdated material or breaks would be a translated install.xml where the list of entities to use is outdated (would be bad enough) but there's a practical reason for moving the include entities to manual.xml: jade and saxon treat relative pathes in entities different for jade all pathes are relative to the directory the top level input file (manual.xml) is in while saxon (don't know if this is true for all XSLT processors) bases them on the directory of the current input file so the entities generated for jade (in chapters.ent) do not work with saxon as their pathes are relative to the toplevel dir while install.xml, the current input file, is in lang/chapters :( so +infinity for moving the include stuff from install.xml to manual.xml, although for a different reason -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
