[MusicXML] use offset for non-spanning directions
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
See #282185: Musicxml: use direction offset tag during export (and import) for the discussion and justification. This issues replaces backup/forward by offset for non-spanning directions only, to improve braille translation.
Fix version
3.4.0
Comments
Relates to #270643: [EPIC] MusicXML import/export issues and #281511: [EPIC] Braille friendly musicxml export
https://github.com/musescore/MuseScore/pull/5534
Fixed in branch master, commit c65916e4bf
fix #298552 - [MusicXML] use offset for non-spanning directions
Fixed in branch master, commit 5af1357e89
_Merge pull request #5534 from lvinken/use-direction-offset-tag
fix #298552 - [MusicXML] use offset for non-spanning directions_
Fixed in branch 3.4beta, commit 1d9169d299
_Merge pull request #5534 from lvinken/use-direction-offset-tag
fix #298552 - [MusicXML] use offset for non-spanning directions_
Automatically closed -- issue fixed for 2 weeks with no activity.