> > It's still true. I had some ideas on moving that to phpdoc/install, > > but there were no replys from the guys, so I just didn't do it. > > I would not like to do anything in a hurry, without us deciding > > what to do, because this is why that crappy install part is there. > > Because someone done too much before asking the other guys. > > IMHO those files should be moved to phpdoc/install, and should be > > chnaged in their structure, to reflect some more hierarchy in the > > content (not to express hierarchy in title prefixes, huh...) > > I can't say anything about structure (changes) because I'm not involved in > this theme. To split this files is IMHO a good idea to support faster > translation.
Split was truly a good idea. What was bad IMHO is to name those files like you can see them right now, leave them there, break XSLT builds with relative entity path values, and not changing the structure the same time. I have added the DO_NOT_TRANSLATE file, because I think it needs a heavy change in structure, and maybe in manual placement. I expressed my visions here in many mails, but there were not too much replys (though all replys agreed with me ;). What we need to do with those files: - find a final place, with much smaller files names - add structure to them, and not to use title prefixes to structure the content > In my opinion it is very important to have translated install tutorials. > Installation is one of the most frequently ask question in de.comp.lang.php. > In the german dclp-FAQ, we have made a seperate chapter for installation > (http://www.dclp-faq.de/ch-install.html). As long as you can follow the changes which will be applied to the structure, it's up to you to translate. > > So it should be changed in structure and place... I have no > > plans right know to change it in contents though... > > I think, that we should check the content too and add the apache2 stuff. > Some instructions about extension dependicies would nice too (for instance > need ora client installed for activating oci). I am talking about structure only, because that's what can break your manual builds, and may be hard to adopt and fix translated documents. Missing content is a problem, but no new manual builds is bigger. Now the backward compatibility is provided with the install.xml file check. If there is no install.xml file in one language chapters dir, then the multifile install structure is expected. The new structure change should try to be at least backward compatible, but this cannot be guaranteed... Goba
