Minor updates #43
Minor updates #43
Conversation
…e escape sequences list
gkellogg
added
the
spec:enhancement
| <a href="#grammar-production-IRIREF" ><code>IRIREF</code> </a>, | ||
| <a href="#grammar-production-STRING_LITERAL_SINGLE_QUOTE" ><code>STRING_LITERAL_SINGLE_QUOTE</code> </a>, | ||
| <a href="#grammar-production-STRING_LITERAL_QUOTE" ><code>STRING_LITERAL_QUOTE</code> </a>, | ||
| <a href="#grammar-production-STRING_LITERAL_LONG_SINGLE_QUOTE"><code>STRING_LITERAL_LONG_SINGLE_QUOTE</code></a>, or | ||
| <a href="#grammar-production-STRING_LITERAL_LONG_QUOTE" ><code>STRING_LITERAL_LONG_QUOTE</code> </a>, |
There was a problem hiding this comment.
Note that the WS gaps between </code> and </a> — though folded to a single variable-width space character — will remain in the HTML, between the text of the anchor and the following comma (e.g., IRIREF ,). This is usually not problematic, but it often looks bad. Better to always have no WS between the content of an <a> element and the closing </a>. If you want to retain the whitespace to make the ReSpec source easier to edit, you can put it into the </a> itself, as </a >.
There was a problem hiding this comment.
It's a pretty long-standing pattern for "RDF Term Constructors", at least Turtle and TriG to make the code easier to maintain. Other places, such as you note here, don't present the same layout problem.
Preview | Diff