[ENHANCEMENT] [MER-5771] replace blank foreign tags with spaces - #300
Merged
Conversation
rgachuhi
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A related issue to MER-5771, handling white space within foreign tags, is use of blank foreign tags containing only a single space character. These were inserted at many places in Pima French 101 XML to achieve spacing between other foreign-tagged elements. These migrate correctly, however Torus authoring's content normalization strips them before rendering so the desired inter-word spacing is not seen in authoring view. Author preview and Student delivery do render the spaces so are not affected.
This has migration tool replace these blank foreign tags with ordinary text spaces. This is simple to do and achieves the desired effect in all torus views including authoring.