public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ash at contact dot bg" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug localedata/2625] New: Added support for MIK encoding Date: Mon, 01 May 2006 05:54:00 -0000 [thread overview] Message-ID: <20060501055403.2625.ash@contact.bg> (raw) Added is a patch for MIK encoding. patch is produced with diff -Naur patch is against CVS HEAD about 2006-04-27 04:16:31 Summary of changes: * iconvdata/testdata/MIK: added testfile * iconvdata/testdata/MIK..UTF8: added testfile * iconvdata/Makefile: ** modules: added MIK ** distribute: added mik.c ** gen-8bit-gap-modules: added mik * iconvdata/TESTS: added MIK * iconvdata/gconv-modules: added MIK * iconvdata/mik.c: new file, no holes, uses 8bit-gap.c * iconvdata/tst-tables.sh: added MIK * localedata/charmaps/MIK: added the MIK charmap -- Summary: Added support for MIK encoding Product: glibc Version: unspecified Status: NEW Severity: enhancement Priority: P2 Component: localedata AssignedTo: libc-locales at sources dot redhat dot com ReportedBy: ash at contact dot bg CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i386-linux-elf GCC host triplet: i386-linux-elf GCC target triplet: i386-linux-elf http://sourceware.org/bugzilla/show_bug.cgi?id=2625 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-05-01 5:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-01 5:54 ash at contact dot bg [this message] 2006-05-01 5:58 ` [Bug localedata/2625] " ash at contact dot bg 2006-05-01 6:10 ` drepper at redhat dot com 2006-05-01 14:19 ` drepper at redhat dot com 2006-05-02 8:38 ` ash at contact dot bg
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=20060501055403.2625.ash@contact.bg \ --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).