I took me some time to create two small syntax highlighting files and find out in which version of UltraEdit for Windows and UEStudio changed the syntax highlighting behavior for substrings starting with a digit.
The first syntax highlighting wordfile is with hyphen character
not included in list of word delimiters which is required to be able to syntax highlight a string being a date (or date+time) beginning with year and month in format yyyy-MM.
Code: Select all
/L1"Text" Noquote DisableMLS File Extensions = TXT
/Delimiters = ! $ '()*+,/:;<=>@[\]^`{|}~
/C1"Dates"
** 2024-01 2024-02 2024-03 2024-04 2024-05 2024-06 2024-07
/C2"Hyphen"
-
/C3"Test"
** test-
The second syntax highlighting is with hyphen character in list of word delimiters as in most syntax highlighting language definitions just for seeing the differences.
Code: Select all
/L1"Text" Noquote DisableMLS File Extensions = TXT
/Delimiters = ! $ '()*+,-/:;<=>@[\]^`{|}~
/C1"Dates"
** 2024-01 2024-02 2024-03 2024-04 2024-05 2024-06 2024-07
/C2"Hyphen"
-
/C3"Test"
** test-
The result of the first language definition with hyphen being interpreted as a
word character can be seen on the image below in first row and the second wordfile with hyphen as a
word delimiter produced the second row.
I have found out in my tests with versions archived by me from 28.20.0.92 to currently latest 2023.0.0.41 (30.0.0.41) that the syntax highlighting of substrings beginning with a digit according to a definition in a color group takes precedence over the built-in highlighting of strings beginning with a digit as number up to UE/UES v2022.0.0.102 (29.0.0.102).
The precedence of built-in number string highlighting over a substring highlighting of strings starting with a digit defined in a color group changed with UE/UES v2022.1.0.70 with the
syntax highlighting parser overhaul as briefly described in file
changes.txt in program files directory of UltraEdit respectively
changes_ues.txt in program files directory of UEStudio.
There can be sent to support of UltraEdit only a syntax highlighting issue report by email with describing the issue and requesting a change back to former behavior regarding to syntax highlighting of strings starting with a digit with taking precedence of substring definitions in color group 1 over substring definitions in color group 2 ... and finally as last one number string highlighting. There is no possibility to get back the former syntax highlighting behavior for this use case by changing something in the wordfile because of the built-in number syntax highlighting cannot be disabled with something in the wordfile.