Support

May 8, 2013 at 12:50 pm

Hey there 🙂

I’m translating Event Espresso now for over a year, and i want to suggest the following thing:

Seperate Language Files for Payment Gateways and Addons.

When you use Event Espresso e.g. in Germany, one can use the following Gateways: Wire, Check/Cash, Google Wallet and PayPal (Standard and Pro). Thats it. But atm the language files include ALL other payment gateways, with no use for our market, but you kind of have to translate them, since you can never use them.

The same thing is for addons: The Language Files include all strings for them, even if you never want to use a seating chart or Coupons etc.

For me personally, it would be much easier to have a core language file for event espresso, which HAS to up date, and translate the rest as needed. One may say that seperating the language files for addons and gateways will lead to spotty translations, but if no one in specific country can use a payment gateway, there is absolutly no need to translate it. And if the payment provider changes their list of supported countries, and one user wants to have that gateway translated, it were only a few strings to translate anyway. The user who wants to use a gateway will then translate it 😉

I know thats a great change in the source files, but i would fall in love with you guys if you can keep an eye on that in the further development. If you look over to GlotPress, you’ll see that translating 4600 strings is no fun, particularly if about half of them were a waste of time…

Best regards,
Marko