Translation documents out of date?

joachim: I am confused about this too. Yes, localize.drupal.org exists, but I am not sure that it imported existing .PO files, and I don't think that the packaging scripts for modules are using localize.drupal.org yet. But I'm not sure. Probably this discussion should be brought to the attention of someone who does know the answers, but I'm not sure who that is either...

Good idea to ping Gabor and see if he will chime in on this issue. I am leaving in 10 minutes for a week of vacation though, so I cannot pursue this now. Sorry!

Localize.drupal.org will not import .po files from existing packages. Translation teams already do this, and they already complain about the high volume of suggestions waiting without approval. So to make this workable for team leads / moderators, the existing .po files are not at all imported.

"Packaging" of .po files will not be tied to the packaging of projects themselves. Please read http://localize.drupal.org/faq and if that was not clear, maybe http://hojtsy.hu/blog/2009-jul-30/localizedrupalorg-come-life-so-what-ab... and let me know if the FAQ was not clear enough and needs more info.

I think this issue was referencing docs on drupal.org Handbook, which are likely out of date.

So what we need to do is make sure that the docs here on drupal.org in the Handbook are referencing the docs on localize.drupal.org, rather than trying to synchronize them, I think?

The eventual goal is that drupal.org will document localize.drupal.org as discussed earlier. I'm not building out further docs and only included a quick FAQ for this reason.

i'm not totally up to speed on what's going on at localize.drupal.org - so do either http://drupal.org/handbook/modules/locale or http://drupal.org/handbook/modules/translation or their subpages need to be modified? like jennifer is saying, rather than duplicating efforts, maybe we ought to be cutting back on the content that is in the handbook and linking to l.d.o pages?

@arianek: the l.d.o pages do not allow for community editing of docs, and setting up the same infrastructure as the d.o docs is duplicating efforts. The l.d.o docs are a stopgap before people (including to some degree myself) can get around to update docs on drupal.org.

ahh, ok gabor, i didn't realize they weren't editable. we will carry on business as usual then!

bump. This just came up on IRC today and we do need to update the doc still.

Looks like the docs at http://drupal.org/node/188986 could still use an update - there's no mention of localize.drupal.org there. I'd be happy to take that on, but would want someone to review before I post my changes.

pagaille: If you want to create the doc somewhere and review before posting, I am sure we can find someone to review the changes. You can post here. Thanks!

I'm happy to help review stuff if you point me what to review (and its not a 100 page structure :).

adding tags

I worked A LOT on this in the past few weeks and I think we are in a much better shape now. However, some of the above mentioned issues are indeed not yet solved.

Thanks Gabor! Do you have a list of things that still need addressing? We're having a docs sprint this weekend (no promises).

@jhodgdon: I looked through the above, and already fixed http://drupal.org/node/188986 too. Generally it would be great if someone with a fresh mind can read through the current docs and spot inconsistencies. Basically it needs to communicate the following:

1. If you are a module/theme/distro maintainer, just (a) use the localization API properly, (b) tag releases (vs. -dev releases). If you do these two, localize.druupal.org will automatically support your project. You don't need to do ANYTHING else. No .po and .pot files in CVS anymore. This is documented in short at http://drupal.org/node/188986

2. If you are a translator, localize.drupal.org is the way to go. Your translations are automatically exported in .po files at most weekly. These are available from ftp.drupal.org like other drupal.org project packages. This is somewhat documented on http://drupal.org/node/302194 If you as a translator want to work offline, you can still work with .po files, but those are not maintained in CVS anymore.

3. If you are a user, use translations from localize.drupal.org, translations in d.o projects are outdated and are phased out. You can use http://drupal.org/project/l10n_install to install Drupal right away with those translations and http://drupal.org/project/l10n_update on existing sites to keep translations updated for your modules. (I don't think this is documented yet on d.o).

These are the basics, and I worked on the docs to update it for 1 and 2 recently. Don't think 3 is documented already. Basically, the docs might be inconsistent still and not fully updated. So it would be great if someone can read it through with a fresh mind and check if it is consistent and provides the above basic messaging.

Thank you.

OK. I will give the docs a review as per whether it's communicating as outlined in #17. Thanks Gabor!

I've reviewed the existing doc...
http://drupal.org/node/188986 - Best Practices page - has a small section on Translation, and it looks good to me, and points correctly to other references.
http://drupal.org/contribute/translations - Translate Drupal section of Getting Involved - and sub-pages - I did some minor edits, and note that one of the sub-pages (the one that goes into details) does mention the internationalization server/client modules in #3 in the previous comment.
http://drupal.org/node/303984 - Multilingual support section of module dev guide - needed some work, as it was still talking about PO files
http://drupal.org/node/322729 - section on the translation process was still talking about PO files

These pages need additional editing or attention:
http://drupal.org/node/11311 -- I can't figure out how or if this fits into the translation process? Also this applies to its two child pages
http://drupal.org/node/202631 - I think this page just needs to go away completely?

http://drupal.org/node/303984 - thanks, looks good

http://drupal.org/node/322729 - thanks, looks good as well (the subpages will need several updates for Drupal 7's API, but that is entirely outside the scope of this issue :)

http://drupal.org/node/11311 - is I think can still be useful for old hats who used several small files previously

http://drupal.org/node/202631 - should indeed go away completely; FYI there are new (again, better :) processes coming up with localize.drupal.org (not just for Drupal 7), that will be better documented soon on the localize.drupal.org news, and probably as further edits to the docs that I'll make; some of the tools are in development and cannot yet be documented, so that is in progress

OK, I made 202631 go away completely.

Regarding http://drupal.org/node/11311 -- I thought we weren't really using PO and POT files any more, so I wasn't sure if having this page here would be confusing. Maybe it needs an update to say what to do with the files when you're done, or something at the top explaining that it's of use only in situation ...

Hmmm... So just when is this page useful? I guess I think it needs some context.

tagging

Suscribing

The docs have been updated. THis issue is outdated.