2 Jun
2014
2 Jun
'14
2:04 p.m.
On Sun, Jun 1, 2014 at 6:10 PM, Ben Coman <btc(a)openinworld.com> wrote:
in pillar we have both Markdown and GithubMarkdown as export options.
So we can have a solution dedicated to github if required.
Yes. I am doing something similar. btw, is it a strong
convention that Tex commands and environments are all lowercase? That is, should I force
the annotation label in "\begin{note}" to lowercase, or should I pass that
through unchanged.
I think you should not change anything. Is it up to the writer to do
something not stupid.
For Markdown,
we should probably have the same solution as for HTML.
I had a hunt around and it seems that Markdown doesn't support paragraph styles. And
the workaround specified here...
http://stackoverflow.com/questions/1058933/can-i-define-a-class-name-on-par…
apparently does not work on github...
https://github.com/github/markup But Hey! Check this out...
https://github.com/github/markup/blob/master/CONTRIBUTING.md
Maybe we could add a Pillar-->HTML processor to Github?
There should not be any technical problem to do that. Do you want to
try? I can help if you have problems.
"If your markup is in a language other than Ruby,
drop a translator script in lib/github/commands which accepts input on STDIN and returns
HTML on STDOUT..."
https://github.com/github/markup/blob/master/lib/github/markups.rb
So it seems that Text and Markdown cannot produce different formatted paragraphs.
for text it is clear. For Markdown I'm still not sure if it is
possible or not. Maybe a <div class=<annotation>> would work.
In those two cases, I still lean towards putting the
annotation label in the output, but I'm happy enough to leave it out.
for text I think we should not change the current export. For
Markdown, I leave the decision to you.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill