Translating talk:StatusNet

Message docs and message source does not match. Docs say that the error is permanent, while message source indicates it is a temporary error.

Fixed in source. Should be updated soonish.

Very technical. Can't it be just "The site must have a name"?

Fixed in source. Should be updated soonish.

Docs say this is a client error, but in that case why doesn't it just say "The file is too big"?

Fixed in source. Should be updated soonish.

More docs needed what does Bio mean in this context.

Fixed in source. Should be updated soonish.

CLOSED This issue is closed by Siebrand

The source update was accidentally done on the translation. Edit: Hmm ... no, the !!FUZZY!! was interpreted as a translation.

Not sure what you mean.

The message was fuzzied. Instead of appearing on translate it already appeard on proofread.

It was imported as a fuzzied message, probably because it was added by gettext tools automatically.

to what refers this 'you'? to 'you and somebody like this?'

then german translation would be 'Dir' ... 'gefällt das', instead of 'Du und jemandem gefällt das'.

See message documentation: Reference to the logged in user in favourite list.

okay, thank you. changed it to 'Dir'.

What is "it"?

"it" is a group the user will be blocked from by clicking the button.

Thanks.

What does pinging mean here exactly?

The description says that "#. TRANS: Plural is decided on the total number of users liking the notice (count of %%s + %d)."

In fact this would be useful only for deciding the plural form of the verb, but wrong for deciding how to generate the correct singular or plural form of "other/others" which is NOT the total number of users, but only %d (which may be only 1. When this extra number is zero, another resource is used, without "and %d other(s)".

As Gettext cannot take several numbers to generate plurals, it would be more convenient to simply separate the expression "%%s and %d other(s)", to be generated first (using total minus 4, when the total is larger than 4), before inserting the generated string into "%%s liked this", which will take the singular or plural form of the verb according to the total number of users.

Please read the help. It's clear. The code is also correct.

No ! It is INCORRECT, because the generated plurals are just for conjugating the verb.

Here it is ALWAYS plural in French because the verb is conjugated according to the total, but the term "autre" takes the singular or plural. This is equally true in English. E.g. in English : "Peter, Paul, Jack, John and 1 others liked this". 5 people total, but only 1 "other"; the verb is always conjugated as with the plural "they". "Peter, Paul, Jack, John and 10 others liked this". 14 people total, but 10 "others"; the verb is always conjugated as with the plural "they", "others" is now correct.

Please reconsider my message, the description does not solve the problem for "other/others" and the plural is needlessly tested on the verb which will always be conjugated with the plural (in most languages, except Slavic languages that have complex rules for plurals ignoring the hundreds and with several other forms using a genitive for some units) as there are always at least 5 people concerned in the subject.

Note also that the effective code passes the number ($count - 3), not ($count) to gettext, so the plural form will be selected by Gettext according to the wrong number. This will fail for all Slavic forms (for which you must pass up to 4 distinct forms to gettext).

If the code was supposed to pass the number of "other(s)", it should be ($count-4), not ($count-3). And you would have no hint to correctly conjugate the verb !

In other words, the message is buggy, but the code too ! The only "safe" translation is to assume the plural everywhere, without even using the plural template syntax in the message.

Note that for Slavic languages (Russian, Serbian, Czech, Slovak, Bulgarian...), Gettext will be used like this with the template syntax shown: dual See the declaration of plural conditions at the beginning of .pot files for those languages, which determines the number of forms taken for number forms (usually you don't need to provide it, TranslateWiki.net already knows that and generate the line for you for each supported language)

You're using too much text. Please go file a bug report and walls of text somewhere else.

Can you propose a different wording? Or clarify more the context? I'm not sure about my translation. Thanks!

PLURAL should be applied for both parameters separately. Or message should be broken on two/tree if StatusNet could not support this.

 Fixed in code. Still is ugly, though... You'll see :).

Space between sentences is missing. Will be good idea to check other messages for similar problem.

 Fixed. Fixed in code, should be updated soonish. Thanks for spotting that!

Where is the statusnet-i18n mailing list? the link is broken here...

I've asked on the statusnet IRC channel. Will let you know if there is a reply. You can also use the StatusNet bug tracker at http://status.net/open-source/issues.

What do these messages mean when they refer to "salmon"?

• Ostatus-2a74b95df9ef4a88fa54d1a9f322bcd7dd8f980a-Salmon invalid actor for signi (“Salmon invalid actor for signing.”)
• Ostatus-d109a2b46125ad81313cd02d38c9ecf69c705036-Salmon requires "application m (“Salmon requires "application/magic-envelope+xml".”)
• Ostatus-330315b2738133ffa86b665e49d7ea28c968baae-Salmon signature verification (“Salmon signature verification failed.”)
• Ostatus-500f991631de906d2ca665676cce92c3f4923fc3-Salmon post must be an Atom en (“Salmon post must be an Atom entry.”)
• Ostatus-05018fa68d1e0043d1906dc8598aa3bbeb338adc-Received a salmon slap from un (“Received a salmon slap from unidentified actor.”)

The Salmon Protocol is an open, simple, standards-based solution that lets aggregators and sources unify the conversations. In OStatus, Salmon is used as the messaging transport for comments, replies, and notifications between users[1].

OK, I have translated "Salmon" as "Salmon protocol" in Galician messages to improve understanding. Thanks!

...on the Yammer side or ...on the Yammer site? Is that a typo?

Not a typo. Means "in Yammer" or "on the side of Yammer".

Thanks, I wasn't sure about that.

This message contains trailing white space (see backslash at the end). Will be good idea to check all StatusNet messages for similar issue, since it's second one I found.

 Done Fixed in code. Will be active after next update (found two more).

Is trailing backslash intentional or jut mistake?

There is probably trailing whitespace in the source

correct.

Removed from source code. Updated after next export/import.

Email subjects shouldn't have a full stop.

Fixed in code. Will be updated after next update.

Should say 'List', similar to the issue in Thread:Support/About_StatusNet:42744ef97c02abe958450d194e1797e876145d93-Tagged/ar. Please see also:

• StatusNet:Ostatus-8e4b765c0848c91ebbe805a8e3f51410c8f9ead3-Tag_s/en
• StatusNet:Ostatus-6f2c713c7ab418dc46c310865e2bb00d70476b99-Nickname of the user you want/en

Fixed in code. Should be updated soonish.

Other button titles do not end in dots. I don't really know whether titles should or shouldn't end in dots, but please either remove the dot from this message or add ones to the others. See also:

• StatusNet:23768afb237c0887b84de9aefc0deca63fdbc47e-Favor this notice/en
• StatusNet:1e7193628116f76c8e2033448fd0cf889543f651-Delete this notice/en
• StatusNet:57ea18307c97125fec0d3725713273434f9a8846-Reply to this notice/en

All sentence like button titles should end with a period, and most do. Not high priority to change, I'll take care of it someday. Thanks for the report.

Would it help if I committed the change so you can pull to the upstream?

Possibly. I haven't done that yet, but I'll try if you do... Bare with me, please :).

I've made a few code changes (more than you have highlighted above). It's probably not yet fully consistent, but at least more consistent now :).