Allow overriding the default text formatting in each project
It would be good to let the text formatting be selected per project, rather than only a global default. It would be useful for bigger installations that have more diverse set of users.
#2 Updated by Ebrahim Mohammadi over 8 years ago
- File per-project-formatting.diff added
I did an implementation found in
per-project-formatting in: https://bitbucket.org/ebrahim/redmine-patches/qseries (I've attached an snapshot of the patch)
I'd like to receive reviews and comments on the implementation. I'd also like to know if it could be merged upstream.
#3 Updated by Toshi MARUYAMA over 8 years ago
Redmine has tests.
Could you add tests for this patch?
#5 Updated by Ebrahim Mohammadi over 5 years ago
And now the plugin thanks to a-ono: http://github.com/a-ono/redmine_per_project_formatting
#17 Updated by George Notaras about 4 years ago
Alternatively, a special control tag could be invented, for instance
#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.
#18 Updated by Jean-Claude Wippler about 4 years ago
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!
#19 Updated by Jean-Claude Wippler almost 4 years ago
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...