Page 1 of 1
setting the path to framework add-on in transformation scenarios
Posted: Fri May 26, 2023 4:47 pm
by ttasovac
If I need to refer to a file from the built-in TEI framework in, say, a transformation scenario, I will use
. I prefer toI install the TEI framework as an add-on — it may contain a more recent version of TEI. Where do add-ons live and how can I make sure that my path refers to the add-on and not the built-in TEI?
Many thanks in advance.
All best,
Toma
Re: setting the path to framework add-on in transformation scenarios
Posted: Mon May 29, 2023 6:22 am
by Radu
Hi Toma,
Oxygen has an user preferences folder named something like "com.oxygenxml" and placed in your user home, depending on the operating system.
You can find out more about our user preferences folder location in our uninstall topic:
https://www.oxygenxml.com/doc/versions/ ... ation.html
In this user preferences folder there is an "extensions" folder where all add-ons are installed, depending on the user version. But referencing content directly from there is not a good idea.
You can use these editor variables instead:
Code: Select all
${framework(fr_name)} - The path (as URL) of the fr_name framework.
${frameworkDir(fr_name)} - The path (as file path) of the fr_name framework.
For example
${framework(TEI P5)}, if your add-on is named "TEI P5" exactly like our base TEI framework folder, Oxygen will prefer to load and use the "TEI P5" framework add-on instead of the base "TEI P5" framework.
Regards,
Radu