From gdt at ir.bbn.com  Tue Aug 21 10:29:30 2007
From: gdt at ir.bbn.com (Greg Troxel)
Date: Tue, 21 Aug 2007 10:29:30 -0400
Subject: [Greg Troxel] [OTR-dev] finished converstations a bad UI choice!
Message-ID: <rmihcmt9d11.fsf@fnord.ir.bbn.com>

The scenario I described in the attached message happened again today.  

Any thoughts?  Do people disagree with how I think things should work?
Is it just a question of not enough round tuits to implement it?
If I send a patch to do behavior 2 below, will it be accepted?

I'm on the verge of stopping using OTR.

-------------- next part --------------
An embedded message was scrubbed...
From: Greg Troxel <gdt at ir.bbn.com>
Subject: [OTR-dev] finished converstations a bad UI choice!
Date: no date
Size: 2734
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20070821/44ab1c67/attachment.mht>

From ian at cypherpunks.ca  Tue Aug 21 20:45:35 2007
From: ian at cypherpunks.ca (Ian Goldberg)
Date: Tue, 21 Aug 2007 20:45:35 -0400
Subject: [Greg Troxel] [OTR-dev] finished converstations a bad UI choice!
In-Reply-To: <rmihcmt9d11.fsf@fnord.ir.bbn.com>
References: <rmihcmt9d11.fsf@fnord.ir.bbn.com>
Message-ID: <20070822004535.GR15409@yoink.cs.uwaterloo.ca>

On Tue, Aug 21, 2007 at 10:29:30AM -0400, Greg Troxel wrote:
> The scenario I described in the attached message happened again today.  
> 
> Any thoughts?  Do people disagree with how I think things should work?
> Is it just a question of not enough round tuits to implement it?
> If I send a patch to do behavior 2 below, will it be accepted?
> 
> I'm on the verge of stopping using OTR.

There's certainly always the tuit problem, and I'm sorry I haven't had a
chance to reply sooner.  I'm still not totally convinced your solution
is strictly better, though.

> There are then two cases:
> 
>   OTR is enabled, with automatic initiation, but not required)
> 
>     Here, we know that OTR recently worked with this peer.  So choices
>     are
> 
>        0) send in clear - dangerous, violates user expectations
>        1) fail (current behavior)
>        2) try to initiate, and send message if negotatiation is successful
> 
>   OTR is enabled, with automatic initiation, and further is required)
> 
>     Here, there are two choices
> 
>        0) send in clear - against stated policy, dangerous
>        1) fail
>        2) try to initiate, and send message if negotatiation is successful
> 
> 
> In the required case, note that these are the same options as in a "not
> private" state.  But in "not private", otr-gaim does option 2, which is
> useful and what the user expects.  In the 'not required' case, option 2
> seems preferred - a savvy user can always 'end private' if that's what
> they want.
> 
> I have no objection to "Conversation is in state finished; trying to
> initiate private conversation" message.
> 
> I realize this is work to change.  But does anyone really think that the
> current behavior is useful and reasonable?  To me it's gratuitously
> difficult when there's a better behavior without security problems.

The problem occurs when your buddy ends the private conversation and
then logs in again, when they're *not* set to "required".  What with the
limited set of clients that currently support OTR (more now than when
the feature was implemented, admittedly), it's totally possible that
your buddy does not in fact support OTR any more.  So at best,
libotr could send an automatic OTR Query message (which would annoy
your buddy if that's indeed the case).

If libotr stashed the plaintext in the same way as when you type
something in "required" mode, it would in fact get automatically sent if
your buddy does support OTR, but something mysterious would probably
happen otherwise, that could probably only be detected by a super-ugly
timeout or something like that.

So it's not so much that there hasn't been a tuit to implement a
solution to this problem, but rather that there hasn't been one to spec
it, I think.

Does that make sense?  All that having been said, I'd be totally happy
to see someone spec a solution, or better, supply both a spec and then a
patch. ;-)

Thanks,

   - Ian


From gdt at ir.bbn.com  Wed Aug 22 09:37:41 2007
From: gdt at ir.bbn.com (Greg Troxel)
Date: Wed, 22 Aug 2007 09:37:41 -0400
Subject: [Greg Troxel] [OTR-dev] finished converstations a bad UI choice!
References: <rmihcmt9d11.fsf@fnord.ir.bbn.com>
	<20070822004535.GR15409@yoink.cs.uwaterloo.ca>
