|
Ray
|
November 27, 2015 at 7:09 am
Hi
I was trying to add German translation by using Loco Translate.
But neither in the plugin folder nor in the global folder the translations seem to work.
Please advice on how or what to change to get translations working.
Many thanks.
|
|
Tony
|
November 27, 2015 at 7:14 am
Hi Ray,
Are you scanning and creating your own translation file for this?
Event Espresso and its add-ons are all included in a single translation file available from our GlotPress project here:
http://translate.eventespresso.com/projects/event-espresso-4
Which you can edit the translations from using POEdit.
The filename should be event-espresso-4-{locale}.mo
So German would be event-espresso-4-de_DE.mo
You’ll then need to upload the MO file to /wp-content/uploads/espresso/languages/
|
|
Ray
|
November 27, 2015 at 7:32 am
Hi
Thanks for your answer.
Did I understand right: There is only one single file handling all EE4 core and plugin translations?
|
|
Tony
|
November 27, 2015 at 7:47 am
Yes.
We debated individual translation files for the add-ons but chose a single file as we found it easier for users to manage a single file rather than multiple files.
|
|
Ray
|
November 27, 2015 at 8:14 am
I believe thats easier.
Since I am using Loco translate very successfully with plugins, what other location can I move the .mo file to, so I have my translations.
The quality of the translations is very low and I do want to keep translations stable.
Or is there a way that I can tell EE4 to always pick the file located in languages/plugins?
|
|
Josh
|
November 27, 2015 at 8:24 am
We recommend the /wp-content/uploads/espresso/languages/ locations because files in that location will not be overwritten. There are other locations, like right within the /languages/ folder of the plugin, but if you put the file there it will get overwritten on an update.
|
|
Ray
|
November 27, 2015 at 8:46 am
ok. let me run some tests and see if I can get it working.
I was hoping to create a variable to tell EE4 where to look for the file, as the languages/plugin folder.
|
|
Josh
|
November 27, 2015 at 9:03 am
It doesn’t look like you can create a variable to move the location, because it’s set as a constant.
define( 'EE_LANGUAGES_SAFE_DIR', EVENT_ESPRESSO_UPLOAD_DIR . 'languages' . DS );
|
|
Ray
|
November 27, 2015 at 10:06 am
In point of view there is a partial risk of handling translation proprietary.
But I also see your strategy, which does not seem to be a standard.
All translations been in place before are gone.
I’m not sure what the most effective solution looking forward would be..
GlotPress is a pain, offline as well.
Let me know what you think.
Thanks
|
|
Josh
|
November 27, 2015 at 10:16 am
I think PoEdit is a good solution.
|
|
Ray
|
November 28, 2015 at 3:32 am
Where are translation bugs reported to?
– E.g. not found strings
Thanks
|
|
Tony
|
November 28, 2015 at 11:53 am
You can report those here and we’ll get them fixed.
Also you translations should not be lost if you placing them within:
/wp-content/uploads/espresso/languages/
If your placing them within the languages directory within:
/wp-content/plugins/event-eapresso-core-reg/languages/
Then that’s not recommended when the plugin updates that directory will be removed.
You can use loco translate to build your own po files but you will need to move them to the above location.
|
