There are open FIXME's regarding the behavior of the GLib unicode backend compared to to the ICU one.
Test cases need to be created to ensure identical behavior of both for cases mentioned in TextBreakIteratorGtk.cpp, such as:
1) FIXME: assumes no surrogate pairs
2) FIXME: UBRK_WORD case: Single multibyte characters (i.e. white space around them), such as the euro symbol â¬,
are not marked as word_start & word_end as opposed to the way ICU does it. This leads to - for example - different word selection behaviour when right clicking.
3) FIXME: This needs closer inspection to achieve behaviour identical to the ICU version.
When this has been done, we should be able to remove the configure-time stability warning for the GLib unicode backend that's currently autotools/webkit.m4.
is the WTF_USE_GLIB_ICU_UNICODE_HYBRID define still needed? I see two places in ThreadGlobalData.h where one still mentions it, but it seems to be cleared from ThreadGlobalData.cpp though.
(In reply to comment #1)
> is the WTF_USE_GLIB_ICU_UNICODE_HYBRID define still needed? I see two places in
> ThreadGlobalData.h where one still mentions it, but it seems to be cleared from
> ThreadGlobalData.cpp though.
You're right, this is orphaned and should go away. I created bug #35726 and attached a patch for review. Thanks for the reminder.
GLib backend is gone per bug 109627, closing.