-
Notifications
You must be signed in to change notification settings - Fork 152
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
use Text parser for plaintext pasting #263
Milestone
Comments
@YoranBrondsema I'm going to tackle this today...Let me know if you already looked at it, otherwise hopefully I can finish it up today. |
@bantic I haven't, please go ahead! |
bantic
added a commit
that referenced
this issue
Dec 16, 2015
The text parser recognizes multiple sections for text separated by line breaks and will parse lists when lines of text start with "*" (unordered) or "<number>." (ordered). fixes #263
bantic
added a commit
that referenced
this issue
Dec 16, 2015
The text parser recognizes multiple sections for text separated by line breaks and will parse lists when lines of text start with "*" (unordered) or "<number>." (ordered). fixes #263
bantic
added a commit
that referenced
this issue
Dec 16, 2015
The text parser recognizes multiple sections for text separated by line breaks and will parse lists when lines of text start with "*" (unordered) or "<number>." (ordered). fixes #263
bantic
added a commit
that referenced
this issue
Dec 16, 2015
The text parser recognizes multiple sections for text separated by line breaks and will parse lists when lines of text start with "*" (unordered) or "<number>." (ordered). fixes #263
bantic
added a commit
that referenced
this issue
Dec 16, 2015
The text parser recognizes multiple sections for text separated by line breaks and will parse lists when lines of text start with "*" (unordered) or "<number>." (ordered). fixes #263
bantic
added a commit
that referenced
this issue
Dec 16, 2015
The text parser recognizes multiple sections for text separated by line breaks and will parse lists when lines of text start with "*" (unordered) or "<number>." (ordered). fixes #263
bantic
added a commit
that referenced
this issue
Dec 16, 2015
The text parser recognizes multiple sections for text separated by line breaks and will parse lists when lines of text start with "*" (unordered) or "<number>." (ordered). CR+LF and CR line endings are normalized to single LF before parsing. fixes #263
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#262 adds code to fall back to using the text/plain paste data when text/html is not available, but the plaintext is still parsed into mobiledoc with the HTML parser. There should be a text parser instead that can do things like translate linebreaks into multiple sections, etc.
The text was updated successfully, but these errors were encountered: