WordPress Ideas » Topic: A wat to preserve language files when updating themes and plugins http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins WordPress Ideas » Topic: A wat to preserve language files when updating themes and plugins en-US Thu, 20 Jun 2013 08:32:45 +0000 http://bbpress.org/?v=1.1 brasofilo on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-22005 Thu, 17 May 2012 23:52:27 +0000 brasofilo 22005@http://wordpress.org/ideas/ Just found an excellent article: Loading WordPress language files the right way, by Geert de Deckere.

My conclusion from 4 lines of code is that it is up to plugin and theme developers to do it the right way: check first inside WP_LANG_DIR and fallback to defaults if not found there.

IMO, now it's a matter of getting this info in the Codex and related documents. Encourage plugin/theme authors to implement this concept and give a clear advice to users where to put his/hers translated files.

Just tested with one of my plugins and it works!

]]> OC2PS on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-21825 Sat, 21 Apr 2012 23:41:32 +0000 OC2PS 21825@http://wordpress.org/ideas/ I think you should encourage plugin developers to use GlotPress.

At the same time, the framework should provision for "child translations" for GlotPress (the few fields where site owner can specify a custom translation different from the GlotPress version)

]]> Ipstenu (Mika E.) on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-21680 Thu, 05 Apr 2012 14:02:19 +0000 Ipstenu (Mika E.) 21680@http://wordpress.org/ideas/ The perfect world is supposed to be that the plugin dev will add any language packs you send them. Doesn't always happen.

Option 1 would be best, IMO. Just totally separate it, so if you have to delete a plugin due to bug sillyness, it's easier to replace.

]]> brasofilo on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-21679 Thu, 05 Apr 2012 12:48:39 +0000 brasofilo 21679@http://wordpress.org/ideas/ @Binary, only if there were child plugins too :)

]]> Binary op Tions on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-21678 Thu, 05 Apr 2012 12:28:39 +0000 Binary op Tions 21678@http://wordpress.org/ideas/ Why not make a child theme to preserve the custom language? For me that seems to be the best solution...

]]> brasofilo on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-21650 Thu, 29 Mar 2012 16:19:08 +0000 brasofilo 21650@http://wordpress.org/ideas/ I'd suggest that /wp-content/languages/plugin-name.mo be the first place where a plugin/theme search for its language files.

Then it's up to the user to sync new versions with his translated files.

Sometimes, you update something (in development or production site) and then "ups..., forgot to backup my translations..."

]]> kallumamaji on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-20557 Sat, 29 Oct 2011 12:01:27 +0000 kallumamaji 20557@http://wordpress.org/ideas/ Best thing would be to submit your translation to GLOTPRESS
available at http://translate.wordpress.org/projects which is also completely in sync with the main repositories and the preferred method for translating WordPress into your language.

This way your translation will be incorporated into plugin

]]> Jan Egbert on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-17010 Mon, 10 May 2010 10:28:01 +0000 Jan Egbert 17010@http://wordpress.org/ideas/ The best method would probably be to overwrite existing .po and .mo files.

BTW The reason I submitted this idea is that I rarely use the easy update feature in WordPress. So I'm still stuck with the old fashioned downloading, unpacking, FTP uploading, etc.

]]> Mark on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-17007 Sun, 09 May 2010 21:25:13 +0000 Mark 17007@http://wordpress.org/ideas/ I see the problem. But what if the plugin includes updated translation files?

]]> Jan Egbert on "A wat to preserve language files when updating themes and plugins" http://wordpress.org/ideas/topic/a-wat-to-preserve-language-files-when-updating-themes-and-plugins#post-17006 Sun, 09 May 2010 18:35:26 +0000 Jan Egbert 17006@http://wordpress.org/ideas/ In the current situation when I update a theme or plugin all files are deleted before the updated software is being put in place. This means that language files which are not incorporated in the theme or plugin are gone after update.

I have two suggestions:

  1. Search for translation files in the languages folder in wp-content and wp-includes.
  2. Let the update script check for extensions .po and .mo before deleting all files.
    ]]>