+1

I'm considering moving from Trac too, but ReStructuredText is a lot nicer than Textile...
--------------------------------------------------------------------------------
+1

Yes, we also use Trac and rst. It would be good to see it in Redmine.
--------------------------------------------------------------------------------
please add rst support...
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Redmine uses RedCloth to convert Textile to xhtml. In recent versions of redmine, one can add more wiki syntax engines, but we have to wonder if they should co-exist, and at which level ? IOW, should the whole instance use a uniform syntax ? Should this setting be per-project ? Per-wiki-page ?

What I mean is that using a wiki syntax or an other is generaly a matter of personal taste and nothing else. A wiki is aimed at collaborative editing, so if many syntax co-exist in the same wiki, every users will have to learn them all to be able to edit any page. So IMO, a per-page freedom of syntax is a bad idea. At least per project syntax consistency is required, but still I don't like this idea.

The other possibility is to enforce the use of two-ways full-converters in redmine. Such a two-ways converter should be able to produce xhtml from a given wiki syntax, and produce back the same wiki syntax from xhtml. That way, each user can select the wiki syntax (s)he wants to work with, and data is stored in xhtml in the model. Per-user preference really is the right level for such a setting.
--------------------------------------------------------------------------------
per-user preference sounds fine to me. the inline markup switch ala trac would be nice too. eg. #!html
--------------------------------------------------------------------------------
+10

Is this goint to be implemented? Issue #1860 also ask for this.

I prefer reST because it:

* Allows line breaking a paragraph without losing track.
* Allows a blank line between items on a list without making two separate lists.
* Sublists are defined by indentation level. This is far more readable than several * signs.

The cons:
* The extensible way of making custom links is something like :rev:`12726` which is worse than r12726. However this could be easily overcome.

--------------------------------------------------------------------------------
I'd be just as happy with one setting for the whole installation. We use restructured text for any text-based documentation everywhere so there's no one on the team who even wants to use anything else.

I think, generally, a group is going to be used to one format or another and it doesn't need to be too granular.

Please do one global setting and, if anyone needs more, let them bring it up again later.

I love Redmine so far and this is the one real sore spot in an otherwise awesome product.
--------------------------------------------------------------------------------
Paul Rivier wrote:
> Redmine uses RedCloth to convert Textile to xhtml. *_In recent versions of redmine, one can add more wiki syntax engines_*

Is there any documentation on how to do this, please?

I just upgraded to Redmine 0.8.7.stable but there's still only textile in the wiki formatting dropdown in the settings.

We only want to support restructured text across the whole app; nothing fancy, we just want restructured text to be the default everywhere.

Can this be done?

Thanks,

S

--------------------------------------------------------------------------------
The issue remains that is NOT a native RST parser for Ruby. Until there is one the request for support is pretty much moot.

--------------------------------------------------------------------------------
I saw this issue and took "Larry Baltz's markdown formatter":http://github.com/bitherder/redmine_markdown_formatter and converted it into a simple "redmine reStructuredText formatter":http://github.com/autodata/redmine_restructuredtext_formatter plugin using either my "RbST reStructuredText gem":http://github.com/autodata/rbst that processes RST via python's docutils or my "PandocRuby":http://github.com/autodata/pandoc-ruby wrapper for Pandoc.

The reason for including both options is that docutils supports all of RST but is slow (probably too slow for public-facing Redmine install), while Pandoc is faster but only supports a subset of RST (eg, no support for RST tables). Remine does formatting via a helper, so each request is dependent on the performance of the formatter.

As James noted, there is no native Ruby reStructuredText parser and I wouldn't hold my breath for one, but this plugin should be sufficient. Note that I disabled the toolbar, but feel free to fork this and put a working one back in.
--------------------------------------------------------------------------------
Hello,
I am migrating from trac to redmine.
Migration worked fine except for RST, so I tried to install the RbST and redmine reStructuredText formatter plugin (following instructions found at github link).
After installing python, docutils, RbSt and reStructuredText formatter plugin,
redmine is not starting any more.
The following error is shown:

