Bug 441858 - Please add pam_krb5 to transifix
Summary: Please add pam_krb5 to transifix
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora Localization
Classification: Fedora
Component: l10n-requests
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Dimitris Glezos
QA Contact: A S Alam
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-10 15:42 UTC by Nalin Dahyabhai
Modified: 2013-07-03 00:49 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-04-10 19:16:24 UTC
Embargoed:


Attachments (Terms of Use)

Description Nalin Dahyabhai 2008-04-10 15:42:53 UTC
Module name: pam_krb5
Description: A module which allows PAM-aware applications to use Kerberos for
checking passwords.
Project webpage: 
VCS root, module, branch: ssh://git.fedorahosted.org/git/pam_krb5.git, N/A, master
File filter (eg. `.*/po/.*`) /po/.*
Changelog file (if applicable) /ChangeLog
Web front-end to VCS: http://git.fedorahosted.org/git/pam_krb5.git/

Thank you!

Comment 1 Dimitris Glezos 2008-04-10 19:16:24 UTC
Thanks Nalin. Project added and tested on Transifex.

  https://translate.fedoraproject.org/submit/module/pam_krb5/

Translation statistics page should show up in a few hours.

  http://translate.fedoraproject.org/module/pam_krb5/

Note that currently the POT creation fails using intltool, and the statistics
will *not* show up for translators, because of the following error:

$ intltool-update -r
ERROR: xgettext failed to generate PO template file because there is non-ASCII
       string marked for translation. Please make sure that all strings marked
       for translation are in uniform encoding (say UTF-8), then *prepend* the
       following line to POTFILES.in and rerun intltool-update:

           [encoding: UTF-8]

Please make sure the above command does produce a POT file successfully (even if
a POT is provided). For more information you can refer to
http://fedoraproject.org/wiki/L10N/FAQ#error-no-pot.


Note You need to log in before you can comment on or make changes to this bug.