Reports

Configuring reports

Keys are required and must not be removed or changed. Keys map a string to a location in the report, and are the same in each language file. If you change or remove keys, the FortiAnalyzer unit cannot associate your string with a location in the report, string file validation will fail, and the string file upload will not succeed.

String values may be changed to customize report text. If your custom string values use a different encoding or character set than the default language file, customize your format file to reflect your new character set and/or encoding.

Comment lines are optional; you can add them throughout the file to provide notes on your work.

The format file contains settings for the file format renderers, including encodings. The format file contains sections that are preceded by an output type label, consisting of the file format name followed by a colon character (:). Within each output type’s section, one or more settings exist, consisting of a variable name followed by an equal symbol (=) and its value, contained by quote characters (“). You can add comments to the format file by preceding them with a number symbol

(#).

For example, in these lines:

#Localization uses a Latin character set. html:

html_charset="iso-8859-1"

The comment is:

# Localization uses a Latin character set.

The output type label is html:, the variable name is html_charset, and the variable’s value is iso-8859-1.

Variables are required and must not be removed or changed. If you change or remove variables, the FortiAnalyzer unit may not be able to properly format your reports.

If your custom string values use a different encoding or character set than the default language file, you must customize your format file to reflect your new character set and/or encoding. If your string file requires double-byte encoding, also set doublebytes="1". Otherwise, set doublebytes="0". The variable’s value must be in a pattern acceptable by the output type. If variable value syntax is not correct, format file validation will fail, and the format file upload will not succeed.

Supported encodings used by the string file and referenced in the format file include those specified by the PDF, RTF, and HTML standards. For character set and encoding syntax and other specifications, see:

W3C HTML 4.01 Specification

Adobe PDF Reference

Microsoft Word 2003 Rich Text Format (RTF) Specification, version 1.8

Comment lines are optional; you can add them throughout the file to provide notes on your work.

If you require further format file customization, including adjustments to PDF objects, contact Fortinet Technical Support.

FortiAnalyzer Version 3.0 MR7 Administration Guide

 

05-30007-0082-20080908

129

Page 133
Image 133
Fortinet 3.0 MR7 manual Comment is, # Localization uses a Latin character set, 129