Import keys

Currently, Gleef does not provide any native integration with localization software. See more here.

​

Why importing existing keys?

Importing existing keys in the Plugin has 2 main benefits:

• Keys generated by the Plugin thereafter will be consistent with your current pattern: e.g. delimiters used, nomenclature etc.
• Keys can be re-used if they already exist in your localization files.

​

How to import existing keys?

It depends on your current localization stack:

​

With a localization software

If you are using a localization software, you can export your localization keys to a CSV or JSON file and import it in the Plugin. The process depends on which localization software you use.

You can contact us if you need help exporting your keys.

​

Without a localization software

If you are not using a localization software, you can directly import the file you use to manage your localization keys and variables. You can import XML, CSV or JSON file.

Any issue while importing your current keys? Contact us

​

When importing existing keys?

​

Onboarding

During the onboarding you can import existing keys so that our Plugin will already be set-up for your company.

​

After onboarding

Thereafter, at anytime you can easily import your localization keys in the Plugin.

You won’t see how many files you’ve already imported, because Gleef doesn’t store your files, but vectorise all the keys, generating embeddings in a database specific to your company. You’ll just see the last update date so that you might know if the Plugin database is up to date or not.