Textual Components

All textual components are optional. If you do not provide them, Information Builders will use the default values shown in the following table. Most of these textual components have obvious branding on them. If you do not provide them, your resulting app will bear Information Builders branding.

Component	What It Is	File Name	Format
Application "About us" content	A view-ready HTML file that describes your company and the app. The page that you provide is also auto-stamped with the app version information and build date.	`ll`_about_us.htm where: `ll` Is the corresponding ISO language code for each language that you want to support. For a list of ISO codes for languages, see http://www.loc.gov/standards/iso639-2/php/code_list.php. For example, es_about_us.htm would be used for a Spanish file.	HTML
Privacy notice	A view-ready HTML file that provides the standard legal privacy policy for your company. Refer to the sample used in the Information Builders Mobile Faves app for current guidelines.	`ll`_Privacypolicy.htm where: `ll` Is the corresponding ISO language code for each language that you want to support. For a list of ISO codes for languages, see http://www.loc.gov/standards /iso639-2/php/code_list.php. For example, es_about_us.htm would be used for a Spanish file.	HTML

Component

What It Is

File Name

Format

Application "About us" content

A view-ready HTML file that describes your company and the app. The page that you provide is also auto-stamped with the app version information and build date.

ll_about_us.htm

where:

ll: Is the corresponding ISO language code for each language that you want to support. For a list of ISO codes for languages, see http://www.loc.gov/standards/iso639-2/php/code_list.php. For example, es_about_us.htm would be used for a Spanish file.

HTML

Privacy notice

A view-ready HTML file that provides the standard legal privacy policy for your company. Refer to the sample used in the Information Builders Mobile Faves app for current guidelines.

ll_Privacypolicy.htm

where:

ll: Is the corresponding ISO language code for each language that you want to support. For a list of ISO codes for languages, see http://www.loc.gov/standards /iso639-2/php/code_list.php. For example, es_about_us.htm would be used for a Spanish file.

HTML

Note:

To supply content in multiple languages, you need to provide separate versions of the preceding files, named using the patterns above, where the file title string ll in the previous table is replaced by the ISO language code for each language that you want to support. For a list of ISO codes for languages, see http://www.loc.gov/standards/iso639-2/php/code_list.php. The common languages delivered with Mobile Faves are:
- English/en
- Spanish/es
- German/de
- French/fr
- Simplified Chinese/zh
- Japanese/jp
For any view-ready HTML content that you provide, you cannot provide external Cascading Style Sheet (CSS) or other graphical components for use with these files. You can use inline CSS and inline base-64 encoded bitmap graphics (for example, you can use binary-encoded graphics inside the file itself). You can use the IMG element and set the data attribute as follows:
```
<IMG src="data:image/gif;base64,[insert
base-64 data for embedded base64 version of your image]" >
```
For your convenience, Adobe® Illustrator® (EPS) and Adobe Photoshop® (PSD) file versions of all PNG files mentioned previously are included in the Branding Kit for your art department to use as design templates. The output format for these files must be PNG, and must follow the specifications in the Mobile Faves Customer-Branded Versions documentation.
It is not necessary to return edited versions of these files.

	WebFOCUS