You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ace knows how to render an ASCII line feed (U+000A) (as a line break), but apparently does not know how to render a Unicode line separator (which should also be rendered as a line break).
Replacing all the Line Separators with line feeds does not seem like an acceptable solution; text editors should not change the text that they are editing unless the user says so.
The text was updated successfully, but these errors were encountered:
Apple's TextEdit renders it just fine. So does Xcode. These are the main editors that I use. As an experiment, I tried emacs, and it fails to render U+2028 correctly. I would guess that this might be true of many legacy editors that pre-date Unicode. I would expect that a modern editor like Ace would work fine for Unicode, or at least for that subset of Unicode that Javascript supports.
Ace knows how to render an ASCII line feed (U+000A) (as a line break), but apparently does not know how to render a Unicode line separator (which should also be rendered as a line break).
Replacing all the Line Separators with line feeds does not seem like an acceptable solution; text editors should not change the text that they are editing unless the user says so.
The text was updated successfully, but these errors were encountered: