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

Should expression text be output as <dynam>? #198

Open
th-we opened this issue Oct 2, 2022 · 3 comments
Open

Should expression text be output as <dynam>? #198

th-we opened this issue Oct 2, 2022 · 3 comments

Comments

@th-we
Copy link
Member

th-we commented Oct 2, 2022

At the moment, Sibmei exports Expression text as <dynam>. Is that actually sensible? I guess e.g. "dolce" should be an Expression text, but should it be output as <dynam>, or rather as <dir>?

Suggested solutions:

  • Export as <dir> and set @class to the style ID from Sibelius (with the leading text.staff. or text.system. stripped). Example for that: text.staff.technique => technique, text.staff.expression => expression.
  • Projects should define their own styles or style mappings and use a Sibmei extension or a postprocessing step to get their desired encoding.
@th-we
Copy link
Member Author

th-we commented Oct 2, 2022

This is of course not the whole picture as all the dynamics (forte, piano, ...) are input as Expression. We therefore have to analyize the content to generate <dynam> for those cases.

@rettinghaus
Copy link
Member

For now we should leave expressions as they are and just make sure other sorts of texts are actually exported.

@rettinghaus
Copy link
Member

Connected to #201

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants