-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Whitespace handling #18
Comments
What are the downsides of reversing the behaviour?
|
Sorry, I'm not following. Reversing which behavior? If you mean make the no-break features work by removing line breaks, then both issues are largely unaffected—i.e., they're still issues. The specific problem there isn't what's being done so much as how it's being done—i.e., modifying the source before anything else sees it versus as part of normal process—though, what's being done is sub-optimal as well. |
What I meant is changing the processing so that it treats line-breaks the same way that a web-browser do when they are encounter in HTML, (eg. it ignores them, unless in |
So, remove the That's definitely an idea, though, like the changing the syntax one, it's on the outer limits. What I mean is that lots of users do use the no-break features, but my feeling is that those are the squeaky wheels and most actually do make use of the I do like the idea in principle though. |
If blocks are introduced (I recognize that this is a suggestion on a suggestion on a suggestion) you could add features like nobr and even silently to the blocks themselves through some sort of syntax. Maybe tags or some other syntax element at the start of a block. |
If you reverse the behavior, that does not mean you cannot still have means to optionally turn it back on--you could by default ignore newlines much like the browser does and fall back to the scv2 default behavior upon I picked "nlbr" because it was short (in fact the same size as "nobr") and means "newline break" meaning newlines get treated as markup and are turned into line breaks ( |
Should whitespace handling be changed? Currently, there are a couple basic mechanisms to control line breaks, but not much more than that.
Spacing control
There are no current spacing control mechanisms.
Line break control
The two basic mechanisms of line break control are (in order of implementations): line continuations and the no-break features—in order:
nobr
tag,<<nobr>>
macro,Config.passages.nobr
setting.Line continuations: (markup-based)
No-breaks: (source editing-based)
<<script>>
code.A potential fix for both of the issues of the no-break features would be to make them, essentially, markup-based as well by simply having them disable the
lineBreak
parser. The downside would be that thenobr
tag could not be converted over thus and would need to be dropped, leaving only the macro and global setting.The text was updated successfully, but these errors were encountered: