Making FM use @href instead of @entity when writing to XML

I finally found out how to suppress the <ENTITY> statements when exporting to XML. I created the DTD for the exported XML by saving the EDD as DTD. That process included the@entity on images, which kicks the <ENTITY> output mechanism into action, no matter which read-write rules you have set up. Once the @11272877 was removed from the DTD, those annoying statements were gone and the read-write rules (in which I map the fm file property to an @href) took over.

I would have expected the read-write rules to take precedence over some automatic fall-back entity mechanism. That would have saved me a lot of trial and error time.

Replying my own question, as nobody else seems to have a solution.

1. In XSLT I can dereference the entity declaration, but that leads to an absolute path, which is not always what I want to have, especially if the graphic files are in a subdirectory of the folder in which the FM file is located.

2. I decided to add an @href to each image and populate it using an ExtendScript - this files the file property of the graphic and writes it into the attribute. This allows the post-processing to simply ignore the @11272877 and use the @href instead.