Parse nbsp into spaces, render nbsp where needed#209
Merged
Conversation
This was referenced Nov 3, 2015
* Mobiledoc should, ideally, not contain any HTML entities. Instead these should be converted into their property plain text pair. This changes the parsing code to disallow nbsp chars, instead converting them into regular spaces. * The Content-Kit renderer must display spaces correctly when there are multiple spaces in a row. This patch ensures that at least every other space character is displayed as an nbsp. Fixes bustle#195
mixonic
added a commit
that referenced
this pull request
Nov 3, 2015
Parse nbsp into spaces, render nbsp where needed
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
1 participant
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.
Fixes #195