Dave Fisher wrote:
I think that we can purge these *.htm duplicates, but if we do it
will be a "sledgehammer" build.

It will also be a problem, unless we accompany it with other changes: for example, http://www.openoffice.org/pt/ would completely break, and all external sites that now link to some of our .htm files would break too.

It was intentional. Before doing so we would need to make a group
decision about how to treat the two types of files.

Regardless of what templates we apply, the best solution should:
1) Allow a .htaccess redirect/rewrite from .htm to .html (to preserve existing internal and external links) 2) Have the SVN file names match the URLs: editing a file named "news.htm" in SVN should not result in a change in a page with URL ".../news.html". The current handling confuses the CMS too (for example, no diff is reported). So either we mass-rename files from .htm to .html and rely on 1) above, or we don't change .htm to .html but publish .htm URLs.

There are two different procedures from view.pm used:  ...
There are several templates used from templates/.

To me, .htm and .html are not different file types and were never used as such: I mean, volunteers historically committed .htm or .html according to their habits, but it doesn't make sense to have different ways of handling them now. So I would tend to rename all .htm to .html and put the .htaccess redirect in place, and have only one "type" of HTML files to handle.

Regards,
  Andrea.

Reply via email to