A little more info: I’ve always used both methods, i.e. po/mo files for plugins/theme translation and WPML string translation for things that the po/mo files didn’t cover (like titles of widgets and the site tagline). Using po/mo files, when possible, seems to be the better solution since they are portable and can be used across sites. The po file can also be version controlled which is nice. Using WPML string translation seems better for site-specific stuff (again, like titles of widgets and the site tagline). I’ve never had an issue mixing po/mo file usage with WPML string translation usage, and in fact, I believe WPML specifically tries to play nice by allowing you to choose if you want to use WPML only or WPML first with po/mo files as a backup.
I’ve always used the latter for the reasons mentioned above. I’d like to continue using the latter with GD (meaning upload the mo file and modify minimal things with WPML as needed). I’ve got multiple sites and it has been nice to change a common (version controlled) translation and then just re-upload to all sites (rather than messing around with WPML on all sites).
The only real problem I’ve ever run into is GD using the Japanese strings on the admin site when I have my language set to English. Since other plugins don’t do this, I was wondering if GD is doing something with translations that is different than other plugins.
Is the scenario I like possible with GD?
kairei 6 years, 9 months ago.
