You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
In my current work, we send the translations to another company that needs a XLSX file. Currently i'm using BabelEdit, and this is the only missing feature for us to move completely to i18n-manager ;-)
(with a checkbox for each language this folder has, all are checked by default)
Option to choose to export "all translations" or "selected/filtered items"
Filtered example: If i'm filtering only for the 'Missing' translations, the XLSX file would have only the keys that have missing translations for the above chosen languages
The Excel file should have the following columns:
Translation Key
The complete translation key hierarchy needs to be exported in each cell (for the import feature to work afterwards). Example: "buttons.save"
Language1
Language2
etc.
Observation:
The separator can be excel's default ; . If any translation has ;, this probably needs to be treated (with a ```;```` or something)
Import Feature
Add an Import button, that reads exported XLSX files.
This overwrites all translations contained in the XLSX file.
The text was updated successfully, but these errors were encountered:
Amazing!
I'm glad that your team will move to i18n manager!
The translation key will contain some additional specific path parts, like .data. and .Symbol(LanguageIndex).. These items are part of the tree generation algorithm and make the files consolidation possible. Is this a problem for you?
Translation key, any other extra columns and even column names you can play around. It doesn't need any compatibility with other translation software.
This is basically a feature to export to XLSX/CSV, so people can sent to translators that are more used to translate Word and Excel files. And then import those changes back into i18n-manager.
Background
In my current work, we send the translations to another company that needs a XLSX file. Currently i'm using BabelEdit, and this is the only missing feature for us to move completely to i18n-manager ;-)
Here's Babel's documentation for Import/Export: https://www.codeandweb.com/babeledit/documentation#export
Features
Export Feature
The Excel file should have the following columns:
Observation:
;
. If any translation has;
, this probably needs to be treated (with a ```;```` or something)Import Feature
The text was updated successfully, but these errors were encountered: