Can a Custom Refactoring Operation Use Saxon's EXPath Extensions?
Posted: Fri Oct 18, 2024 9:25 pm
Hi,
I'm looking into creating a new custom refactoring operation for my team that would ideally rename DITA files and then update the references to these files in <topicref> and <xref> elements.
I found that Saxon supports using EXPath extensions which would provide support for "renaming" files (this would probably be a move function) through the file module: https://www.saxonica.com/html/documenta ... xpath.html
I'm wondering though if Oxygen's refactoring engine uses Saxon to process the XSLT and if I can use the EXPath extensions in a custom refactoring operation?
I'm also open to any other ideas you might have for how a refactoring operation could rename DITA files and then update all references.
The reason I'm investigating a refactoring operation is because we have over 500+ files that we would like to rename and we want to avoid having to rename them individually.
Thank you!
I'm looking into creating a new custom refactoring operation for my team that would ideally rename DITA files and then update the references to these files in <topicref> and <xref> elements.
I found that Saxon supports using EXPath extensions which would provide support for "renaming" files (this would probably be a move function) through the file module: https://www.saxonica.com/html/documenta ... xpath.html
I'm wondering though if Oxygen's refactoring engine uses Saxon to process the XSLT and if I can use the EXPath extensions in a custom refactoring operation?
I'm also open to any other ideas you might have for how a refactoring operation could rename DITA files and then update all references.
The reason I'm investigating a refactoring operation is because we have over 500+ files that we would like to rename and we want to avoid having to rename them individually.
Thank you!