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

89 lines
1.8 KiB
Markdown
Raw Normal View History

lstinline with braces can be used (verb cannot be used with braces) (#3535) * Fix lstinline handling: lstinline with braces can be used (verb cannot be used with braces) * Use codeWith and determine the language from lstinline * Improve code * Add another test: convert lstinline without language option
2017-03-29 14:49:46 +02:00
```
% pandoc -f latex -t html
I want to explain the interface of \lstinline[language=Java]{public class MyClass}.
^D
HTML writer: don't break attributes values when wrapping.
2022-01-10 19:40:49 +01:00
<p>I want to explain the interface of <code
class="sourceCode java"><span class="kw">public</span> <span
class="kw">class</span> MyClass</code>.</p>
lstinline with braces can be used (verb cannot be used with braces) (#3535) * Fix lstinline handling: lstinline with braces can be used (verb cannot be used with braces) * Use codeWith and determine the language from lstinline * Improve code * Add another test: convert lstinline without language option
2017-03-29 14:49:46 +02:00
```
```
% pandoc -f latex -t html
I want to explain the interface of \lstinline{public class MyClass}.
^D
Add text wrapping to HTML output. Previously the HTML writer was exceptional in not being sensitive to the `--wrap` option. With this change `--wrap` now works for HTML. The default (as with other formats) is automatic wrapping to 72 columns. A new internal module, T.P.Writers.Blaze, exports `layoutMarkup`. This converts a blaze Html structure into a doclayout Doc Text. In addition, we now add a line break between an `img` tag and the associated `figcaption`. Note: Output is never wrapped in `writeHtmlStringForEPUB`. This accords with previous behavior since previously the HTML writer was insensitive to `--wrap` settings. There's no real need to wrap HTML inside a zipped container. Note that the contents of script, textarea, and pre tags are always laid out with the `flush` combinator, so that unwanted spaces won't be introduced if these occur in an indented context in a template. Closes #7764.
2021-12-20 22:44:03 +01:00
<p>I want to explain the interface of <code>public class
MyClass</code>.</p>
lstinline with braces can be used (verb cannot be used with braces) (#3535) * Fix lstinline handling: lstinline with braces can be used (verb cannot be used with braces) * Use codeWith and determine the language from lstinline * Improve code * Add another test: convert lstinline without language option
2017-03-29 14:49:46 +02:00
```
```
% pandoc -f latex -t native
I want to explain the interface of \lstinline[language=Java]{public class MyClass}.
^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 21:09:51 +02: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-29 06:17:53 +02:00
[ Str "I"
, Space
, Str "want"
, Space
, Str "to"
, Space
, Str "explain"
, Space
, Str "the"
, Space
, Str "interface"
, Space
, Str "of"
, Space
, Code ( "" , [ "java" ] , [] ) "public class MyClass"
, Str "."
]
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 21:09:51 +02:00
]
lstinline with braces can be used (verb cannot be used with braces) (#3535) * Fix lstinline handling: lstinline with braces can be used (verb cannot be used with braces) * Use codeWith and determine the language from lstinline * Improve code * Add another test: convert lstinline without language option
2017-03-29 14:49:46 +02:00
```
Add support for latex mintinline (#4365)
2018-08-18 05:57:36 +02:00
```
% pandoc -f latex -t html
I want to explain the interface of \mintinline{java}{public class MyClass}.
^D
HTML writer: don't break attributes values when wrapping.
2022-01-10 19:40:49 +01:00
<p>I want to explain the interface of <code
class="sourceCode java"><span class="kw">public</span> <span
class="kw">class</span> MyClass</code>.</p>
Add support for latex mintinline (#4365)
2018-08-18 05:57:36 +02:00
```
```
% pandoc -f latex -t html
I want to explain the interface of \mintinline{java}|public class MyClass|.
^D
HTML writer: don't break attributes values when wrapping.
2022-01-10 19:40:49 +01:00
<p>I want to explain the interface of <code
class="sourceCode java"><span class="kw">public</span> <span
class="kw">class</span> MyClass</code>.</p>
Add support for latex mintinline (#4365)
2018-08-18 05:57:36 +02:00
```
```
% pandoc -f latex -t native
I want to explain the interface of \mintinline[linenos]{java}{public class MyClass}.
^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 21:09:51 +02: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-29 06:17:53 +02:00
[ Str "I"
, Space
, Str "want"
, Space
, Str "to"
, Space
, Str "explain"
, Space
, Str "the"
, Space
, Str "interface"
, Space
, Str "of"
, Space
, Code ( "" , [ "java" ] , [] ) "public class MyClass"
, Str "."
]
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 21:09:51 +02:00
]
Add support for latex mintinline (#4365)
2018-08-18 05:57:36 +02:00
```
Reference in a new issue Copy permalink