Efter upload af CSV- eller XLSX-filer til projektet, kræver de yderligere opsætning, før systemet kan importere filindholdet.
Følg disse trin for at opsætte CSV- og XLSX-filer:
De samme opsætninger, som nævnt i denne artikel, gælder også for TSV-filformatet. Den væsentligste forskel mellem CSV- og TSV -iler er, at de bruger forskellige kolonneafgrænsere (dvs. komma i CSV og Tab i TSV).
Ved opsætning af XLSX-filer, findes flg. muligheder:
Importér alle celler - importér hver celle som en separat kildestreng. Derudover kan Indholdssegmentering bruges til opdeling af kildefilens indhold i kortere tekststykker, typisk sætninger og korte afsnit. Dette er nyttigt under oversættelse af indholdsenheder bestående af flere sætninger, da det er lettere at oversætte mindre tekststykker. Segmenteringsregler eXchange (SRX) bruges til automatisk indholdssegmentering.
Opsæt kolonner til import - angiv den foretrukne kolonnerækkefølge.
Ved opsætning af CSV- eller XLSX-filer vha. valgmuligheden Opsæt kolonner til import, kan flg. kolonnetyper angives:
Once you open the configuration dialog for source files in CSV or XLSX formats, the system automatically detects the file scheme based on the column names specified in the first row. The identification is performed in a case-insensitive manner. Columns that weren’t detected automatically will be left as Not chosen for manual configuration. Automatic column identification is especially helpful when you upload multiple multilingual spreadsheets that contain many languages and additional columns (e.g., Context, Labels, Max. Length).
To get the most out of the automatic column detection, we recommend that you name the columns in your CSV or XLSX source files using the values displayed in the table below:
Column type | Expected value |
---|---|
Key | identifier , key |
Source String | source phrase , source_phrase , source string , source_string |
Source String/Translation | source or translation , source_or_translation , source/translation |
Oversættelse | translation |
Context | context |
Etiketter | labels |
Max. Length | max. length , max_length |
Language (for multilingual files) | Language name (e.g., Ukrainian), Crowdin language code, Locale (e.g., uk-UA), Locale with underscore (e.g., uk_UA), Language code ISO 639-1 (e.g., uk), Language code ISO 639-2/T (e.g., ukr) |
By default, during scheme configuration, the system treats CSV and XLSX source files as monolingual. To autodetect file scheme for multilingual source files, follow these steps:
If multiple files have the same configuration scheme, save your current configuration as a template by clicking Templates > Save as template, then specify the template name and click Save. You’ll be able to apply the template to the newly imported files.
If you don’t want to translate the column headers, select Do not import the first row (header).
If you’d like to start the spreadsheet configuration over, click More and select Reset Configuration.
If your file contains several columns with translations into different languages, select Multilingual Spreadsheet and map the languages to the appropriate columns.
By default, when you configure the multilingual spreadsheets, the Import translations option is selected. If you’d like not to import the existing translations from the file, you can clear this option.
If your multilingual source file doesn’t contain enough columns for all project target languages, click Add column. To remove one of the added columns, click More and select Delete Selected Column.
To configure several selected CSV or XLSX files, right-click and select Configure files.
To configure all CSV or all XLSX files at once, click Configure All.
I opsætningsvinduet kan skiftes mellem de valgte filer for at forhåndsvise og tjekke, om den anvendte opsætning er korrekt for alle filer.
You might want to update CSV or XLSX files and change the initially configured scheme. The scheme update might be needed when you add a new target language to your Crowdin project.
To change the scheme for your source file, follow these steps: