Skip to main content

Rigi Documentation

Excel and CSV parser – one file per target language (mono)
  • Parser ID: Excel_mono.

  • Use cases: One Excel file is available for each target language. The Excel file can contain the source language, but that is not required.

  • Key features:

    • Compose string ID based on multiple columns and postfix.

    • Detect column for target language based on patterns.

    • Overwrite source texts, or write target to another column.

    • Select comments for each source string.

    • CSV and Excel support.

  • Parser settings. For details, see the Excel parser settings section.

Examples

All examples use one Excel file with a file ID sample.

Example 6. One column with texts

Source file

1.png

Settings

Table 5.

Parameter

Argument

Header row

1

First row with data

2

String ID columns

A

String ID postfixes

Source columns

B

Target columns

B

Comment columns

C

Fallback columns


Resulting IDs

sample.key1
sample.key2
sample.key3

Target file

2.png


Example 7. Target texts are in another column

Similar to example 1, but now the translations must be written to another column.

Source file

3.png

Settings

Table 6.

Parameter

Argument

Header row

1

First row with data

2

String ID columns

A

String ID postfixes

Source columns

B

Target columns

C

Comment columns

D

Fallback columns


Resulting IDs

sample.key1
sample.key2
sample.key3

Target file

4.png


Example 8. Two columns with source texts

In this example, the source file has 2 columns with translatable source texts. Targets must be written to the same columns.

The comment in column D must apply to both the name and the tooltip.

Source file

5.png

Settings

Table 7.

Parameter

Argument

Header row

1

First row with data

2

String ID columns

A

String ID postfixes

name

tooltip

Source columns

B

C

Target columns

B

C

Comment columns

D

-

Fallback columns


Resulting IDs

sample.key1.name
sample.key1.tooltip
sample.key2.name
sample.key2.tooltip
sample.key3.name
sample.key3.tooltip

Target file

6.png


Example 9. Multiple columns with IDs (and hash)

In this example, the unique ID can be composed by combining columns A (Screen) and the source text (B). The source text can contain characters that are invalid for string IDs. In this case, the source can be hashed.

Source file

7.png

Settings

Table 8.

Parameter

Argument

Header row

1

First row with data

2

String ID columns

A

B hash

String ID postfixes

Source columns

B

Target columns

C

Comment columns

D

Fallback columns


Resulting IDs

sample.menu.8cf04a9734132302f96da8e113e80ce5
sample.menu.cce99c598cfdb9773ab041d54c3d973a
sample.main.f4f70727dc34561dfde1a3c529b6205c
sample.main.8cf04a9734132302f96da8e113e80ce5

Target file

8.png