Frequently used words (click to add to your profile)

javac++androidlinuxc#windowsobjective-ccocoa誰得qtpythonphprubygameguibathyscaphec計画中(planning stage)翻訳omegatframeworktwitterdomtestvb.netdirectxゲームエンジンbtronarduinopreviewer



最近のWikiの更新 (Recent Changes)

No changes on this wiki.


サイドバー (Side Bar)


  • R/O
  • R/O (HTTP)
  • R/W (SSH)
  • R/W (HTTPS)

A Markdown shard for the Crystal programming language

Release Files

No download files.

Recent Commits

Révisionl'heureAuteurMessage: RSS
e90bbdf62023-12-28 13:08:25supercellRemove unused spec/ file
f00309f92023-12-28 12:19:51supercellAdd support for AlertBlockSyntaxes
9dc34d222023-12-28 10:56:46supercellUpdate CHANGELOG
7e2c36ae2023-12-28 10:54:19supercellMerge branch 'solvin-master'
626ded052023-12-25 20:45:43Ian RashAdded attributes with no value
d73c648e2023-12-25 16:23:14supercellFix Regex match error (match limit exceeded) ... another...
4a8dea4e2023-12-07 13:56:58supercellUpdate CHANGELOG
6ac4176f2023-12-07 13:48:42supercellAdd spec for AutolinkExtension unmatched par. See: https...
d548a69d2023-12-07 13:36:33MioMerge pull request 'Fixed issues with paren and autolink'...
326b87422023-12-07 12:40:09solvinUpdate src/extern/


Luce is a CommonMark compliant parser and renderer which supports a few common extensions.

Luce is a port of the Dart markdown package.


  1. Add the dependency to your shard.yml:

      version: ~> 0.4.0
  2. Run shards install


require "luce"

puts Luce.to_html("Hello *Markdown*") # => <p>Hello <em>Markdown</em></p>

Syntax extensions

A few Markdown extensions, beyond what was specified in the orignal Perl Markdown implementation, are supported. By default, the ones supported in CommonMark are enabled. Any individual extension can be enabled by specifying an Array of extension syntaxes in the block_syntaxes or inline_syntaxes argument of Luce.to_html.

The currently supported inline extension syntaxes are:

  • - approximately CommonMark's definition of "Raw HTML".

The currently supported block extension syntaxes are:

  • FencedCodeBlockSyntax - Code blocks familiar to Pandoc and PHP Markdown Extra users.
  • HeaderWithIdSyntax - ATX-style headers have generated IDs, for link anchors (akin to Pandoc's auto_identifiers).
  • SetextHeaderWithIdSyntax - Setext-style headers have generated IDs for link anchors (akin to Pandoc's auto_identifiers).
  • TableSyntax - Table syntax familiar to GitHub, PHP Markdown Extra, and Pandoc users.

For example:

html = Luce.to_html(%(Hello <span class="green">Markdown</span>),
    inline_syntaxes: [])

puts html # => <p>Hello <span class="green">Markdown</span></p>\n

Extension Sets

To make extension management easy, you can also just specify an extension set. Both Luce.to_html and accept an extension_set named parameter. Currently, there are four pre-defined extension sets.

  • Luce::ExtensionSet::NONE includes no extensions. With no extensions, Markdown documents will be parsed with a default set of block and inline syntax parsers that closely match how the document might be parsed by the original Perl Markdown implementation.

  • Luce::ExtensionSet::COMMON_MARK includes two extensions in addition to the default parsers to bring the parsed output closer to the CommonMark specification:

    • Block Syntax Parser

    • FencedCodeBlockSyntax

    • Inline Syntax Parser

    • InlineHTMLSyntax

  • Luce::ExtensionSet::GITHUB_FLAVOURED includes five extensions in addition to the default parsers to bring the parsed output cose to the GitHub Flavoured Markdown specification:

    • Block Syntax Parser

    • FencedCodeBlockSyntax

    • TableSyntax

    • Inline Syntax Parser

    • InlineHTMLSyntax

    • StrikethroughSyntax
    • AutolinkExtensionSyntax
  • Luce::ExtensionSet::GITHUB_WEB includes eight extensions. The same set of parsers used int he GITHUB_FLAVOURED extension set with the addition of the block syntax parsers, HeaderWithIdSyntax and SetextHeaderWithIdSyntax, which add id attributes to headers and inline syntax parser, EmojiSyntax, for parsing GitHub style emoji characters:

    • Block Syntax Parser

    • FencedCodeBlockSyntax

    • HeaderWithIdSyntax, which adds id attributes to ATX-style headers, for easy intra-document linking.
    • SetextHeaderWithIdSyntax, which adds id attributes to Setext-style headers, for easy intra-document linking.
    • TableSyntax

    • Inline Syntax Parser

    • InlineHTMLSyntax

    • StrikethroguhSyntax
    • EmojiSyntax
    • AutolinkExtension

Custom syntax extensions

You can create and use your own syntaxes.

require "luce"

syntaxes = ["nyan", sub: "~=[,,_,,]:3")]
puts Luce.to_html("nyan", inline_syntaxes: syntaxes)
# => <p>~=[,,_,,]:3</p>

HTML sanitization

This shard offers no features in the way of HTML sanitization. Read Estevão Soares dos Santos' great article, "Markdown's XSS Vulnerability (and how to mitigate it)", to learn more.

The authors recommend that you perform any necessary sanitization on the resulting HTML.


Currently matches version 7.0.2 of the Dart markdown package. Work continues on updating to match newer releases. That said, until we've matched the latest version of Dart markdown (7.1.0 as of writing), Luce will stay pre-1.0, since there will be some breaking changes.


  1. Fork it (
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

CommonMark compliance

This shard contains a number of files in the tools directory for tracking compliance with CommonMark.

Updating the CommonMark stats when changing the implementation

  1. Update the shard and test code, making sure that tests still pass.
  2. Run crystal tools/ --update-files to update the per-test results tools/common_mark_stats.json and the test summary tools/common_mark_stats.txt.
  3. Verify that more tests now pass - or at least, no more tests fail.
  4. Make sure you include the updated stats files in your commit.

Updating the CommonMark test file for a spec update

  1. Check out the CommonMark source. Make sure you checkout a major release.
  2. Dump the test output overwriting the existing tests file.

    > cd /path/to/commonmark-spec
    > python3 test/ --dump-tests > \
  3. Update the stats files as described above. Note any changes in the results.

  4. Update any references to the existing spec by searching for in the repository. (Including this one.) Verify the updated links are still valid.
  5. Commit changes, including a corresponding note in


Latest updated Tickets

No tickets

About Chamber Wiki

Welcome to OSDN Wiki system. Here is your chamber Wiki space.

Check Wiki Guide (English) to refer syntax and functions.