The key is that I want to reflect directories that are ancestors of the file being processed. For example, say that files can be in project/a/b/c or project/d/e/f and I want to generate files in project/new/a/b/c or project/new/d/e/f--I don't see a way to do that without having different scenarios or modifying the scenario for each different starting directory. It precludes applying the transform to the common parent of both input directories and having it just work. And of course, if I could really have everything I wanted I'd like to be able to apply a regular expression to the incoming filename and then reference groups in order to construct the result filename.... Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com On 2/7/14, 5:49 PM, "Peter West" <lists@pbw.id.au> wrote:
There is already the variable ${pdu} which is the URL of the project directory. If that were complemented with ${rppd} for relative path within project directory, that would do the trick, wouldn't it?
On 8/02/2014 8:05 am, Eliot Kimber wrote: ....
I'm thinking that what I'd really like is the ability to get any component of the input file's path so that I can then construct the result path, something like:
../../../newdir/${parent:3}/${parent:2}/${parent:1}/$cfn-newbit.xml
Where the tokens are addressed from nearest (parent) to farthest, as for the ancestor:: axis.
If I had that I could have single transform scenarios I could apply to large sets of files in different structures and get the required result without having to rejigger the transform scenario for each different output location.
-- Peter West "For what does it profit a man if he gains the whole world and loses or forfeits himself?" _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user