> > Now, we need to discuss where they should go. I would be fine > > with phpdoc/install for install.anything.xml files, and > > phpdoc/install/configure or phpdoc/configure for > > install.configure.anything.xml files. > > Yes, ack. > > > phpdoc/configure/databases.xml > ... > > phpdoc/configure/xml.xml > > There will be two more files in here. See, whats commented > out in install.configure.xml
OK. Please do not only ACK my folder ideas, but please also give your opinion. For example whether it would be better to put condigure things into install/configure or configure/. I previously expressed my visions about the future stucture of the manual. This may be a complete misleading way, but it seems to me that it is right. In this vision, the configure options existed inside the logical parts (eg. databases, text processing, etc), side by side with functions, ini settings, feature descriptions, conceptual indexes, and so on... So what I would like to say with this is configure/ or configure/install is only a temporary place for this thing in my eyes. Though as my vision may be completely bad, this may also be a final place, so it needs to be carefully choosen... > > Another thing: where is general installation > > steps in the breaked up install parts? Its nowhere!! > > Are there other parts left out? Can anybody please check? > > Should be in install.xml So, I need to write down correctly, what is my problem with this breakup structure. You have a TOC and some text in install.xml, and text in other install.notconfigurebutsomeother.xml files. Lets say we introduce a new server, BadBlue as install.badblue.xml, and we add it into the English install.xml TOC. This server will not appear in translations as long as they update their install.xml. The same for install.configure.xml This thing is what we would like to avoid with breaking up function xml files, so it is a bad idea IMHO to introduce it in install and configure files. The problem is that we have a file with text that needs to be translated, and TOC that needs to be constantly updated. The basic idea behind the central manual.xml file, is to have a common toc, and use files from the en tree if there is no file in the current language for the topic. As manual.xml is used by all the languages, it does not contain any parts that need to be translated (these parts are in entities in language-defs.ent). IMHO to support the automatic english file usage, we need to have a file with no translateable content, and all the content need to reside in "content files". This is easy to accomplish with install, not that easy with install.configure, I'll look over this thing... > > Yes, you can say, that we have a note on the configure > > options page, that these are compile time options. > > But there are many places, where we refer to "configure > > options", and "configuration directives" (yes, we use > > these two words for the two things). This is one major > > thing need to be discussed! > > +1 for "settings" What others think about this? This will be a convention, so a community agreement need to be made :) Goba
