[[latex(source:trunk/a/path/a_file.tex)]]

[anonymous]

Wiki content from latex documents

I am a PhD and I use Trac in my university for our research projects, even preparing papers for conferences by latex documents.

Motivation

It would be really useful if with a macro like this:

[[latex(source:trunk/a/path/a_file.tex)]]

one could preview the content from the a_file.tex in a wiki format. This would make easier to make annotations and suggestions, so giving the necessary feedback to the developer team to that content, for example, putting any comment below the above macro but now in a wiki format.

Parser

It would be a parser and a first version could be so simple, parsing only:

\title{the_title} --> = the_title =
\section{a_section} --> == a_section ==
\subsection{a_subsection} --> === a_subsection ===
 ... and so forth
\textit{text_in_it} --> ''text_in_it''
\textbf{text_in_bf} --> '''text_in_bf'''

This version could work without generating images for latex formulas and inserted figures and tables. But, an advanced parser could provide this functionality and a full support for the most common latex tags, enabling for example page separation, double column, etc. As I can see, it will work like a ​processor.

Enhancements

TOC

It would be great that, even it must be activated in the Trac configuration files, this latex parsing already would build the TOC of this style, for example:

[[TOC(depth=4)]]

enabling the inline and depth configuration in some way within the latex macro, for example:

[[latex(source:trunk/a_file.tex, inline)]]
[[latex(source:trunk/a_file.tex, depth=2)]]
[[latex(source:trunk/a_file.tex, inline, depth=3)]]

Related Work

There exists the WikiToLatex macro #2296, but it just performs the opposite operation.

Thank you in advance. I hope you will find this proposal interesting. We believe that this functionality is very useful.

[anonymous]

Related Work

This parser could employ the ​TTH: the TEX to HTML translator, according to the current wiki template.

[diroussel]

No offense, mr anonymous, but if you want it, then have a look at PluginDevelopment and go implement the IWikiSyntaxProvider or IWikiMacroProvider interfaces. Seems you've worked out how it should work already.

[Christian Boos]

Sure, this is way too specialized to be implemented in Trac itself.

However, we're always interested in sharing ideas and getting feedback about how well the base functions of Trac are supporting the development of plugins (see TracDev/PluginDevelopment).

[hyuga <hyugaricdeau@…>]

I would add, this is why anonymous posts, particularly ones that request features, are so annoying. Some people might also have a use for that feature, or be interested in implementing it. But since you don't leave any contact information there's no way to reach you for further discussion.

I don't know why anonymous tickets are allowed… It just leads to countless poorly-written bug reports that are never given any follow up.

[anonymous]

Thank you for your clarifications and your comments. I'm sorry if I annoyed anybody. I saw this feature, this plugin, quite more useful and interesting than all of you. Maybe because I thought on this possibility. Perhaps later I implement this plugin and, if done, I sent it to you for being publicly available.

Regards.

The "anonymous"