Bumped Kramdown to 1.9.0

[Stargator]

Changes that come with updating from 1.5.0 to 1.9.0

Changes from 1.9.0

• 10 changes:
  • Updated Rakefile to fix website generation
  • Simplified AST converter and renamed it to HashAST
  • Implements an Abstract Syntax Tree converter that returns a Ruby hash
  • If the footnote_backlink option is empty, no backlinks will be created
  • Added line location test for GFM parser with hard wrapped paragraphs
  • Added missing location to elements created while using hard_wrap option.
  • Enhanced rouge syntax highlighter to allow separate span/block options
  • Fixed testing script
  • Mentioned in Rouge docs that Rouge options are supported, too
  • Added link to the news page with change information in the readme

Changes from 1.8.0

• 4 minor changes:
  • The LaTeX converter now uses \texttt instead of \tt for code spans (fixes #257, reported
    by richard101696)
  • New option footnote_backlink for changing the backlink of footnotes in the HTML converter
    (fixes #247, requested by Benjamin Esham)
  • A quote directly followed by an ellipsis is now converted into an opening quotation mark (fixes
    #253, requested by Michael Franzl)
  • Removed warning for self-closing HTML elements that are not self-closed (fixes #262, requested
    by Gregory Pakosz)
• 3 bug fixes:
  • Fixed #251: The special character sequence ``` now works correctly when used in footnotes
    or headers that appear in the table of contents (reported by Peter Kehl)
  • Fixed #254: kramdown crashed on encountering a table with multiple consecutive separator lines
    (reported by Christian Kruse)
  • Fixed #256: Certain footnote definitions and codeblocks lead to crashes or unneeded
    backtracking in the regular expression engine - fixed by using atomic grouping (reported by Ali
    Ok)

Changes from 1.7.0

This release brings among other things support for the ‘minted’ syntax highlighter for LaTeX and a new math engine based on MathJax-Node that outputs to MathML.

• 4 minor changes:
  • The syntax highlighter 'minted' for the LaTeX
    converter is now available (fixes issue #93, initial patch #242 by
    l3kn)
  • A new math engine based on MathJax-Node that outputs to
    MathML is now available (patch #240 by Tom Thorogood)
  • Fixed #244, #246: Fenced code blocks now allow a dash in the code language name (requested
    and patched by Dennis Günnewig)
  • The option list in the man page as well in the output of kramdown --help is now sorted.
• 2 bug fixes:
  • Fixed #230: Warning message for method in lib/kramdown/utils/configurable.rb will not show
    anymore (reported by Robert A. Heiler)
  • Fixed #239: Handling of single/double quotes in reference style links now follows the same
    rules as with inline links (reported by Josh Davis)

Changes from 1.6.0

This release contains many fixes and minor enhancements as well as one major goodie that comes with a small caveat: block IALs can now be applied to link and abbreviation definitions!

It may not sound like much but allowing block IALs to be applied to link definitions alleviates the problem that additional attributes could only be specified via span IALs. Now such attributes can be stored together with the URL and title at the link definition

• 7 minor changes:
  • Block IALs can now be applied to link and abbreviation definitions (inspired by issue #194
    from cabo)
  • The syntax highlighting engine for Rouge now allows custom formatter classes to be used (issue
    #214, requested by BackOrder)
  • The MathJax math engine now allows adding previews (issue #225, requested by jethrogb)
  • The "toc_levels" option can now also take a Range object (pull request #210 by Jens Krämer)
  • The generated table of contents of the HTML converter now contains ID attributes on the links so
    that back-references can be used (issue #195, requested by Ciro Santilli)
  • A warning is now generated when duplicate HTML attributes are detected (issue #201, requested
    by winniehell)
  • Updated used version of prawn to 2.0.0
• 8 bug fixes:
  • Fixed #192: Emphasis by using underscore sometimes wrongly worked within a word (reported by
    Michael Franzl)
  • Fixed #198: Empty alt attributes on <img> tags are now correctly handled by the kramdown
    converter (reported by winniehell)
  • Fixed #200: Trailing whitespace is now really removed in paragraphs (reported by winniehell)
  • Fixed #220: HTML blocks with attributes weren't correctly detected when directly after another
    block (reported by Bill Tozier)
  • Fixed #199: Empty title attributes are now ignored for images when using the kramdown
    converter (reported by and pull request #206 from winniehell)
  • Leading and trailing white space from math statements is now stripped as the whitespace
    sometimes lead to LaTeX conversion errors
  • Fixed #226: Class names may now start with a dash in IALs/ALDs (reported by Adam Hardwick)
  • Multiple consecutive block IALs before an element are now correctly processed

[fernseed]

+1 for this, block IALs for links and images (kramdown 1.6.0 and above) would be extremely handy.

[gjtorikian]

@Stargator Any interest in bringing this to 1.8.0?

I've also sent this over for review to our security team. No estimates on when the review will be completed. Thanks for your patience!

[Stargator]

No problem @gjtorikian. I'll update by tomorrow. The wait isn't an issue either. I chose to polish up the branches during a vacation I had, so it just gave me stuff to do.

Considering there have been a few changes to the master branch here, I'm not sure how to just update the branch without it trying to pull in all the changes. Or should I just create an update branch and up Kramdown to 1.8.0?

I want to keep the commits that get pulled as simple as possible.

[parkr]

I usually create a new branch with every change, so perhaps submit a new PR?

[pathawks]

I'm not sure how to just update the branch without it trying to pull in all the changes.

Hard reset to the previous commit, pull from master, make the change. 👍

[Stargator]

Updated to version 1.8.0. Thanks @pathawks that helped a lot.

[parkr]

@Stargator Can you update the pull request description, too? To include 1.7.0 to 1.8.0 changes.

[Stargator]

@parkr Yes I can. 😄

[aldanor]

@gjtorikian

Is there any news re: bumping this to 1.8.0?

[gjtorikian]

To be honest, this was 👍ed by security, I just haven't had a chance to bring it in yet due to other Life Events. Assigning it to myself so I don't forget.

[mstred]

Hey guys, is it OK to merge this to master?

[Stargator]

@mstred it seems to be since @gjtorikian stated security gave the 👍

[parkr]

@mstred There's a little more legwork to be done on GitHub's side once Security gives the 🆗 . They'll get to it soon!

[Stargator]

Thanks @parkr for the clarification!

[mstred]

Thank you all. I'll stay tuned. 👍

[Stargator]

I am reopening the pull request as I have updated it to Kramdown 1.9.0. I didn't intend to close it, it seems that was done automatically through Github's own monitoring process.

[benbalter]

Added this commit to the WIP Jekyll 3.0.x PR, and hope to be able to merge it as part of the 3.0.x bump to minimize the number of rounds of potential user-facing changes.

[benbalter]

@Stargator thanks for the pull request. Bumped by #180 in preparation for Jekyll 3.0.x, and now live.