1 <?xml version="1.0" encoding="utf-8"?> 2 <!-- 3 /* 4 ** Copyright 2012, The Android Open Source Project 5 ** 6 ** Licensed under the Apache License, Version 2.0 (the "License"); 7 ** you may not use this file except in compliance with the License. 8 ** You may obtain a copy of the License at 9 ** 10 ** http://www.apache.org/licenses/LICENSE-2.0 11 ** 12 ** Unless required by applicable law or agreed to in writing, software 13 ** distributed under the License is distributed on an "AS IS" BASIS, 14 ** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 15 ** See the License for the specific language governing permissions and 16 ** limitations under the License. 17 */ 18 --> 19 20 <!-- These resources are around just to allow their values to be customized 21 for different hardware and product builds. DO NOT TRANSLATE. --> 22 <resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2"> 23 24 <!-- National Language Identifier codes for the following two config items. 25 (from 3GPP TS 23.038 V9.1.1 Table 6.2.1.2.4.1): 26 0 - reserved 27 1 - Turkish 28 2 - Spanish (single shift table only) 29 3 - Portuguese 30 4 - Bengali 31 5 - Gujarati 32 6 - Hindi 33 7 - Kannada 34 8 - Malayalam 35 9 - Oriya 36 10 - Punjabi 37 11 - Tamil 38 12 - Telugu 39 13 - Urdu 40 14+ - reserved --> 41 42 <!-- National language single shift tables to enable for SMS encoding. 43 Decoding is always enabled. 3GPP TS 23.038 states that this feature 44 should not be enabled until a formal request is issued by the relevant 45 national regulatory body. Array elements are codes from the table above. 46 Example 1: devices sold in Turkey must include table 1 to conform with 47 By-Law Number 27230. (http://www.btk.gov.tr/eng/pdf/2009/BY-LAW_SMS.pdf) 48 Example 2: devices sold in India should include tables 4 through 13 49 to enable use of the new Release 9 tables for Indic languages. --> 50 <integer-array name="config_sms_enabled_single_shift_tables"><item>1</item></integer-array> 51 52 <!-- National language locking shift tables to enable for SMS encoding. 53 Decoding is always enabled. 3GPP TS 23.038 states that this feature 54 should not be enabled until a formal request is issued by the relevant 55 national regulatory body. Array elements are codes from the table above. 56 Example 1: devices sold in Turkey must include table 1 after the 57 Turkish Telecommunication Authority requires locking shift encoding 58 to be enabled (est. July 2012). (http://www.btk.gov.tr/eng/pdf/2009/BY-LAW_SMS.pdf) 59 See also: http://www.mobitech.com.tr/tr/ersanozturkblog_en/index.php?entry=entry090223-160014 60 Example 2: devices sold in India should include tables 4 through 13 61 to enable use of the new Release 9 tables for Indic languages. --> 62 <!-- <integer-array name="config_sms_enabled_locking_shift_tables"></integer-array> --> 63 64 </resources> 65
