Text domain in .pot
-
May I suggest a small change in the code, making your fine plugins easier to translate? In some of your files, you’ll see the text domains ‘tp-hotel-booking’ or ‘tp-hotel-coupon’ in __e-statements (or in some cases no text domain at all). It’s a bit of a problem, if you are using tools like ‘Loco Translate’ for translation. The domains ‘tp-hotel-something’ is probably something left from the old name of the plugin.
As an example, Loco suggests ‘wp-hotel-booking-coupon’ as text domain for your WP Hotel Booking Coupon plugin (changing the value to ‘tp-hotel-booking’ don’t help).
Result: Using the translated strings fails (strings shows in US English, when running on a Windows IIS platform (the only platform we have tried so far)).
Changing the text domain to ‘wp-hotel-booking-coupon’ just like the .pot file name (as an example __( ‘Coupon applied: %s’, ‘wp-hotel-booking-coupon’ ), and it works and shows the translated strings.
PS: We can easily fix this ourselves, but then it’s overwritten by next update.
- The topic ‘Text domain in .pot’ is closed to new replies.
