-
Notifications
You must be signed in to change notification settings - Fork 14
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
Translate <<x>> to «x» #16
Comments
The issue with angle brackets is that they're element-like. We use fancy characters in some places (like <=, >=, etc.) so I wonder if we can get away with just requiring people to paste in the proper character... |
I'd be ok with e.g. It kind of sucks that we can't have EMD convert |
I am not familiar with the relevant algoriths but a > with a space before it and a < with a non-letter character after it seem to be auto-escaped? Perhaps emd can use similar heuristics to know what unescaped < and > characters belong to tags and which don't? |
Upon re-visiting this it seems completely fine to me to translate |
The problem with this is that if the document is first passed through an HTML parser (which is the case for an emu document), If we require a space around the list name, eg: |
Oh, right... that makes sense. I mean, you could imagine a world where EMD is the outer layer before you get to a HTML parser, but that's a whole can of worms. OK, reverting to |
is |
Whitespace sensitivity always feels meh... Maybe it's fine though? Maybe something to ask the userbase about after getting a bit more experience. |
MD is already whitespace sensitive in a few places (lists, eg.) and EMD in at least one more place (inside |
In the latest draft Allen updated the convention for "List literals" to use «x» instead of (x).
To make this easier to type we might want to let people type it as ASCII and convert it to the correct Unicode characters.
The text was updated successfully, but these errors were encountered: