Feature #2623
C# syntax highlighting
| Status: | New | Start date: | 2009-01-30 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Third-party libraries | |||
| Target version: | Unplanned | |||
| Resolution: |
Description
This would be useful both for inline code in wiki pages/forum posts and for browsing files in the repository.
Related issues
History
#1 Updated by Sergej Jegorov over 4 years ago
+1
#2 Updated by Adrien Crivelli about 4 years ago
That would be neat indeed. But I guess that's rather CodeRay job. It's planned for 1.0RC1 which is due in ~50 days. So hopefully it will soon be available in Redmine too. ( http://code.licenser.net/issues/show/78 )
#3 Updated by Paul Quirk about 4 years ago
Meantime, for wiki markup etc, using java lang support via the code markup tag does a pretty good job on c# code
#4 Updated by Mischa The Evil about 2 years ago
- Category changed from Wiki to Third-party libraries
Changed issue-relations to reflect the upstream roadmap:
| - | related to Feature #4264: Update CodeRay to 1.0 final |
| + | blocked by Feature #8253: Update CodeRay to 1.1 final |
and changed to new - more appropriate - category...
#5 Updated by Mischa The Evil about 2 years ago
- Target version set to Unplanned
#6 Updated by Ebrahim Mohammadi about 2 years ago
Implementing #8120 as discussed would solve C# syntax highlighting, since both Google Code Prettify and Sunlight support C#.
#7 Updated by Nuno Duarte almost 2 years ago
+1
#8 Updated by Terence Mill almost 2 years ago
+1
#10 Updated by Mischa The Evil 2 months ago
Just came around forum-message: . Although it is old (for CodeRay 0.7.6.227; Redmine 2.3.0 uses 1.0.6 [source:/tags/2.3.0/Gemfile#L6]), it might provide (the base for) an interim solution untill the scanner has been actually implemented upstream.
#11 Updated by Etienne Massip 2 months ago
Mischa The Evil wrote:
Redmine 2.3.0 uses 1.0.6 [source:/tags/2.3.0/Gemfile#L6]
Up to 1.0.9 =)
it might provide (the base for) an interim solution untill the scanner has been actually implemented upstream.
FTR, the issue in the Coderay IT is located here : https://github.com/rubychan/coderay/issues/54.