Loading development environment (Rails 2.3.5)
/opt/redmine-0.9.2-0/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- RbST (MissingSourceFile)
from /opt/redmine-0.9.2-0/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /opt/redmine-0.9.2-0/apps/redmine/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in `require'
from /opt/redmine-0.9.2-0/apps/redmine/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in'

Any help is appreciated.
Thanks
--------------------------------------------------------------------------------
Hello,
I am migrating from trac to redmine.
Migration worked fine except for RST, so I tried to install the RbST and redmine reStructuredText formatter plugin (following instructions found at github link).
After installing python, docutils, RbSt and reStructuredText formatter plugin,
and now the plugin shows up correctly in the Plugins section.
I am now trying to figure out how to use it.
More: is the plugin supposed to get invoked when migrating from a trac site with wiki pages using renstructured text?
Thanks
--------------------------------------------------------------------------------
Hello,

You must install rbst. *gem install RbST*

If the problems persists (the sames happen to me (I am using Debian)) the solutions is weird.

You need to edit the file *lib/redmine_restructuredtext_formatter/wiki_formatter.rb* and change the line *require 'RbST'* to *require 'rbst'*
*

Paolo Freuli wrote:
> Hello,
> I am migrating from trac to redmine.
> Migration worked fine except for RST, so I tried to install the RbST and redmine reStructuredText formatter plugin (following instructions found at github link).
> After installing python, docutils, RbSt and reStructuredText formatter plugin,
> redmine is not starting any more.
> The following error is shown:
>
> Loading development environment (Rails 2.3.5)
> /opt/redmine-0.9.2-0/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- RbST (MissingSourceFile)
> from /opt/redmine-0.9.2-0/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
> from /opt/redmine-0.9.2-0/apps/redmine/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in `require'
> from /opt/redmine-0.9.2-0/apps/redmine/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in'
>
> Any help is appreciated.
> Thanks

--------------------------------------------------------------------------------
My bad. Yeah, the require didn't play well with case-sensitive file systems. It should be fixed in the github repo now.
--------------------------------------------------------------------------------
FWIW, my plugin has moved to http://github.com/alphabetum/redmine_restructuredtext_formatter
--------------------------------------------------------------------------------
William - any chance you could add support for macros and TOC etc?
--------------------------------------------------------------------------------
I created a similar plugin that should be a little more turnkey. It has a simple toolbar and help link like the Textile formatter and updates some styles for the fixed-length nature of reSt. If you have Pygments installed you can also use the @sourcecode@ directive and get free pygmentized syntax highlighting. There is currently no RbST requirement in my version either, but that may change since the author recently pushed an updated just for me. =)

Documentation is forthcoming, but from now on the master branch will remain stable.

"Red reSt - Redmine reStructuredText wiki formatter":http://dev.remarkablewit.com/redmine/projects/red_rest
--------------------------------------------------------------------------------
I added a toolbar to William's plugin: http://github.com/ebrahim/redmine_restructuredtext_formatter

Note that my fork has some other changes as well.
--------------------------------------------------------------------------------
"reStructuredText" is one word. Please fix the title.
--------------------------------------------------------------------------------
Not sure it really matters but even if it did - I can't update the title.

--------------------------------------------------------------------------------
I've replaced plain textarea of redmine_restructuredtext_formatter with CodeMirror 2 for syntax highlighted rich text editor for reStructuredText. Feel free to give it a try after checking out my "@codemirror@ branch":https://bitbucket.org/ebrahim/redmine_restructuredtext_formatter/src/codemirror/. Any kind of feedback is welcome.
--------------------------------------------------------------------------------
Is this plugin fit for purpose? Should this issue be closed?

I'm considering JIRA vs Redmine based on this. I'll need the following from Redmine:

* *Markdown* for issues (reST is good to have here)
* *reST* for wiki (must have)

Consider that *Markdown* syntax is very similar to *reST*. They complement each other. We use *reST* for complex documents, and *Markdown* for quick notes.

Ah, I see this _Redmine_ instance uses _Textile_. In _Markdown_, Asterisks mean *bold* in _Textile_.

Nested lists in _Textile_ is a deal-breaker for me. General human-readability is better with _reST_.

Nothing compares to _Redmine_. We hope to use _Redmine_ if at all possible.
--------------------------------------------------------------------------------

duplicates,Closed,1860,reST (reStructuredText) support