That sounds about right, but is there some kind of functional/technical spec or description of how the upgrade process will work? It's hard to figure out what adjustments might be needed for localized distributions without first knowing what we're actually dealing with.
On Thu, Aug 7, 2008 at 8:19 PM, Stefano Aglietti <[EMAIL PROTECTED]>wrote: > On Thu, 7 Aug 2008 09:18:06 -0700, "Ryan Boren" <[EMAIL PROTECTED]> wrote: > > >Let's determine the i18n requirements in this thread. > > I think there ie few requirement... > > 1) check the current installation to see if a locale is set > 2) check the wordpress-i18n repository to see if there is a a new > version for that locale > 3) update using the new locale, if not locale is available but it's in > the repository warn the user about it sayin tha upgrade will use the > english version and aasking if he wanna wait few days to have the > upgrade in his languages > > The warning messages about the new version available should say if the > update is available in english or in the locale. > > I don't think there is anything else to cjheck or to do. To make stuff > complicated an upgrade using english version should inform about the > availability of locale update and thiss will just ciopy the locale > files from the wordpress-i18n repository, > > -- > > Stefano Aglietti - StallonIt on IRCnet - ICQ#: 2078431 > Email: [EMAIL PROTECTED] [EMAIL PROTECTED] > Sites: http://www.40annibuttati.it (personal blog) > http://www.wordpress-it.it (WordPress Italia) > _______________________________________________ > wp-polyglots mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-polyglots > -- -- RYH♡, ranh.co.il
_______________________________________________ wp-polyglots mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-polyglots
