hmm.. I ran a few tests, including building nb_NO versions for WP 2.9.1 and
2.9.2 at nb.wordpress.org. Then I set up a local install of 2.9.1 (nb_NO),
and I immediately got the option to upgrade to the norwegian 2.9.2 version..
I think I should wait a bit and see what happens. But are there any other
differences between the regular packages and the localized packages except
for:

   - the addition of mo and po files
   - localized wp-config-sample.php (and other optional files in /dist)
   - the line $wp_local_package = 'nb_NO'; in wp-includes/versions.php ?

I tried editing my versions.php on a site that was installed using a
non-localized version, which has since been upgraded to 3.0-RC3-15260 with
the beta tester plugin (and it is set to nb_NO in wp-config.php as well) -
but when I re-ran the upgrade, it didn't fetch the package from
http://nb.wordpress.org/wordpress-3.0-RC3-15260-nb_NO.zip - and the
versions.php was reverted to not include the line  $wp_local_package =
'nb_NO'; ...

Peter


On Wed, Jun 16, 2010 at 19:46, Peter Holme <[email protected]> wrote:

> I do run the nightly build...
>
> 2010/6/16 José Fontainhas <[email protected]>
>
>>
>>>> I built it from GP. Yes, I just thought that once you release the
>>> package, it would be possible to automatically get the translation files to
>>> my WordPress sites from within the WP backend (not having to d/l the tar and
>>> FTP-ing it over the old install)
>>>
>>> Only if you're running a beta/nightly build already... the upgrade tool
>> will not suggest an upgrade from a stable release to a beta or RC
>>
>> Z
>>
>> _______________________________________________
>> wp-polyglots mailing list
>> [email protected]
>> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>>
>>
>
>
> --
> +47 920 42 782
>



-- 
+47 920 42 782
_______________________________________________
wp-polyglots mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-polyglots

Reply via email to