Our translation tools read the src files literally, line by line, only
reacting on specific patterns (e.g., 'Text [en-US] = "...";'). Therefore
use of macros like this cannot work.

The problem was that these are flags, not toggles.

Part XLIII
Modules
uui

Part XLIII
Modules
unoxml

Part XLII
Modules
unotools

Part XLI
Modules
ucbhelper, unodevtools

Unfortunately msiinfo.exe has a limitation, it truncates Language
property in Summary Information at char position 254.
The replacement, WiLangId.vbs does not have this limitation.

Also insert full date acceptance pattern at first position instead of
appending to have it be first in checks.

Implemented a simple character based comparison of the exported file and
the reference file

As in: that the compiler won't see the variables in the condition when OSL_DEBUG_LEVEL==0

On the other hand, column position 1 is not guaranteed to exist.
nCurPos will be BROWSER_INVALID_ID, not 0, in case of error in setting it

They are virtually unused (at least the LibO code base has only a
single use of UNO_REF_QUERY) but confuse static analysis tools that
classify unused function parameters as "tags" (which legalizes the
unusedness of those parameters) if they are of an enum type with
exactly one value defined.