Message-ID: <rmilkc3ellm.fsf@fnord.ir.bbn.com>

Ian Goldberg <ian at cypherpunks.ca> writes:

> On Tue, Aug 21, 2007 at 10:29:30AM -0400, Greg Troxel wrote:
>> Any thoughts?  Do people disagree with how I think things should work?
>> Is it just a question of not enough round tuits to implement it?
>> If I send a patch to do behavior 2 below, will it be accepted?
>
> There's certainly always the tuit problem, and I'm sorry I haven't had a
> chance to reply sooner.  I'm still not totally convinced your solution
> is strictly better, though.

Thanks for replying.  I certainly agree that deciding on the proper
behavior is hard; my big point was the current behavior is a problem.

> So it's not so much that there hasn't been a tuit to implement a
> solution to this problem, but rather that there hasn't been one to spec
> it, I think.

For discussion, I'll assume that Alice is in state finished and Bob
has reappeared.

So if Alice has Bob configured to "required", do you agree that Alice's
OTR implementation should auto-initiate and send if a message is
entered?  I don't see any downside to that. (Except for maybe getting
fussy about private vs unverified and a downgrade attack there.  But
that's really not about finished - it's more general and I think should
be addressed separately.)

> The problem occurs when your buddy ends the private conversation and
> then logs in again, when they're *not* set to "required".  What with the
> limited set of clients that currently support OTR (more now than when
> the feature was implemented, admittedly), it's totally possible that
> your buddy does not in fact support OTR any more.  So at best,
> libotr could send an automatic OTR Query message (which would annoy
> your buddy if that's indeed the case).

I see your point.  It's a question of an OTR Query being annoying to Bob
(who has just used an OTR client and is now using a non-OTR client, so
he kind of deserves the poke :-), vs a baffling failure to Alice (who
isn't a cryptographer, and for whom Bob had installed OTR).

> If libotr stashed the plaintext in the same way as when you type
> something in "required" mode, it would in fact get automatically sent if
> your buddy does support OTR, but something mysterious would probably
> happen otherwise, that could probably only be detected by a super-ugly
> timeout or something like that.

While timeouts are ugly, they seem hard to avoid in all cases, and the
current behavior has led to failure to communicate in actual user
testing.  I won't suggest options to configure how to respond, as that
seems too hairy.

But, I do not understand how these two situations differ

  client in state not private, OTR required
  client in state finished, OTR required

It seems to me that the issues surrounding save text, initiate, send if
successful, are all the same.  It seems reasonable to have a timeout of
a minute or so and inform the user that negotiation failed - but even
without addressing that it seems that the same behavior as not private
is appropriate for finished.

I wonder if a popup dialog is in order in the non-required case, with
choices:

  try to re-initiate OTR
  end private conversation (warning: messages will be sent unencrypted)
  no change (stay in finished and discard message)

This seems hard, but the fundamental underlying issues really are hard.

> If libotr stashed the plaintext in the same way as when you type
> something in "required" mode, it would in fact get automatically sent if
> your buddy does support OTR, but something mysterious would probably
> happen otherwise, that could probably only be detected by a super-ugly
> timeout or something like that.

For the required case, do you agree that treating it like not private
(save message, initiate, send) is appropriate?  That's the case that's
causing me grief.

> Does that make sense?  All that having been said, I'd be totally happy
> to see someone spec a solution, or better, supply both a spec and then a
> patch. ;-)

Yes, makes sense - thanks for spending the time to think about this.


From michael.meier at mmsources.de  Wed Aug 29 16:32:06 2007
From: michael.meier at mmsources.de (Michael Meier)
Date: Wed, 29 Aug 2007 22:32:06 +0200
Subject: [OTR-dev] German translation for pidgin-otr
Message-ID: <46D5D7C6.1060903@mmsources.de>

Hello,

i've created a translation of pidgin-otr in my native language. I hope
it meets your requirements.
I have also subscribed to this list and would like to continue
maintaining the german translation for future releases.

Regards,

Michael
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: de.po
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20070829/08e4e7ff/attachment.ksh>

From ian at cypherpunks.ca  Wed Aug 29 17:50:30 2007
From: ian at cypherpunks.ca (Ian Goldberg)
Date: Wed, 29 Aug 2007 17:50:30 -0400
Subject: [OTR-dev] German translation for pidgin-otr
In-Reply-To: <46D5D7C6.1060903@mmsources.de>
References: <46D5D7C6.1060903@mmsources.de>
Message-ID: <20070829215030.GV15409@yoink.cs.uwaterloo.ca>

On Wed, Aug 29, 2007 at 10:32:06PM +0200, Michael Meier wrote:
> Hello,
> 
> i've created a translation of pidgin-otr in my native language. I hope
> it meets your requirements.
> I have also subscribed to this list and would like to continue
> maintaining the german translation for future releases.

Cool, thanks!  I'm about to go away for the long weekend, but I'll take
a closer look when I get back.

   - Ian


From cactusthesaint at yahoo.com  Wed Aug 29 18:16:18 2007
From: cactusthesaint at yahoo.com (Cactus The Saint)
Date: Wed, 29 Aug 2007 15:16:18 -0700 (PDT)
Subject: [OTR-dev] Slovene translation for pidgin-otr
Message-ID: <910558.26176.qm@web55209.mail.re4.yahoo.com>

Hello,

I made, er, begged my wife to make a Slovene translation of pidgin-otr; it's her native language.  She worked off the Slovak translation from not too long ago.  Hopefully it meets the requirements.  I have also attached the translation as a utf-8 formatted file, as I have no confidence that yahoo mail won't butcher this email.

In other news, there's a kopete otr plugin at http://kopete-otr.follefuder.org/, but I don't see that url on http://www.cypherpunks.ca/otr/  I have no affiliation with that plugin, but I asked a friend who uses Ubuntu to install it and it seems to work, so perhaps it deserves consideration for inclusion on the OTR page.

Regards,

Derek

-----

#: ../gtk-dialog.c:913 ../gtk-dialog.c:2095
msgid "_What's this?"
msgstr "_Kaj je to?"

#: ../gtk-dialog.c:924
msgid "_More..."
msgstr "_Ve?..."

#. Create the Advanced... button, and left-justify it.  This
#. * involves adding the button, and a blank label as a spacer, and
#. * reordering them so that they're at the beginning.
#: ../gtk-dialog.c:980
msgid "Advanced..."
msgstr "Podrobno..."

#: ../gtk-dialog.c:1025
msgid "Enter secret here"
msgstr "Vnesi geslo tukaj"

#: ../gtk-dialog.c:1030
msgid "This buddy is already authenticated."
msgstr "Ta kolega je ?e potrjen."

#: ../gtk-dialog.c:1049
msgid ""
"To authenticate, pick a secret known only to you and your buddy.  Enter this "
"secret, then wait for your buddy to enter it too.  If the secrets don't "
"match, then you may be talking to an imposter."
msgstr ""
"Za potrditev izberite geslo, ki ga poznate le vi in vas kolega. Vnesite to "
"geslo, nato po?akajte, da ga vnese tudi vas kolega. ?e se geslo ne "
"ujema, morda govorite z vsiljivcem."

#: ../gtk-dialog.c:1053
msgid ""
"If your buddy uses multiple IM accounts or multiple computers, you may have "
"to authenticate multiple times.  However, as long as they use an account and "
"computer that you've seen before, you don't need to authenticate each "
"individual conversation."
msgstr ""
"?e vas kolega uporablja razli?ne racunalnike, boste morda morali "
"potrditi ve?krat. ?e uporablja predal in "
"ra?unalnik, ki ga ?e poznate, ni potrebno potrjevati vsakega"
"posameznega klepeta."

#: ../gtk-dialog.c:1058 ../gtk-dialog.c:1322 ../gtk-dialog.c:1326
#: ../gtk-dialog.c:1423 ../gtk-dialog.c:1590 ../gtk-dialog.c:1750
#: ../gtk-dialog.c:1850 ../gtk-dialog.c:1935
msgid "?lang=en"
msgstr "?lang=slo"

#: ../gtk-dialog.c:1059
msgid "Click here for more information about authentication in OTR."
msgstr "Kliknite tukaj za ve? podatkov o potrditvi v OTR."

#: ../gtk-dialog.c:1063
msgid ""
"Authenticating a buddy helps ensure that the person you are talking to is "
"who they claim to be."
msgstr ""
"Potrditev kolega zagotavlja, da je oseba, s katero govorite, resni?no ta, "
"za katero se izdaja."

#: ../gtk-dialog.c:1113
msgid "Authenticating Buddy"
msgstr "Potrjujem kolega."

#: ../gtk-dialog.c:1140
msgid "Authenticating"
msgstr "Potrjujem"

#: ../gtk-dialog.c:1201
msgid "Generating private key"
msgstr "Izdelujem osebni klju?"

#: ../gtk-dialog.c:1202
msgid "Please wait"
msgstr "Prosim po?akajte"

#: ../gtk-dialog.c:1210 ../gtk-dialog.c:1627 ../gtk-dialog.c:1664
#: ../gtk-ui.c:175 ../otr-plugin.c:115 ../otr-plugin.c:212 ../ui.c:110
msgid "Unknown"
msgstr "Neznan"

#. Create the Please Wait... dialog
#: ../gtk-dialog.c:1213
#, c-format
msgid "Generating private key for %s (%s)..."
msgstr "Izdelujem osebni klju? za %s (%s)..."

#: ../gtk-dialog.c:1258
#, c-format
msgid "%s Done."
msgstr "%s Kon?ano."

#: ../gtk-dialog.c:1320
#, c-format
msgid ""
"%s is contacting you from an unrecognized computer.  You should <a href=\"%s%"
"s\"authenticate</athis buddy."
msgstr ""
"%s ?eli stopiti v stik z vami iz neprepoznanega ra?unalnika. Priporo?amo, da <a "
"href=\"%s%s\"potrdite</atega kolega."

#: ../gtk-dialog.c:1324
#, c-format
msgid ""
"%s has not been authenticated yet.  You should <a href=\"%s%s"
"\"authenticate</athis buddy."
msgstr ""
"%s ?e ni bil prepoznan. Priporo?amo, da <a href=\"%s%s\""
"potrdite</atega kolega."

#: ../gtk-dialog.c:1365 ../gtk-ui.c:76
msgid "Finished"
msgstr "Kon?ano"


#: ../gtk-dialog.c:1366 ../gtk-ui.c:75
msgid "Private"
msgstr "Zasebno"

#: ../gtk-dialog.c:1367 ../gtk-ui.c:74
msgid "Unverified"
msgstr "Nepotrjeno"

#: ../gtk-dialog.c:1368 ../gtk-ui.c:73
msgid "Not private"
msgstr "Javno"

#: ../gtk-dialog.c:1370
msgid "Start a private conversation"
msgstr "Za?ni z zasebnim pogovorom"

#: ../gtk-dialog.c:1371
msgid "Refresh the private conversation"
msgstr "Obnovi zasebni pogovor"

#: ../gtk-dialog.c:1375
msgid "Start _private conversation"
msgstr "Za?ni z zasebnim pogovorom"

#: ../gtk-dialog.c:1376
msgid "Refresh _private conversation"
msgstr "Obnovi _zasebni pogovor"

#: ../gtk-dialog.c:1555
msgid "I have not"
msgstr "Nisem"

#: ../gtk-dialog.c:1556
msgid "I have"
msgstr "Sem"

#: ../gtk-dialog.c:1558
msgid " verified that this is in fact the correct"
msgstr " potrdil/a, da je to resni?no pravilni"

#: ../gtk-dialog.c:1567
#, c-format
msgid "fingerprint for %s."
msgstr "prstni odtis za %s."

#: ../gtk-dialog.c:1579
msgid ""
"To verify the fingerprint, contact your buddy via some <iother</i"
"authenticated channel, such as the telephone or GPG-signed email.  Each of "
"you should tell your fingerprint to the other."
msgstr ""
"Za potrditev prstnega odtisa stopite v stik s kolegom preko nekega <idrugega</i"
"verodostojnega kanala kot je telefon ali z GPG podpisano elektronsko pismo. "
"Vsak naj drugemu sporo?i prstni odtis."

#: ../gtk-dialog.c:1583
msgid ""
"If everything matches up, you should indicate in the above dialog that you "
"<bhave</bverified the fingerprint."
msgstr ""
"?e se vse ujema, potrdite v zgornjem pogovornem oknu, da <bste "
"</bodobrili prstni odtis."

#: ../gtk-dialog.c:1585
msgid ""
"If your buddy has more than one IM account, or uses more than one computer, "
"he may have multiple fingerprints."
msgstr ""
"?e ima va? kolega ve? kot en IM predal, ali uporablja ve? kot en ra?unalnik, "
"ima lahko ve? prstnih odtisov."

#: ../gtk-dialog.c:1587
msgid ""
"However, the only way an imposter could duplicate one of your buddy's "
"fingerprints is by stealing information from her/his computer."
msgstr ""
"Edini na?in, s katerim bi vsiljivec lahko ponaredil prstni odtis va?ega kolega "
"je kraja teh podatkov z njenega/njegovega ra?unalnika."

#: ../gtk-dialog.c:1591
msgid "Click here for more information about fingerprints."
msgstr "Kliknite tukaj za podrobnosti o prstnih odtisih."

#: ../gtk-dialog.c:1594
msgid ""
"A <bfingerprint</bis a unique identifier that you should use to "
"authenticate your buddy."
msgstr ""
"<bPrstni odtis</bje edinstveni prepoznavalec, ki ga morate uporabiti "
"pri prepoznavanju va?ega kolega."

#: ../gtk-dialog.c:1616
#, c-format
msgid "Verify fingerprint for %s"
msgstr "Potrdi prstni odtis za %s"

#: ../gtk-dialog.c:1620
msgid "[none]"
msgstr "[nobeden]"

#: ../gtk-dialog.c:1628
#, c-format
msgid ""
"Fingerprint for you, %s (%s):\n"
"%s\n"
"\n"
"Purported fingerprint for %s:\n"
"%s\n"
msgstr ""
"Va? prstni odtis, %s (%s):\n"
"%s\n"
"\n"
"Ponujeni prstni odtis %s:\n"
"%s\n"

#: ../gtk-dialog.c:1633 ../gtk-ui.c:681
msgid "Verify fingerprint"
msgstr "Potrdite prstni odtis"

#: ../gtk-dialog.c:1660
#, c-format
msgid "Authenticate %s"
msgstr "Potrdite %s"

#: ../gtk-dialog.c:1665
#, c-format
msgid "Enter a secret known only to %s and yourself.\n"
msgstr "Vnesite geslo, ki ga pozna le %s in vi.\n"

#: ../gtk-dialog.c:1668
msgid "Authenticate buddy"
msgstr "Potrdite kolega"

#: ../gtk-dialog.c:1700
msgid "An error occurred during authentication."
msgstr "Pri potrditvi je pri?lo do napake."

#: ../gtk-dialog.c:1716
msgid "Authentication successful."
msgstr "Potrditev je bila uspe?na. "

#: ../gtk-dialog.c:1719
msgid "Authentication failed."
msgstr "Potrditev ni uspela."

#: ../gtk-dialog.c:1744
#, c-format
msgid "Private conversation with %s started.%s"
msgstr "Zasebni pogovors s %s se je za?el.%s"

#: ../gtk-dialog.c:1748
#, c-format
msgid "<a href=\"%s%s\"Unverified</aconversation with %%s started.%%s"
msgstr "<a href=\"%s%s\"Nepotrjen</apogovor s %%s se je za?el.%%s"

#. This last case should never happen, since we know
#. * we're in ENCRYPTED.
#: ../gtk-dialog.c:1756
#, c-format
msgid "Not private conversation with %s started.%s"
msgstr "Javni pogovor s %s se je za?el.%s"

#: ../gtk-dialog.c:1762 ../gtk-dialog.c:1863
msgid "  Warning: using old protocol version 1."
msgstr " Opozorilo: uporaba starega protokola verzija 1."

#: ../gtk-dialog.c:1782
#, c-format
msgid "Private conversation with %s lost."
msgstr "Zasebni pogovor z %s je prekinjen."

#: ../gtk-dialog.c:1817
#, c-format
msgid ""
"%s has ended his/her private conversation with you; you should do the same."
msgstr ""
"%s je kon?al svoj zasebi pogovor z vami; ravnajte enako."

#: ../gtk-dialog.c:1842
#, c-format
msgid "Successfully refreshed the private conversation with %s.%s"
msgstr "Uspe?no obnovljen zasebni pogovor z %s.%s"

#: ../gtk-dialog.c:1847
#, c-format
msgid ""
"Successfully refreshed the <a href=\"%s%s\"unverified</aconversation with "
"%%s.%%s"
msgstr ""
"Uspe?no osve?en <a href=\"%s%s\"nepotrjen</apogovor z %%s.%%s"

#. This last case should never happen, since we know
#. * we're in ENCRYPTED.
#: ../gtk-dialog.c:1856
#, c-format
msgid "Successfully refreshed the not private conversation with %s.%s"
msgstr "Uspe?no osve?en javni pogovor z %s.%s"

#: ../gtk-dialog.c:1883
#, c-format
msgid "Attempting to refresh the private conversation with %s..."
msgstr "Posku?am osve?iti zasebni pogovor z %s..."

#: ../gtk-dialog.c:1885
#, c-format
msgid "Attempting to start a private conversation with %s..."
msgstr "Posku?am za?eti zasebni pogovor z %s..."

#: ../gtk-dialog.c:2045
msgid "OTR:"
msgstr "OTR:"

#: ../gtk-dialog.c:2054
msgid "OTR Messaging"
msgstr "OTR sporo?anje"

#: ../gtk-dialog.c:2060
msgid "_End private conversation"
msgstr "_Kon?aj zasebni pogovor"

#.
#. * Don't show the Verify fingerprint menu option any more.  You can
#. * still get to the dialog through Authenticate connection -
#. * Advanced...
#. *
#. menuverf = gtk_menu_item_new_with_mnemonic(_("_Verify fingerprint"));
#. gtk_menu_shell_append(GTK_MENU_SHELL(menu), menuverf);
#. gtk_widget_show(menuverf);
#.
#: ../gtk-dialog.c:2078
msgid "_Authenticate buddy"
msgstr "_Potrdi kolega"

#: ../gtk-ui.c:96
#, c-format
msgid "Fingerprint: %.80s"
msgstr "Prstni odtis: %.80s"

#: ../gtk-ui.c:100
#, c-format
msgid "No key present"
msgstr "Klju? ni zaznan"

#: ../gtk-ui.c:105
#, c-format
msgid "No account available"
msgstr "Predal ni na voljo"

#: ../gtk-ui.c:165
msgid "Unused"
msgstr "Neuporabljeno"

#: ../gtk-ui.c:171
msgid "Yes"
msgstr "Da"

#: ../gtk-ui.c:171
msgid "No"
msgstr "Ne"

#: ../gtk-ui.c:396
msgid "Enable private messaging"
msgstr "Omogo?i zasebno sporo?anje"

#: ../gtk-ui.c:398
msgid "Automatically initiate private messaging"
msgstr "Avtomatsko za?ni zasebno sporo?anje"

#: ../gtk-ui.c:400
msgid "Require private messaging"
msgstr "Zahtevaj zasebno sporo?anje"

#: ../gtk-ui.c:403
msgid "Don't log OTR conversations"
msgstr "Ne bele?i OTR pogovorov"

#: ../gtk-ui.c:531
msgid "My private keys"
msgstr "Moji zasebni klju?i"

#: ../gtk-ui.c:540
msgid "Key for account:"
msgstr "Klju? za predal:"

#: ../gtk-ui.c:565
msgid "Generate"
msgstr "Izdelaj"

#: ../gtk-ui.c:596
msgid "Default OTR Settings"
msgstr "Standardne nastavitve OTR"

#: ../gtk-ui.c:625
msgid "Screenname"
msgstr "Uporabni?ko ime"

#: ../gtk-ui.c:626
msgid "Status"
msgstr "Status"

#: ../gtk-ui.c:627
msgid "Verified"
msgstr "Potrjen"

#: ../gtk-ui.c:628
msgid "Fingerprint"
msgstr "Prstni odtis"

#: ../gtk-ui.c:629
msgid "Account"
msgstr "Predal"

#: ../gtk-ui.c:665
msgid "Start private connection"
msgstr "Za?ni zasebni pogovor"

#: ../gtk-ui.c:673
msgid "End private connection"
msgstr "Kon?aj zasebni pogovor"

#: ../gtk-ui.c:689
msgid "Forget fingerprint"
msgstr "Pozabi prstni odtis"

#: ../gtk-ui.c:738
msgid "Config"
msgstr "Nastavi"

#: ../gtk-ui.c:740
msgid "Known fingerprints"
msgstr "Poznani prstni odtisi"

#: ../gtk-ui.c:838 ../otr-plugin.c:577
msgid "OTR Settings"
msgstr "Nastavitve OTR"

#. Set the title
#: ../gtk-ui.c:856
#, c-format
msgid "OTR Settings for %s"
msgstr "OTR nastavitve pre %s"

#. Make the cascaded checkboxes
#: ../gtk-ui.c:873
msgid "Use default OTR settings for this buddy"
msgstr "Uporabi standardne nastavitve OTR za tega kolega"

#: ../otr-plugin.c:113
#, c-format
msgid "You are not currently connected to account %s (%s)."
msgstr "Trenutno niste povezani s predalom %s (%s)."

#: ../otr-plugin.c:117
msgid "Not connected"
msgstr "Nepovezan"

#: ../otr-plugin.c:161
#, c-format
msgid "Out of memory building filenames!\n"
msgstr "Zmanjkalo spomina pri ustvarjanju imen datotek!\n"

#: ../otr-plugin.c:167
#, c-format
msgid "Could not write private key file\n"
msgstr "Ni mo? izpisati zasebnega klju?a datoteke\n"

#: ../otr-plugin.c:210
#, c-format
msgid "Unknown account %s (%s)."
msgstr "Neznani predal %s (%s)."

#: ../otr-plugin.c:214
msgid "Unknown account"
msgstr "Neznani predal"

#: ../otr-plugin.c:953
msgid "Off-the-Record Messaging"
msgstr "neuradno sporo?anje"

#: ../otr-plugin.c:954
msgid "Provides private and secure conversations"
msgstr "Omogo?a zasebne in varne pogovore"

#: ../otr-plugin.c:955
msgid ""
"Preserves the privacy of IM communications by providing encryption, "
"authentication, deniability, and perfect forward secrecy."
msgstr ""
"Ohranja zasebnost IM komuniciranja z zagotavljanjem kodiranja, "
" potrditve, mo?nosti zavrnitve in tajnosti."

#: ../ui.c:108
#, c-format
msgid "Account %s (%s) could not be found"
msgstr "Predala %s (%s) ni bilo mo? najti"

#: ../ui.c:112
msgid "Account not found"
msgstr "Predala ni"




       
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. 
http://mobile.yahoo.com/go?refer=1GNXIC



From cactusthesaint at yahoo.com  Wed Aug 29 18:22:49 2007
From: cactusthesaint at yahoo.com (Cactus The Saint)
Date: Wed, 29 Aug 2007 15:22:49 -0700 (PDT)
Subject: [OTR-dev] Slovene translation for pidgin-otr
Message-ID: <535535.30075.qm@web55209.mail.re4.yahoo.com>



> I have also attached the translation as a utf-8 formatted file

Derek's a big fat liar, news at 11.





       
____________________________________________________________________________________
Choose the right car based on your needs.  Check out Yahoo! Autos new Car Finder tool.
http://autos.yahoo.com/carfinder/
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pidgin-slovene-utf8.txt
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20070829/815447b9/attachment.txt>

From tommy.b at gmx.net  Fri Aug 31 15:50:23 2007
From: tommy.b at gmx.net (Thomas B.)
Date: Fri, 31 Aug 2007 21:50:23 +0200
Subject: [OTR-dev] German translation for pidgin-otr
In-Reply-To: <46D5D7C6.1060903@mmsources.de>
References: <46D5D7C6.1060903@mmsources.de>
Message-ID: <20070831195023.GA23975@tommy>

On Wed, Aug 29, 2007 at 10:32:06PM +0200, Michael Meier wrote:
> Hello,
> 
> i've created a translation of pidgin-otr in my native language. I hope
> it meets your requirements.
> I have also subscribed to this list and would like to continue
> maintaining the german translation for future releases.

Cool! I can confirm that the language file works and that the
translations make sense to me as a German ;-)

Regards,
Thomas