Frequently asked questions

Q: Is High-Light compatible with RapidWeaver 4.0?
A: Yes, High-Light version 1.2.2 and greater works with RapidWeaver 4.0. But if you should stumble upon a problem let me know.
Back to TOC
Q: I found a warning text on one of the pages where i'm using High-Light
A: When High-Light is not able to apply the requested language formatting it will instead output this text:

    #######################################################
    WARNING: High-Light was unable to convert the text
             according to the applied language: C++
    #######################################################

This can happen if you mark the text when High-Light is configured with source-highlight v2.x and you have since switched to v1.x which supports less languages. The same thing can happen if you switch between the dynamic and static menu for source-highlight v2.x. Or if you have manually edited the “tags.plist”. The solution is to mark the text and apply the High-Light formatting again on that page.
Back to TOC
Q: Why is there no option available to wrap the output inside <pre>…</pre> tags?
A: <pre> tags have been intentionally disabled in High-Light because the styled text areas in RW does not handle <pre> tags properly. There is no way to properly render the text inside those tags. The text will either change to be on one line only or it will get <br /> tags added at the end of each line inside the tag. Maybe this will change in the future but for now it is disabled.
Back to TOC
Q: Why isn't a newer version of source-highlight bundled with the plugin?
A: source-highlight is developed independently from High-Light and sometimes a newer version becomes available shortly after new version of High-Light is released. It also takes some time to check that the new version of source-highlight does not break the current behaviour. But for each development cycle the aim is to update source-highlight to the latest available version.
Back to TOC