public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egmont at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/13547] Different strings collate as equal in Hungarian Date: Tue, 08 Sep 2015 08:35:00 -0000 [thread overview] Message-ID: <bug-13547-131-A5Z0iRHUAF@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13547-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=13547 --- Comment #3 from Egmont Koblinger <egmont at gmail dot com> --- Please note that the patch applied here was incorrect. It fixed a corner case, while broke a more generic one. By tokenizing "ssz" as <s_or_sz><sz> rather than <sz><sz>, and ordering the tokens as <s> < <s_or_sz> < <sz>, the corner case when the only difference in the two words is "ssz" vs. "szsz" is fixed. However, sorting of e.g. "kasza" <k><a><sz><a> vs. "kassza" <k><a><s_or_sz><sz><a> became broken. The correct ordering would be "kasza" < "kassza" (since it's actually <k><a><sz><sz><a>), but with the current solution they're ordered backwards (due to <s_or_sz> preceding <sz>). The solution is to tokenize both "ssz" and "szsz" as <sz><sz> (as we did before), but apply something weaker, something along the lines of a "fake accent" (SINGLE-OR-COMPOUND vs. COMPOUND) on top of them that might distinguish later. Let's leave this bug closed. A fix is available in bug 18934. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2015-09-08 8:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-03 0:18 [Bug localedata/13547] New: " egmont at gmail dot com 2012-01-03 0:28 ` [Bug localedata/13547] " egmont at gmail dot com 2012-01-07 16:05 ` drepper.fsp at gmail dot com 2014-06-27 11:20 ` fweimer at redhat dot com 2015-09-08 8:35 ` egmont at gmail dot com [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-13547-131-A5Z0iRHUAF@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).