No commit activity in last 3 years
No release in over 3 years
PseudoHikiParser parses texts written in a Hiki like notation, and coverts them into HTML, Markdown or other formats.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.3
~> 1.3.1
>= 0
~> 0.31
 Project Readme

PseudoHikiParser

PseudoHikiParser parses texts written in a Hiki like notation, and converts them into HTML, Markdown or other formats.

I am writing this tool with following objectives in mind,

  • provide some additional features that do not exist in the original Hiki notation
    • make the notation more line oriented
    • allow to assign ids to elements such as headings
  • support several formats other than HTML
    • The visitor pattern is adopted for the implementation, so you only have to add a visitor class to support a certain format.

And, it would not be compatible with the original Hiki notation.

License

BSD 2-Clause License

Installation

gem install pseudohikiparser

or if you also want to try out experimental features,

gem install pseudohikiparser --version 0.0.6.develop

Usage

Samples

And results of conversion

You will find these samples in develop branch.

pseudohiki2html

(Please note that pseudohiki2html is currently provided as a showcase of PseudoHikiParser, and the options will be continuously changed at this stage of development.)

After the installation of PseudoHikiParser, you can use a command: pseudohiki2html.

Type the following lines at the command prompt:

pseudohiki2html <<TEXT
!! The first heading
The first paragraph
TEXT

And it will return the following result to stdout:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
  "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
<meta content="en" http-equiv="Content-Language">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<meta content="text/javascript" http-equiv="Content-Script-Type">
<title>-</title>
<link href="default.css" rel="stylesheet" type="text/css">
</head>
<body>
<div class="section h2">
<h2> The first heading
</h2>
<p>
The first paragraph
</p>
<!-- end of section h2 -->
</div>
</body>
</html>

And if you specify a file name with --output option:

pseudohiki2html --output first_example.html <<TEXT
!! The first heading
The first paragraph
TEXT

the result will be saved in first_example.html.

For more options, please try pseudohiki2html --help

Incompatible changes

Until version 0.0.4, the name of the command was pseudohiki2html.rb.

From version 0.0.0.9.develop, command line options are renamed as follows:

old name new name note
-f -F '-f' is now used as the short version of '--format-version'
-h -f '-h' is now used as the short version of '--help'
--html_version --format-version other formats than html should be supported
--encoding --format-encoding '--encoding' is now used as the long version of '-E' option
- --encoding now same as '-E' option of MRI

class PseudoHiki::BlockParser

A class method PseudoHiki::BlockParser.parse composes a syntax tree from its input, and a visitor class converts the tree into a certain format.

If you save the lines below as a ruby script and execute it:

#!/usr/bin/env ruby

require 'pseudohikiparser'

hiki_text = <<TEXT
!! The first heading
The first paragraph
TEXT

tree = PseudoHiki::BlockParser.parse(hiki_text)
html = PseudoHiki::HtmlFormat.format(tree)
puts html

you will get the following output:

<div class="section h2">
<h2> The first heading
</h2>
<p>
The first paragraph
</p>
<!-- end of section h2 -->
</div>

In the example above, HtmlFormat is a visitor class that converts the parsed text into HTML 4.01 format.

Other than HtmlFormat, XhtmlFormat, Xhtml5Format, PlainTextFormat and MarkDownFormat are available.

WikiNames

If you want to use WikiNames, you have to pass an instance of PseudoHiki::AutoLink::WikiName as the argument of BlockParser.new or the second argument of BlockParser.parse.

require 'pseudohiki/blockparser'
require 'pseudohiki/htmlformat'
require 'pseudohiki/autolink' # PseudoHiki::AutoLink::WikiName is defined in this file.

text = <<TEXT
a line with an ^EscapedWikiName and a WikiName.
TEXT

puts "--- with default options:"
wiki_name_link = PseudoHiki::AutoLink::WikiName.new
tree = PseudoHiki::BlockParser.parse(text, wiki_name_link)
puts PseudoHiki::XhtmlFormat.format(tree)

