Tissevert/pandoc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions1
pandoc/test/rtf/formatting.native

46 lines
974 B
Text
Raw Permalink Normal View History

Use pretty-simple to format native output. Previously we used our own homespun formatting. But this produces over-long lines that aren't ideal for diffs in tests. Easier to use something off-the-shelf and standard. Closes #7580. Performance is slower by about a factor of 10, but this isn't really a problem because native isn't suitable as a serialization format. (For serialization you should use json, because the reader is so much faster than native.)
2021-09-19 12:09:51 -07:00
Pandoc
Switch from pretty-simple to pretty-show for native output. Update tests. Reason: it turns out that the native output generated by pretty-simple isn't always readable by the native reader. According to https://github.com/cdepillabout/pretty-simple/issues/99 it is not a design goal of the library that the rendered values be readable using 'read'. This makes it unsuitable for our purposes. pretty-show is a bit slower and it uses 4-space indents (non-configurable), but it doesn't have this serious drawback.
2021-09-28 21:17:53 -07:00
Meta
{ unMeta =
fromList
[ ( "operator"
, MetaInlines [ Str "John" , Space , Str "MacFarlane" ]
)
]
Use pretty-simple to format native output. Previously we used our own homespun formatting. But this produces over-long lines that aren't ideal for diffs in tests. Easier to use something off-the-shelf and standard. Closes #7580. Performance is slower by about a factor of 10, but this isn't really a problem because native isn't suitable as a serialization format. (For serialization you should use json, because the reader is so much faster than native.)
2021-09-19 12:09:51 -07:00
}
[ Para
Switch from pretty-simple to pretty-show for native output. Update tests. Reason: it turns out that the native output generated by pretty-simple isn't always readable by the native reader. According to https://github.com/cdepillabout/pretty-simple/issues/99 it is not a design goal of the library that the rendered values be readable using 'read'. This makes it unsuitable for our purposes. pretty-show is a bit slower and it uses 4-space indents (non-configurable), but it doesn't have this serious drawback.
2021-09-28 21:17:53 -07:00
[ Str "This"
, Space
, Str "is"
, Space
, Str "a"
, Space
, Str "test"
, Space
, Str "of"
, Space
, Str "FORMATTING."
, Space
, Str "This"
, Space
, Str "is"
, Space
, Str "hidden:"
, Space
, Str "."
]
, Para [ SmallCaps [ Str "Small" , Space , Str "Caps" ] ]
, Para [ Strong [ Str "bold" ] ]
, Para [ Emph [ Str "italics" ] ]
, Para
[ Strong
[ Str "bold"
, Space
, Emph [ Str "and" , Space , Str "italics" ]
]
]
, Para [ Underline [ Str "underlined" ] ]
, Para [ Strikeout [ Str "strikeout" ] ]
, Para [ Str "x" , Superscript [ Str "superscript" ] ]
, Para [ Str "x" , Subscript [ Str "subscript" ] ]
Use pretty-simple to format native output. Previously we used our own homespun formatting. But this produces over-long lines that aren't ideal for diffs in tests. Easier to use something off-the-shelf and standard. Closes #7580. Performance is slower by about a factor of 10, but this isn't really a problem because native isn't suitable as a serialization format. (For serialization you should use json, because the reader is so much faster than native.)
2021-09-19 12:09:51 -07:00
]
Reference in a new issue Copy permalink