mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/toolkit/locale/intl.properties

26 строки
2.2 KiB
Properties
Исходник Обычный вид История

move the i18n part of browser.properties into the toolkit (intl.properties) Even if the platform dependent files intl.properties are identical for en-US, I think it's a good idea to keep them in seperate directories, to not mislead localizers.
2003-11-15 11:26:10 +03:00
# all.js
#
bug 233391 : bug 224847 change was not reflected in FB/TB (r=p_ch)
2004-02-08 07:45:00 +03:00
# Localization Note: Cases of charset names must be preserved. If you're
# adding charsets to your localized version, please refer to
# intl/uconv/src/charsetalias.properties file for the list of canonical
# charset names and use canonical names exactly as listed there.
bug 55300: add 'Unicode' submenu to the 'Character Encoding' menu. The new submenu has UTF-8, UTF-16*, UTF-32* and UTF-7. UTF-8 was also added to the static list. (r=neil, sr=blizzard, moa for ff = pch)
2004-03-06 09:11:48 +03:00
# Also note that "UTF-8" should always be included in intl.charsetmenu.browser.static
move the i18n part of browser.properties into the toolkit (intl.properties) Even if the platform dependent files intl.properties are identical for en-US, I think it's a good idea to keep them in seperate directories, to not mislead localizers.
2003-11-15 11:26:10 +03:00
general.useragent.locale=en-US
font.language.group=x-western
intl.accept_languages=en-us, en
bug 55300: add 'Unicode' submenu to the 'Character Encoding' menu. The new submenu has UTF-8, UTF-16*, UTF-32* and UTF-7. UTF-8 was also added to the static list. (r=neil, sr=blizzard, moa for ff = pch)
2004-03-06 09:11:48 +03:00
intl.charsetmenu.browser.static=ISO-8859-1, UTF-8
bug 233391 : bug 224847 change was not reflected in FB/TB (r=p_ch)
2004-02-08 07:45:00 +03:00
intl.charsetmenu.browser.more1=ISO-8859-1, ISO-8859-15, IBM850, x-mac-roman, windows-1252, ISO-8859-14, ISO-8859-7, x-mac-greek, windows-1253, x-mac-icelandic, ISO-8859-10, ISO-8859-3
intl.charsetmenu.browser.more2=ISO-8859-4, ISO-8859-13, windows-1257, IBM852, ISO-8859-2, x-mac-ce, windows-1250, x-mac-croatian, IBM855, ISO-8859-5, ISO-IR-111, KOI8-R, x-mac-cyrillic, windows-1251, IBM866, KOI8-U, x-mac-ukrainian, ISO-8859-16, x-mac-romanian
intl.charsetmenu.browser.more3=GB2312, x-gbk, gb18030, HZ-GB-2312, ISO-2022-CN, Big5, Big5-HKSCS, x-euc-tw, EUC-JP, ISO-2022-JP, Shift_JIS, EUC-KR, x-windows-949, x-johab, ISO-2022-KR
intl.charsetmenu.browser.more4=armscii-8, GEOSTD8, TIS-620, ISO-8859-11, windows-874, IBM857, ISO-8859-9, x-mac-turkish, windows-1254, x-viet-tcvn5712, VISCII, x-viet-vps, windows-1258, x-mac-devanagari, x-mac-gujarati, x-mac-gurmukhi
intl.charsetmenu.browser.more5=ISO-8859-6, windows-1256, IBM864, x-mac-arabic, x-mac-farsi, ISO-8859-8-I, windows-1255, ISO-8859-8, IBM862, x-mac-hebrew
bug 55300: add 'Unicode' submenu to the 'Character Encoding' menu. The new submenu has UTF-8, UTF-16*, UTF-32* and UTF-7. UTF-8 was also added to the static list. (r=neil, sr=blizzard, moa for ff = pch)
2004-03-06 09:11:48 +03:00
# Localization Note: Never change the following entry.
intl.charsetmenu.browser.unicode=UTF-8, UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE, UTF-7
move the i18n part of browser.properties into the toolkit (intl.properties) Even if the platform dependent files intl.properties are identical for en-US, I think it's a good idea to keep them in seperate directories, to not mislead localizers.
2003-11-15 11:26:10 +03:00
intl.charset.default=ISO-8859-1
intl.charset.detector=
Add Windows-1255 to mail compose character encodings menu. Bug 244141 (toolkit part). r=jshin, sr=bienvenu
2004-07-20 23:15:28 +04:00
intl.charsetmenu.mailedit=ISO-8859-1, ISO-8859-15, ISO-8859-6, armscii-8, geostd8, ISO-8859-13, ISO-8859-14, ISO-8859-2, GB2312, GB18030, Big5, KOI8-R, windows-1251, KOI8-U, ISO-8859-7, ISO-8859-8-I, windows-1255, ISO-2022-JP, EUC-KR, ISO-8859-10, ISO-8859-3, TIS-620, ISO-8859-9, UTF-8, VISCII
move the i18n part of browser.properties into the toolkit (intl.properties) Even if the platform dependent files intl.properties are identical for en-US, I think it's a good idea to keep them in seperate directories, to not mislead localizers.
2003-11-15 11:26:10 +03:00
# valid collation options are: <empty string> or useCodePointOrder
intl.collationOption=
# valid intl.menuitems.appendedacceskeys are: true or false, <empty string> (missing or empty preference equals false)
intl.menuitems.alwaysappendaccesskeys=