Just want to add that some dtdV1todtdV2.xsl files already exist in
$FORREST_HOME/main/webapp/resources/stylesheets.
It could be a good idea to maintain these kind of files in order to
migrate old forrest site...
For instance, we recently change the skinconf.xsl from v6-3 to v7 and
the motd declaration is completly different.
A skinconfv63tosxkinconfv70.xsl would have been welcome.
WDYT ?
Cyriaque,
Ferdinand Soethe a �crit :
Ross Gardler wrote:
It is a good idea to clearly mark deprecated DTD's. In fact I would go a
step further and say we move them to a deprecatedDTD plugin. This would
be an internal plugin. This would leave only active DTD's in core so new
users will not be tempted to use deprecated ones.
Certainly worth consideration.
However, it is not as simple as it may sound. For example, document1.3
extends document 1.2 which extends document 1.1, therefore for document
1.3 we need all earlier versions. It would therefore seem that the first
step would be to do as you propose, move the earlier DTD's into a
deprecated folder and think about the next step later.
Yes, I figured that we have more important issues to program so I took
a simple solution. Besides, this solution would be more general and
could also be applied to old howtos such as the one on CVS-SSH.
(Although we could donate that to projects still using CVS :-))
--
Ferdinand Soethe
