|
Nijen
|
September 11, 2015 at 3:00 am
Hi, just a note.
I just updated to Version 4.8.9.p and discovered that the detailed view of the ticket selector has a few new language strings that are not (yet) present at GlotPress.
Thus they are not possible to translate. Would be fantastic with an update!
Thanks
Nijen
|
|
Tony
|
September 11, 2015 at 7:41 am
Hi Nijen,
Glotpress has now been updated with the latest POT file, please us know if there are any strings unavailable for translation.
|
|
Lorenzo Orlando Caum
|
September 12, 2015 at 2:47 pm
Hello again Nijen,
We have a new resource that explains how to translate Event Espresso. You can view it here:
https://eventespresso.com/wiki/how-to-translate-event-espresso/
Also, GlotPress now has translation strings that are up to date for the current Event Espresso 4.8.x platform.
—
Lorenzo
|
|
Nijen
|
September 20, 2015 at 3:42 pm
Hi Lorenzo,
Thanks for reply and great that you updated the wiki! – Hopefully that will get more people to translate.
However – I am sorry to tell you but the missing strings in EE 4.8 ticket chooser are still not searchable in the pot-file at Glotpress: http://translate.eventespresso.com/projects/event-espresso-4/sv/event-espresso-sv_SE
The missing ones are:
• %s / ticket
• Ticket Price Breakdown
• Total ticket price
• Event Access
– This ticket allows access to the following event dates and times.
Here is link to a screenshot: https://www.dropbox.com/s/uo1wrgciitymcfb/ticketselector-no-swedish.png?dl=0
Cheers!
Nijen
|
|
Lorenzo Orlando Caum
|
September 21, 2015 at 11:01 am
Hi Nijen,
I think something else is occurring. In 4.8.8 we removed some of the headings/descriptions that reference “ticket” since Event Espresso is used for a variety of events where ticket may not be a good fit.
Are you on the latest version of Event Espresso 4.8.9?
I do see that some of the translations have already been updated. However, would you happen to be using a customized version of the ticket selector template?
If so, that would use the old translation strings and not the new ones.
A workaround would be to setup a gettext filter that will translate the old translation strings to the new ones:
https://eventespresso.com/wiki/how-to-change-wording-with-poedit/#custom-function
—
Lorenzo
|
