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

use Text parser for plaintext pasting #263

Closed
bantic opened this issue Dec 14, 2015 · 2 comments · Fixed by #268
Closed

use Text parser for plaintext pasting #263

bantic opened this issue Dec 14, 2015 · 2 comments · Fixed by #268
Assignees
Milestone

Comments

@bantic
Copy link
Collaborator

bantic commented Dec 14, 2015

#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.

@bantic
Copy link
Collaborator Author

bantic commented Dec 16, 2015

@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 bantic self-assigned this Dec 16, 2015
@bantic bantic added this to the 0.8 milestone Dec 16, 2015
@YoranBrondsema
Copy link
Collaborator

@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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants