aboutsummaryrefslogtreecommitdiff
path: root/localedata/locales/ku_TR
diff options
context:
space:
mode:
authorMike FABIAN <mfabian@redhat.com>2017-08-07 17:19:07 +0200
committerMike FABIAN <mfabian@redhat.com>2017-08-09 11:02:03 +0200
commit39b20aae21e4635296f4ebc4d80f4eb6c1cb4cbe (patch)
tree70201be1a218eadd2b33c26baaeeef24776d9aca /localedata/locales/ku_TR
parente119dfcfd674b37b6c2b6a3414fe055ba675975a (diff)
downloadglibc-39b20aae21e4635296f4ebc4d80f4eb6c1cb4cbe.tar
glibc-39b20aae21e4635296f4ebc4d80f4eb6c1cb4cbe.tar.gz
glibc-39b20aae21e4635296f4ebc4d80f4eb6c1cb4cbe.tar.bz2
glibc-39b20aae21e4635296f4ebc4d80f4eb6c1cb4cbe.zip
Remove “% Charset: ...” comments from locale sources
These comments are useless and only confusing. The encodings used to create binary locales from source locales are listed in the localedata/SUPPORTED file. The source files itself are ASCII or UTF-8 encoded where non-ASCII UTF-8 is currently only used in comments. If all locale source files are UTF-8 anyway, there is no need to specify that in a special comment.
Diffstat (limited to 'localedata/locales/ku_TR')
-rw-r--r--localedata/locales/ku_TR1
1 files changed, 0 insertions, 1 deletions
diff --git a/localedata/locales/ku_TR b/localedata/locales/ku_TR
index a028693815..6c889355e5 100644
--- a/localedata/locales/ku_TR
+++ b/localedata/locales/ku_TR
@@ -19,7 +19,6 @@ escape_char /
% Revision: 0.1
% Date: 2003-07-27
% Users: general
-% Charset: UTF-8
% History:
LC_IDENTIFICATION