Docs: Broken formatting in Reflection guide

[ChrisMaddock]

https://docs.microsoft.com/en-us/dotnet/framework/reflection-and-codedom/specifying-fully-qualified-type-names

On this page the table "Backus-Naur Form Grammar for Type Names" is rendering incorrectly. Here's what it previously looked like on msdn: https://msdn.microsoft.com/it-it/library/yfsftwz6(v=vs.110).aspx

OLD

NEW

[mairaw]

Thanks for letting us know @ChrisMaddock! We'll address it shortly. It's probably due to the use of pipes.

[BillWagner]

@terrajobst One solution would be to translate from BNF to ANTLR, and use the ANTLR grammar syntax highlighter. See example from the C# grammar

Thoughts?

[terrajobst]

Like this? Yep, looks very readable to me. 👍

TypeSpec
    : ReferenceTypeSpec
    | SimpleTypeSpec
    ;

ReferenceTypeSpec
    : SimpleTypeSpec '&'
    ;

SimpleTypeSpec
    : PointerTypeSpec
    | ArrayTypeSpec
    | TypeName
    ;

PointerTypeSpec
    : SimpleTypeSpec '*'
    ;

ArrayTypeSpec
    : SimpleTypeSpec '[ReflectionDimension]'
    | SimpleTypeSpec '[ReflectionEmitDimension]'
    ;

ReflectionDimension
    : '*'
    | ReflectionDimension ',' ReflectionDimension
    | NOTOKEN
    ;

ReflectionEmitDimension
    : '*'
    | Number '..' Numero
    | Number '…'
    | ReflectionDimension ',' ReflectionDimension
    | NOTOKEN
    ;

Number
    : [0-9]+
    ;

TypeName
    : NamespaceTypeName
    | NamespaceTypeName ',' AssemblyNameSpec
    ;

NamespaceTypeName
    : NestedTypeName
    | NamespaceSpec '.' NestedTypeName
    ;

NestedTypeName
    : IDENTIFIER
    | NestedTypeName '+' IDENTIFIER
    ;

NamespaceSpec
    : IDENTIFIER
    | NamespaceSpec '.' IDENTIFIER
    ;

AssemblyNameSpec
    : IDENTIFIER
    | IDENTIFIER ',' AssemblyProperties
    ;

AssemblyProperties
    : AssemblyProperty
    | AssemblyProperties ',' AssemblyProperty
    ;

AssemblyProperty
    : AssemblyPropertyName '=' AssemblyPropertyValue
    ;

[BillWagner]

@mairaw Do you want help with this one?

[mairaw]

Hey @BillWagner, thanks for the offer. I'm not particularly attached to this issue, so feel free to take over if you'd like.