Tissevert/pandoc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
pandoc/test/command/sloppypar.md

230 lines
3.7 KiB
Markdown
Raw Normal View History

LaTeX reader: parse sloppypar environment (#4517)
2018-04-02 18:33:29 +02:00
```
% pandoc -f latex+raw_tex -t native
\begin{sloppypar}
Sequi id qui facere et incidunt ut. Et fuga ut voluptate enim qui. Odit unde magni ipsam dicta modi. Modi soluta velit est aut aut possimus.
Qui et temporibus explicabo. Esse ab ut quidem. Vel qui perspiciatis quae odio consectetur alias non sed. Quo consectetur libero omnis quos eius ad vel.
\end{sloppypar}
^D
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 "Sequi"
, Space
, Str "id"
, Space
, Str "qui"
, Space
, Str "facere"
, Space
, Str "et"
, Space
, Str "incidunt"
, Space
, Str "ut."
, Space
, Str "Et"
, Space
, Str "fuga"
, Space
, Str "ut"
, Space
, Str "voluptate"
, Space
, Str "enim"
, Space
, Str "qui."
, Space
, Str "Odit"
, Space
, Str "unde"
, Space
, Str "magni"
, Space
, Str "ipsam"
, Space
, Str "dicta"
, Space
, Str "modi."
, Space
, Str "Modi"
, Space
, Str "soluta"
, Space
, Str "velit"
, Space
, Str "est"
, Space
, Str "aut"
, Space
, Str "aut"
, Space
, Str "possimus."
]
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 "Qui"
, Space
, Str "et"
, Space
, Str "temporibus"
, Space
, Str "explicabo."
, Space
, Str "Esse"
, Space
, Str "ab"
, Space
, Str "ut"
, Space
, Str "quidem."
, Space
, Str "Vel"
, Space
, Str "qui"
, Space
, Str "perspiciatis"
, Space
, Str "quae"
, Space
, Str "odio"
, Space
, Str "consectetur"
, Space
, Str "alias"
, Space
, Str "non"
, Space
, Str "sed."
, Space
, Str "Quo"
, Space
, Str "consectetur"
, Space
, Str "libero"
, Space
, Str "omnis"
, Space
, Str "quos"
, Space
, Str "eius"
, Space
, Str "ad"
, Space
, Str "vel."
]
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
]
LaTeX reader: parse sloppypar environment (#4517)
2018-04-02 18:33:29 +02:00
```
```
% pandoc -f latex -t native
\begin{sloppypar}
Sequi id qui facere et incidunt ut. Et fuga ut voluptate enim qui. Odit unde magni ipsam dicta modi. Modi soluta velit est aut aut possimus.
Qui et temporibus explicabo. Esse ab ut quidem. Vel qui perspiciatis quae odio consectetur alias non sed. Quo consectetur libero omnis quos eius ad vel.
\end{sloppypar}
^D
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 "Sequi"
, Space
, Str "id"
, Space
, Str "qui"
, Space
, Str "facere"
, Space
, Str "et"
, Space
, Str "incidunt"
, Space
, Str "ut."
, Space
, Str "Et"
, Space
, Str "fuga"
, Space
, Str "ut"
, Space
, Str "voluptate"
, Space
, Str "enim"
, Space
, Str "qui."
, Space
, Str "Odit"
, Space
, Str "unde"
, Space
, Str "magni"
, Space
, Str "ipsam"
, Space
, Str "dicta"
, Space
, Str "modi."
, Space
, Str "Modi"
, Space
, Str "soluta"
, Space
, Str "velit"
, Space
, Str "est"
, Space
, Str "aut"
, Space
, Str "aut"
, Space
, Str "possimus."
]
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 "Qui"
, Space
, Str "et"
, Space
, Str "temporibus"
, Space
, Str "explicabo."
, Space
, Str "Esse"
, Space
, Str "ab"
, Space
, Str "ut"
, Space
, Str "quidem."
, Space
, Str "Vel"
, Space
, Str "qui"
, Space
, Str "perspiciatis"
, Space
, Str "quae"
, Space
, Str "odio"
, Space
, Str "consectetur"
, Space
, Str "alias"
, Space
, Str "non"
, Space
, Str "sed."
, Space
, Str "Quo"
, Space
, Str "consectetur"
, Space
, Str "libero"
, Space
, Str "omnis"
, Space
, Str "quos"
, Space
, Str "eius"
, Space
, Str "ad"
, Space
, Str "vel."
]
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
]
LaTeX reader: parse sloppypar environment (#4517)
2018-04-02 18:33:29 +02:00
```
Reference in a new issue Copy permalink