The parameter --input-language determines the country setting for the switch “numeric format” (\#)("numerisches Format”).

Syntax

--input-language=<Sprache>
<Sprache>: englisch/english oder german/deutsch

Description

Currently there are the valid values “English“/“englisch“ and “German“/“deutsch“. Default is ”German“. If the value is set to “German”, CIB merge interprets dots in the number format specification as an instruction to structure the number to be output with 1000 dots or with substitute characters of the set output language. Commas are interpreted as subdivisions between places before and after the decimal point. The character that matches the set output language is also output here. If the value is set to "English", dots and commas are interpreted in reverse. Nevertheless, the output is still in the output language.

The numbers must be specified in German in the CSV file. They are written in {=...} fields only understanding them in German. Likewise, the parser of the switch \# expects that the field result contains the number in German before using the switch.

Examples

• English RTF with English formatting

--input-language=english

The cover letter is written in English and therefore the specification of the number format. This fact is specified using the parameter --input-language.

This is demonstrated in the use case example Gap Text.

• Calculation examples

--input-language=german

There is the following statement in an RTF document:

{=1234 + 1 \# #.####0,00€}

Result: 1.235,00€

The instruction

{=12,34 + 1 \# #.####0,00€}

delivers the result: 13,34€

 

--input-language=english

There is the following statement in an RTF document:

{=1234 + 1 \# #,####0.00€}

Result: 1.235,00€

The instruction

{=12,34 + 1 \# #,####0.00€}

delivers the result: 1.334,00€

The reason for the different result from the German is the interpretation of the separators in English:

Thousands separator comma and decimal point