Re: [bug-mailutils] Issues with translations

[Sergey Poznyakoff]

> I more or less have ready a Catalan translation which we can use to test
> stuff. At least two of us can read it ;)

Great :^)

> There's a few problems with the pot file.
> Two messages have \r's at the end, which Gettext isn't happy about.
> #: comsat/action.c:338

OK, I'll fix it.

> Two messages have a "\v" in them, which gets "translated" as a ^K
> character in the pot file:
> 

It's a bit harder to fix. These are used in help messages, argp
understands them as an instruction to "place this string after the
option list". The same effect can be achieved by carefully arranging
priorities for the help strings. This will require some
experimenting... Looks like a gettext bug.

> There's the message:
> #: pop3d/user.c:92
> #, c-format
> msgid "Possible probe of account '%s'"
> 
> Does this mean someone is possibly attacking this account with a
> dictionary probe? I guess it could be clarified.

Sure. This means that someone attempted to check for the existence
of the given account (this doesn't imply any attempt to crack the
password). For the pop3 it is done by issuing USER command immediately
followed by QUIT.

> 
> Finally, I have a few context problems in a few messages, or problems
> in general :)
> 
> #: readmsg/readmsg.c:44
> msgid "Output formfeeds between messages"
> 
> What is a formfeed?

That is ASCII 014, or \f in C notation. It makes line printer devices
eject the page. I've never heard the term in Catalan, I guess its
meaning can be rendered as "entrega de foli" or "Lliurament de foli".

> #: sieve/sieve.c:80
> msgid "Ticket file for mailbox authentication"
> 
> What is a ticket file? How is it used?

It's a file containing user's credentials to connect to the remote
mailbox via pop3 or imap4d protocol. It is used to avoid typing
the user name and cleantext password in the mailbox url when
invoking a mailutilts utility.

> Oh, and the typo:
> 
> #: pop3d/popauth.c:55
> msgid "GNU popauth -- manage pop3 authentcation database"

Oops! We should use Ispell more often, I guess :)

Regards,
Sergey