Repository navigation
Capitalization, punctuation and spelling fixes - #784
Conversation
Use straight marks in source files (txt, md) and curly marks in rendered files (html)
What is the rationale for harmonizing on straight marks in source files? I don't feel strongly about that outside of the license texts themselves, but I'd rather not touch those. The other two changes look good, thanks! |
|
It's common to limit source files to ASCII-only characters, where possible, to facilitate editing, search/replace operations, avoid potential ambiguities in diffs, etc. I understand that the license texts themselves are not supposed to be edited, but in practice things like typo fixes (case in point!), line wrapping, indentation adjustments, etc. tend to happen, so it's best to keep them text-editor friendly. This is also recommended by style guides such as Google's and Wikipedia's. (As an aside, this article may be an interesting read on this topic.) By the way: these were pretty much the only non-ASCII characters ( |
|
The .html and .md files here each get rendered as HTML. I pushed another commit to use curly throughout, and reverted the license text changes. I'd prefer license text changes get made in https://github.com/spdx/license-list-XML first, and copy what happens there here. |
Use "Sentence case" instead of "Title Case", since the former style was more prevalent.
Use straight marks in source files (txt, md) and curly marks in rendered files (html).