Modify the Language Configuration Files

You configure the period names and formats as desired in each language configuration file (periods_<language>.conf).

You must use the long and short period names provided to support retail calendars (listed under the comments indicating that they are imported). For English, these period names are as follows:



Do not use long and short month names LONG_NAME_MONTH_1 through LONG_NAME_MONTH_12 or SHORT_NAME_MONTH_1 through SHORT_NAME_MONTH_12. Keep this requirement in mind as you revise each language configuration file.

If, for example, the fiscal years you want to generate for your retail calendar have up to thirteen periods, you must add and specify LONG_NAME_PERIOD_13 and SHORT_NAME_PERIOD_13. If, on the other hand, the fiscal years you want to generate for your retail calendar have no more than eleven periods, delete LONG_NAME_PERIOD_12 and SHORT_NAME_PERIOD_12.

When you use the default calendar year format {cccc} for period names, the year displayed on the right of the period depends on the calendar year in which the eighth day of the period falls. For example, consider a period from December 26, 2008 to January 22, 2009. Because January is the month in which this period's eighth day falls and January is in calendar year 2009, the period name in this example is displayed as January 2009.

If you rename the periods such that they are not named for months, for example if you specify the short names for periods as Per 1: through Per 12:, you might want the period formats to include fiscal years—format {yyyy}—instead of calendar years. For example, if you specify the period format to include fiscal years and if fiscal year 2009 starts on November 3, 2008, then the period that starts on November 3, 2008 would be shown as Per 1: 2009, reflecting the fiscal year, rather than Per 1: 2008.

To configure period names and formats, see Changing Names of Months and Changing Formats of Periods.