I just filed a support case with PTC. The topic is one I've slammed them on
before several years ago. The rest of this is me venting a bit, but there
is a serious issue in my venting. PTC CHANGING OUR DATA so it will not work
outside of Epic.
<venting>
Recall my question on the Epic support of the OASIS TR 96-01 a couple of
weeks ago. Well I spent a great deal of time modifying my document to work
with the <xi:include> adding nearly 70 file references. Once done, the main
document did parse in Spy and Oxygen.
Well I still prefer to use Epic as my primary authoring tool, but
occasionally I am on a machine without an Epic license, but that has one or
the other of Spy or Oxygen. Imagine my surprise (read TOTALLY PO'd) when
many of the files I had spent hours fixing were back the way they had
started out.
Seems that Epic is changing my data when they save any of the referenced
files that were changed. They wrap the entire DOCTYPE header subset (the
DOCTYPE, SYSTEM call, AND ANY DECLARED ENTITIES) in a comment. So this:
<section>.</section>
Becomes this:
<section>..</section>
PTC, you DO NOT CHANGE MY DATA WITHOUT MY PERMISSION. You have done this in
the past and stopped. It is time to do so again. By adding the not
universally supported TR, you now negate my XML working outside of PTC. THIS
IS UNACCEPTABLE for what is supposed to be 'transportable'.
I am not suggesting PTC stop their support of the TR, but give me the option
as to whether or not I want the DOCTYPE header changed or not.
</venting>
Lynn