Hi Hussein, Three things...
1) I think that adding an attribute to the <copyDocument> command may work. But this depends on how the stylesheet gets processed. If the stylesheet processor does not itself expand the xincludes, this will be fine. If it does perform the expansion, I think we'll end up with the same result. 2) It'd be really nice if in the macros/processes it would be possible to read the file name and the path of the file on which we are operating. I don't know if this is possible or not. 3) I know that this can't be done (others have brought up this issue in the support forum), but we'd sure like to be able to replace the entire document at once. That way, if I process the entire document using a stylesheet, I can easily put the results back into the document I am editing. We have a work-around for this, but it's not great. This isn't a hard requirement for us, I just thought I'd add my voice to the chorus. Thanks, --Rick >Hussein, > > > OK, we'll add an attribute to the <copyDocument> process command element > > which will allow you to save a copy of the document being edited where > > XIncludes or entity references or both are not expanded. > >Excellent - thank you. When would you expect to have this available? > > > Note that copies of the XIncluded documents or referenced external > > entities will not be saved in the temporary directory created by the > > process command. But from what I have undesrtood, this should not annoy >you. > >I don't think this is a problem, but I'll check with Rick. I know that one >other thing Rick would love to be able to do is be able to call a command to >return the name and/or path of the file within macro or process...is this >similarly possible? > >Eric
