-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Most of these are updates, and this isn't meant to make a quantitative difference, mostly just dealing w/ little typos, and tweaks. I hope this doesn't seem like a drag, cause i don't have another option as of now but to ask for someone to commit.
New: http://l10n.gnome.org/vertimus/xdg-user-dirs-gtk/HEAD/po/crh Updates: http://l10n.gnome.org/vertimus/gtk+/HEAD/po-properties/crh http://l10n.gnome.org/vertimus/gtk+/HEAD/po/crh http://l10n.gnome.org/vertimus/libgnome/HEAD/po/crh http://l10n.gnome.org/vertimus/libgnomecanvas/HEAD/po/crh http://l10n.gnome.org/vertimus/libgnomeui/HEAD/po/crh http://l10n.gnome.org/vertimus/alacarte/HEAD/po/crh http://l10n.gnome.org/vertimus/ekiga/HEAD/po/crh http://l10n.gnome.org/vertimus/gnome-menus/HEAD/po/crh http://l10n.gnome.org/vertimus/gnome-panel/HEAD/po/crh http://l10n.gnome.org/vertimus/gnome-session/HEAD/po/crh Claude Paroz wrote: > > The exact release date of each module may be different, depending on the > time frame the maintainer has to do it. > But you can still continue to translate for 2.26, as most distributions > include also the .1 release (and maybe even .2 or .3). > When a module branch its development, it is recommended for translators > to commit in both branch and trunk. P.S. On that subject, if i send another email in 24 hours, can some more stuff get committed on Tuesday, so that it's shipped on Wednesday w/ 2.26.0? - -- Thanks. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJvd8nLWBb0X5S4xURApbkAKCTClnP6OcU9HVstROEOoNVfECV6QCeJnMy iaavrf1x21XWfOOHpjZgzWM= =mOYl -----END PGP SIGNATURE----- _______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n