I created a .pot file from version 6.x-1.0-rc2 using the Translation template extractor (http://drupal.org/project/potx) which can be translated using a tool like Poedit (http://www.poedit.net).

The translation files should be copied to a yet to be created "translations" sub-folder in the module folder.

hth
Frank

CommentFileSizeAuthor
#13 privatemsg_pot4.patch17.29 KBberdir
#12 privatemsg_pot3.patch30.31 KBberdir
#9 privatemsg_pot2.patch31.52 KBberdir
#8 privatemsg.pot.patch26.64 KBberdir
privatemsg.pot10.08 KBfrank ralf

Comments

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Needs work

Thanks, but please re-create the file for the -dev release, there were many many changes since rc2.

Edit: Also, I can see from your profile that you do have CVS access. You should be able to commit that file yourself, every translations directory is writable for all developers.

frank ralf’s picture

frank ralf commented

Have just committed that file (http://drupal.org/node/293907#comment-1525810). Will re-create it for the dev release.

Frank

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

You should create a pot (and po) per submodule, so that only translations that are actually used are loaded when you enable the module.

frank ralf’s picture

frank ralf commented

Hi Sascha,

I thought about that but think one pot/po file per module is a better approach because that way it's easier to maintain a consistent translation across all sub-modules.

Doing so won't create any overhead IMO. Drupal loads all provided translations at install time into the locales_source and locales_target tables in the database. The t() and locale() (http://api.drupal.org/api/function/locale/6) functions do a just-in-time translation for all the strings on a loaded page and will retrieve the translated strings from the database tables if present. If not, those strings will be added to those tables.

So creating separate pot/po files for each sub-module would only save some space in the database and even that only if you never installed that sub-module. As the current pot file is only about 12 KB I think this effect is negligible.

So I would suggest sticking to one pot/po file.

Cheers,
Frank

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

AFAIK it's common to use multiple files, a example:

./date/date_repeat/translations/date_repeat.pot
./date/date_copy/translations/date_copy.pot
./date/date/translations/date.pot
./date/date_php4/translations/date_php4.pot
./date/date_popup/translations/date_popup.pot
./date/date_timezone/translations/date_timezone.pot

Same for CCK, FileField and many others.

frank ralf’s picture

frank ralf commented

As I see this as a general issue I moved this discussion over to the Internationalization User Group (http://groups.drupal.org/node/21731).

Frank

litwol’s picture

litwol commented

I feel that it is always a good idea to keep related items together, the whole point of breaking the private message functionality into sub-modules is to give options and ultimate flexibility to the users of privatemsg. On that same note i think translations are not exempt from the same approach. Users shouldn't need to clutter their DB with translations that do not need to be translated for various reasons.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Version: 6.x-1.0-rc2 » 6.x-1.x-dev
Status: Needs work » Needs review
StatusFileSize
new privatemsg.pot.patch26.64 KB

The attached patch does update the *.pot files and also splits them up per sub-module. The diff against privatemsg.pot is pretty much useless, though... :)

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
StatusFileSize
new privatemsg_pot2.patch31.52 KB

Updated the patch, will commit this soon.

I used --mode=multiple and all strings that occur in multiple modules are part of privatemsg.pot.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Needs review » Patch (to be ported)

Commited, needs to be done for 7.x too

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Patch (to be ported) » Fixed

Commited to 7.x. This will need another update short before the 1.0 release but is fixed for now.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Fixed » Patch (to be ported)
StatusFileSize
new privatemsg_pot3.patch30.31 KB

Updated to include the latest chance, the strings should now be fixed for the 1.0 release.

Note that this does also partly revert the change from http://drupal.org/cvs?commit=292344 since that commited merged all strings into a single file again.

I wil commit this to 6.x-1.x-dev now.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
StatusFileSize
new privatemsg_pot4.patch17.29 KB

A few more changes because of the paging issue. Committing this against 6.x-1.x-dev now. Fixes also a typo and double escapes in the german translation.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Component: User interface » Code
Status: Patch (to be ported) » Fixed

I'm closing old translation related issues, translation should be handled on localize.drupal.org now.

Please see Maintainer News dec 7 2010 for more information:

A. If you are a translation maintainer: you've already been contacted, and
your team is in the process of moving from drupal.org to localize.drupal.org.

B. If you are a translator: stop working on .po files in CVS (either for
Drupal core or contrib), instead import existing .po files from CVS to
localize.drupal.org (if not already), remove the imported file from CVS and
work on localize.drupal.org from now on.

C. If you are a drupal.org project maintainer: do not accept .po files
anymore in your issue queues and remove your .pot files from CVS; tell people
to use localize.drupal.org.

Status: Fixed » Closed (fixed)
Issue tags: -translation, -template, -.pot file

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +translation, +template, +

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Issue tags: -translation, -template, -.pot file

I am removing issue tags used from one to four issues. I apologize for bumping the issue.