`separator="|"` does not work, only comma symbol supported

[egberts]

Seems like only separator symbol that works is a comma symbol.

I have tried to use the "pipe" ("|") symbol to no avail.

Looks like the generator does not parse the HTML attributes of jtable.

A rehash of the just_table ([jtable]) usage:

[jtable caption="This is caption" separator="|" th=0 ai="1"]

• caption - the table caption
• separator - default is comma
• th - table header (=0 means disable)
• ai - auto-index, adds a column numbering starts at 1

[egberts]

WORKAROUND

Remove smarty extension from MARKDOWN setting in your pelicanconf.py (or publishconf.py) Python configuration file:

MARKDOWN = {
  'extension_configs': {
#    'markdown.extensions.smarty': {},
    'markdown.extensions.extra': {},
    'markdown.extensions.footnotes': {},
    'markdown.extensions.meta': {},
    'markdown.extensions.toc': {'baselevel': 1},
    'markdown.extensions.codehilite': {'css_class': 'codehilite'}
  },
  'output_format': 'html5'}

While it is an effective workaround, this took away the ability to do smart quoting for your Markdown text files, but you have table features back.

HOW

The original Markdown file containing just_table tag+attribute looked like this:

[jtable th="1" caption="A captioned phrase"]
...
[/jtable]

And Markdown smarty extension replaced all double-quotes each with &rdquo, looking like this:

[jtable th=&rdquo1&rdquo caption=&rdquoA captioned phrase&rdquo]
...
[/jtable]

just_table plugin preprocessor and processor had zero chance to examine the original source line (devoid of &rdquo) in which to extract the settings of just_table from within.

I think some redesign of just_table must be made to accommodate such 'bastardization' of [jtable option=&rdquooptions], OR .... or perhaps like PRE-PREPROCESSING the just_table before the Markdown smarty extension starts munging the Jinja/just_table stuff, no?

EDIT: Right now, I do not see a way for just_table plugin to avoid Markdown smarty extension from kicking in FIRSTLY so that just_table options can be properly examined and extracted their own tag+attributes correctly.