|
Aurelio
|
July 13, 2016 at 6:19 am
In this below page, we couldn’t find translation for buttons “Resend Registration”, “View Transaction” and “View/Edit Contact”.
/wp-admin/admin.php?page=espresso_registrations&action=view_registration&_REG_ID=5&view_registration_nonce=xxxxxx
|
|
Lorenzo Orlando Caum
|
July 13, 2016 at 9:36 am
Hello,
I’ve checked some of those translation strings and they already appear to be translated:
https://translate.eventespresso.com/projects/event-espresso-4/pt-br/event-espresso-pt_BR?filters%5Bterm%5D=Resend+Registration&filters%5Buser_login%5D=&filters%5Bstatus%5D=current_or_waiting_or_fuzzy_or_untranslated&filter=Filter&sort%5Bby%5D=translation&sort%5Bhow%5D=asc
—
Lorenzo
|
|
Lorenzo Orlando Caum
|
July 13, 2016 at 9:51 am
Hello,
On further troubleshooting, the following text is not translation ready:
View/Edit Contact
We have corrected that string and this will be available in an updated version of Event Espresso 4 and we’ll also be sure to update GlotPress.
Once that is available, then you can one-click update through your WP dashboard.
—
Lorenzo
|
|
Aurelio
|
July 15, 2016 at 1:53 pm
Yes. We had translated that strings at GlotPress but they doesn’t apply in site. I believe that code issue.
By the way, EE4 use “.po” files?
|
|
Tony
|
July 15, 2016 at 2:07 pm
WordPress/EE4 uses the .MO files.
.PO files are the files you edit to add translations.
.MO files are the machine code files generated from the .PO files, those files contain all of the translations and are the files used to actually translate the site.
We have some documentation on how to translate EE here:
https://eventespresso.com/wiki/how-to-translate-event-espresso/
|
|
Aurelio
|
July 18, 2016 at 5:50 am
Thanks
|
|
Tony
|
July 18, 2016 at 6:08 am
You’re most welcome.
If you have any further problems pleas do let us know.
|
|
Aurelio
|
July 18, 2016 at 7:07 am
Hi again.
“Resend Registration” and “View Transaction” buttons remain without translation. They’re ignoring updates in “.mo” file.
Page: http://url/admin.php?page=espresso_registrations&action=view_registration&_REG_ID=19&view_registration_nonce=a648eac495
|
|
Aurelio
|
July 18, 2016 at 7:11 am
See them http://goo.gl/Mo5XtR
|
|
Aurelio
|
July 18, 2016 at 7:18 am
UPDATE: Further buttons, the text in same page “Para o event:” couldn’t be translated. The string for “event” was not found.
We begin with 10%. After hard work, we’re in 42% (4th place) Yeah!
|
|
Tony
|
July 19, 2016 at 7:48 am
“Resend Registration” and “View Transaction” buttons remain without translation. They’re ignoring updates in “.mo” file.
Those strings are missing the text domain for translation, we’ll get that fixed in the next version of Event Espresso.
UPDATE: Further buttons, the text in same page “Para o event:” couldn’t be translated. The string for “event” was not found.
Whilst it is possible to translate the string in use there, its part of a display strategy used for outputting different outputs for different object types, translating the string will force the same output for each object.
The string used to output that text is here:
https://translate.eventespresso.com/projects/event-espresso-4/pt-br/event-espresso-pt_BR?filters%5Bterm%5D=%251%24sfor+the+%252%24s%3A+%253%24s%254%24s&filters%5Buser_login%5D=&filters%5Bstatus%5D=current_or_waiting_or_fuzzy_or_untranslated&filter=Filter&sort%5Bby%5D=translation&sort%5Bhow%5D=asc
The %2$s is used to replace the object type (Event or Ticket), however as mentioned I would advise against changing this as it will have unexpected results.
I have created a ticket for some feedback from our developers on this and will update this thread shortly.
|
|
Aurelio
|
July 19, 2016 at 7:57 am
Thanks for your fast reply.
|
|
Josh
|
July 25, 2016 at 3:15 pm
The fix for the issue you reported here was included in the latest update (Event Espresso version 4.9.4).
|
