Brian Milby

Results 10 comments of Brian Milby

The note should be renamed to `19157.md` to conform to the naming convention.

So, would something like this work? ``` function CheckForBOM pInput put numtobyte(0xFF) & numtobyte(0xFE) into kUTF16LE put numtobyte(0xFE) & numtobyte(0xFF) into kUTF16BE put kUTF16LE & numtobyte(0x00) & numtobyte(0x00) into kUTF32LE...

I think you may need to reverse the order. UTF16LE and UTF32LE start with the same 2 bytes. I'm not seeing how it works for UTF8 yet though.

Just checked it and it does work for UTF 8. Now to figure out why :)

I'm getting something odd though. I can see the bytes shift from UTF32 LE/BE, but for UTF16 BE is returning blank in LC9DP8. Works as expected in 8.1.6

Never mind, must have been a typo (was getting blank when just having the textencode print in the msg box)

What about non-inline block comments? If `/* ... */` spans multiple lines, that would seem to be an ideal thing to fold.

Probably a good time to ensure there are no prefs included that are no longer referenced/used. I like the new look.

#1988 will go along well with this addition - will be able to filter platform specific widgets/libraries.

I was poking around and stumbled across this: `function revIDELocalise pString, pSubstitutions` It currently doesn't do any actual localization, but it is called just over 80 times. It is a...