Category talk:OoRexx: Difference between revisions
Content added Content deleted
m (→Plagiarism: corrected a couple of typos.) |
m (→Coloring / Highlighting Rexx code: added a comment concerning Shared CSS/Javascript) code which gives me a switch to disable highlighting at will.) |
||
| Line 175: | Line 175: | ||
But it's far beyond my reach whether this is feasible and even further to implement it. |
But it's far beyond my reach whether this is feasible and even further to implement it. |
||
--[[User:Walterpachl|Walterpachl]] 07:14, 10 June 2012 (UTC) |
--[[User:Walterpachl|Walterpachl]] 07:14, 10 June 2012 (UTC) |
||
::: I've done this via some code (Shared CSS/JavaScript) that was written/given to me, so I have a toggle switch that gives me the ability to turn off syntax highlighting when I want. I think that switch should be made available to everyone without the need for everyone to install the script to enable the toggle. If anybody wants to view it, I could display it within a html PRE window. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 23:59, 25 March 2016 (UTC) |
|||
: Categorically NO to “crexx” (well, unless someone produces a REXX variant that actually has that name after case-normalization). The parameter to <nowiki><lang></nowiki> is semantic, not just some flag to the highlighter; it's actually used for some of the off-line tools associated with RC. However, having a separate oorexx version ''is OK'' exactly because that is naming a language variation; it would cause different semantic markup to be applied (which might happen to include some extra syntax classes, but that's a side-effect). |
: Categorically NO to “crexx” (well, unless someone produces a REXX variant that actually has that name after case-normalization). The parameter to <nowiki><lang></nowiki> is semantic, not just some flag to the highlighter; it's actually used for some of the off-line tools associated with RC. However, having a separate oorexx version ''is OK'' exactly because that is naming a language variation; it would cause different semantic markup to be applied (which might happen to include some extra syntax classes, but that's a side-effect). |
||