Appearance of block_dlist for tex backend about asciidoctor-latex

[jirutka]

How can I address it? What dlist code do you mean?

[jxxcarlson]

Its this code:

https://github.com/asciidoctor/asciidoctor-latex/blob/master/lib/asciidoctor/latex/node_processors.rb#L224-L239

the tex output would look better if when a dlist has lists as items, those lists
start underneath the definition term. Otherwise the first item is out of line line with the others and while it succeeds syntactically and semantically, it fails esthetically.

See what I mean by looking at the pdf output arising from block_dlist.tex

I don’t recall writing this code and thought perhaps tat you did.

On Apr 27, 2015, at 7:03 PM, Jakub Jirutka [email protected] wrote:

How can I address it? What dlist code do you mean?

—
Reply to this email directly or view it on GitHub.

[jirutka]

There’s a nice feature in git called blame, see this. I’ve just fixed some (technical) bug, don’t know how it looks in LaTeX. So feel free to edit it as you like. :)

[jxxcarlson]

I don’t see your changes. Where do I look?

I see that the code is Otavo’s. Blame is great except possibly for the name_.

On Apr 27, 2015, at 7:47 PM, Jakub Jirutka [email protected] wrote:

There’s a nice feature in git called blame, see this https://github.com/asciidoctor/asciidoctor-latex/blame/master/lib/asciidoctor/latex/node_processors.rb#L224-L239. I’ve just fixed some (technical) bug, don’t know how it looks in LaTeX. So feel free to edit it as you like. :)

—
Reply to this email directly or view it on GitHub #31 (comment).

[mojavelinux]

Blame is great except possibly for the name

Unfortunately true. It is terminology that was inherited from subversion and now deeply embedded in the revision control community. The proper name for it is "annotate". SVN has even aliased the term "praise" since.

[jirutka]

Actually this name is correct in this case – James needed to find who to blame for the code. 😼

[jxxcarlson]

Ah — but it was more praise than blame! Very good code (by @otavo) — needs
one esthetic tweak.

On Apr 28, 2015, at 7:37 AM, Jakub Jirutka [email protected] wrote:

Actually this name is correct in this case – James needed to find who to blame for the code.

—
Reply to this email directly or view it on GitHub #31 (comment).