puts "--- when :escape_wiki_name option is set to true:"
escape_wiki_name_link = PseudoHiki::AutoLink::WikiName.new({:escape_wiki_name => true})
escaped_tree = PseudoHiki::BlockParser.parse(text, escape_wiki_name_link)
puts PseudoHiki::XhtmlFormat.format(escaped_tree)

will print

--- with default options:
<p>
a line with an ^<a href="EscapedWikiName">EscapedWikiName</a> and a <a href="WikiName">WikiName</a>.
</p>
--- when :escape_wiki_name option is set to true:
<p>
a line with an EscapedWikiName and a <a href="WikiName">WikiName</a>.
</p>

And if you don't like the default behavior, you may prepare a class/module that substitutes AutoLink::WikiName.

class PseudoHiki::Format

If you don't need to reuse a tree parsed by PseudoHiki::BlockParser.parse, you can use following class methods of PseudoHiki::Format.

Method name Result of conversion
to_html HTML 4.01
to_xhtml XHTML 1.0
to_html5 HTML 5
to_plain plain text
to_markdown Markdown
to_gfm Github Flavored Markdown

For example, the script below returns the same result as the example of PseudoHiki::BlockParser

#!/usr/bin/env ruby

require 'pseudohikiparser'

hiki_text = <<TEXT
!! The first heading
The first paragraph
TEXT

puts PseudoHiki::Format.to_html(hiki_text)

Development status of features from the original Hiki notation

  • Paragraphs - Usable
  • Links
    • WikiNames - Provided as an option but not tested well
    • Linking to other Wiki pages - Not supported
    • Linking to an arbitrary URL - Maybe usable
  • Preformatted text - Usable
  • Text decoration - Partly supported
    • Means of escaping tags for inline decorations is just experimetal.
    • The notation for inline literals by backquote tags(``) is converted into not <tt> element but <code> element.
  • Headings - Usable
  • Horizontal lines - Usable
  • Lists - Usable
  • Quotations - Usable
  • Definitions - Usable
  • Tables - Usable
  • Comments - Usable
  • Plugins - Not supported (and will not be compatible with the original one)

Additional Features

Assigning ids

If you add [name_of_id], just after the marks that denote heading or list type items, it becomes the id attribute of resulting html elements. Below is an example.

!![heading_id]heading

*[list_id]list

will be rendered as

<div class="section h2">
<h2 id="HEADING_ID">heading
</h2>
<ul>
<li id="LIST_ID">list
</li>
</ul>
<!-- end of section h2 -->
</div>

Escaping tags for inline decorations

(Please note that this is just an experimental feature.)

Tags for inline decorations are escaped when they are enclosed in plugin tags:

For example, {{''}} and {{==}} can be escaped.
And {{ {}} and {{} }} should be rendered as two left curly braces and two right curly braces respectively.

will be rendered as

For example, '' or == can be escaped.
And {{ and }} sould be rendered as two left curly braces and two right curly braces respectively.

Nesting of link tags

If a link tag is nested inside another link tag, the outer tag is always treated as a link even when its url is for an image.

So you can make a link from a thumbnail as in the following example.

