Hojtsy Gabor wrote: > These are problems that should be discussed.
thats exactly the reason for me writing the PDF almost everything i mention in there has already been talked about on this list in some way without much work going on on it so i tried to summarize the identified problems and the possible solutions > So reworded: using namespaces to define tags, and use them > along DocBook tags. This is exaclty not extending DocBook, > but defining a DTD for our custom elements and use those > two DTDs (DocBook and PHPDoc) side-by-side. this topic came up after i had finished my first draft so it is not mentioned yet, but it definetly should be in there > Although I am __not__ speaking of extending DocBook, > there is a chapter about "Customizing DocBook", in > "DocBook: The definitive Guide". This customizing is what > Jirka is talking about. So for DocBook it is allowed. if we wouldn't mind cutting us off of other DocBook aware environments we could customize whatever we want we distribute the DTD anyway and the extensibility of the modular stylesheets allow as much costomization as we want to have we would have to call it something else but DocBook then, maybe PHPBook or so but as soon as we start changing the DTD it would probably become sort of pandoras box getting more and more a thing of its own ... > It is our job to decide, whether we choose customizing > or another way. I am against customizing DocBook this > way, so we are on the same side (and so Hartmut, as > I can see in this PDF). well, i tried to stay somehow neutral in this text, but customizing DocBook definetly comes for a price so the benefits we would gain from customizing do not compensate this for now IMHO
