Page 1 of 1
Variables ${pd} in DITAVAL pathname spec
Posted: Wed Jan 22, 2014 8:52 pm
by manthony
Hi,
I've set up some DITAVAL files that are intended to be shared in common among our group. The files themselves work perfectly for our conditional text.
The problem I have is in specifying the path to the file. The dialog implies I can set this:
${pd}/contents/emr.ditaval
However, when I do this, the Oxygen editor ignores the file. Do I have to map ${pd} someplace in options?
Mary
Re: Variables ${pd} in DITAVAL pathname spec
Posted: Thu Jan 23, 2014 12:40 pm
by Radu
Hi Mary,
${pd} means Project Directory. All editor variables supported by Oxygen are described here:
http://www.oxygenxml.com/doc/ug-editor/ ... ables.html
Oxygen has a Project view in which you can create a new project and add resources to it:
http://www.oxygenxml.com/doc/ug-editor/ ... -view.html
Defining an Oxygen Project (all the project data is saved in an XML file called
yourProjectName.xpr) for your DITA content is also useful because you can save several of the option pages in the Oxygen Preferences to Project options and thus have all writers edit content with the same common preferences.
For example for our user manual we have a shared project which is edited using Subversion:
http://www.oxygenxml.com/demo/Collabora ... rsion.html
An alternative for you would be to use the editor variable called
${cfd} which expands to the directory where the DITA Map which is currently opened and gets transformed is located.
Regards,
Radu
Re: Variables ${pd} in DITAVAL pathname spec
Posted: Fri Jan 24, 2014 3:48 am
by manthony
Radu,
Thank you. I'd already read the docs on the variables. We use the project feature. I have a project defined. All my files including the DITAVAL files are in there.
The problem I am having is that the variables are not expanding. They aren't expanding in the dialog; maybe they are not supposed to that is not clear from the doc. So, I can't determine if that is a bug or not.
The problem I am try to solve is that when I use use the variables in the DITAVAL specification in Oxygen. Then, the application no longer works with my Profiling Attributes. My conditions do not filter. Not when viewing a file in the Editor. Not when transforming the map.
The only way I can get a DITVAL file to work is to hard code the file path. Is there a piece I am missing?
Mary