Redmine

It would be nice to let formatting of project's Wiki be selected independently of issues (and other parts') formatting.

Redmine has tests.
https://bitbucket.org/redmine/redmine/src/f4d8b015a399/test/

Could you add tests for this patch?

Shall I change and extend existing tests, or shall I write a new test case in a separate file? May you give me an starting point? (I'm not deep into Rails.)

And now the plugin thanks to a-ono: http://github.com/a-ono/redmine_per_project_formatting

Are there any plans to implement this?

Alternatively, a special control tag could be invented, for instance #markup:textile or #markup:markdown, which, if found as the first line of the text, it would indicate the parser that should be used. This is an easy way to add maximum flexibility without having to make decisions about the used markup at the web site or project level. Such a solution would also be helpful in cases where markup needs to be migrated at slow pace page per page.

I hope someone looks into this issue more closely, because right now, IMO, Redmine is doing it wrong.

Thanks in advance.

George

+1

As the original requestor of the Markdown formatting feature, I have to shamefully admit that I have not yet Flipped The Big Switch.

The reason for this is that conversion from Textile to Markdown is an all-or-nothing proposition right now. Having this setting per-project would make it much simpler: not only to convert a site gradually, project-by-project, but also to start new projects off with Markdown. I wouldn't mind sealing some projects and starting fresh ones in some cases, just to force this formatting transition on its users.

So here's my vote to making the Textile/Markdown flag settable for each project!

-jcw

What is the status of this feature request? Could and will a per-project Markdown/Textile setting be implemented?

With such a feature, migration becomes a per-project issue, and new projects could be set up appropriately.
That last benefit alone would solve a major headache for me - as it is, I can't even set up a new Markdown area.

I'm eagerly looking forward to a response / verdict from one of the maintainers...
-jcw

+1

We are using Redmine for several years with textile formating and we would like to switch to Markdown progressively.
Will this feature request be implemented soon ?

Currently, we use the following plugin:
https://www.redmine.org/plugins/per-project-formatting

but it would be nice to have this upstream. Or even per page formatting!

+1 on this.
We have a redmine instance containing projects of over a decade. We would like to switch to CKeditor but up till now all is done in textile formatting. Changing the global setting to the new editor would break all existing wiki pages and issue descriptions and notes, which makes a switch impossible now.

+1

+1

+1

An easier approach could be that every issue/... has a option markdown/textile. Default to markdown and keep the old issues at textile. So you can create every new issue/... with markdown and easily convert the old ones if needed. So you have no upgrade problems and no additional manual work.

Currently its basically impossible to use markdown if you have a rather big collection based at textile. Bulk converting is not working without manually checking everything again.

Christian Kay wrote in #note-33:

Currently its basically impossible to use markdown if you have a rather big collection based at textile. Bulk converting is not working without manually checking everything again.

Interesting. We are going to migrate everything on markdown. Could you tell, what is broken?

Could you tell, what is broken?

We tried it some years ago
- some stuff is not supported at Markdown so the conversion breaks the intended layout/function
- wrong usage of textile can create a mess with markdown
- intended layout of more complex issues broke

Overall you needed to fix too much manually, but this depends ofc at the size of the redmine install.