5 ms·
Semantic Linefeeds (2012)
- 082349872349872 4y agocf https://vanemden.wordpress.com/2009/01/01/ventilated-prose/ https://vanemden.wordpress.com/2009/01/01/ventilated-prose/ (one of the early hints that Donald Knuth was of the tribe which would become known as "geek" is that as a schoolchild he loved diagramming sentences)
- trynewideas 4y agoIf you prefer this in the form of a Creative Commons-licensed spec for some reason, https://github.com/sembr/specification https://github.com/sembr/specification
- jwilk 4y agoPreviously: 2019: https://news.ycombinator.com/item?id=19256059 https://news.ycombinator.com/item?id=19256059 (11 comments) 2012: https://news.ycombinator.com/item?id=4642395 https://news.ycombinator.com/item?id=4642395 (35 comments)
- chrismorgan 4y agoI took up a similar style for most of my writing perhaps a year ago, with a strong preference for breaking at punctuation. (I even sometimes do it to a more limited extent in handwriting.) This has influenced my writing style, which naturally inclines to more complex structures, to favour shorter clauses—though certainly I still end up with plenty of non-punctuation-adjacent line breaks. My greatest annoyance with the style (which honestly is the sole reason I didn’t take it up a few years earlier) is bad handling of em dashes, of which I am fond. In normal English typesetting, there is a line-breaking opportunity before and after the dash, but no space; but in all markup languages that I know of that support soft breaks, the line break is equivalent to a space. Well, actually this is no longer normative for HTML (see https://www.w3.org/TR/css-text-3/#line-break-transform https://www.w3.org/TR/css-text-3/#line-break-transform, which shows the problem for CJK, which doesn’t use spaces between words), but for now, all user agents still implement it as “line break → space”. Consequently, when writing in these markup languages, I can’t break the line after an em dash as I would like to, because it would change the output. One of the features of the lightweight markup language I’ve been designing, then, is the ability to control soft break behaviour in order to correctly handle at least CJK and em dashes that were not otherwise paired with a space. (And I’m curious if anyone has similar cases not well-served by current rules.) —⁂— (If you’re not sure what I’m talking of: source: Example: an em dash— like this. Expected result: > Example: an em dash—like this. Actual result in the likes of HTML, Markdown and reStructuredText: > Example: an em dash— like this.
- yakubin 4y agoShouldn't an em dash be surrounded with spaces on each side anyway?
- kqr 4y agoNot in English. The two equivalent English alternatives -- as far as I know -- are the en dash surrounded by spaces---or the em dash with no space. I actually like the look of the em dash with no space better, but for the reasons mentioned in the GP I end up using the en dash anyway. (Another reason is that Swedish, which I also write, only has the en dash, so its nice that I can be consistent.)
- kragen 4y agoi've read a lot of books professionally typeset in english that either do or don't space around em dashes — used to denote pauses, in the way we are discussing here. my preference is to space around them, but i prefer using \u2009 'thin space' instead of a full word space. unfortunately hn rewrites that to a full word space.
- chrismorgan 4y agoI don’t think I’ve ever seen a professionally-set work using spaces around em dashes. The two popular conventions are space–en-dash–space (“a – b”) and em-dash (“a—b”). I only recall ever encountering space–em-dash–space a few times (one of which was within the last few days, and the previous was probably years ago), in amateur work. THIN SPACE would certainly make me much more amenable to it, but frankly that suggests a font problem (and I do certainly know of fonts where the em dash spacing is awful and if forced to use that font I would insert THIN SPACE (or very occasionally NARROW NO-BREAK SPACE) every time).
- shanebellone 4y agoMight the em dash convention be a byproduct of the printing press and fixed-width layouts?
- somat 4y agoI picked up the habit of putting a line feed after most puncuation from writing troff(mandoc actually) manual pages, where it is almost required. That it also works in html and markdown is nice. The main advantage is that you get really nice diffs.
- greenbit 4y agoA trove of links in that, a pdf-hoarder's delight. Some of the linked pages appear to be in Japanese, though scrolling down on those reveals a fair amount of English content, for those who don't grok Japanese.
- kqr 4y agoThis is something I've attempted to adopt at a few times, but I come back to editing the text closer to the format in which I'll read it. Whenever I try to analyse my reasons for this, I find they're all bogus except perhaps one: with fewer linebreaks, there's a higher density of stuff on screen, which means I can refer back to more text as I'm writing. I don't think this is a particularly good reason in the age of marks, though.
- kragen 4y agoprobably in 01974 with an asr-33 printing 10 characters per second†, where you also had the ability to tear off an unlimited amount of scrollback and arrange it on your desk wherever you wish, the ergonomic considerations were somewhat different ______ † previous versions of this comment erroneously stated higher (and implausible) data rates
- deleted 4y ago[deleted]
- pwdisswordfishc 4y agoThe lengths to which people go to accommodate line-based diffing algorithms instead of creating better diff tools.
- meindnoch 4y agoOr just use git diff —-word-diff
- funstuff007 4y agoRachel by the Bay would hate this: https://rachelbythebay.com/w/2012/08/30/pain/ https://rachelbythebay.com/w/2012/08/30/pain/ https://rachelbythebay.com/w/2012/08/31/lines/ https://rachelbythebay.com/w/2012/08/31/lines/
- mjburgess 4y agoAs far as I can tell, that's more-or-less her position. Code has semantic breakable-points throughout lines of code, and she's advocating breaking.
- Rich_Morin 4y agoBreaking lines at logical boundaries in the "source code" makes it easier for me to see the structure of the text. It also gives me the ability to see the text in two different layouts; this often lets me spot errors which would otherwise slip by.
- wwalexander 4y agoI have my résumé written in LaTeX and format it like this, mostly so that I can comment or un-comment specific bullet points depending on what’s relevant to a certain job application, rather than maintaining multiple versions.
- benibela 4y agoOr write everything in one line It is annoying when you search for two words and they are not found, because they are on different lines We just need better diff/merge tools that can handle text without line breaks. wdiff is installed everywhere for in-line diffs, but no one seems to maintain it. There have been patches sitting around for years: https://savannah.gnu.org/patch/?group=wdiff https://savannah.gnu.org/patch/?group=wdiff