cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X

DOCTYPE Fragment - revisited

LynnHales
1-Newbie

DOCTYPE Fragment - revisited

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



5 REPLIES 5

I know we had some issues with this, and I apologize if this was already said, but have you looked at the fragmentheader and fragmentheaderpreserve settings under Advanced Preferences? Not sure if this will resolve this particular issue or not.


Trevor Hendricks<">mailto:->
Project Analyst -- Publication Systems
Technical Communications, MS: 078

Trevor,



I have not tested those set commands. It looks like what I need.



One suggestion. I searched the ‘help center’ for information on “DTD
fragments” and I neither of these set commands show up in the search
results. It would be nice if these commands appeared in such a search.



I really did not think PTC would allow data to be changed like that.



Lynn


I agree. It took a long time to find those setting. Help didn't help much on that particular issue (most of the time though it's great).

Did you change the entity mode? You have to choose fragments or xinclude - it defaults to entities.


Sent from my Samsung Galaxy Note® II

Dan,



Yes, I’d already done that. Trevor hit the nail on the head with the ‘set fragmentheader’ (help 7741) and ‘set fragmentheaderpreserve’ (help 19437) commands.



The first is defaulted to write the TR header and changes the DOCTYPE name to the agree with the DTD root and not the XML root element name. Setting it to ‘document’ fixes that. The preserve command makes no changes when saving the file.



Lynn
Top Tags