help-gss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gss-1.0.4 released [beta]


From: Simon Josefsson
Subject: Re: gss-1.0.4 released [beta]
Date: Sun, 07 Aug 2022 14:44:32 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)

Benno Schulenberg <coordinator@translationproject.org> writes:

> Hello Simon,
>
> Op 06-08-2022 om 15:45 schreef Simon Josefsson:
>>   https://alpha.gnu.org/gnu/gss/gss-1.0.4.tar.gz
>>   https://alpha.gnu.org/gnu/gss/gss-1.0.4.tar.gz.sig
>
> Hmm... why is this on alpha, when the other 1.0.* are on ftp?

Hi Benno.  My mistake, gnulib's release scripts allows alpha, beta and
stable as targets, and I thought only alpha ended up on alpha.gnu.org,
but it seems beta also ends up there.  I have uploaded it to ftp.gnu.org
now, will probably take a while until all mirrors has it.

> Also, may I request that the following msgid be split into three
> separate ones?
>
>  msgid ""
> +"  -a, --accept-sec-context[=MECH]\n"
> +"                    Accept a security context as server.\n"
> +"                    If MECH is not specified, no credentials\n"
> +"                    will be acquired.  Use \"*\" to use library\n"
> +"                    default mechanism.\n"
> +"  -i, --init-sec-context=MECH\n"
> +"                    Initialize a security context as client.\n"
> +"                    MECH is the SASL name of mechanism, use -l\n"
> +"                    to list supported mechanisms.\n"
> +"  -n, --server-name=SERVICE@HOSTNAME\n"
> +"                    For -i and -a, set the name of the remote host.\n"
> +"                    For example, \"imap@mail.example.com\".\n"
>
> It would make things much easier for translators, especially when one day
> there would be a small change in one of those lines.
>
> (There is no need to split also the other large msgid -- better not, in fact,
> because it would invalidate current translations.  But when adding new texts,
> or changing existing ones, please think of the translators and make their task
> easier.)

I'm preparing a fix now, so the gss.pot file now looks like below.  I'll
probably do a 1.0.5 with some minor fixes in the following week, so you
may hold the announcement if you want...

#: src/gss.c:87
msgid ""
"  -a, --accept-sec-context[=MECH]\n"
"                    Accept a security context as server.\n"
"                    If MECH is not specified, no credentials\n"
"                    will be acquired.  Use \"*\" to use library\n"
"                    default mechanism.\n"
msgstr ""

#: src/gss.c:93
msgid ""
"  -i, --init-sec-context=MECH\n"
"                    Initialize a security context as client.\n"
"                    MECH is the SASL name of mechanism, use -l\n"
"                    to list supported mechanisms.\n"
msgstr ""

#: src/gss.c:98
msgid ""
"  -n, --server-name=SERVICE@HOSTNAME\n"
"                    For -i and -a, set the name of the remote host.\n"
"                    For example, \"imap@mail.example.com\".\n"
msgstr ""

/Simon

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]