Good morning -
* Now we're migrating more and more content to DITA, I have a range of different conversion parameters to manage. OK, so I know about saving them as .xml files ... but I've had to start adding a comment at the top of each .ditamap to remind me which .xml parameter-file to load. Is there an easier way of making sure that each .ditamap or .bookmap is associated with its own set of conversion parameters? * It looks to me as though loading a saved set of conversion parameters is not replacing parameters already specified; for instance, if the current parameters specify an .fo title-page and I load a set of parameters with no title-page specified, the original title-page is not removed. Only parameters specified in both sets are updated. Tips and reassurance welcome! Niels Grundtvig Nielsen technical author Worldline Terminals Atos Expert in technical communications you know what you're talking about - I can help you say it ********************************************************************************************* Worldline SA/NV - Chaussee de Haecht 1442 Haachtsesteenweg - 1130 Brussels - Belgium RPM-RPR Bruxelles-Brussel - TVA-BTW BE 0418.547.872 Bankrekening-Compte Bancaire-Bank Account 310-0269424-44 BIC BBRUBEBB - IBAN BE55 3100 2694 2444 "The information contained in this e-mail and any attachment there to be confidential and may contain information which is protected by intellectual property rights. This information is intended for the exclusive use of the recipient(s) named above. This e-mail does not constitute any binding relationship or offer toward any of the addressees. If you are not one of the addressees , one of their employees or a proxy holder entitled to hand over this message to the addressee(s), any use of the information contained herein (e.g. reproduction, divulgation, communication or distribution,...) is prohibited. If you have received this message in error, please notify the sender and destroy it immediately after. The integrity and security of this message cannot be guaranteed and it may be subject to data corruption, interception and unauthorized amendment, for which we accept no liability."
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support