[[[[thumbnail of an image|http://www.example.org/image_thumb.png]]|http://www.example.org/image.png]]

will be rendered as

<a href="http://www.example.org/image.png"><img alt="thumbnail of an image" src="http://www.example.org/image_thumb.png">
</a>

Experimental

The following features are just experimental and available only in develop branch.

Decorator for blocks

By lines that begin with '//@', you can assign certain attributes to its succeeding block.

For example,

//@class[class_name]
!!A section with a class name

paragraph

will be rendered as

<div class="class_name">
<h2>A section with a class name
</h2>
<p>
paragraph
</p>
<!-- end of class_name -->
</div>

Defining sections

When a certain part of a document is enclosed by //@begin[section\_name] and //@end[section\_name], HtmlFormat and its subclasses will convert the tags into <div> or <section> elements with id or class attributes.

!! title

paragraph 0

//@begin[main-part]

!!! main part subtitle 1

paragraph 1

!!! main part subtitle 2

paragraph 2

//@end[main-part]

//@begin[additional-part]

!!! additional part subtitle

paragraph 3

//@end[additional-part]

will be rendered as

<div class="section h2">
<h2> title
</h2>
<p>
paragraph 0
</p>
<div class="section main-part">
<div class="section h3">
<h3> main part subtitle 1
</h3>
<p>
paragraph 1
</p>
<!-- end of section h3 -->
</div>
<div class="section h3">
<h3> main part subtitle 2
</h3>
<p>
paragraph 2
</p>
<!-- end of section h3 -->
</div>
<!-- end of section main-part -->
</div>
<div class="section additional-part">
<div class="section h3">
<h3> additional part subtitle
</h3>
<p>
paragraph 3
</p>
<!-- end of section h3 -->
</div>
<!-- end of section additional-part -->
</div>
<!-- end of section h2 -->
</div>

Not Implemented Yet

Visitor classes

Please note that some of the following classes are implemented partly or not tested well.

Their class method (HtmlFormat|XhtmlFormat).format returns a tree of HtmlElement objects, and you can traverse the tree as in the following example.

#!/usr/bin/env ruby

require 'pseudohikiparser'

hiki_text = <<HIKI
!! heading

paragraph 1 that contains [[a link to a html file|http://www.example.org/example.html]]

paragraph 2 that contains [[a link to a pdf file|http://www.example.org/example.pdf]]
HIKI

html = HtmlFormat.format(hiki_text)

html.traverse do |elm|
  if elm.kind_of? HtmlElement and elm.tagname == "a"
    elm["class"] = "pdf" if /\.pdf\Z/o =~ elm["href"]
  end
end

puts html.to_s

will print

<div class="section h2">
<h2> heading
</h2>
<p>
paragraph 1 that contains <a href="http://www.example.org/example.html">a link to a html file</a>
</p>
<p>
paragraph 2 that contains <a class="pdf" href="http://www.example.org/example.pdf">a link to a pdf file</a>
</p>
<!-- end of section h2 -->
</div>

This visitor is for HTML5.

Currently there aren't many differences with XhtmlFormat except for the handling of <section> elements.

This visitor removes markups from its input and returns plain texts. Below are examples

:tel:03-xxxx-xxxx
::03-yyyy-yyyy
:fax:03-xxxx-xxxx

will be rendered as

tel:	03-xxxx-xxxx
	03-yyyy-yyyy
fax:	03-xxxx-xxxx

And

||cell 1-1||>>cell 1-2,3,4||cell 1-5
||cell 2-1||^>cell 2-2,3 3-2,3||cell 2-4||cell 2-5
||cell 3-1||cell 3-4||cell 3-5
||cell 4-1||cell 4-2||cell 4-3||cell 4-4||cell 4-5

will be rendered as

cell 1-1	cell 1-2,3,4	==	==	cell 1-5
cell 2-1	cell 2-2,3 3-2,3	==	cell 2-4	cell 2-5
cell 3-1	||	||	cell 3-4	cell 3-5
cell 4-1	cell 4-2	cell 4-3	cell 4-4	cell 4-5

This visitor is for (Git Flavored) Markdown and just in experimental stage.

The following are a sample script and its output:

#!/usr/bin/env ruby

require 'pseudohiki/markdownformat'

md = PseudoHiki::MarkDownFormat.create
gfm = PseudoHiki::MarkDownFormat.create(gfm_style: true)

hiki = <<TEXT
!! The first heading

The first paragraph

||!header 1||!header 2
||''cell 1''||cell2

TEXT

tree = PseudoHiki::BlockParser.parse(hiki)
md_text = md.format(tree).to_s
gfm_text = gfm.format(tree).to_s
puts md_text
puts "--------------------"
puts gfm_text

(You will get the following output.)

## The first heading

The first paragraph

<table>
<tr><th>header 1</th><th>header 2</th></tr>
<tr><td><em>cell 1</em></td><td>cell2</td></tr>
</table>

--------------------
## The first heading

The first paragraph

|header 1|header 2|
|--------|--------|
|_cell 1_|cell2   |

Limitations

You cannot convert malformed lists with this visitor class. That means list items must be nested hierarchically and if you skip a level in the sequence of items, the result of coversions will be corrupted.

The following is an example of malformed list in which the first level is skipped:

**First item
**Second item