translation

English: The reason we have deprecated the nynorsk (nno) and the norwegian (no) projects at drupal.org is that we are promoting the correct use of language codes for Norwegian Bokmål and Norwegian Nynnorsk, which are nb and nn respectively. A patch has been sent as an issue at drupal.orgs Issue Tracker to support this standardization. Hopefully, this will be implemented from Drupal 6.x

In the meantime, we at Drupal Norge would like to remind everyone to support this journey to standardized norwegian language codes in Drupal by correcting their sites. Instructions on this matter are to be found in both english and norwegian versions.

Instructions in english:
http://drupal.org/project/nb
http://drupal.org/project/nn

Instructions in norwegian can be found in the norwegian Drupal handbook (Installering og grunnleggende konfigurering):
http://www.drupalnorge.no/bok/installering-og-grunnleggende-konfigurerin...

The instructions are for those who are installing the norwegian language/s from scratch. If you use «no» on your existing site and need help or support in changing it to nb or nn, you can create a support ticket at http://www.drupalnorge.no/support.

[scroll down for English version]

Adjunto un archivo "po" para la localización del Drupal 5.0
Es mejor que uno simplemente exportado del 4.7 porque hemos agregado muchos términos que faltan en 5.0.
Pero no es completo.
El grupo debería trabajar juntos para completarlo y normalizarlo para argentina.
El archivo está listo para utilizar en poedit (los seteos para los plurales está ajustado).
Discutiremos en la próxima reunión como proceder, entre tanto, utilizar y que les venga bien, y ... agreguen términos!

Comme vous l'aurez peut-etre remarqué, le site de la traduction francaise de drupal (drupalfrancais.zapto.org) est désormais drupalfr.org. Il est important pour nous de remercier Patechinois qui nous a fourni jusque la un peu de place sur son server ainsi que son temps.

Ce premier changement marque ainsi le début d'une série d'évolutions qui ont pour but d'améliorer le site, de rendre drupalfr plus proche de vos attentes, et de vous faire découvrir tout le potentiel de ce superbe outil qu'est drupal.

D'autres surprises sont aussi à venir...

I've managed to completely translate E-Commerce modules to German. Translation is based on 4.7 and needs a one-liner-patch to cart.module (missing t()-function). So now I've got 9 gettext files and 1 mini patch I'd like to contribute.
After several hours of translating, testing and translating I don't want to create one issue for each file, so can I please mail them to someone to commit them? (gordon?) I doubt I should use the file attachments here. So please come by and help me to get this in!

My motivation is to get more German users to E-Commerce. Drupal with E-Commerce is a fantastic solution compared to other online store systems like osC, xtC, JOS VirtueMart and so on. Altogether we have to remedy some major deficiencies in E-Commerce, f.e. the incomplete tax system and some legal rules we have to implement for usage of E-Commerce in Germany/Europe and even more important for selling internationally (different currency and tax per language and the like).

Hi there,

I would like to participate in this project, since I am in touch with a group of translators who belong to various non-commercial organizations and who would richly benefit, and I have promised to help them get up a group collaboration site for translating, and I cannot do it on my own. Even if I could, it would not be as good as a group effort.

And many would benefit from such a site.

I have hosting and could host a site for us to prototype on.
Would like to have a discussion on requirements.

I suggest to limit such a suite to online translations. Some backend scripts should periodically extract these and merge the PO files against the Drupal core and contrib POT files.