Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Specification Alternatives
Similar projects and alternatives to specification
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better specification alternative or higher similarity.
specification reviews and mentions
Posts with mentions or reviews of specification.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-10.
-
What do you all think about (setq sentence-end-double-space nil)?
If you publish to HTML from a format that uses double line breaks as paragraph breaks, such as Markdown, you should strongly consider putting line breaks after each sentence. This leads to more useful diffs. If you do that consistently, full stops at line end are sentence ends; full stops within a line are not.
-
Markdown alternative for personal documents (not web!)
Markdown's treatment of white space is a feature, not a bug. It supports semantic line breaks.
-
markdown-mode: how to render visually wrapped multi-line list items as a block?
Prefer breaking lines between sentences first, then at clause boundaries, then, if necessary, at smaller units. This makes it more likely that you get meaningful, readable diffs when using a version control system. See https://sembr.org/ for examples, guidelines, and further explanations.
-
Semantic Linefeeds (2012)
If you prefer this in the form of a Creative Commons-licensed spec for some reason, https://github.com/sembr/specification
-
LaTeX Makes Me Angry
> How is that difficult? Most text editors support word wrapping and syntax highlighting.
To add to this, I personally prefer using semantic linefeeds — adding a newline after each sentence or clause (as in e.g. [0] [1]). I find this works exceptionally well with LaTeX, since I get the benefit of the newlines as I write and edit, while the typeset version is formatted nicely into paragraphs for me.
(Not that this is unique to LaTeX, of course; Markdown would be no different. The technique works well with all such tools.)
[0] https://vanemden.wordpress.com/2009/01/01/ventilated-prose/
[1] https://sembr.org/
- Semantic Line Breaks
- No-one knows what they are doing
-
Writing One Sentence per Line
SemBr author here. I chose SHOULD NOT for this rule for a couple reasons: First, as an affordance for text with ambiguous or unknown meaning. Second, as a hedge against introducing new meaning unintentionally.
Adding a semantic line break inherently changes the relationship between words, and we can't always be sure about the intended meaning of text. If this were MUST NOT, then any modification would risk violating the spec.
Then again, this may be my own, idiosyncratic reading of RFC 2119. If you'd like to discuss this further, feel free to open an issue on the GitHub repo here: https://github.com/sembr/specification/issues
-
A note from our sponsor - InfluxDB
www.influxdata.com | 1 May 2024
Stats
Basic specification repo stats
9
70
0.0
2 months ago
Popular Comparisons
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com