Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

Export / Import XLSX File #384

Open
iurikothe opened this issue Apr 25, 2020 · 2 comments
Open

Export / Import XLSX File #384

iurikothe opened this issue Apr 25, 2020 · 2 comments
Labels

Comments

@iurikothe
Copy link

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

  • Add an Export button, with the following options:
  • Choose languages
    • (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.
@gilmarsquinelato
Copy link
Owner

Hey @iurikothe

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?

This feature can be added in v3.1

@iurikothe
Copy link
Author

Thanks Gilmar!

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.

Cheers!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants