451 451 </pre>
452 452 </nowiki>
453 453 <h2><a name="source-hilight">Source highlighting</a></h2>
454 454 <h3>Motivation</h3>
455 455 * You want to have source code highlighting for the files in your repository
456 456
457 457 <h3>Problem</h3>
458 -The main purpose of Fossil is to do versioning the source code. Although it provides a standalone server and lets you navigate through the repository files additional features like source code highlighting from my perspective (I am not a developer of Fossil) is out of scope for an SCM. Just keep the Unix principle: small little programs that do their task and do it well.
458 +The main purpose of Fossil is to do versioning for source code. Although it provides a standalone server and lets you navigate through the repository files additional features like source code highlighting from my perspective (I am not a developer of Fossil) are out of scope for an SCM. Just keep the Unix principle: small little programs that do their task and do it well.
459 459
460 -However to have a source code highlighting in the presented web pages would still be desirable.
460 +However to have source code highlighted in the presented web pages would still be desirable.
461 461
462 462 <h3>Solution</h3>
463 463 There are two scenarios how to implement such a feature:
464 464 * Fossil pipes the source code through a filter before sending it to the browser. The filter could be defined as a configuration option to Fossil. One solution for this might be the <a href="http://www.gnu.org/software/src-highlite">GNU Source code Highlighting</a> program.
465 465 * Use a Javascript library that renders the code within your browser. One solution for this might be <a href="http://code.google.com/p/syntaxhighlighter">Google Syntax Highlighter</a>
466 466
467 467 I estimate that the <i>pipe</i> solution needs some more work/ code changes. Thus I am solely looking at the Javascript solution.