Sorry, I'm resending without the word "spam" in the subject! 

  

-----Original Message-----

From: Peter <pshau...@tomsawyer.com>
To: oxygen-user <oxygen-user@oxygenxml.com>
Date: Wednesday, 1 November 2023 4:11 PM EDT
Subject: Re: {Spam}[oXygen-user] Read only section of Xml

  
Hi Karl! 
  
I don't know if this is exactly what you want, but what if you... 
  
1, Create a new XML file that you will only use as the source for a conref 
2, Move your historical content into a <section> or a <div> element within that 
new XML file 
3, Place a condition on the <section> or <div> element containing the 
historical content, like product="historical" or maybe 
deliveryTarget="historical" 
4, Define that condition in your DITAVAL file, for example, <prop 
action="exclude" att="deliveryTarget" val="historical"/> 
5, In the current file, insert a conref to the historical content 
  
Because the information is in a conref, the content will be read only when you 
are in the current/parent file (unless you double-click it to open it). 
  
Because the content is marked with a "historical" condition, and "historical" 
is defined to be excluded, it will not show up in the output. 
  
-Peter 
  
    
From: Karl <kst...@gmail.com>
To: oxygen-user <oxygen-user@oxygenxml.com>
Date: Wednesday, 1 November 2023 1:42 AM EDT
Subject: {Spam}[oXygen-user] Read only section of Xml

  
Hello Group! 
  
I'm wondering if there is a way to markup a section of xml as readonly and then 
for Oxygen to honor this by either blocking or warning you of making changes 
within this section. 
  
Scenario is simple.  You have current content in some Xml node and then you 
stash historical content in some other Xml node that you intend to keep around 
but not to edit. 
  
This would be useful to me because I'll take the current information in my Xml 
and stuff it into the historical section of my Xml as I roll into a new season. 
 The issue I am having is accidentally changing content in the historical 
section of my Xml but I intended to make those changes in the current Xml node. 
  
This is not mission critical, but would be a nice feature. 
  
Karl.. 
        
_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

Reply via email to