Support for custom XML formats #4308
Comments
reckart
added a commit
that referenced
this issue
Nov 16, 2023
- Ability to add custom XML formats similar to editor plugins - but just defining the content policy and CSS
reckart
added a commit
that referenced
this issue
Nov 17, 2023
- Ability to add custom XML formats similar to editor plugins - but just defining the content policy and CSS
reckart
added a commit
that referenced
this issue
Nov 17, 2023
…for-custom-XML-formats #4308 - Support for custom XML formats
reckart
added a commit
that referenced
this issue
Nov 17, 2023
- Added documentation - Turned it into an experimental feature that is disabled by default
reckart
added a commit
that referenced
this issue
Nov 17, 2023
- Expanded documentation - Added a `PASS_NO_NS` action for attributes in the content policy rules - this renders the attribute without its namespace in the browser which then allows accessing it from CSS using the attr() function which does not appear to support namespaces neither as `attr(myns\:attrib)` nor as `attr(myns|attrib)`.
reckart
added a commit
that referenced
this issue
Nov 18, 2023
- Expanded documentation - Added a `PASS_NO_NS` action for attributes in the content policy rules - this renders the attribute without its namespace in the browser which then allows accessing it from CSS using the attr() function which does not appear to support namespaces neither as `attr(myns\:attrib)` nor as `attr(myns|attrib)`.
reckart
added a commit
that referenced
this issue
Nov 18, 2023
…for-custom-XML-formats #4308 - Support for custom XML formats
reckart
added a commit
that referenced
this issue
Nov 19, 2023
- Fix format ID for custom XML formats - Use the Apache Annotator editor as preferred editor for custom XML formats
reckart
added a commit
that referenced
this issue
Nov 19, 2023
…for-custom-XML-formats #4308 - Support for custom XML formats
reckart
added a commit
that referenced
this issue
Nov 21, 2023
* main: (68 commits) #4316 - Dissolve generic API module #4316 - Dissolve generic API module #4316 - Dissolve generic API module #4316 - Dissolve generic API module #4316 - Dissolve generic API module #4316 - Dissolve generic API module #4314 - Move project API to own module #4308 - Support for custom XML formats #4308 - Support for custom XML formats #4308 - Support for custom XML formats #4310 - Viewport tracking does not work well in RecogitoJS editor #4308 - Support for custom XML formats #4302 - Files imported as HTML do not show properly in HTML-based editor #4305 - New predictions message is shown even if no new predictions were generated #4304 - Log more startup messages through boot logger #4229 - Better project template selection #4298 - Recommender status says "Waiting for evaluation" for recommenders that cannot be evaluated #4297 - Popover always showing "tag not in tagset" even if feature has no tagset at all #4294 - Infer paragraph boundaries when displaying plain text files in HTML-based editors #4150 - Upgrade dependencies ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, rendering a particular XML format requires either implementing a format support in Java or an editor plugin.
Describe the solution you'd like
It would be nice if a custom XML format could be defined by supplying a content policy and a CSS stylesheet. That way, the format could be used with different editors (e.g. Apache Annotator or RecogitoJS).
The text was updated successfully, but these errors were encountered: