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

Re: [RFR2] Smuxi po templates



On Sat, 21 Nov 2009 14:16:28 +0000
Justin B Rye <jbr@edlug.org.uk> wrote:

> Mirco Bauer wrote:
> >>> #: ../src/Frontend/SshTunnelManager.cs:366
> >>> #, csharp-format
> >>> msgid ""
> >>> "Couldn't get OpenSSH version (exit code: {0})\n"
> >>> "\n"
> >>> "SSH program: {1}\n"
> >>> "\n"
> >>> "Program Error:\n"
> >>> "{2}\n"
> >>> "Program Output:\n"
> >>> "{3}\n"
> >>> msgstr ""
> >> 
> >> What "get" means in this? Use? Find? Really download?
> > 
> > It starts the ssh application and tried to read the version number
> > from it. If that fails for some reason the above error messages
> > will be shown. retrieve? parse? I don't know better terms for this
> > one :)
> 
> I suppose there's the alternative of phrasing it as something like:
>    "OpenSSH version not found (exit code: {0})\n"
> ...but I'm not sure it helps.

It doesn't look for a specific version. It want's to check what the
currently installed OpenSSH version is.

> 
> >>> #: ../glade/smuxi-frontend-gnome.glade.h:60
> >>> msgid ""
> >>> "The nickname to use. You can specify extra nicknames (separated
> >>> by spaces) " "which will be used as fallbacks when the first
> >>> choice is not available. By " "default $nick_ and $nick__ will be
> >>> used as fallback." msgstr ""
> >> 
> >> Should the last word be "fallbacks"?
> > 
> > This is what Justin B Rye <jbr@edlug.org.uk> wrote, to me it
> > doesn't look correct either as there are 2 named nicks to be used
> > as fallback.
> > 
> > Justin any comment on this?
> 
> I was thinking of the whole thing as fallback behaviour, but now you
> mention it, yes, plural is better.

OK, taken.

> 
> >>> #: ../src/Frontend-GNOME/Views/Chats/GroupChatView.cs:233
> >>> #, csharp-format
> >>> msgid "Syncing chat persons of {0}..."
> >>> msgstr ""
> >> 
> >> Hmm. I don't understand what the string means. (Would make it hard
> >> to
> > > translate. ;-) Could it be rephrased?
> > 
> > I know it's very technical, what about:
> > // TRANSLATOR: {0} is the name of the chat
> > Retrieving chat attendees of {0}...
> 
> I've never seen the word "attendee" used outside the context of
> business functions and conventions.  (The word also has a more
> logical-seeming sense as "person served by attendants", but that's
> archaic.)
> 
> I wouldn't use the word "chat" that way, either.  As a non-count
> noun, "chat" can refer to the communications medium; but "a/the 
> chat" has to be in the sense of a conversation (probably offline).
> The "place" you go to for an online chat session isn't a "chat",
> it's a channel, group, chatroom, board, or whatever.  Maybe you
> should just leave it out.
> 
> I'd suggest something like:
>   Retrieving channel residents of {0}...
>   Checking current population of {0}...
> or indeed
>   Performing census of {0}...

Hm all of them sound horrible.... "Retrieving channel residents of {0}"
is pretty close though. The term channel is specific for the IRC
protocol while Smuxi is not an IRC-only chat application.
What about:
"Retrieving chat room users of {0}..." that should be protocol neutral
but hopefully understandable by someone else too :)

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey@meebey.net  http://www.meebey.net/
PEAR Developer    meebey@php.net     http://pear.php.net/
Debian Developer  meebey@debian.org  http://www.debian.org/


Reply to: