Title: Translation problems/Crappy code
Last modified: August 22, 2016

---

# Translation problems/Crappy code

 *  Resolved [sunhort](https://wordpress.org/support/users/sunhort/)
 * (@sunhort)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/translation-problemscrappy-code/)
 * I’ve spent so much time translating plugin into Russian, and got so many strings
   that are not being translatd!
    If you do pot/po thing you have to make sure it’s
   working right. Strings like : “The password should be at least..” , “Please login
   to continue..” “Profile”, “Dashboard” were translated but doesn’t come up right
   in the front-end. So now after getting into code, I won’t be able to update as
   the site will go in production in a month.
 * Here is file with translation:
    [Dropbox](https://www.dropbox.com/sh/stgjgrcssgcee3s/AAArPh4CjYhbbDPdkpRo6unna?dl=0)
 * just try it and you’ll see how bad this plugin works with ALL STRINGS TRASNLATED!!!
 * Other people on the net also getting problem with partial strings translation
   in this plugin.
    If you don’t know that you have to use npp++ and convert encoding
   to “utf-8 without bom” in those php files you will never be able to make it work
   right if your language is other than English.
 * [https://wordpress.org/plugins/theme-my-login/](https://wordpress.org/plugins/theme-my-login/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Jeff Farthing](https://wordpress.org/support/users/jfarthing84/)
 * (@jfarthing84)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/translation-problemscrappy-code/#post-5952767)
 * Crappy code?
 * The plugin used to use WP’s core translations where applicable, rather than retranslating
   them all. However, WP then split the core translation files, moving most of the
   core strings that TML uses into the admin translation file. The plugin has not
   been updated since this happened.
 *  Plugin Author [Jeff Farthing](https://wordpress.org/support/users/jfarthing84/)
 * (@jfarthing84)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/translation-problemscrappy-code/#post-5952774)
 * The remaining untranslated strings have had the text domain added to them. This
   issue should be resolved in 6.3.11.
 *  Thread Starter [sunhort](https://wordpress.org/support/users/sunhort/)
 * (@sunhort)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/translation-problemscrappy-code/#post-5952814)
 * Thanks a lot for fixing issues with those strings, now it looks like it is working
   correctly,
    tnx again!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Translation problems/Crappy code’ is closed to new replies.

 * ![](https://ps.w.org/theme-my-login/assets/icon-256x256.png?rev=1891232)
 * [Theme My Login](https://wordpress.org/plugins/theme-my-login/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/theme-my-login/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/theme-my-login/)
 * [Active Topics](https://wordpress.org/support/plugin/theme-my-login/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/theme-my-login/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/theme-my-login/reviews/)

## Tags

 * [translation problems](https://wordpress.org/support/topic-tag/translation-problems/)

 * 3 replies
 * 2 participants
 * Last reply from: [sunhort](https://wordpress.org/support/users/sunhort/)
 * Last activity: [11 years, 1 month ago](https://wordpress.org/support/topic/translation-problemscrappy-code/#post-5952814)
 * Status: resolved