Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-element-type encoding #120

Open
StokesMIDE opened this issue Nov 1, 2022 · 0 comments
Open

Per-element-type encoding #120

StokesMIDE opened this issue Nov 1, 2022 · 0 comments
Labels
Decoding Related to the importing of EBML data enhancement New feature or request Schema Related to the EBML schemata utilities Relating to tools (e.g. util.py)

Comments

@StokesMIDE
Copy link
Member

When exporting to XML, there are various cases in which it would be useful to specify how individual element values get converted to text, similar to the BinaryElement encoding added in PR #99. Specifically, there are cases in which certain IntegerElements would be more easily read (by humans) if displayed in hex.

There are a couple of things that could be done (not mutually exclusive):

  • Add a parameter to functions like ebml2xml() that allows a dictionary of element names and encoding functions. Simple, but would take some effort to rework the command-line utilities.
  • Add an 'encoding' attribute to the element definitions in the schema. A bit more work, but likely a better approach.
@StokesMIDE StokesMIDE added enhancement New feature or request Decoding Related to the importing of EBML data Schema Related to the EBML schemata utilities Relating to tools (e.g. util.py) labels Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Decoding Related to the importing of EBML data enhancement New feature or request Schema Related to the EBML schemata utilities Relating to tools (e.g. util.py)
Projects
None yet
Development

No branches or pull requests

1 participant