Re: Status of textile branch

[Paul R <paul.r.ml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

Hi John,

I notice you made a lot of nice improvements to the textile reader,
thank you very much, I have been very busy lately, therefore have not
hacked much in spite of my strong desire to polish the work :)


John> Is that right? Or is there a metadata format?

I don't think there is one, but if you decide to implement an extended
format for meta information such as the YAML discussed recently, I think
it would fit as a nice extention to the standard Textile. But there is
not much to do in the meantime.

>> footnotes
John> It should be possible to implement these using the same technique
John> as the markdown reader uses. One thing that's not clear to me from
John> the spec is whether a footnote can contain multiple block
John> elements -- also, relatedly, where does the footnote end? Probably
John> this needs to be determined by experimenting with redcloth.

I see you just worked on it, that's a big step forward.


>> - registered, trademark, and copyright symbols
John> Again, easy.

Again, you just did it :)


>> - acronyms
John> Nothing corresponding to this in the Pandoc structure, but we
John> could just discard the part in parens: i.e., parse
John> "EPA(Environmental Protection Agency" as "EPA"

As a user, I would prefer to have pandoc just leave the info as it is
instead of striping the expanded form.


>> - definition lists
John> Wouldn't be too hard, I think.

I plan to work on it soon.

>> - continued blocks (ex bq..)
John> Also wouldn't be too hard, I suspect. One just needs a way of
John> recognizing when the continuation ends. Then one can treat it like
John> a markdown block quote.

I might work on it, but reading the spect, I suspect it is not widely
used.

Also, I will try to get smart punctuation working with as little code
duplication as possible, also this week.

regards,


-- 
  Paul