|
Cristi Constantin
|
December 2, 2013 at 3:18 pm
After installing “Codestyling Localization” and scanning the source files of Event Espresso 3.1.36.P, there were several problems encountered, which should be cleaned in EE php source files:
1. multiple text domains are used, besides ‘event-espresso’; probably it is unintentional, the list being composed of:
twentyten, event_espress, debug-bar, default
These strings totaling 61.
2. Strings which you add in newer EE versions take a while to get to GlotPress. Currently, there are about 66 strings (except the 61 above) which are part of ‘event-espresso’ text domain, but are not present on GlotPress. This leads to delays in translation availability.
Thank you.
|
|
Cristi Constantin
|
December 2, 2013 at 3:50 pm
3. String ‘Add Additional Attendee’ is present in the source code as __(‘Add Additional Attendee’, ‘event_espresso’), but on GlotPress there is no sign of this, is this the effect of no. 2.?
|
|
Josh
|
December 2, 2013 at 4:39 pm
Thanks for the feedback.
|
|
Cristi Constantin
|
December 4, 2013 at 8:26 am
Is it possible that you fix point 1. in the next EE 3 release version? I am planning to launch in the next weeks and this translation issues are keeping me blocked.
I am willing to give you all my support for this task, it a simple translation task like:
before: __(‘Price Type:’)
after: __(‘Price Type:’, ‘event_espresso’)
or:
before: _e(‘Juridico’,’event_espress’)
after: _e(‘Juridico’,’event_espresso’)
The plugin which I have mentioned really helps in identifying the source files and situations.
Thank you.
|
|
Josh
|
December 5, 2013 at 10:53 am
We went through and standardized the text domains for the front end for version .37.
|
|
Cristi Constantin
|
December 5, 2013 at 11:54 am
Thanks, I appreciate it. Any opinion about why 2. and 3. are happening?
|
|
Josh
|
December 5, 2013 at 12:19 pm
Glotpress needs some updating.
|
