[wp-polyglots] WordPress languages folder

[Peter Westwood]

I completely understand the size issue.

I wonder if in the long run the best solution is for the plugin api to be locale aware and to build zips with only the required locales in for plugins with many translations.

Something automated like that would be really nice.

--
Peter Westwood
http://peter.westwood.name

On 30 Jun 2010, at 22:36, "John James Jacoby" <in at j-3.me> wrote:

> All of our translations are managed by separate committers on a separate SVN. To include all of these translations would force everyone to download all languages (300kb po + 100kb mo * 10 languages = 4mb in extra translations for every download)
> 
>  
> 
> To do this, we would have to download each translation separately and add it to the tagged package on wp.org.
> 
>  
> 
> My thought was that if you needed the translation, we could just have a cute downloader in BuddyPress that would grab the file, and put it in wp-content/languages/buddypress/ for safe keeping. We have our own function that loads the po/mo anyhow, so changing the directory that it points to is no big deal. Then when BuddyPress 1.2.6 comes out, they won’t have to worry about their previously downloaded language getting wiped out, or have to download 4MB of additional translations they won’t use.
> 
>  
> 
> From: wp-polyglots-bounces at lists.automattic.com [mailto:wp-polyglots-bounces at lists.automattic.com] On Behalf Of Peter Westwood
> Sent: Wednesday, June 30, 2010 5:29 PM
> To: wp-polyglots at lists.automattic.com
> Subject: Re: [wp-polyglots] WordPress languages folder
> 
>  
> 
>  
> 
> On 30 Jun 2010, at 21:02, John James Jacoby wrote:
> 
> 
> 
> 
> Hey everyone! First time using this list so be gentile. J
> 
>  
> 
> For BuddyPress, we have a large number of users in languages other than English, and when BuddyPress gets updated their po/mo’s are deleted, and they are forced to redownload their translations.
> 
>  
> 
> I was wondering if there is any compelling reason for plugins to NOT put their translation files into wp-content/languages/*plugin-folder-name* and then write their own functions to load those files, and update those files when needed.
> 
>  
> 
> Seems to me this would fix our problems, but I wanted to consult with you all before giving it a go.
> 
>  
> 
>  
> 
> I just include all current po/mo's in the plugin download.
> 
>  
> 
> Does this not work for you?
> 
>  
> 
> e.g. https://plugins.svn.wordpress.org/wordpress-beta-tester/tags/0.92/
> 
>  
> 
> -- 
> Peter Westwood
> http://blog.ftwr.co.uk | http://westi.wordpress.com
> C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5
> 
>  
> 
> _______________________________________________
> wp-polyglots mailing list
> wp-polyglots at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-polyglots
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100701/290bd38e/attachment.htm>