This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Adding a new encoding to GNU C library


Hi glibc hackers,

I and my co-developer would like to add a new encoding to be supported by glibc. The encoding is the cyrillic MIK encoding that is mainly popular in Bulgaria.

More formal information about the encoding is given in the always helpful cyrillic soup of Czyborra:
http://czyborra.com/charsets/cyrillic.html
And some information on Wikipedia:
http://en.wikipedia.org/wiki/MIK_Code_page


The MIK code page came into existence due to some very ancient 8086 compatible machnines produced locally.

However - due to this fact - it is extensively used in some legacy systems. We hope to get some of those things gradually migrated or (if not possible) gracefully plugged into by some GNU/Linux updates.

It will be most convenient for us if we had this encoding in the GNU C library.

So - could someone point me to the proper way to do this - a former mail
discussion, documentation, bug report - whatever so that we can prepare:
patches, docs, test cases that can be susequently merged into glibc?

I hoped that glibc was migrated to subversion so I could get the links between commits and have an overall idea of what is to be changed to get a new encoding, however - glibc is still using CVS an changes are per file.

I am not subscribed currently to this list - I see it is a very high volume one. PLease cc me directly. I will still check the archives anyway.

Kind regards:
al_shopov


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]