GNOME Bugzilla – Bug 339986
Patch to select localized strings exactly
Last modified: 2007-01-31 23:23:47 UTC
This problem fixes the problem of when you display a multibyte word you can't select the word exactly.
Created attachment 64439 [details] [review] patch fixing problem
I like the idea (though not the duplication of those three lines). Just wondering, where does the 0xa0 come from? It probably doesn't make any difference, but I suggest 0x80 instead. So we fallback to the default for all non-ASCII chars. Or maybe remove that check completely. What it means is that A-Z, a-z, and 0-9 will always be word chars no matter what the set ranges are. I cannot imagine someone wanting to remove any of them from the word chars. What do you think?
*** Bug 170668 has been marked as a duplicate of this bug. ***
*** Bug 341717 has been marked as a duplicate of this bug. ***
Yes, 0x80 is ok instead of 0xa0. I think the original bug is #170668 and this is a duplicated bug.
I dupped 170668. Doesn't matter.
I committed a functionally similar patch without the code duplication. 2006-07-10 Behdad Esfahbod <behdad@gnome.org> Bug 339986 – Patch to select localized strings exactly Patch from Takao Fujiwara * src/vte.c (vte_terminal_is_word_char): Fall back on Unicode properties for non-ASCII characters or when no array is set.
*** Bug 156279 has been marked as a duplicate of this bug. ***