Bug 733331 - Part 1: Add the mapping of MCC and corresponding extra national language table tuples to enable in ril_consts.js. r=btseng

This commit is contained in:
Samael Wang 2015-03-24 18:54:09 +08:00
parent ffc7e75f58
commit 4c21ba9df2

View File

@ -1692,6 +1692,31 @@ this.PDU_NL_IDENTIFIER_TAMIL = 11;
this.PDU_NL_IDENTIFIER_TELUGU = 12;
this.PDU_NL_IDENTIFIER_URDU = 13;
// The mapping of mcc and their extra GSM national language locking / single
// shift table tuples to enable. The default GSM alphabet and extension table
// are always enabled and need not to be list here.
//
// The content should be updated when a relevant national regulatory body
// requests. See 'NOTE 2' of 6.2.1.2.5 in 3GPP TS 23.038:
// "
// Encoding of a message using the national locking shift mechanism is not
// intended to be implemented until a formal request is issued by the
// relevant national regulatory body. This is because a receiving entity
// not supporting the relevant locking-shift decoding will present different
// characters from the ones intended by the sending entity.
// "
this.PDU_MCC_NL_TABLE_TUPLES_MAPPING = {
// Configuration for Turkey.
//
// The Turkish single shift table contains 7 extra characters
// (Ğ, İ, Ş, ç, ğ, ı, ş) than the GSM default alphabet extension table. Since
// all the 7 characters are also included in Turkish locking shift table, it's
// not necessary to enable Turkish single shift table. Using GSM default
// alphabet extension table instead saves 3 octets when these extension table
// characters present in a message.
286: [[PDU_NL_IDENTIFIER_TURKISH, PDU_NL_IDENTIFIER_DEFAULT]]
};
/*
* 3GPP TS 23.038 - 6.2.1 GSM 7 bit Default Alphabet
*/