|
ARAGATO
|
July 6, 2016 at 6:50 am
I am localising my event espresso installation. I followed your translation guideline and everything worked. However, after successfully translating many strings I came across some strings that are not translated in the front-end although they are correctly translated in the .mo file that is being used.
It is on the single event details page in the section “more details”.
http://uploads.aragato-server.net/screenshots/20160706e99ce77a50.jpg
http://uploads.aragato-server.net/screenshots/201607061250e4d971.jpg
http://uploads.aragato-server.net/screenshots/201607069525b9f130.jpg
|
|
Lorenzo Orlando Caum
|
July 6, 2016 at 8:57 am
Hello,
I added one of those translation strings within our GlotPress project:
https://translate.eventespresso.com/projects/event-espresso-4/de/event-espresso-de_DE
Does it work as expected if you generate an MO file from GlotPress and then move that into place on your website?
—
Lorenzo
|
|
ARAGATO
|
July 6, 2016 at 10:10 am
Does not change anything.
|
|
ARAGATO
|
July 6, 2016 at 11:21 am
Again, many other strings translate perfectly. Its only these two that do not work.
|
|
Josh
|
July 6, 2016 at 1:56 pm
The strings for the ticket selector display are actually:
Total%sSold
and
Total Spaces%sLeft
https://translate.eventespresso.com/projects/event-espresso-4/de/event-espresso-de_DE?filters%5Bterm%5D=Total%25sSold&filters%5Buser_login%5D=&filters%5Bstatus%5D=current_or_waiting_or_fuzzy_or_untranslated&filter=Filter&sort%5Bby%5D=priority&sort%5Bhow%5D=desc
https://translate.eventespresso.com/projects/event-espresso-4/de/event-espresso-de_DE?filters%5Bterm%5D=Total+Spaces%25sLeft&filters%5Buser_login%5D=&filters%5Bstatus%5D=current_or_waiting_or_fuzzy_or_untranslated&filter=Filter&sort%5Bby%5D=priority&sort%5Bhow%5D=desc
|
|
ARAGATO
|
July 6, 2016 at 3:09 pm
Quality answer!
Working, thank you.
|
