At the moment it is possible to specify a custom file extension when generating documentation by using "_.html" or "_.htm", etc.
I have decided to follow the convention of giving each topic a GUID for the id attribute. It would be highly beneficial if generated files used the topic ID instead of the dita topic filename because it would avoid issues with browser bookmarking/favourites/seo. The following file structure seems most appropriate for my needs: /user-guide/chapter-name/super-section/overview.dita /user-guide/getting-started/installation/overview.dita Except this generates files with the convention "overview_1.htm", "overview_2.htm" which will likely lead to broken URLs in the future (where favourites/bookmarks are saved). Obviously postfixes will still be required to resolve ambiguity in cases where the same topic ID has been assigned to multiple topics. In my scenario this cannot happen because each newly created topic is assigned a unique GUID. Also it would be nice if generated links did not include the hash reference when not required because this results with links like "aaf1c496-0c0d-4404-a8e0-5e7c6a178b14.htm#aaf1c496-0c0d-4404-a8e0-5e7c6a178b14" which need only be "aaf1c496-0c0d-4404-a8e0-5e7c6a178b14.htm" (unless sub element is cross-referenced). Many of the online user documentation that I have seen recently seems to follow this technique.
-- XMLmind DITA Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/ditac-support
