Type
library
Collect missing translations in specified folder or the entire Magento 2 Root. Adds database editing and management of translations.
library
proprietary
None
None
None
None
None
Add a CLI command to Collect missing translations in specified folder or the entire Magento 2 Root and add an Admin Grid to display and update or add database/inline translations (Stores > Translations > Database/Inline Translations)
experius/module-missingtranslations
It is possible to generate a CSV file which contains the original string and an empty string.
This CSV file can be generated through the following command:
php bin/magento experius_missingtranslations:collect [-m|--magento] [-l|--locale="..."] [-s|--store="..."] [directory]
Use the command like this:
php bin/magento experius_missingtranslations:collect --magento --locale nl_NL
This file can be used by a Translation Agency to complete the translations for the webshop.
After the Translation Agency has fully translated the csv file it is possible to transform it to a language pack.
This can be done by removing the suffix missing
and eventually transform it to a language pack by adding a language.xml
and a registration.php
Besides transforming the file to a language pack it is possible to add new translations through the admin interface, which can be found under Stores > Translations > Database / Inline
only if you generated it to a file with the following filename a file in app/i18n/Vendor/missing/locale_code.csv. (Example: app/i18n/Vendor/missing/nl_NL.csv.)
For this functionality see Translations to database (Existing and Missing)
In addition to gathering missing translations this module also supports database translation (formerly known as inline translate)
This makes it possible for merchants to edit any translation in the Magento Admin Panel.
Collecting and importing the translations happens nightly when it is enabled by default this functionality is disabled This is done on global scope for all locales that are used in at least one storeview (based on the configured locales).
03:13 AM server time, all existing csv translations are added to the database.
This functionality Imports the Existing CSV Translations into the Database then the Original String will differ from the Translated String.
03:23 AM server time, all missing translations found are added to the database.
This functionality Imports the Missing Translations into the Database then the Original String will be equal to the Translated String.
Manually gathering the translations (and adding them to the database) is possible. This can be done by one of the following two Console commands:
php bin/magento experius_missingtranslations:existing-translations-to-database --global --locale nl_NL
php bin/magento experius_missingtranslations:missing-translations-to-database --global --locale nl_NL
Herein --global is defined to save the translations for any storeview with the specified locale
To specify a specific store_id add the store ID parameter (--store [store_id]) WARNING: This is not recommended unless translations differ for the same language in separate storeviews Example:
php bin/magento experius_missingtranslations:addtodatabase --store 1 --locale nl_NL
(Stores > Settings > Configuration > General > General > Locale Options > Language vendor for missing translations)
(Stores > Settings > Configuration > General > General > Locale Options > Existing translations cron enabled)
(Stores > Settings > Configuration > General > General > Locale Options > Missing translations cron enabled)
For database translations - Add flag to translation table database (user_defined); if user edit's a translation, user_defined is flagged as true. - Add --force update for every entry that is not flagged as user_defined; to update csv changes into database.