public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "samuel.thibault@ens-lyon.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2253] unicode combining accents can't be iconv-ed to latin//translit (and others) Date: Sun, 06 May 2012 14:52:00 -0000 [thread overview] Message-ID: <bug-2253-131-z1IEbjXhAU@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-2253-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=2253 Samuel Thibault <samuel.thibault@ens-lyon.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|unicode combining accents |unicode combining accents |can't be iconv-ed to latin |can't be iconv-ed to |(and others) |latin//translit (and | |others) --- Comment #4 from Samuel Thibault <samuel.thibault@ens-lyon.org> 2012-05-06 14:51:41 UTC --- Right, thus changing bug title: the transliteration however still produces "e", while it could produce "é". -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-05-06 14:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-2253-131@http.sourceware.org/bugzilla/> 2012-05-06 9:08 ` [Bug libc/2253] unicode combining accents can't be iconv-ed to latin " aj at suse dot de 2012-05-06 12:24 ` bugdal at aerifal dot cx 2012-05-06 14:52 ` samuel.thibault@ens-lyon.org [this message] 2014-02-07 2:55 ` [Bug localedata/2253] unicode combining accents can't be iconv-ed to latin//translit " jsm28 at gcc dot gnu.org 2014-06-26 5:08 ` pravin.d.s at gmail dot com 2015-05-04 18:23 ` maiku.fabian at gmail dot com 2015-05-05 9:40 ` maiku.fabian at gmail dot com
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-2253-131-z1IEbjXhAU@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).