Why don't you fix them and provide a patch?
I've no idea where in the source tree I'd find them.
For that matter, are they a Code::Blocks thing, or are they sourced from Scintilla?
(and I've had issues logging on to
http://developer.berlios.de -- it keeps telling me to turn cookies on, but I've allowed them for their domain, and quite a few others.)
(Heck, I really hope they aren't hand-generated, but programmatically created. But probably not.)
- - -
Regardless: Why submit a patch of a few XML files when I have a working prototype, which can fix the XML automagically. =)
(Well, except for the weird spacing in attributes; I maintained that, as it helps readability and the fix may be beyond the scope of the XML.)
(If you want to do so, comment out the line "SetThemeForNode( $theme_map, $style_node, @theme_names );"; line 423. It will regenerate the .xml files in a more
standard's compliant format.)
This is a PROTOTYPE.
It creates new versions of the lexer_<foo>.xml files with the new syntax highlighting styles.
The program works buy slurping in the existing lexer files and regenerating them (in another location) with the new style settings.
You need to replace the .xml files (/usr/share/codeblocks/lexer/*.xml on fedora 18, and probably most other unix/linux installs). BACK THE ORIGINALS UP FIRST.
You have to set the theme settings (colors, bold, etc.) by hand in the cb_theme.xml file (sample attached); well, assuming you don't want to use my semi-random/semi-use-based settings. You will also probably disagree with some of the name/alias mappings I made in the cb_theme.xml files. That's fine, the XML file is fairly straight-forward.
There are known issues (the program will abort if it finds the same theme-type name/alt-name multiple times in the config file. The program will abort if it finds a style name in a lexer file it does not recognize, rather than treating it as 'no style attributes'. The Pretty-print output has occasional issues (some nodes being more indented than they should; some less; most attributes are one-per-line, but not all).
Cavaet Emptor.
- - -
(Future versions will create themes that can be imported, rather than change the theme file. This is a proof of concept prototype. Future versions will also have README, CHANGES, etc., rather than just the perl code and sample config file.)
Requires:
libxml2
perl 5.014
Perl Modules:
Getopt::Long::Descriptive
XML::LibXML