Feature #8095
Allow overriding the default text formatting in each project
Status: | New | Start date: | 2011-04-07 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Text formatting | |||
Target version: | - | |||
Resolution: |
Description
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.
Related issues
History
#1
Updated by Ebrahim Mohammadi almost 12 years ago
It would be nice to let formatting of project's Wiki be selected independently of issues (and other parts') formatting.
#2
Updated by Ebrahim Mohammadi almost 12 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 almost 12 years ago
Redmine has tests.
https://bitbucket.org/redmine/redmine/src/f4d8b015a399/test/
Could you add tests for this patch?
#4
Updated by Ebrahim Mohammadi almost 12 years ago
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.)
#5
Updated by Ebrahim Mohammadi about 9 years ago
And now the plugin thanks to a-ono: http://github.com/a-ono/redmine_per_project_formatting
#6
Updated by Toshi MARUYAMA about 9 years ago
- Related to Feature #5995: Text formatting can be dfferent base on project added
#7
Updated by Toshi MARUYAMA about 9 years ago
- Related to deleted (Feature #5995: Text formatting can be dfferent base on project)
#8
Updated by Toshi MARUYAMA about 9 years ago
- Related to Feature #617: wiki: thoughts of WYSIWYG added
#9
Updated by Toshi MARUYAMA about 9 years ago
- Related to Feature #4015: Make app settings overridable at project level added
#10
Updated by Toshi MARUYAMA about 9 years ago
- Duplicated by Feature #5995: Text formatting can be dfferent base on project added
#11
Updated by Toshi MARUYAMA about 9 years ago
- Duplicated by Feature #5624: the Text formatting configuration in each project. added
#12
Updated by Toshi MARUYAMA about 9 years ago
- Duplicated by Feature #12095: Per project wiki formatter setting added
#13
Updated by Go MAEDA almost 8 years ago
- Duplicated by Feature #19112: Markdown for specific projects added
#14
Updated by Go MAEDA almost 8 years ago
- Duplicated by Feature #19591: Text formatting (textile/markdown) configurable on a per project basis added
#15
Updated by Go MAEDA almost 8 years ago
- Related to Feature #5112: Texting formatting setting is global (Allow override in module level) added
#16
Updated by George Notaras over 7 years ago
Are there any plans to implement this?
#17
Updated by George Notaras over 7 years ago
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
#18
Updated by Jean-Claude Wippler over 7 years ago
+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
#19
Updated by Jean-Claude Wippler over 7 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...
-jcw
#20
Updated by Go MAEDA about 7 years ago
- Related to deleted (Feature #5112: Texting formatting setting is global (Allow override in module level))
#21
Updated by Go MAEDA about 7 years ago
- Related to Feature #5112: Texting formatting setting is global (Allow override in module level) added
#22
Updated by Go MAEDA over 4 years ago
- Related to Feature #28823: Multi-format markup for text fields added
#23
Updated by Go MAEDA over 4 years ago
- Related to Feature #3492: Specify different text formatters for certain parts of Redmine added
#24
Updated by Valera Moskalev over 4 years ago
+1
#25
Updated by Gérard L about 4 years ago
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 ?
#26
Updated by Peter Volkov over 3 years ago
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!