Next: Coding Scheme, Previous: Obsolete Special Texts, Up: Top [Contents][Index]
Gcal 4.1 is able to represent text variables, special texts and date formats especially in a very comfortable and uniform manner by using a format instruction.
Here comes the description of the format instruction components, now called format in the further context. In general, the template of a format instruction is:
alignment [sign] [zero] width [style] [suffix] format
If a format of above mentioned template is used, its components must be specified in the above mentioned order, at which the definition of the components embraced by ‘[ ]’ is of course optional. The single components of the format instruction are assembled as follows:
< Field contents is placed at the left margin of the field
by using the width width: Field contents is placed in centered manner in the field
by using the width width> Field contents is placed at the right margin of the field
by using the width width+ Numerical value is provided with leading sign0 Numerical value is filled with leading zero(es)u Field contents is converted to upper-case lettersl Field contents is converted to lower-case lettersw Field contents is converted to capitalized words& Numerical value is provided with an Ordinal Number suffix* Field contents is not cut after position width# Field contents is cut after position widthIf a given width component is greater 256 but less than 999, a field width of 256 is assumed. But if a given width component is zero, this interrupts the interpretation phase of Gcal so that the complete format is not interpreted anymore and is therefore displayed respectively assigned as is. The same happens if a component is misspelled, given in wrong order, or one of the required components is unspecified.
Furthermore, a style component may be specified case-independently. See Calendar option --translate-string=text, for further annotations how the style component is used correctly.
Next: Coding Scheme, Previous: Obsolete Special Texts, Up: Top [Contents][Index]