Report design

Some of the issues discussed in the Application design section of this chapter directly affect the layout and functionality of reports in your application. These issues may be more immediately relevant if you’re in the process of preparing your application for an international market. However, keeping these topics in mind as you begin designing your application will help make future localization easier.

There are six aspects of report layouts that are likely to be different from one locale to another.

Allowing extra space for translated text

Translation of English to other languages typically increases the length of the text by thirty to fifty percent. You can allow for this expansion by making the columns for your data wider than required for English text.

The actual space required for translated text depends largely upon the target language, so your individual requirements may vary.


Rearranging fields on a report

Some report fields may need to be repositioned to accommodate local standards for reporting.

Adjusting for different standard paper sizes

The standard Dexterity Report Writer text report layouts work best with 8.5 x 11-inch (216 x 279 mm) paper. If you’re planning to market your application in a locale that uses A4 (210 x 297mm) paper instead, you may need to adjust the locations of fields on the report to ensure that they’re printed correctly.

You also can adjust the report layout by marking the Best Text Fit option in the Dexterity Report Definition window. Reports will take longer to print if this option is marked, so it’s better to rearrange the layout so the report can be printed in normal text mode.

When you display graphics report layouts, guides will indicate the correct margins for the currently-selected printer and page size. You can use these guides to reposition fields on the report. Be aware that a graphics report created according to the specifications for a particular printer may not be printed correctly when using a different printer. It’s best to create graphics reports only when you can be sure of the type of printer that will be used to print the report.

Verifying calculated fields and restrictions

If you’ve created calculated fields or restrictions based upon the value of a string or message, be sure to translate any necessary text in the calculated expressions and restriction expressions. Be sure to verify that your calculated fields and restrictions still work after you’ve completed the translation process.

Using graphics

As with graphic elements used in windows, be aware that some images may be offensive or inappropriate in certain cultures or contexts.


Documentation Feedback