|
Cristi Constantin
|
November 18, 2013 at 6:50 am
Hi,
What needs to be done as to activate, for EventEspresso, a translation (mo/po) downloaded from GlotPress?
I have put the .mo file into uploads/espresso/languages, named it properly, but still it isn’t enough. EE translates ok (into Romanian) but uses a partial translation which was packed in the latest release.
Thank you.
|
|
Jonathan Wilson
|
November 18, 2013 at 3:49 pm
Hi Cristi,
You will also need to export and upload the .mo file. You can get it from Glotpress as well.
|
|
Sidney Harrell
|
November 18, 2013 at 4:33 pm
Check the filesize of the .mo file. It should be 367.32 kb. If it’s not, then go here and hit the “View Raw” link. You shouldn’t have to rename it, it should be “event_espresso-ro_RO.mo”.
|
|
Cristi Constantin
|
November 18, 2013 at 11:43 pm
Mine is over 600k, it has many translations not present in the github version. I said that it was downloaded from glotpress,so there is no raw version, there is just an export button.
|
|
Dean
|
November 19, 2013 at 4:46 am
Hi,
Check the file name, for example when I downloaded the German file from out Glotpress it had the file name as event-espresso-de.po. This wont work. Renaming it to event-espresso-de_DE.po made it functional.
|
|
Cristi Constantin
|
November 19, 2013 at 4:49 am
The naming is ok. This is the file:
|
|
Cristi Constantin
|
November 19, 2013 at 4:50 am
|
|
Cristi Constantin
|
November 19, 2013 at 4:51 am
Cannot get the link to work: https://www.dropbox.com/s/mf9k2obrn27zlj0/event_espresso-ro_RO.mo?m=
|
|
Dean
|
November 19, 2013 at 5:10 am
Hi,
Thanks for the file copy. It works fine for me http://d.pr/i/ygGx
Things to check:
Does the uploads/espresso/languages folder contain a blank index.php file?
Have you changed your wp_config.php file to read define(‘WPLANG’, ‘ro_RO’); ?
|
|
Cristi Constantin
|
November 19, 2013 at 5:28 am
Let’s take a look at an exact sample: please check, in wp-admin/admin.php?page=support , the translation of “Order Post Types Objects using a Drag and Drop Sortable javascript capability”. Here it is translated: http://staging.eventespresso.com/glotpress/projects/event-espresso/ro/event-espresso-ro_RO?filters%5Bterm%5D=Order+Post+Types+Objects&filters%5Buser_login%5D=&filters%5Bstatus%5D=current&filter=Filter&sort%5Bby%5D=original_date_added&sort%5Bhow%5D=asc . Also, if you search the .mo file using Notepad++, there are the two strings (EN and RO). The folder which you have mentioned does contain a blank index.php file.
I think it is an issue, maybe, on EE side, like even though the strings are present on GlotPress, they are relatively new, and are not integrated 100% into EE code (for example, maybe there is some size check/limit, something?).
|
|
Dean
|
November 19, 2013 at 5:56 am
Hi,
Thanks for the example. These are none essential strings that are currently not translatable.
I can put in a request to have them translated but it would be low priority.
If these strings absolutely need to be translated you can add them to the po file, and then use Poedit to open the modified po file and save it, making them usable.
If there are any strings that are pertinent to the running of the plugin that are not translated please let me know and I can add a request for those.
I am surprised Glotpress picked these strings up as they are not marked for translation.
|
|
Cristi Constantin
|
November 19, 2013 at 6:01 am
What I have found so far:
“Map and Directions” and “Unlimited” (regarding number of available seats).
Secondly, maybe you can check and solve the GlotPress issue, because everyone who is trying to do a full translation will also spend a lot of time with this unessential strings.
|
|
Dean
|
November 20, 2013 at 2:11 am
Hi Christi,
Thanks for those strings and looking closer at what is happening is that the strings ARE translatable, just not in version 3.1.X. We have some strings that are going into 4.0 onwards that are already included in the translation files.
|
|
Cristi Constantin
|
November 20, 2013 at 2:13 am
Thank you, too. So I understand that the mentioned strings will see a fix in the next minor release?
Do you happen to know why GlotPress still displays 1 string as being untranslated into Romanian?
|
|
Dean
|
November 20, 2013 at 3:48 am
“So I understand that the mentioned strings will see a fix in the next minor release?”
I cannot guarantee this, I simply add the tickets and the developers work on priority.
“Do you happen to know why GlotPress still displays 1 string as being untranslated into Romanian?”
Honestly, no. Even though it states 99% and 1 untranslated, it isn’t showing them. As it isn’t showing I would say it’s a GlotPress bug, I wouldn’t worry about it.
|
