Summary: | New locale request: tt_RU@iqtel | ||
---|---|---|---|
Product: | glibc | Reporter: | Reshat Sabiq <tatar.iqtelif.i18n> |
Component: | localedata | Assignee: | GNU C Library Locale Maintainers <libc-locales> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | glibc-bugs |
Priority: | P2 | Flags: | fweimer:
security-
|
Version: | 2.4 | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Bug Depends on: | 3326 | ||
Bug Blocks: | |||
Attachments: |
Starter locale file by Yours truly.
Using UTF-8 instead of ISO-8859-9 Same changes as last attachment (Using UTF-8 instead of ISO-8859-9), but as a patch file. |
Description
Reshat Sabiq
2006-10-13 00:53:57 UTC
Created attachment 1374 [details]
Starter locale file by Yours truly.
I'm using ISO-8859-9 in this file too, but the comments made for Crimean Tatar
are valid here as well: whatever is chosen there, would be appropriate here,
although here UTF-8 would be even more favorable. I can submit an updated file
w/ ISO-8859-9 replaced w/ UTF-8, if needed.
I've added the locale as tt_RU@iptelif. Created attachment 1561 [details]
Using UTF-8 instead of ISO-8859-9
I intended to post this in time once a decision was made on crh_UA. Not a big
deal, but per prior discussion, i made a small update to use UTF-8 instead of
ISO-8859-9 in comments.
Also, i've checked the CVS, and the new locale is there. @iqtelif sounds good
as well: 2 characters more to type w/ more clarity involved is a sensible
trade-off. ;)
Thanks.
Created attachment 1562 [details]
Same changes as last attachment (Using UTF-8 instead of ISO-8859-9), but as a patch file.
Just in case it makes it easier.
|