>>< vbg > is ok
>><vbg> is not
>
>Looks like it's been fixed.

Yes, this logic is quite complicated. For every message display, there is several routines that are being called and the order of the calling sequence is really important. As we are now supporting the < to be included as is in a message/code, there is some additional parsing logic to handle it. However, the acronyms verification was done before and it now has to be done after as we need to identify the < occurences before applying the HTML conversion of the acronyms.