Page tree

This page has not yet been translated to English.

Skip to end of metadata
Go to start of metadata

Exporting localizable game data to a specified file.

Example:

Charon.exe DATA I18N EXPORT --dataBase "c:\my app\gamedata.json" --entities Character --sourceLanguage en --targetLanguage fr --output "c:\my app\character_loc.xliff" --outputFormat xliff

Command parameters

ParameterTypeRequiredDescriptionExample
dataBase

string

yes

Path to game data file. Use quotation marks if your path contains spaces.

"c:\my app\gamedata.json"
/User/Data/gamedata.json
entities

list of strings

no

A list of entities to export. Documents are selected from the root list of entities. Embedded documents will be included in export. You can prevent that by removing attributes with Document & Document list types.

  • You can use wildcards (*) in the beginning and in the end of names.
  • You can use identifier in { } instead of entity name.
  • You can exclude certain names by using exclamaiton mark (!).

Default: all entities.

Character
Char*
*Modifier
*Mod*
{18d4bf318f3c49688087dbed}
Char* !Character
!*Item*

sourceLanguage

Language tag
(BCP 47)

yes

Source (original) language for localization.

en-US

targetLanguage

Language tag
(BCP 47)

yes

Target language for localization.

es-ES

output

file, err, null, out, url

no

Path to a file to which data will be exported. If the file exists, it will be overwritten. The directory must already exist. Alternatively, you can use output to Standart Error, Standart Output, dev/null & URL.
Default: out.

"c:\my app\output.xliff"
/User/Data/output.xliff
http://example.com/output.xliff
outputFormat

xliff, xliff1, xliff2

no

Format to use when saving game data. See Supported data formats for more information.

Default: xliff2


outputFormattingOptions

string

no

Additional formatting parameters. Depend on selected data format.


Related pages