Project

Profile

Help

Feature #3218

Supply base64 encoded SEF and/or source to SaxonJS.transform

Added by Debbie Lockett over 3 years ago. Updated over 2 years ago.

Status:
Won't fix
Priority:
Low
Category:
-
Sprint/Milestone:
-
Start date:
2017-05-11
Due date:
% Done:

0%

Estimated time:
Applies to JS Branch:
1.0
Fix Committed on JS Branch:
1.0
Fixed in JS Release:
SEF Generated with:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

See https://saxonica.plan.io/issues/3163

To resolve the problems in the bug, a work around was produced (using some custom JavaScript) so that a base64 encoded SEF could be supplied to SaxonJS.transform via the stylesheetNode option. We should look at taking this further, e.g. provide more accessible options implemented in Saxon-JS to do this kind of thing.

History

#1 Updated by Debbie Lockett over 2 years ago

  • Status changed from New to Won't fix
  • Assignee set to Debbie Lockett
  • Applies to JS Branch 1.0 added
  • Fix Committed on JS Branch 1.0 added

We considered adding a "stylesheetText" option to the SaxonJS.transform API, so that the SEF can be supplied as a string (after any required decoding). But since we are already working on Saxon-JS 2.0 for which the SEF is in JSON format rather than XML, we have decided not to make changes for 1.x, as hopefully a better solution will be possible using Saxon-JS 2.0.

Also, it remains unclear exactly what base64 decoding methods we could usefully expose. The work around produced for issue #3163 was rather a special case.

Marking this as "won't fix".

Please register to edit this issue

Also available in: Atom PDF Tracking page