-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rouge #1266
Comments
iirc the trick was that there are some special css tags that when added to the generated html output, then github will pick them up and apply the syntax highlighting pass on them. |
@wallyqs is it possible for an individual to do this with a local installation? |
I'm not sure tbh how it is done these days... |
GitHub uses Rouge for syntax highlighting in GitHub Pages, but we use our own highlighter on github.com. In either case, we post-process the HTML output from this gem -- see https://github.com/github/markup/blob/master/README.md and note item 3. @wallyqs You recall correctly! We search for |
@kivikakk where is repo for "our own highlighter"? is it this? |
@cup No -- our highlighter, PrettyLights, is closed source. This is regrettable because it's a nice piece of software, but unfortunately licensing issues that are completely out of our hands prevent us from open-sourcing it. (We've tried to address this with our upstream a number of times to no avail.) |
github.com utilizes Rouge for syntax highlighting. This is good, but it even
uses Rouge with markups that lack Rouge support. For example if you make a file
readme.org:
github.com will correctly render the file with highlighting. What is confusing
is that the Org-Ruby Gem currently only supports Coderay or Pygments.rb:
https://github.com/wallyqs/org-ruby#current-status
So how is github.com using Org-Ruby with Rouge?
The text was updated successfully, but these errors were encountered: