You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Vitaliy-1 has pointed out in #233 that the saxon9ee.jar is hard-coded into docx/build-from.xml. There are actually more than 20 instances of this use of the EE version of Saxon, and I think all of them could be replaced by the HE version for users who don't have a licence for Saxon or Oxygen. We would need to check whether the processes might be using EE-only functionality, and find ways to code around it.
The text was updated successfully, but these errors were encountered:
Yes, I think it works fine for everything (otherwise a non-Oxygen install of the Stylesheets wouldn't be able to do all the transformations). My understanding is that ee was used because Oxygen has some special optimizations for ee which make it run more quickly; I don't know what the optimizations are -- perhaps they're a trade secret -- but I've encountered a couple of cases where they actually result in problems (TEIC/oxygen-tei#15).
@Vitaliy-1 has pointed out in #233 that the saxon9ee.jar is hard-coded into docx/build-from.xml. There are actually more than 20 instances of this use of the EE version of Saxon, and I think all of them could be replaced by the HE version for users who don't have a licence for Saxon or Oxygen. We would need to check whether the processes might be using EE-only functionality, and find ways to code around it.
The text was updated successfully, but these errors were encountered: