Hi, when will be a 3.4 sub-project created on GlotPress?
Because, if I build a package from development branch, it will end up with 3.5-alpha package, and the next branch is 3.3, which will end up a 3.3.2 package…
Hi, when will be a 3.4 sub-project created on GlotPress?
Because, if I build a package from development branch, it will end up with 3.5-alpha package, and the next branch is 3.3, which will end up a 3.3.2 package…
I exported from 3.4 (dev) and imported to 3.3.x. There is no untranslated string, yet there is no “3.3 and 3.3.x” option. Help please.
Could you check if it’s due to the missing “/messages” folder structure and files in svn?
From the [wp-hackers] mailing list, this concerns all here:
Hi, everyone.
I want to present my GSoC project Language Packs, which will be incorporated
in the core for version 3.3.
You can follow installation guide
http://gsoc.svn.wordpress.org/2011/Osho34/documentation/trunk/Installation%20and%20Deployment%20Guide.odt
Detailed description is here: http://gsoc2011.wordpress.com/language-packs/
I would be happy if you suggest me some enhancements or report some bug.Best Regards
Great news, from the links:
This project consists of a plugin, server side endpoint, which will be deployed on api.wordpress.org, and protocol in which communicate between.
The plugin is displayed as an options page, located in the Settings box. The plugin lists all plugins and themes, which are installed and offers an option to translate a blog in other languages. Plugin also manages po and mo files for the core, plugins and themes in the wp-content/languages/ folder. The role of plugin is also to take care about versions of plugins, themes and core.
The server API endpoint deals with requests for downloading po and mo files, depending on language, plugin or theme name and version. The server endpoint could also manage simple and batch requests, which are defined by plugin functions and protocol. The server sends po and mo file only if this version of plugin or theme is fully translated, unless sends the message that plugin is not translated. If some plugin ot theme is not translated, user can request translation via the plugin options page.
The protocol for communication between the plugin and the server endpoint override the HTTP protocol and is incorporated in the plugin and the server functions. On the plugin side, the protocol uses the WP HTTP API.
== Installation ==
1. Upload the whole plugin folder to your /wp-content/plugins/ folder.
2. Go to the Plugins page and activate the plugin.
3. That’s all, everything will work automatically
== Frequently Asked Questions ==
1. What is the purpose of this plugin?
This plugin is a prototype for the future core feature language packs.
Daniel Koskinen 9:04 am on June 25th, 2012 Permalink |
Hi, you need to select revision 21078 to get 3.4
DjZoNe 11:12 am on June 25th, 2012 Permalink |
Good hint 🙂
Wacław J. 10:06 am on June 27th, 2012 Permalink |
+1