>Okay, so I’ll admit that setting I used was a tad bright and might have given somebody skin cancer from the sun that it was channelling. So, the nice thing is that you can emulate other editor syntax colors as well. Here is a screen shot of the Web Standard Tools XML editor taking on the look of the Oxygen XML syntax colors:
- tag names and tag delimiters – blue
- attribute names – orange
- attribute values – brown
- comments and comment delimiters – green
- processing instructions and processing instruction delimiters – purple
- entity declarations – tan
- text – black
What was interesting in setting this up, is that Oxygen XML has a few more tweakable pieces that the Web Standard Tools can’t tweak. The following is what Web Standard Tools can’t set to a different color:
- Equals sign can’t be changed. It has no syntax color setting in the XML editor preferences.
- Qutoes can’t be changed. Both single and double. Again these are part of the attribute value region.
- Processing Instruction Name. This takes on the same color as the tag name.
- DocType Name. Again this is treated as a tag name in wtp.
- Prefixes. Oxygen has the ability to reset the tag and tag delimiter colors based on the prefix name. So items in a docbook or schema, or other prefix can have their own colors.
But these are really minor issues, and you can emulate any other editor’s syntax colors fairly easily. Play around with it and see what you can come up with.