[wp-polyglots] Repository automation proposal

[Stefano]

Il Tue, 1 Mar 2005 22:21:09 -0800, Morgan Doocy <morgan at doocy.net>
scrive:

>1. Track only "source" files in the repository. These include:
>    - POT files
>    - PO files
>    - Hard-translated themes
>    - Gettexted themes
>    - Hard-translated WP core files

I think there should NEVER be WP core file hard-traslated, after this
works around the 1.5 i18n future version of WP will start on full i18n
version, developpers will just need to care to apply i18n function to
any ned string they add.

>    - Repository tools

Like what?

>2. Use hook scripts [1] to generate compiled files and do packaging on 
>each commit. Depending on what files are changed in a commit, any or 
>all of the following would be automatically generated for the affected 
>locale:
>    - MO files
>    - Packaged localized theme downloads (both hard-coded and gettexted 
>versions)
>    - Packaged localized versions of full WordPress with localized 
>themes, MOs, and dist files
>    - Different versions of all of the above for each of a locale's most 
>popular character encodings
>3. Place auto-generated content in a public "staging area" for 
>downloading. (e.g. http://wordpress.org/international/ or 
>http://wordpress.org/localized/)

About all other points it sounds good to me.
-- 

Stefano Aglietti - StallonIt on IRCnet - ICQ#: 2078431
Email: steagl at people.it - steagl at despammed.com
BlogPage: http://www.40annibuttati.it/
PGP keys available on keyservers  (cripted & signed PGP mail welcome)