[wp-polyglots] 2.7 is coming
mst at eyesx.com
Mon Oct 27 22:27:51 GMT 2008
Sure in other cases a locale site at wordpress would be a benefit, but
in case of automatic updates it doesn't really matter. It could easily
be checked against SVN. I think this should be up to the language teams
to decide. Lets say the update checks the locale site first, if nothing
there the SVN is checked.
well organized ;)
In the matter of finding language files for first time users I think as
long as there is no drop down, flags or other direct links on the first
page of wp.org, users tend to use other means to find the information
directly in their native language, instead of browsing around on a site
in a language maybe not so familiar. (This has been pointed out to me a
bunch of times by our Swedish portal members)
If reorganized to make it easier to find on wp.org I'll be sure to
reconsider a locale site. As is now, I still can't see the point, more
than as an _extra_ reference.
Peter Westwood skrev:
> Mattias Tengblad wrote:
>> Ok, my point here is that this is supposed to be an *automatic update
>> service* for the users. Where in this do the extra site help if the
>> users never gonna visit it anyway. In that case why not just check
>> SVN directly like a extra site would for the update?
>> Sure it can be a good reference point but not for an _automatic_
>> update! Just some sort of middleman. Or am I missing something here?
>> Do you still need to manually download the language file from a page?
> I think the point is that by having the site there is a process for
> publishing the zip file which includes the translated files and there
> is a place for new users to find a translation of WordPress when they
> visit wordpress.org
> BTW - It would be nice to have a page on the main wordpress.org site
> which linked to all the hosted I18N sites which I wanted to do from my
> recent blog post 
>  - http://westi.wordpress.com/2008/10/26/wordpress-in-your-language/
More information about the wp-polyglots