koka-lang / madoko

Madoko is a fast markdown processor for high quality academic and technical articles

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

\noindent needs a space after it, I think

tom-newhall opened this issue · comments

Hi Daan,

I can't tell how actively you are still working on the Madoko project, but I wanted to thank you for it, and hope you continue to work on it. I am a researcher on Chinese and Japanese Buddhism based in Japan, and basically do almost all my writing in Madoko now, which seems odd, but with all the annotations and complex formatting needed for the type of documents I work on, this is really a much better solution than working directly in LaTeX or other word processors. I hope this project keeps thriving, as I really don't know of any other software like it.

Anyway, there appears to be one small bug that I think can be fixed by simply adding a space or perhaps moving a bracket in the source code. I tried fixing it by playing with prelude.mdk but that didn't seem to work.

For styles that use the latex command \noindent such as in footnotes, I occasionally get an Undefined control sequence error, from text at the beginning of a footnote, etc. that gets transformed into \noindent仏教体系版. I can fix this by adding a &zwsp; before 仏教体系版 in the source code, or by adding {before:"&zwsp;";} to the footnote class, but this doesn't always work, and it is not clear to me which elements use the \noindent command.

I should also say that, while \noindent is the main culprit for me personally, the same error also occurs when, for example one tries to make text bold, in particular, chinese text, for instance *文法* gets converted to {\bfseries文法} which results in an Undefined control sequence error. This seems to not be a problem if I replace *文法* with *Grammar* which renders to {\bfseries Grammar} which doesn't throw up an error, presumably because of the space after the \bfseries command

Sorry, I'm not really a programmer, but I hope that my description of the problem is clear enough!

Thank you,
Tom