DITA and XMetaL Discussion
bjorn August 22, 2016 at 6:43 am
XMetaL90.ini optionsAugust 22, 2016 at 6:43 amParticipants 0Replies 1Last Activity 5 years, 10 months ago
I'm about to customize the XMetaL90.ini but I can't find information for all the options in the [url=http://xmetal.com/webhelp/en/xmetaldeveloper/cg/7.0/cg.html#Configuration%20variables]http://xmetal.com/webhelp/en/xmetaldeveloper/cg/7.0/cg.html#Configuration%20variables[/url]. Some of the options seems self explanatory, but I just want to confirm there actions.
- parser_lax_empty_content = false
- image_path = C:XMetaLimages
- document_path = C:XMetaLdocs
- new_dlg_rules_path = C:XMetaLdtds
BjørnDerek Read August 22, 2016 at 9:45 pm
Reply to: XMetaL90.ini optionsAugust 22, 2016 at 9:45 pm
The first three settings you should not need to worry about. A lot of old INI settings (such as #2 and #3 here) were implemented when INI settings were the way all settings were remembered in Windows (before Microsoft started pushing the registry) so these are not really things a developer would generally need to do anything with.
Here's what I can gather for all of these.
parser_lax_empty_content = false
This INI setting is undocumented. It should be left set to true in older versions of the software where your users might encounter documents that contain comments inside empty elements. It is an awkward location for a comment but the XML Recommendation allows it. We have seen some CMS systems or automated systems introduce comments inside empty elements. This setting tells XMetaL to treat such documents as valid. In the current release this setting has no effect as the validation engine should just do the right thing. I'm not sure about the behaviour with version 9, but the issue was identified in version 8 so 9 introduced the setting. Whether it ever did anything I'm not sure. We might have just implemented the correct behaviour. Or it might have been in a very early build of 9 for testing and then dropped. We generally implement bug fixes with what we consider to be the best behaviour but include a secret INI setting in order for the one or two clients that might want an old behaviour (even if it might be considered wrong, as in this case) to have the ability to disable the new behaviour. In this case it seems that the behaviour has been considered to be so incorrect, and no clients have complained (which makes sense because the XML Recommendation should just be followed without question), that we have simply dropped it in newer releases.
image_path = C:XMetaLimages
If the user has never browsed for an image file this is the path they should be taken to. It is almost useless to bother setting this but you might have some specific need for it. Once the user browses for an image that location will be remembered instead (unless some custom dialog has been implemented in your customization).
document_path = C:XMetaLdocs
If the user has never browsed for an XML file this is the path they will be taken to. It is almost useless to bother setting this but you might have some specific need for it. Once the user browses for a file that location will be remembered instead (unless some custom dialog has been implemented in your customization).
new_dlg_rules_path = C:XMetaLdtds
I'm not familar with this setting and cannot find any information on it. I don't see any indication that it is supported.
- You must be logged in to reply to this topic.