Ales Katona wrote:
Felipe Monteiro de Carvalho wrote / napísal(a):
On Jan 25, 2008 6:23 PM, Ales Katona <[EMAIL PROTECTED]> wrote:
That's not enougth. It already works for ascii characters today.
Please test with both unicode and non-unicode IDE on strings with
accented characters.
ASCII doesn't have accented chars. If you mean "non-utf local non-latin1
encoding" then pre-patch doesn't work on those, anything out of
['A'-'z'] is considered block before my patch.
With my patch, anything NOT listed in TSynWordBlockChars +
TSynWhiteChars (if there's no highlighter), or
Highlighter.WordBlockChars + TSynWhiteChars is considered a valid
word-character (which MIGHT include some nonsense chars, but at least it
doesn't block known word-chars, + it can be runtime adjusted (in a way
to also support utf-8), unlike the current situation (where you simply
cannot support utf-8 because "allowed chars" is a set of 8bit char).
I agree on Ales here. this afternoon Ales and I spoke while he was
inmplementing this. The curretn handling of Synedit now is imo plain
stupid and never will work when the carset is growing bigger than 255
chars. Defining a set of nonword + whithespace chars is imo better.
If someone enters a nonsence char and it is considered a part of a word
is imo a lot better than acception only lower ascii.
Marc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
