https://bugs.freedesktop.org/show_bug.cgi?id=77071
--- Comment #9 from Eike Rathke <[email protected]> --- Great stuff.. ICU as of 53.1 checks Hangul syllables for contractions starting with Jamo L or V and refuses to process collation rules that contain them. Quoting from collationbuilder.cpp CollationBuilder::addRelation() "The runtime code decomposes Hangul syllables on the fly, with recursive processing but without making the Jamo pieces visible for matching. It does not work with certain types of contextual mappings." "While handling a Hangul syllable, contractions starting with Jamo L or V would not see the following Jamo of that syllable." (this is where we bail out already with the first syllable of ko_charset.txt) Another condition to fail is described as "A contraction ending with Jamo L or L+V would require generating Hangul syllables in addTailComposites() (588 for a Jamo L), or decomposing a following Hangul syllable on the fly, during contraction matching." Not being familiar at all with Korean, Hangul syllables or Jamo contractions I wonder if we can make further sense of ko_charset.txt at all, or if we have to drop it and hope that ICU in the mean time handles Korean collation sufficiently. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
