/L20"BBCode" EnableSpellasYouType Nocase String Chars = ` File Extensions = UBB
/Delimiters = ~!@$%^&()_+=|\{}[]:;"'<> , .?
/Indent Strings = ""
/Unindent Strings = ""
/Open Fold Strings = "[ CODE]" "[INDENT]" "[ LIST]" "[QUOTE]"
/Close Fold Strings = "[ /CODE]" "[/INDENT]" "[ /LIST]" "[/QUOTE]"
/C1"Tags code indent list quote"
// /CODE /INDENT /LIST /QUOTE
CODE
INDENT
LIST
QUOTE
[
]
/C2"Tags color img size url"
*
// /COLOR /IMG /SIZE /URL
COLOR
IMG
SIZE
URL
/C3"Operators and colors"
=
black
blue
green
orange
red
/C4"Tags B I U"
// /B /I /U
B
I
U

• Be sure to update the extension part (i.e. File Extensions = UBB) in the above /L definition. I name BBCode files .UBB for some historical reason (maybe "Ultra Bulletin Board", or something).
• I spread out the color coding so that tags for indentation (code, indent, list, quote) have one color, special tags that should stand out (color, img, size, url) another color, and finally your standard text styles (bold, italics, underline) a third.
• The block oriented tags (code, indent, list, quote) support folding.
• In the /C3"Operators and colors" section you can explicitly name colors for highlighting if you like.
• If you want you could auto-indent/unindent the block tags by replacing:

  Code: Select all

  /Indent Strings = ""
  /Unindent Strings = ""

  with

  Code: Select all

  /Indent Strings = "[ CODE]" "[INDENT]" "[ LIST]" "[QUOTE]"
  /Unindent Strings = "[ /CODE]" "[/INDENT]" "[ /LIST]" "[/QUOTE]"

  Note: The space after [ on CODE and LIST tags are just for not getting those BBCode tags parsed here as BBcode tags by this forum. In the wordfile those four spaces must not exist.
  
  Issue: The indentation will work, but not the un-indenting of e.g. [ /code]. I have no idea why that is. I personally do not use such indentation because the forums often force you to manually delete empty lines or indentations to actually properly space the content. And each forum seems to have its own set of inconsistent rules.
• Alas convenient code like

  Code: Select all

  /Marker Characters = "[]"

  simply highlighting everything between any [ and ], i.e. the meta HTML tabs, is not allowed and does not work. But anyway I prefer to color code the specific tags by function (indentation, special, style).
• To properly implement BBCode, UE would need to have a special language tag treating tags in [...] specially, i.e. like this is the case for HTML and <> using HTML_LANG.
• There is another issue with String Chars = `. If you do not define a string delimiter (i.e. String Chars = ), the whole above highlighting will mess up. If you simply delete the parameter from the /L line, the default delimiters " and ' will be used.Is there actually a way to completely turn off String Chars =?

• Use Noquote instead of String Chars = ` to turn off syntax highlighting for strings.
   
• Add to color group 2 the string /* as shown below:
  
  // /* /COLOR /IMG /SIZE /URL
  
  because forums using phpBB v3.0 and later use [ /*] (without space after [) in lists for the closing </li> element.
   
• At color group 3 add the color names for all 16 VGA standard colors + orange specified in CSS 2.1:
  
  aqua
  black blue
  fuchsia
  gray green
  lime
  maroon
  navy
  olive orange
  purple
  red
  silver
  teal
  white
  yellow
   
• I don't have problems with:
  
  /Indent Strings = "[ CODE]" "[ INDENT]" "[ LIST]" "[ QUOTE]"
  /Unindent Strings = "[ /CODE]" "[ /INDENT]" "[ /LIST]" "[ /QUOTE]"
  
  Note: Please ignore the space after each [ in the two lines above just added to avoid that those BBCode tags are parsed as BBCode tags by the forum.
  
  Indenting and un-indenting works perfect.
   
• Do you know the BBCode tag list file I wrote and sent to IDM and which is online for download on user-submitted tag files and autocomplete files page?
  
  If you look into this file you will find some more common BBCode tags which should be highlighted also like the tags for a horizontal rule.

1. [ ]
2. LEFT ARROW
3. /INDENT
4. RIGHT ARROW
5. RETURN

/L20"BBCode" EnableSpellasYouType Noquote Nocase File Extensions = UBB
/Delimiters = ~!@$%^&()_+=|\{}[]:;"'<> , .?
/Indent Strings = "[ALIGN]" "[ CODE]" "[INDENT]" "[ LIST]" "[PHP]" "[PRE]" "[QUOTE]"
/Unindent Strings = "[/ALIGN]" "[ /CODE]" "[/INDENT]" "[ /LIST]" "[/PHP]" "[/PRE]" "[/QUOTE]"
/Open Fold Strings = "[ALIGN]" "[ CODE]" "[INDENT]" "[ LIST]" "[PHP]" "[PRE]" "[QUOTE]"
/Close Fold Strings = "[/ALIGN]" "[ /CODE]" "[/INDENT]" "[ /LIST]"  "[/PHP]" "[/PRE]" "[/QUOTE]"
/C1"Blocks: code indent ..."
// /ALIGN /CODE /INDENT /LIST /PHP /PRE /QUOTE
ALIGN
CODE
INDENT
LIST
PHP
PRE
QUOTE
[
]
/C2"Special: color img ..."
*
// /* /COLOR /EMAIL /FLASH /FONT /HR /IMG /MARQ /SIZE /URL /VIDEO
COLOR
EMAIL
FLASH
FONT
HR
IMG
MARQ
SIZE
URL
VIDEO
/C3"Operators: ="
=
/C4"Styles: b i sub sup u"
// /B /I /SUB /SUP /U
B
I
SUB
SUP
U
/C5"Colors"
aqua
black blue brown
cyan
darkblue
fuchsia
gray green
indigo
lime
maroon
navy
olive orange
purple
red
silver
teal
violet
white
yellow
/C6"Font Names"
Arial
Courier New
Lucida Console
System
Tahoma
Verdana
/C7"Alignment: left ..."
center
down
justify
left
right
up
/C8"Parameters: width ..."
height
width

• I added a few more color (/C) sections: Colors, Font Names, Alignment.
   
• The only thing that does not properly work is the highlighting of the font names with a space in them, i.e. "Courier New" and "Lucida Console". The first word is highlighted the second is not. One could probably *hack* this problem by adding two more lines with "New" and "Console".
  
  Test code:

  Code: Select all

  [font=Courier New] ... [/font]
  [font=Lucida Console] ... [/font]
  [font=Verdana] ... [/font]

  But is there a better way?

pietzcker wrote:As you probably know, you can define ".core" as well as "tango", so both will be highlighted. You could even still detect typos like tanggo.core - but you'd miss methods bound to wrong (but otherwise legal) objects. That doesn't look like so much of a problem.