Update license-matching-guidelines-and-templates.md #2469
Conversation
fixes #1617 Adds guideline for ---, ***, etc. Also updated punctuation guideline to note that exceptions (e.g., Oxford comma or not) may have markup.
|
heads up @goneall - I did NOT put this in the punctuation guideline, since this is not punctuation, but is more like code comments (in my view) as these are similarly characters that are not there for the text, but more for formatting. I was trying not to make an entirely new guideline, since it doesn't seem to warrant that. |
Thanks for the heads-up - the changes look good to me and are already implemented in the Java and online tools |
|
@swinslow - you want to review and merge? |
|
|
||
| ### B.7.1 Purpose <a name="B.7.1"></a> | ||
|
|
||
| To avoid the possibility of a non-match due to the existence or absence of code comment indicators placed within the license text, e.g. at the start of each line of text. | ||
| To avoid the possibility of a non-match due to the existence or absence of code comment indicators placed within the license text, e.g., at the start of each line of text, or repetitive characters to establish a separation of text, e.g., ---, ===, ___, or ***. |
There was a problem hiding this comment.
Super-minor nit, looks like there's a stray extra space introduced by accident between "to" and "the"
Signed-off-by: Steve Winslow <steve@swinslow.net>
fixes #1617
Adds guideline for ---, ***, etc.
Also updated punctuation guideline to note that exceptions (e.g., Oxford comma or not) may have markup.