I am using UltraEdit to pre-tag my Ventura Publisher texts and I am attempting to use the UltraEdit syntax highlighting feature to make my tasks easier. I know I am using this feature in a non-standard way because Ventura tagging is not programming code at all but, obviously, I am attempting to customize the program to my needs.
I wrote a language specification (thanks to Dalibor for his template) to add to the Wordfile.txt but it's not perfect at all. I would like to emphasize (i.e., to see in a different lighter color) some pieces of text, typically paragraph tags and text attributes. So I'll explain the Ventura tagging as briefly as possible and I would be very grateful if someone could help me with the Wordfile definition.
Ventura text files start with a tag like this:
It's only to identify the tagging as a post version 7 tagging style (different to previous versions of the program). Any Ventura paragraph tag starts with "@" and ends with " = " (the spaces before and after the = are mandatory). The paragraph tag is active up to the next carriage return (DOS style).
After this tag, a new tag defines the first paragraph type. For example:
@Heading = HEADING NAME
This syntax is used also for tables. Body text doesn't require any tagging and the name of the tags labels are free, as long as they start with "@" and they finish with " = ". In this area, I attempt to emphasize the whole string, from the beginning of the line (@) to the end of the tag (=). So I am able to concentrate on the text and the tagging is less disturbing. At present (see the enclosed language definition) I am getting it via /C1 definition but, as long as the names for the paragraph labels are unlimited, my proceeding is not very practical because I have to constantly modify my language definition. If I could use Auto Brace Matching, better but not indispensable.
On the other hand, I would like to make the text attributes and other codes less visible. All start with "<" and finish with ">". They can be several lines long. For example:
<I>: Italic on.
<I*>: Italic off.
<B>: Bold on.
<W0>: Bold off.
And so small caps, base line jump, begin/end kerning, point size, line break, etc. etc.
<$F: Footnote start. It finishes with a matching ">" but, in the middle, italic, bold or other attributes can appear.
<$I: Index entry. It finishes with a matching ">".
And so cross references, equations, variables, frame anchors, hidden text, etc. etc. Auto Brace Matching is indispensable in this case.
Typically, there are many codes started by "<$" but the essential signs are, as previously stated, the left acute angle and the right acute angle.
I know it's impossible to fold those strings, I have spent a long time attempting to use Marker Characters without any success and I suspect I am not correctly defining delimiters (obviously, I'd like to see my angles empasized but not my punctuation signs). Any suggestion would be welcome.
This is my language definition:
/L14"Ventura" Case File Extensions = TXT
/Delimiters = <>@=
/Function String =
/Indent Strings =
/Unindent Strings =
/Open Brace Strings = "<" "@"
/Close Brace Strings = ">" " = "
/Open Fold Strings =
/Close Fold Strings =
End of my language definition.
Thank very much in advance.