Line wrapping fixes #149
Line wrapping fixes #149
Conversation
the md->rfc process doesn’t auto-linewrap inserted code, so these xml were exceeding the allowed 72 char width. Intended to resolve #148
breaks alignment but fixes compliance with chars-per-line limit
| @@ -320,7 +320,7 @@ The path defines the allowed storage locations of the `EBML Element` within an ` | |||
| The `path` attribute is REQUIRED. | |||
|
|
|||
| ``` | |||
| EBMLFullPath = EBMLElementOccurrence "(" EBMLReferencePath ")" | |||
| EBMLFullPath = EBMLElementOccurrence "(" EBMLReferencePath ")" | |||
There was a problem hiding this comment.
LUTM, but fixes the issue (U = ugly ;-)
There was a problem hiding this comment.
i can't think of a better idea, unless @robUx4 wants to rename one of these components to use a shorter string length.
There was a problem hiding this comment.
Unless @retokromer comes with something less U, I think it's fine.
There was a problem hiding this comment.
Could also resolve by renaming VariableParentOccurrence to VarParentOccurrence.
There was a problem hiding this comment.
No, I don’t have a proposal having less U. As Dave said, only shorter names would prevent it. That said, this fixes the issue of the «miniature pages».
There was a problem hiding this comment.
I think shorter names are less U than breaking alignment.
|
fixes #148 |
|
LGTM although it might break the ugly code that's generating various code from the XML source. |
breaks alignment but fixes compliance with chars-per-line limit