1 /*

     2 * Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies).

     3 * All rights reserved.

     4 * This component and the accompanying materials are made available

     5 * under the terms of "Eclipse Public License v1.0"

     6 * which accompanies this distribution, and is available

     7 * at the URL "http://www.eclipse.org/legal/epl-v10.html".

     8 *

     9 * Initial Contributors:

    10 * Nokia Corporation - initial contribution.

    11 *

    12 * Contributors:

    13 *

    14 * Description: 

    15 *

    16 */

    17 

    18 #ifndef __BLDPUBLIC_HRH

    19 #define __BLDPUBLIC_HRH

    20 

    21 //Defining only language 01 for SF build purposes

    22 #define LANGUAGE_IDS LANG sc 01  

    23 

    24 

    25 /** #FF_3D_RINGING_TONES 

    26 Device supports 3D ringing tones.

    27 */

    28 #undef FF_3D_RINGING_TONES                                

    29 

    30 /** #FF_3G_CELLBROADCAST 

    31 Cell Broadcasting support on 3G mode.

    32 */

    33 #undef FF_3G_CELLBROADCAST                                

    34 

    35 /** #FF_ADAPTIVE_WLAN_SCANNING_SUPPORT 

    36 Adaptive WLAN Scanning (AWS) is a component that tells WLAN engine how often to

    37 perform WLAN background scanning. AWS listens and receives events from other

    38 components, concludes what would be the preferred scanning period, and then

    39 tells it to WLAN engine.

    40 */

    41 #undef FF_ADAPTIVE_WLAN_SCANNING_SUPPORT                  

    42 

    43 /** #FF_AI_WLANSNIFFER_WIDGET 

    44 Flag for WLANSniffer Homescreen widget.

    45 */

    46 #undef FF_AI_WLANSNIFFER_WIDGET                           

    47 

    48 /** #FF_ASYNCH_FILE_SAVE_QUEUE 

    49 Camcorder requires support from the Asynchronous File Save Queue.

    50 */

    51 #define FF_ASYNCH_FILE_SAVE_QUEUE                          

    52 

    53 /** #FF_AUDIO_MESSAGING_INCLUDE_IN_ROM 

    54 This flags controls whether the Audio Messaing ROM files are included in the

    55 build.

    56 */

    57 #define FF_AUDIO_MESSAGING_INCLUDE_IN_ROM                  

    58 

    59 /** #FF_AUDT 

    60 Device supports Always Up-to-date Device Time (AUDT). This is an ability to

    61 update the device time, date and country/city automatically in phone start-up.

    62 */

    63 #undef FF_AUDT                                            

    64 

    65 /** #FF_AUTO_REDIAL_FOR_VIDEO_CALL 

    66 "This flag indicates redial sequence, when video call is not succeeded for

    67 certain reasons."

    68 */

    69 #define FF_AUTO_REDIAL_FOR_VIDEO_CALL                      

    70 

    71 /** #FF_AVKON_EMOTION_ICON_ENABLED 

    72 to enable/disable the emotion icon support in avkon editor control

    73 */

    74 #undef FF_AVKON_EMOTION_ICON_ENABLED                      

    75 

    76 /** #FF_BIRTHDAY_IMPROVEMENT 

    77 This feature flag is required for the enabling/disabling customized birthday &

    78 anniversary notifications for MyFaves contact in Calendar (under Community 1.0)

    79 into 3.2.3 platform. 

    80 

    81 The requirement is 

    82 

    83 B’day & Anniversary Notification for MyFaves contact

    84 

    85 •	Picture of the MyFaves contact in the popup which can be masked as circular

    86 

    87 •	Currently Birthday notification is same as any other Calendar alarm

    88 

    89 */

    90 #undef FF_BIRTHDAY_IMPROVEMENT                            

    91 

    92 /** #FF_BROWSER_PROGRESSIVE_DOWNLOAD 

    93 This feature flag is needed to enable/disable the progressiveness of the

    94 downloads in download manager server and its clients.

    95 */

    96 #define FF_BROWSER_PROGRESSIVE_DOWNLOAD                    

    97 

    98 /** #FF_CAPACITIVE_DISPLAY 

    99 Device uses capacitive touch technology in its display.

   100 

   101 */

   102 #define FF_CAPACITIVE_DISPLAY                              

   103 

   104 /** #FF_CHINESE_FONTS_HIRES 

   105 This flag controls whether Chinese variants use TrueType fonts instead of the

   106 current stroke fonts in high resolution devices.

   107 

   108 Current stroke fonts have good readability in small sizes and lower resolution

   109 devices. However, with the introduction of ever sharper and larger displays

   110 (HVGA, VGA), the stroke fonts look increasingly "too simple" and "stick-like" in

   111 bigger sizes. Fonts with thicker, more stylistic strokes are required for a

   112 proper look and user experience.

   113 

   114 Following requirements already make a case for TTF fonts in Chinese:

   115 417-16400: Chinese TrueType font for 9.1

   116 406-137: TrueType font for Chinese

   117 

   118 Note: The feature name intentionally avoids mentioning TrueType or TTF, as the

   119 font technology is irrelevant, high resolution being the operative keywords.

   120 */

   121 #undef FF_CHINESE_FONTS_HIRES                             

   122 

   123 /** #FF_CLOCK_MULTIPROCOL_SUPPORT 

   124 This flag shall be used to determine if product programs need clock's

   125 multiprotocol support, i.e. getting time information from different time source

   126 protocols like GPS, SNTP, etc.. Product program can make a choice such that

   127 multiprotocol feature support can be made on or off. When multiprotocol support

   128 is off, then default NITZ protocol shall be choosen.

   129 */

   130 #undef FF_CLOCK_MULTIPROCOL_SUPPORT                       

   131 

   132 /** #FF_COMMSDAT_CREATION_FROM_XML 

   133 There will be a new component in S60 called CommsDatCreator (CDC) that will

   134 initialize CommsDat using an input XML file which is generated by the

   135 Configuration Tool.

   136 When generating CommsDat the CDC needs that the default CommsDat in

   137 Z:\private\10202be9\cccccc00.cre is empty. 

   138 The requested flag FF_COMMSDAT_CREATION_FROM_XML  enables the empty CommsDat to

   139 be included to the image as the default CommsDat.

   140 

   141 */

   142 #undef FF_COMMSDAT_CREATION_FROM_XML                      

   143 

   144 /** #FF_COMMSDAT_CREATOR 

   145 This flags controls whether the CommsDatCreator component to be included to the

   146 image.

   147 */

   148 #define FF_COMMSDAT_CREATOR                                

   149 

   150 /** #FF_CONNECTION_OVERRIDE 

   151 The feature enables the better utilisation of the WLAN connections that the user

   152 has manually opened from the WLAN widget. Such connections, called as 'user

   153 connections', will be automatically utilised in all applications that would

   154 normally use Internet SNAP connection. If the feature is enabled, the 'user

   155 connection' is enforced by default. The user can still control the utilisation

   156 of the 'user connection' by enabling/disabling the connection enforcement from

   157 WLAN settings.

   158 */

   159 #define FF_CONNECTION_OVERRIDE                             

   160 

   161 /** #FF_CONTACTS_GROUP_FUNCTIONALITY 

   162 We need a feature flag for ROM Creation time variation. The Phonebook2

   163 application is constructed on a plugin based architecture. This design allows

   164 the Phonebook2 application to be composed of various plugin components. The S60

   165 platform Phonebook2 component contains a group UI plugin component, which

   166 implements the whole contacts group functionality. To enable a variant to create

   167 their own contact group functionality we need a feature flag so that the variant

   168 can remove the platform group plugin component. This allow the component to be

   169 removed from the ROM image, thus making the ROM size smaller.

   170 */

   171 #define FF_CONTACTS_GROUP_FUNCTIONALITY                    

   172 

   173 /** #FF_CONTACTS_NICKNAME 

   174 The nickname functionality needs a feature flag for the following reasons:

   175 -Phonebook2 component exports a central repository initialization file, which is

   176 used to improve the Phonebook application launch -The initialization file is

   177 read by the Symbian Contacts model server to initialize the Contacts view during

   178 the device boot sequence

   179  * S60 specifications define which fields take part in the device's contact name

   180 creation (first name, last name, company name)

   181  * The nickname requirement changes the S60 name creation rules, by adding the

   182 contacts nickname field to the above list of fields

   183  * Therefore the content of the Contacts view needs to be initialized

   184 differently depending on whether the nickname feature is enabled or disabled

   185  * The initialization file contains the configuration of the view, e.g. the

   186 contact fields which are used for sorting the Phonebook names list view

   187  * A feature flag is needed which allows Phonebook2 to export the correct

   188 variant of the Contact view initilization file

   189  * There is a considerable RAM usage penalty associated with keeping the

   190 nickname field in the contact view when the nickname feature is disabled

   191  * For further description of the Symbian Contacts view initilization see

   192 \src\common\generic\app-engines\cntmodel\documentation\Contacts_How-To_Improve_Application_Start-up_Time.doc

   193 -Run-time variation can be used inside the Phonebook2 application to configure

   194 the application sort order

   195  * But the Symbian Contacts view's must be configured correctly in order to

   196 maintain existing performance, see above description

   197 

   198 */

   199 #undef FF_CONTACTS_NICKNAME                               

   200 

   201 /** #FF_CUSTOMER_HELPS_IN_USE 

   202 Customer helps are included into image based on this flag.

   203 */

   204 #undef FF_CUSTOMER_HELPS_IN_USE                           

   205 

   206 /** #FF_DEVICE_DIAGNOSTICS_APP 

   207 On enabling this feature flag GSDevDiagPlugin.dll would start the

   208 DevDiagApp.exe. This would load all related plugins. The Diagnostics application

   209 offers self-test service on the Mobile Applications and hardware for the phone

   210 users.

   211 */

   212 #undef FF_DEVICE_DIAGNOSTICS_APP                          

   213 

   214 /** #FF_DM_INSTALL_SECURITY 

   215 OMA DM SW installer implementation included in build.

   216 */

   217 #undef FF_DM_INSTALL_SECURITY                             

   218 

   219 /** #FF_DUAL_LANGUAGE_SUPPORT 

   220 This Flag is used to develop support for dual language feature. This is an

   221 enhancement to the basic prediction feature where words predicted will come from

   222 2 different language databases.

   223 */

   224 #undef FF_DUAL_LANGUAGE_SUPPORT                           

   225 

   226 /** #FF_EMAIL_FRAMEWORK 

   227 Defines whether the product includes the email multiprotocol framework. When the

   228 flag is defined all parts constituting new email solution are in ROM:

   229 application, plugin framework + imap/pop plugin and related settings UIs. 

   230 

   231 legacy email (__EMAIL_UI) must be disabled when FF_EMAIL_FRAMEWORK is enabled.

   232 */

   233 #define FF_EMAIL_FRAMEWORK                                 

   234 

   235 /** #FF_EMAIL_IPS_SERVICES 

   236 Defines whether the product includes IMAP4, POP3 and SMTP protocol support.

   237 */

   238 #undef FF_EMAIL_IPS_SERVICES                              

   239 

   240 /** #FF_EMAIL_MCE_INTEGRATION 

   241 This enables email client selection in MCE. Fex. Freestyle email mailboxes  goes

   242 under email folder in mce-serttings. mce and sendui. Freestyle email settings

   243 can be changed from mce-settings.

   244  All you need to do is install own mtm-plugin and configure central repository

   245 key.

   246 

   247 */

   248 #define FF_EMAIL_MCE_INTEGRATION                           

   249 

   250 /** #FF_EMAIL_PROTOCOL_PLUGINS 

   251 When defined, default email protocol plugins are enabled.

   252 */

   253 #define FF_EMAIL_PROTOCOL_PLUGINS                          

   254 

   255 /** #FF_EMAIL_UI 

   256 Defines whether the product includes email UI application

   257 */

   258 #undef FF_EMAIL_UI                                        

   259 

   260 /** #FF_EMPTY_COMMSDAT 

   261 The override flags FF_EMPTY_COMMSDAT, FF_VANILLA_COMMSDAT and FF_RND_COMMSDAT

   262 determine which default CommsDat will be put to the image independent of image

   263 type (prd or rnd):

   264 

   265 - FF_EMPTY_COMMSDAT: Completely empty CommsDat is used. Typically needed as the

   266 base when creating operator variants with Configuration Tool and

   267 CommsDatCreator. Same as old FF_COMMSDAT_GENERATION_FROM_XML.

   268 

   269 - FF_VANILLA_COMMSDAT: Otherwise empty CommsDat but the S60 default destinations

   270 (Internet, MMS and Operator) as well as the Easy WLAN IAP (in case of WLAN

   271 product) is included. This is suitable for vanilla variants of the phones.

   272 

   273 - FF_RND_COMMSDAT: Platform releases contain typically the RND CommsDat that has

   274 Nokia Test Network IAPs as well as some Finnish operator IAPs (DNA, Sonera,

   275 Elisa) for RnD purposes.

   276 

   277 Maximum of one of these flags should be defined at the time. 

   278 

   279 If none of the override flags is defined then the used CommsDat depends on the

   280 image type: vanilla CommsDat is used for PRD image and RnD CommsDat for the RnD

   281 image. This is typically how it should be and the override flags should only be

   282 used if some special functionality is needed.

   283 

   284 */

   285 #undef FF_EMPTY_COMMSDAT                                  

   286 

   287 /** #FF_FARSI_CALENDAR 

   288 S60 calendar should provide possibility to integrate Farsi calendar application

   289 to S60 calendar.

   290 

   291  S60 calendar should provide variation point to calendar main menu, from where

   292 Farsi calendar application can be launched. In addition S60 calendar setting

   293 should provide access to the Farsi calendar settings. User should comfortably

   294 move btwn Gregorian and Farsi calendars. 

   295 

   296 Farsi calendar will be enabled in the variants English & Farsi. These variants

   297 can be extended further as per the need. 

   298 

   299 This feature is approved and targeted for 3.2.3 products. So variation required

   300 from 3.2.3 onwards. 

   301 */

   302 #undef FF_FARSI_CALENDAR                                  

   303 

   304 /** #FF_FLASHLITE_SCREENSAVER 

   305 When enabled/defined flash can be used as Screensaver.

   306 */

   307 #undef FF_FLASHLITE_SCREENSAVER                           

   308 

   309 /** #FF_FMTX 

   310 FMTX application and Nseries Music Player support for FMTX

   311 */

   312 #undef FF_FMTX                                            

   313 

   314 /** #FF_FULLSCR_HWR_INPUT 

   315 Indicates whether a device needs fullscreen HWR (HandWritingRecognition) input

   316 or not.

   317 */

   318 #undef FF_FULLSCR_HWR_INPUT                               

   319 

   320 /** #FF_GENERIC_FONTS_ASSETS 

   321 This flag is used to check if generic font assets are to be used, this is used

   322 for Symbian foundation where freetype rasterize as well as EFF fonts need to be

   323 used.

   324 */

   325 #undef FF_GENERIC_FONTS_ASSETS                            

   326 

   327 /** #FF_HDMI 

   328 Feature flag to indicate HDMI availability.  IIf defined, device supports HDMI

   329 (High Definition Multimedia Interface)

   330 */

   331 #undef FF_HDMI                                            

   332 

   333 /** #FF_HELP_TUTORIAL_MERGE 

   334 The end-user shall be provided with animated help (tutorial kontent) from CSX

   335 Help application. Both applications will continua existing as separate

   336 applications, though Tutorial will not be visible in application grid, but only

   337 provide animated content for CSX Help.

   338 

   339 This is for REQ 417-16797. Help & Tutorial will look like one application. User

   340 will not feel that they are 2 different applications. To implement this REQ

   341 without breaking the compatibility, one feature flag is needed to make Help &

   342 Toturial applications know if Tutorial is embedded in Help or running as a

   343 standalone application. Also refer to REQ 101-39505.

   344 */

   345 #undef FF_HELP_TUTORIAL_MERGE                             

   346 

   347 /** #FF_HIJRI_CALENDAR 

   348 S60 calendar should provide possibility to integrate separate Hijri calendar

   349 application to S60 calendar.

   350 

   351 S60 calendar should provide variation point to calendar main menu, from where

   352 Hijri calendar application can be launched. In addition S60 calendar setting

   353 should provide access to the Hijri calendar settings. User should comfortably

   354 move btwn Gregorian and Hijri calendars.

   355 

   356 Hijri calendar will be enabled in the variants English, Arabic, Urdu , French &

   357 Farsi. These variants can be extended further as per the need. 

   358 

   359 This feature is approved and targeted for 3.2.3 products. So variation required

   360 from 3.2.3 onwards.

   361 

   362 */

   363 #undef FF_HIJRI_CALENDAR                                  

   364 

   365 /** #FF_HITCHCOCK_APP_SHELL 

   366 "Feature flag 'FF_HITCHCOCK_MENU' to control which AppShell menu to use. If

   367 disabled, old xml based menu2, and if enabled, new hitchcock based menu3."

   368 */

   369 #undef FF_HITCHCOCK_APP_SHELL                             

   370 

   371 /** #FF_HOMESCREEN_COMMON_IDLEFW 

   372 Feature flag for enabling common idle framework to support new widgetized

   373 stand-by mode application of Active Idle 3 on S60 by REQ "101-40598: HomeScreen:

   374 3rd Party widget support" as alternative of existing Active Idle 2 and yet

   375 enabling even custom made stand-by mode app to be active. The binary objects

   376 which comprise common idle framework related components and new active stand-by

   377 application, selection of alternative,  and its depended components, can be

   378 selected at image creation time in case where common ilde fw is accepted by

   379 product/variant decicion.

   380 */

   381 #define FF_HOMESCREEN_COMMON_IDLEFW                        

   382 

   383 /** #FF_HOMESCREEN_OPEN_MENUFW 

   384 Feature flag for activation of open menu framework to support alternative main

   385 menu applications on S60 by REQS "101-40417: Open Shell UI internal menu model

   386 for other applications", "417-8821: Non-touch VGA support for Matrix" and

   387 "404-3950: Matrix: Basic Menu". Existing main menu app, Hitchcock AppShell, can

   388 still be used if product/variant decides so, however, open menu fw which enables

   389 altenative menu applications to run on same content, can be chosen as well. The

   390 binary objects which comprise open menu fw and active main menu application with

   391 its depended components can be selected at image creation time, as well as it is

   392 possible to request appropriate main menu application UID when needed to

   393 configure S60. These requests are, for example, setting the application UID to

   394 launch main menu by "applications" hw-key and hide menu application from itself

   395 etc. 

   396 */

   397 #define FF_HOMESCREEN_OPEN_MENUFW                          

   398 

   399 /** #FF_HOMESCREEN_SWITCHABLE_ROOT 

   400 Homescreen root configuration replaces existing concept of Active Idle

   401 themes/modes from S60 5.1. FF_HOMESCREEN_SWITCHABLE_ROOT variates S60 by

   402 enabling/disabling possibility to switch homescreen root. Homescreen root switch

   403 must be enabled to end user to select operator/product  specific alternative

   404 homescreen active, for example, an alternative root or External Homescreen. This

   405 feature must be able to set at run time also for post-product provision of

   406 alternative homescreen.

   407 */

   408 #undef FF_HOMESCREEN_SWITCHABLE_ROOT                      

   409 

   410 /** #FF_IAUPDATE 

   411 If defined, the phone supports Independent Application Update feature.

   412 */

   413 #define FF_IAUPDATE                                        

   414 

   415 /** #FF_IAUPDATE_PHASE2 

   416 Flag to control whether phone's Independent Application Update feature,

   417 controlled by FF_IAUPDATE, is version two or later, a.k.a. IAD client phase 2.

   418 */

   419 #define FF_IAUPDATE_PHASE2                                 

   420 

   421 /** #FF_IMAGEPRINT_BT_PROTOCOL 

   422 Flag to control whether ImagePrint supports Bluetooth-printing

   423 */

   424 #define FF_IMAGEPRINT_BT_PROTOCOL                          

   425 

   426 /** #FF_IMAGEPRINT_MEMORYCARD_PROTOCOL 

   427 Flag to define whether ImagePrint supports printing to memorycard

   428 */

   429 #define FF_IMAGEPRINT_MEMORYCARD_PROTOCOL                  

   430 

   431 /** #FF_IMAGEPRINT_PICTBRIDGE_PROTOCOL 

   432 Flag to define whether ImagePrint supports PictBridge printing - meaning

   433 printing over USB.

   434 */

   435 #define FF_IMAGEPRINT_PICTBRIDGE_PROTOCOL                  

   436 

   437 /** #FF_IMAGEPRINT_UPNP_PROTOCOL 

   438 Flag to define whether ImagePrint supports UPnP printing

   439 */

   440 #define FF_IMAGEPRINT_UPNP_PROTOCOL                        

   441 

   442 /** #FF_INCLUDE_CHINESE_DICTIONARY 

   443 This feature flag  controls the inclusion/exclusion of chinese dictionary in

   444 chinese variants. The flag is used in dictionary_variant.iby

   445 

   446 */

   447 #undef FF_INCLUDE_CHINESE_DICTIONARY                      

   448 

   449 /** #FF_INPUTS_PER_ORIENTATION 

   450 the feature is implemented to adjust dynamically available input methods

   451 according to autorotation status. 

   452 when autorotation is ON, if orientation is landscape, show menu items exclude

   453 "virtual ITU-T" and virtual ITU-T is also unavailabe, else if orientation is

   454 portrait show menu items exclude "FSQ" and FSQ is also unavailabe.

   455 

   456 */

   457 #undef FF_INPUTS_PER_ORIENTATION                          

   458 

   459 /** #FF_INTELLIGENT_TEXT_INPUT 

   460 Generic QWERTY framework and 2nd generation text input engine integration

   461 */

   462 #undef FF_INTELLIGENT_TEXT_INPUT                          

   463 

   464 /** #FF_JAVA_GLOBAL_INDICATORS_API 

   465 Enables Java Global Indicator API. Global Indicator API can be used to add

   466 indicators to phone status pane.

   467 */

   468 #undef FF_JAVA_GLOBAL_INDICATORS_API                      

   469 

   470 /** #FF_LAYOUT_360_640_NONTOUCH 

   471 New non touch NHD (=QHD) resolution. Flag determine which layout dlls are put to

   472 hw image. 

   473 */

   474 #undef FF_LAYOUT_360_640_NONTOUCH                         

   475 

   476 /** #FF_LAYOUT_360_640_TOUCH_QHD2 

   477 Layout data for QHD2_TOUCH resolution.

   478 */

   479 #undef FF_LAYOUT_360_640_TOUCH_QHD2                       

   480 

   481 /** #FF_LAYOUT_480_640_VGA3 

   482 Layout data for VGA3 resolution.

   483 */

   484 #undef FF_LAYOUT_480_640_VGA3                             

   485 

   486 /** #FF_LAYOUT_640_360_NONTOUCH 

   487 New non touch NHD (=QHD) resolution.  Flag determine which layout dlls are put

   488 to hw image.

   489 

   490 */

   491 #undef FF_LAYOUT_640_360_NONTOUCH                         

   492 

   493 /** #FF_LAYOUT_640_360_TOUCH_QHD2 

   494 Layout data for QHD2 TOUCH resolution.

   495 */

   496 #undef FF_LAYOUT_640_360_TOUCH_QHD2                       

   497 

   498 /** #FF_LAYOUT_640_480_VGA3 

   499 Layout data for VGA3 resolution.

   500 */

   501 #undef FF_LAYOUT_640_480_VGA3                             

   502 

   503 /** #FF_LBT_ENGINE 

   504 To enable/disable LBT engine from S60. By default this should be ON

   505 The Location Triggering subsystem provides a service to applications for

   506 notifications based on the user’s location. Applications can create and remove

   507 location based triggers, and applications can be notified or started when one of

   508 their triggers is fired, i.e. the triggering conditions are met

   509 Feature wiki : https://s60wiki.nokia.com/S60Wiki/Location_based_triggering

   510 REQ: 101-34742

   511 BREL : 405-1756

   512 */

   513 #define FF_LBT_ENGINE                                      

   514 

   515 /** #FF_LBT_EVENTSUI 

   516 To enable EventsUi application. Default is ON

   517 Location events  help the users to create location-based reminders. It allows

   518 the user to create a event and assign a location to it.  When you get close by

   519 to the location, it prompts you with a reminder by playing a alarm tone or

   520 displaying a text note or voice note assigned to that event.

   521 REQ : 403-1621

   522 BREl : 405-1781

   523 */

   524 #define FF_LBT_EVENTSUI                                    

   525 

   526 /** #FF_LBT_MGTUI 

   527 To enable/disable the LBT management UI. Default is On

   528 Settings for Location based trigerring subsystem.

   529 REQ : 403-1621

   530 BREl : 405-1781

   531 */

   532 #define FF_LBT_MGTUI                                       

   533 

   534 /** #FF_LINKED_FONTS_CHINESE 

   535 For enabling linked font in Chinese a new feature flag FF_LINKED_FONTS_CHINESE

   536 is needed.

   537 This flag controls whether a single Chinese font or a linked font is used in

   538 Chinese builds. The linked font will contain latin set from normal S60 latin

   539 fonts and a Chinese part which is the current Chinese font unchanged. To be used

   540 in Chinese variants only.

   541 */

   542 #undef FF_LINKED_FONTS_CHINESE                            

   543 

   544 /** #FF_MDS_CAMERA_SUPPORT 

   545 Enables camera application support for Metadata system.

   546 */

   547 #define FF_MDS_CAMERA_SUPPORT                              

   548 

   549 /** #FF_MEETING_REQUEST_UI 

   550 Meeting request UI from Custom SW will be is part of Common Email. This new flag

   551 replaces Custom SW specific flag FF_ES_MEETING_REQUEST_UI used in Freestyle. MR

   552 UI (viewer) is visible to Email application as Ecom plugin.

   553 

   554 If the flag is not defined, MR UI related components are not in ROM.

   555 */

   556 #undef FF_MEETING_REQUEST_UI                              

   557 

   558 /** #FF_MENU_TEXTURE_PRELOADING 

   559 In Menu (AppShell) application the performance of changing the folder has been

   560 poor in 5.0 (uses Hitchcock). By loading the Hitchcock textures for all the

   561 icons in advance improves the performance radically. The side effect is the

   562 increased memory consumption. This flag enables/disables the texture

   563 pre-loading.

   564 */

   565 #undef FF_MENU_TEXTURE_PRELOADING                         

   566 

   567 /** #FF_MMS_POSTCARD_INCLUDE_IN_ROM 

   568 This flags controls whether the MMS Postcard ROM files are included in the

   569 build.

   570 */

   571 #undef FF_MMS_POSTCARD_INCLUDE_IN_ROM                     

   572 

   573 /** #FF_NCD_ENGINE 

   574 This flag enables building the NCD Engine to S60 release.

   575 */

   576 #define FF_NCD_ENGINE                                      

   577 

   578 /** #FF_NCD_UI 

   579 This flag enables building the NCD UI to S60 release.

   580 */

   581 #define FF_NCD_UI                                          

   582 

   583 /** #FF_NEAR_FIELD_COMMUNICATION 

   584 A feature flag for Near Field Communication feature

   585 */

   586 #undef FF_NEAR_FIELD_COMMUNICATION                        

   587 

   588 /** #FF_NLT_SUPPORT 

   589 This enables National Language Table(NLT) support for encoding SMS messages.

   590 Characters specific to a language must be encoded using the corresponding NLT,

   591 so that the message can be sent and received using a 7-bit alphabet without any

   592 loss of information. The method is specified in 3GPP TS 23.038 v8.0.0 and TS

   593 23.040 v8.1.0. 

   594 */

   595 #undef FF_NLT_SUPPORT                                     

   596 

   597 /** #FF_NO_CUG_SUPPORT 

   598 Allow removal of CUG (Closed User Group) feature from Phone and SIM settings

   599 list (in Control Panel) in cases where CUG is not supported.

   600 */

   601 #undef FF_NO_CUG_SUPPORT                                  

   602 

   603 /** #FF_NO_IDLE_SOFTKEYS 

   604 When the flag is set, Active Idle does not have any softkeys.

   605 

   606 */

   607 #undef FF_NO_IDLE_SOFTKEYS                                

   608 

   609 /** #FF_ODE_COPYRIGHT_NOTICE 

   610 This feature adds ODE physics engine copyright info to About application. The

   611 notice is needed if any of the sw components which using this engine.

   612 Configurability is required to add the copyright information, because the notice

   613 should only displayed when required( e.g., in some products which include it ),

   614 we will decide whether displaying these copyright information by swtich on/off

   615 of this flag. 

   616 */

   617 #undef FF_ODE_COPYRIGHT_NOTICE                            

   618 

   619 /** #FF_OFN_FEATURE 

   620 OFN feature stands for Optical Finger Navigation, a feature of input devices

   621 with optical sensor. Typically phones with the OFN feature contain an optical

   622 joystick, which is an addition to normal rocker navikey user input. Optical

   623 joystick is utilized for various user input functionalities in menus, lists,

   624 browser, maps, image viewer, etc. The optical joystick can be enabled/disabled

   625 by switching the boolean flag defined/undefined. 

   626 

   627 */

   628 #undef FF_OFN_FEATURE                                     

   629 

   630 /** #FF_OMA_SCOMO_ADAPTER 

   631 This feature enables OMA SCOMO feature in "application management component".

   632 

   633 */

   634 #define FF_OMA_SCOMO_ADAPTER                               

   635 

   636 /** #FF_OOM_MONITOR2_COMPONENT 

   637 Feature flag for controlling the inclusion of Out-of-Memory2 component into the

   638 ROM image.

   639 

   640 */

   641 #undef FF_OOM_MONITOR2_COMPONENT                          

   642 

   643 /** #FF_OSS_LEGAL_NOTICE 

   644 This feature adds OSS legal notice to About application. The notice is needed if

   645 any of the sw components, e.g. WRT widgets include any Open Source components. 

   646 

   647 Configurability is required to add the legal notice, because the notice should

   648 only displayed when required( e.g., in some products ), we will decide whether

   649 displaying these information by swtich on/off of this flag.

   650 

   651  

   652 

   653 */

   654 #undef FF_OSS_LEGAL_NOTICE                                

   655 

   656 /** #FF_PLATFORM_SIMULATOR 

   657 Platform Simulator product makes it possible to execute software on simulated

   658 target hardware using a Windows or Linux workstation. Platform Simulator is

   659 based on ARM® RealView® tools that support modeling terminal hardware using LISA

   660 language. Platform Simulator runs any OS e.g. S60 or Linux. The OS is introduced

   661 to the simulator as a core image loaded into the simulated flash memory. 

   662 

   663 Compared to WINS emulator Platform Simulator based S60 simulation is much closer

   664 to exeuction on real hardware. Yet there has to be some differences in the S60

   665 core image. Thus the need for FF_PLATFORM_SIMULATOR flag. The flag  controls S60

   666 PPD release based core image creation for two alternate targets: 

   667  - FLAG DEFINED = compilation shall include components and configurations for

   668 simulated hardware

   669  - FLAG UNDEFINED = compilation shall include components and configurations for

   670 real hardware

   671  

   672 The NCP_COMMON_PLATFORM_SIMULATOR flag has strict dependency to the

   673 FF_PLATFORM_SIMULATOR flag.

   674 

   675 Platform Simulator pilot 1 release models PP71 hardware i.e. a plain RAPU 1.1

   676 configuration. In the future the Platform Simulator targets to support selected

   677 new reference hardware configurations. This makes the flag lifetime permanent.

   678 */

   679 #undef FF_PLATFORM_SIMULATOR                              

   680 

   681 /** #FF_PNPMS_PROV_FILTER 

   682 On enabling this feature flag pnpprovfilter.dll will be created and this feature

   683 flag is used to enable PNPProvisioning HTTP filter which by passes the download

   684 manager launching PNPMS provisioning engine.

   685 */

   686 #undef FF_PNPMS_PROV_FILTER                               

   687 

   688 /** #FF_PNPMS_SERVICE_HELP_PLUGIN 

   689 This feature flag is required for launching PNPMS application from general

   690 settings/Control Panel. On enabling this feature flag servicehelpplugin.dll will

   691 be created and when this feature is enabled Service Help Icon will be present in

   692 General Settings/Control Panel. Service Help will launch browser on selection

   693 and direct the browser with predefined PnPMS server URL where user can download

   694 provisioning settings over HTTP from web server.

   695 */

   696 #undef FF_PNPMS_SERVICE_HELP_PLUGIN                       

   697 

   698 /** #FF_POWER_SAVE 

   699 "Power save mode is a collection of features which are put in a power saving

   700 mode. These features are i.e. display light brightness, light time outs etc.

   701 Power save mode can be extended to be supported by any application which can do

   702 something to save battery by implementing the needed power save mode APIs."

   703 */

   704 #define FF_POWER_SAVE                                      

   705 

   706 /** #FF_PREMINET_CATALOGS_CLIENT 

   707 Preminet Catalogs client.

   708 */

   709 #undef FF_PREMINET_CATALOGS_CLIENT                        

   710 

   711 /** #FF_PROV_AUTHTYPE_PLUGIN 

   712 This flag enables Authentication type plugin. On enabling this feature flag

   713 Authtypeplugin.dll will be created and this feature will be enabled and

   714 authetication type can be changed for configuration message from UI which will

   715 enable item in General Settings and on selection of this item will open list

   716 dialog for changing the authentication type.

   717 */

   718 #undef FF_PROV_AUTHTYPE_PLUGIN                            

   719 

   720 /** #FF_QWERTY_FN_KEY 

   721 The device has a Fn key

   722 */

   723 #undef FF_QWERTY_FN_KEY                                   

   724 

   725 /** #FF_RND_COMMSDAT 

   726 The override flags FF_EMPTY_COMMSDAT, FF_VANILLA_COMMSDAT and FF_RND_COMMSDAT

   727 determine which default CommsDat will be put to the image independent of image

   728 type (prd or rnd):

   729 

   730 - FF_EMPTY_COMMSDAT: Completely empty CommsDat is used. Typically needed as the

   731 base when creating operator variants with Configuration Tool and

   732 CommsDatCreator. Same as old FF_COMMSDAT_GENERATION_FROM_XML.

   733 

   734 - FF_VANILLA_COMMSDAT: Otherwise empty CommsDat but the S60 default destinations

   735 (Internet, MMS and Operator) as well as the Easy WLAN IAP (in case of WLAN

   736 product) is included. This is suitable for vanilla variants of the phones.

   737 

   738 - FF_RND_COMMSDAT: Platform releases contain typically the RND CommsDat that has

   739 Nokia Test Network IAPs as well as some Finnish operator IAPs (DNA, Sonera,

   740 Elisa) for RnD purposes.

   741 

   742 Maximum of one of these flags should be defined at the time. 

   743 

   744 If none of the override flags is defined then the used CommsDat depends on the

   745 image type: vanilla CommsDat is used for PRD image and RnD CommsDat for the RnD

   746 image. This is typically how it should be and the override flags should only be

   747 used if some special functionality is needed.

   748 

   749 */

   750 #undef FF_RND_COMMSDAT                                    

   751 

   752 /** #FF_ROCKER_KEY 

   753 The device has multidirectional "rocker" key.

   754 

   755 */

   756 #define FF_ROCKER_KEY                                      

   757 

   758 /** #FF_ROM_INCLUDE_ALF 

   759 This flags controls whether the UI Accelerator toolkit (ALF) is included in the

   760 build.

   761 */

   762 #define FF_ROM_INCLUDE_ALF                                 

   763 

   764 /** #FF_RUNTIME_DEVICE_CAPABILITY_CONFIGURATION 

   765 To enable the feature to variate the device capability on runtime

   766 */

   767 #define FF_RUNTIME_DEVICE_CAPABILITY_CONFIGURATION         

   768 

   769 /** #FF_S60_HELPS_IN_USE 

   770 Platform helps are included into image based on this flag.

   771 */

   772 #undef FF_S60_HELPS_IN_USE                                

   773 

   774 /** #FF_S60_POSTING_IMPLEMENTATION_IN_USE 

   775 Flag to enable/disable usage of S60 implementation of posting surface api.

   776 Default value for this is disabled.

   777 */

   778 #undef FF_S60_POSTING_IMPLEMENTATION_IN_USE               

   779 

   780 /** #FF_SELECTABLE_EMAIL 

   781 This enables selectable default email. When write message->email is selected

   782 from sendui (with multible mailboxes), the default email account is the initial

   783 selection. Default mailbox can be set from mce-settings.

   784 */

   785 #define FF_SELECTABLE_EMAIL                                

   786 

   787 /** #FF_SENSOR_FW 

   788 FF_SENSOR_FW flag is used for image creation time variation of the sensor

   789 framework. 

   790 Flag should be defined for products that have sensors and undefined for products

   791 that do not.

   792 */

   793 #define FF_SENSOR_FW                                       

   794 

   795 /** #FF_SHOW_MMPLAYER 

   796 By default S60 Media Player will be hidden from UI, and  only be accessible

   797 through embedded playback use cases (e.g browser, messaging, file browser, etc).

   798 

   799 This flag will will allow product manufacturers to re-enable Media Player and

   800 display it in the application shell if desired.  

   801 

   802 */

   803 #undef FF_SHOW_MMPLAYER                                   

   804 

   805 /** #FF_STARTUP_OMA_DM_SUPPORT 

   806 The flag will be used to enable receiving OMA CP/DM messages during system

   807 start-up in those devices that need the feature.

   808 */

   809 #undef FF_STARTUP_OMA_DM_SUPPORT                          

   810 

   811 /** #FF_TACTICONS 

   812 Tacticons are haptic effects that can be played by the applications to indicate

   813 success or failure of actions. Tacticons can be also automatically played

   814 together with some Sound IDs.

   815 

   816 */

   817 #define FF_TACTICONS                                       

   818 

   819 /** #FF_TACTILE_FEEDBACK 

   820 Device supports Tactile Feedback. Tactile feedback is produced by UI components

   821 and applications on pointer down events. Actual physical feedback effect

   822 (vibra/audio/no feedback) depends on current settings and device configuration.

   823 */

   824 #define FF_TACTILE_FEEDBACK                                

   825 

   826 /** #FF_TARM_CAPABILITY_BASED_ACCESS 

   827 This is the feature flag to allow branching of the code flow based on the

   828 capability check or SID check for the third party applications.

   829 */

   830 #define FF_TARM_CAPABILITY_BASED_ACCESS                    

   831 

   832 /** #FF_TCP_MYFAVES_FEATURE 

   833 The feature flag is to turn ON/OFF MyFaves feature in a S60 3.2 complementary

   834 package.

   835 */

   836 #undef FF_TCP_MYFAVES_FEATURE                             

   837 

   838 /** #FF_TCP_MYPROFILE 

   839 This feature flag is for enabling/disabling MyProfile feature in T-Mobile

   840 Complementary package(both International & US)on S60 3.2.3. This feature flag is

   841 valid for MyProfile UI & MyProfile synchronization.

   842 */

   843 #undef FF_TCP_MYPROFILE                                   

   844 

   845 /** #FF_THEME_HAZE 

   846 Haze theme is included in ROM image.

   847 

   848 */

   849 #define FF_THEME_HAZE                                      

   850 

   851 /** #FF_THEME_JINGMASK 

   852 Jingmask theme is included in ROM image.

   853 

   854 */

   855 #define FF_THEME_JINGMASK                                  

   856 

   857 /** #FF_TOUCHSCREENCALIB_IN_STARTUP 

   858 Touch Calibration UI is initiated at device startup.

   859 

   860 */

   861 #undef FF_TOUCHSCREENCALIB_IN_STARTUP                     

   862 

   863 /** #FF_TOUCH_UNLOCK_STROKE 

   864 This flag enables user to response (for example answer) and unlock screen

   865 through sliders (software controls) to mobile terminated calls. This applies

   866 only to touch devices.

   867 */

   868 #undef FF_TOUCH_UNLOCK_STROKE                             

   869 

   870 /** #FF_UPNP_FRAMEWORK_2_0 

   871 Defines whether UPNP application is supported in the platform through

   872 MusicPlayer.

   873 */

   874 #undef FF_UPNP_FRAMEWORK_2_0                              

   875 

   876 /** #FF_USB_CHARGING 

   877 If it is defined, the Starter starts the UsbWatcher.exe in charging mode. 

   878 The USB Watcher or USB MSC Personality Plug-in code is not variated. 

   879 Note. This flag replaces RD_USB_CHARGING in 5.0 release.

   880 */

   881 #define FF_USB_CHARGING                                    

   882 

   883 /** #FF_USB_HOST 

   884 The flag excludes all S60 USB host and OTG related components. 

   885 */

   886 #define FF_USB_HOST                                        

   887 

   888 /** #FF_USE_EGPRS_ICON 

   889 The flag is used to enable EGPRS icon in the status pane. If the flag is

   890 disabled, GPRS icon must be shown instead of EGPRS icon.

   891 

   892 */

   893 #undef FF_USE_EGPRS_ICON                                  

   894 

   895 /** #FF_USE_MASS_STORAGE_CONFIG 

   896 Flag is used for products to select in image creation time if mass storage drive

   897 configuration is used or not. The mass storage drive configuration is following:

   898 C=Phone memory, E=Internal mass storage and F=Memory card.

   899 

   900 The flag affects how S60 components see the drives setup from estart

   901 txt-file(s).

   902 */

   903 #define FF_USE_MASS_STORAGE_CONFIG                         

   904 

   905 /** #FF_USE_ZI_ENGINE 

   906 On enabling this feature flag eZitext engine will be part of the Image and

   907 Ptiengine will utilize eZitext engine for editing features.

   908 */

   909 #undef FF_USE_ZI_ENGINE                                   

   910 

   911 /** #FF_VANILLA_COMMSDAT 

   912 The override flags FF_EMPTY_COMMSDAT, FF_VANILLA_COMMSDAT and FF_RND_COMMSDAT

   913 determine which default CommsDat will be put to the image independent of image

   914 type (prd or rnd):

   915 

   916 - FF_EMPTY_COMMSDAT: Completely empty CommsDat is used. Typically needed as the

   917 base when creating operator variants with Configuration Tool and

   918 CommsDatCreator. Same as old FF_COMMSDAT_GENERATION_FROM_XML.

   919 

   920 - FF_VANILLA_COMMSDAT: Otherwise empty CommsDat but the S60 default destinations

   921 (Internet, MMS and Operator) as well as the Easy WLAN IAP (in case of WLAN

   922 product) is included. This is suitable for vanilla variants of the phones.

   923 

   924 - FF_RND_COMMSDAT: Platform releases contain typically the RND CommsDat that has

   925 Nokia Test Network IAPs as well as some Finnish operator IAPs (DNA, Sonera,

   926 Elisa) for RnD purposes.

   927 

   928 Maximum of one of these flags should be defined at the time. 

   929 

   930 If none of the override flags is defined then the used CommsDat depends on the

   931 image type: vanilla CommsDat is used for PRD image and RnD CommsDat for the RnD

   932 image. This is typically how it should be and the override flags should only be

   933 used if some special functionality is needed.

   934 

   935 */

   936 #undef FF_VANILLA_COMMSDAT                                

   937 

   938 /** #FF_VIRTUAL_FULLSCR_QWERTY_INPUT 

   939 Indicates whether a device needs Virtual full-screen qwerty input or not.

   940 

   941 */

   942 #define FF_VIRTUAL_FULLSCR_QWERTY_INPUT                    

   943 

   944 /** #FF_VIRTUAL_ITUT_INPUT 

   945 Indicates whether a device needs virtual ITUT input or not.

   946 */

   947 #define FF_VIRTUAL_ITUT_INPUT                              

   948 

   949 /** #FF_VMBX_CALL_DIVERT_ICON 

   950 Feature flag controls whether or not a special icon is shown in status pane,

   951 when call divert is set against voice mailbox number. 

   952 

   953 */

   954 #undef FF_VMBX_CALL_DIVERT_ICON                           

   955 

   956 /** #FF_VOICE_CALL_CONTINUITY 

   957 With Voice Call Continuity it is possible to provide seamless user experience

   958 when user in transition between VoIP and cellular networks. This feature brings

   959 a method to seamlessly continue	ongoing voice call from VoIP to cellular and

   960 vice versa. VCC handover logic shall be implemments as installable plugin (SIS)

   961 in order to allow possibility to support several VCC signalling variations.

   962 However VCC needed some platform changes to be fully functional (mainly at

   963 telephony components) and those changes must be run time variable.

   964 */

   965 #define FF_VOICE_CALL_CONTINUITY                           

   966 

   967 /** #FF_VPN_CLIENT 

   968 Feature flag is needed to manage whether VpnClient components are in ROM or not.

   969 */

   970 #undef FF_VPN_CLIENT                                      

   971 

   972 /** #FF_WEBVIDEO_PH2 

   973 When enabled/defined, WEBVIDEO for ph2 is used. This will use Helix XPS

   974 interface for video decoding and postprocessing.

   975 */

   976 #undef FF_WEBVIDEO_PH2                                    

   977 

   978 /** #FF_WLANSNIFFER 

   979 The purpose of the flag is to control whether the WlanSniffer2 application is to

   980 be integrated into 3.2 product builds or not.

   981 */

   982 #undef FF_WLANSNIFFER                                     

   983 

   984 /** #FF_WLANSNIFFER_VOIP_ENHANCEMENTS 

   985 The WLAN Sniffer VoIP enhancements will provide easy way to connect to VoIP

   986 service via Sniffer's Active Idle plugin.

   987 */

   988 #undef FF_WLANSNIFFER_VOIP_ENHANCEMENTS                   

   989 

   990 /** #FF_WLAN_EXTENSIONS 

   991 Device supports extended WLAN functionalities e.g. for association and

   992 authentication.

   993 NB. The code associated with this Feature flag as not been contributed to Symbian.

   994 */

   995 #undef FF_WLAN_EXTENSIONS                                 

   996 

   997 /** #FF_WLAN_WAPI 

   998  WLAN Authentication and Privacy Infrastructure (WAPI) is a Chinese national

   999 standard for WLAN security. Although WAPI was designed to operate on top of the

  1000 IEEE 802.11 WLAN technologies, it is not compatible with the security schemes

  1001 defined in IEEE 802.11 specifications. It specifies its own methods for WLAN

  1002 authentication and data link protection.

  1003 */

  1004 #undef FF_WLAN_WAPI                                       

  1005 

  1006 /** #FF_WLAN_WAPI_INCLUDE_IN_ROM 

  1007 WLAN Authentication and Privacy Infrastructure (WAPI) is a Chinese national

  1008 standard for WLAN security. Although WAPI was designed to operate on top of the

  1009 IEEE 802.11 WLAN technologies, it is not compatible with the security schemes

  1010 defined in IEEE 802.11 specifications. It specifies its own methods for WLAN

  1011 authentication and data link protection.

  1012 

  1013 This feature flag is used only for including WAPI binaries to ROM. WAPI

  1014 functionality can be (run-time) enabled with FF_WLAN_WAPI.

  1015 */

  1016 #define FF_WLAN_WAPI_INCLUDE_IN_ROM                        

  1017 

  1018 /** #FF_XML_IDLE_THEME_BASIC_IDLE 

  1019 Controls if Basic idle theme is going to image or not.

  1020 */

  1021 #define FF_XML_IDLE_THEME_BASIC_IDLE                       

  1022 

  1023 /** #FF_XML_IDLE_THEME_CLASSIC_IDLE 

  1024 Controls if Classic idle theme is going to image or not.

  1025 */

  1026 #define FF_XML_IDLE_THEME_CLASSIC_IDLE                     

  1027 

  1028 /** #FF_XML_IDLE_THEME_FINGERUSE_IDLE 

  1029 Controls if Finger use idle theme goes to image or not.

  1030 */

  1031 #define FF_XML_IDLE_THEME_FINGERUSE_IDLE                   

  1032 

  1033 /** #FF_XML_IDLE_THEME_NAVIBAR_IDLE 

  1034 Controls if Navibar idle theme is going to image or not.

  1035 */

  1036 #define FF_XML_IDLE_THEME_NAVIBAR_IDLE                     

  1037 

  1038 /** #LANGPACK_DEFAULTLANG 

  1039 The default language that is selected during bootup (this selection is

  1040 overridden by the sim language selection). 

  1041 */

  1042 #define LANGPACK_DEFAULTLANG                               

  1043 

  1044 /** #LANGUAGE_ARABIC 

  1045 included Arabic

  1046 */

  1047 #define LANGUAGE_ARABIC                                    

  1048 

  1049 /** #LANGUAGE_BASQUE 

  1050 included Basque

  1051 */

  1052 #define LANGUAGE_BASQUE                                    

  1053 

  1054 /** #LANGUAGE_BULGARIAN 

  1055 included Bulgarian

  1056 */

  1057 #define LANGUAGE_BULGARIAN                                 

  1058 

  1059 /** #LANGUAGE_CATALAN 

  1060 included Catalan

  1061 */

  1062 #define LANGUAGE_CATALAN                                   

  1063 

  1064 /** #LANGUAGE_CROATIAN 

  1065 included Croatian

  1066 */

  1067 #define LANGUAGE_CROATIAN                                  

  1068 

  1069 /** #LANGUAGE_CZECH 

  1070 included Czech

  1071 */

  1072 #define LANGUAGE_CZECH                                     

  1073 

  1074 /** #LANGUAGE_DANISH 

  1075 included Danish

  1076 */

  1077 #define LANGUAGE_DANISH                                    

  1078 

  1079 /** #LANGUAGE_DUTCH 

  1080 included Dutch

  1081 */

  1082 #define LANGUAGE_DUTCH                                     

  1083 

  1084 /** #LANGUAGE_ENGLISH 

  1085 included English

  1086 */

  1087 #define LANGUAGE_ENGLISH                                   

  1088 

  1089 /** #LANGUAGE_ENGLISH_AMERICAN 

  1090 included English_American

  1091 */

  1092 #define LANGUAGE_ENGLISH_AMERICAN                          

  1093 

  1094 /** #LANGUAGE_ENGLISH_APAC 

  1095 included English_APAC

  1096 */

  1097 #define LANGUAGE_ENGLISH_APAC                              

  1098 

  1099 /** #LANGUAGE_ENGLISH_HONGKONG 

  1100 included English_Hongkong

  1101 */

  1102 #define LANGUAGE_ENGLISH_HONGKONG                          

  1103 

  1104 /** #LANGUAGE_ENGLISH_JAPANESE 

  1105 included English_Japanese

  1106 */

  1107 #define LANGUAGE_ENGLISH_JAPANESE                          

  1108 

  1109 /** #LANGUAGE_ENGLISH_PRCCHINA 

  1110 included English_PrcChina

  1111 */

  1112 #define LANGUAGE_ENGLISH_PRCCHINA                          

  1113 

  1114 /** #LANGUAGE_ENGLISH_TAIWAN 

  1115 included English_Taiwan

  1116 */

  1117 #define LANGUAGE_ENGLISH_TAIWAN                            

  1118 

  1119 /** #LANGUAGE_ENGLISH_THAI 

  1120 included English_Thai

  1121 */

  1122 #define LANGUAGE_ENGLISH_THAI                              

  1123 

  1124 /** #LANGUAGE_ESTONIAN 

  1125 included Estonian

  1126 */

  1127 #define LANGUAGE_ESTONIAN                                  

  1128 

  1129 /** #LANGUAGE_FARSI 

  1130 included Farsi

  1131 */

  1132 #define LANGUAGE_FARSI                                     

  1133 

  1134 /** #LANGUAGE_FINNISH