Here comes the Swedish translation.

Some features I would like to be changed:
The date when the revisions was last saved is not able to translate.

The string "A !page displaying your T&C will be automatically created, access to this page can be set via the !access administration page."
Is it needed to have "!page"? Couldn't it just be "page" so it would be translatable.

!access in the above string is not translatable either.

After I set up a document to confirm, every user but #1 could not log in. It complained about permissions.
If I allow the user to create the account himself the confirmation shows up and everything seems ok.

Cheers
/Magnus

CommentFileSizeAuthor
#3 sv.txt6.33 KBmagnus
sv.txt6.47 KBmagnus

Comments

robert castelo’s picture

robert castelo commented

Thanks, we're building up a good set of translations for this module :-)

!page and !access should be translatable, they get filled in by array('!page' => l('page', 'legal'), '!access' => l('permissions', 'admin/user/permissions')), and the two link labels are passed to the translation layer by l().

robert castelo’s picture

robert castelo commented
Status: Active » Closed (fixed)

Added.

magnus’s picture

magnus commented
Version: 6.x-7.x-dev » 6.x-2.0-beta1
StatusFileSize
new sv.txt6.33 KB

Updated the translation.

magnus’s picture

magnus commented
Status: Closed (fixed) » Patch (to be ported)
robert castelo’s picture

robert castelo commented
Status: Patch (to be ported) » Fixed

Thanks - I'll add to the next revision.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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

magnus’s picture

magnus commented
Version: 6.x-2.0-beta1 » 6.x-7.x-dev
Category: feature » task
Status: Closed (fixed) » Fixed

Imported Swedish translation to localization server and removed CVS file.

If anyone wonder why the translation is gone, please see Maintainer News dec 7 2010:

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)

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