Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Onno, very good point. Thanks for this feedback. We will add a check for the next version to avoid this in future. As far as I know this applies to the following labels: > ui/locale/en-US/enigmail.properties:usingAgent= > ui/locale/en-US/enigma

Re: [Enigmail] Request for Translation

Hi Onno, very good point. Thanks for this feedback. We will add a check for the next version to avoid this in future. As far as I know this applies to the following labels: > ui/locale/en-US/enigmail.properties:usingAgent=Using %S executable %S to > encrypt and decrypt > ui/locale/en-US/enigmail

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, thanks for this feedback. As a programmer I fully agree. We (programmers and translators) have the same goal here, because the current mess is a problem for programming and maintenance of the code. We didn't though have enough time to clean

Re: [Enigmail] Request for Translation

This is weird - I received this email and Thunderbird showed it as coming from Onno Ekker. I clicked on the Details button to view key properties and find I'm looking at Patrick Brunschwig's cert (which does check with the cert ref shown in the header). And reading the email shows that indeed it

Re: [Enigmail] Request for Translation

One more thing :-) In enigmail.properties i see several strings with more placeholders (e.g. offlineSave "Save %S message to %S in Unsent Messages folder?"). I think you should use %1s and %2s here, because the order in which the two arguments are may vary from language to language. See also this

Re: [Enigmail] Request for Translation

Hello. On Fri, Jul 4, 2014 at 1:24 PM, Onno Ekker wrote: > It would also be nice if you give the labels and accesskeys the same name. > For instance, now there's a label called enigmail.keyMan.keyProps.label > with accesskey called enigmail.keyMan.keyDetails.accesskey. This makes it > very hard

Re: [Enigmail] Request for Translation

It would also be nice if you give the labels and accesskeys the same name. For instance, now there's a label called enigmail.keyMan.keyProps.label with accesskey called enigmail.keyMan.keyDetails.accesskey. This makes it very hard to find the correct accesskey, because you first have to find the xu

Re: [Enigmail] Request for Translation

I wanted to check the original html files, to see if the translation is still correct, but in en-US the files are empty on BabelZilla... Onno On Tue, Jul 1, 2014 at 9:21 AM, Patrick Brunschwig wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 30.06.14 18:39, Kosuke Kaizuka wrot

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 03 Jul 2014 11:59:57 +0200, Ludwig Hügelschäfer wrote: > On 03.07.14 07:48, Kosuke Kaizuka wrote: >> I'm also considering that enigmail.keyservers.sample will be >> modified in ja-JP locale shown below. > >> pool.sks-keyservers.net (current

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 03.07.14 07:48, Kosuke Kaizuka wrote: > You mean to change to "pool.sks-keyservers.net, keys.gnupg.net, > pgp.mit.edu"? Good choice. These were the keyservers which did work when testing this change in january. > I'm also considering that enig

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 02 Jul 2014 21:09:31 +0200, Ludwig Hügelschäfer wrote: >> I think that keeping the pool in the example is probably a >> better for resilience, redundancy, and not putting too much >> strain on any individual keyserver. I suspect that people

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01.07.14 21:51, Daniel Kahn Gillmor wrote: > On 06/30/2014 12:01 PM, Patrick Brunschwig wrote: >> On 30.06.14 12:49, Kosuke Kaizuka wrote: >>> - enigmail.keyservers.sample does not include >>> pool.sks-keyservers.net >> >> Yes, we removed it. >

Re: [Enigmail] Request for Translation

On 06/30/2014 12:01 PM, Patrick Brunschwig wrote: > On 30.06.14 12:49, Kosuke Kaizuka wrote: >> - enigmail.keyservers.sample does not include >> pool.sks-keyservers.net > > Yes, we removed it. why? the currently listed example keyservers are: sks.dnsalias.net, pgp.mit.edu, ldap://certserver.pg

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30.06.14 18:44, Kosuke Kaizuka wrote: > On Mon, 30 Jun 2014 18:15:18 +0200, Patrick Brunschwig wrote: >>> Is it better to send localized files to you directly instead of >>> Babelzilla? > >> Sure, you can always do that. > > Sure, I will send t

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30.06.14 18:39, Kosuke Kaizuka wrote: >>> -- enigmail.seeAccountSettings.label says "(see Account >>> Settings -> OpenPGP Security)" > >>> 2. help/messenger.html > >>> - line 31 and 33 do not follow re-labeling OpenPGP to Enigmail >>> - line 4

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 30 Jun 2014 18:15:18 +0200, Patrick Brunschwig wrote: >> Is it better to send localized files to you directly instead of >> Babelzilla? > > Sure, you can always do that. Sure, I will send to you directly. > I'm not quite happy with Babelz

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > On 30.06.14 12:49, Kosuke Kaizuka wrote: >> Hi Patrick, > >> I have found several problems of locale files. > >> 1. enigmail.dtd > >> - enigmail.keyservers.sample does not include >> pool.sks-keyservers.net > > Yes, we removed it. >> - enigma

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30.06.14 18:03, Kosuke Kaizuka wrote: > Hi Patrick, > > There is a serious problem with Babelzilla. > > dtd entities containing are completely broken after > uploading files. and following sentence have been > erased. This happens not only in

Re: [Enigmail] Request for Translation

Hi Patrick, There is a serious problem with Babelzilla. dtd entities containing are completely broken after uploading files. and following sentence have been erased. This happens not only in localized ones like ja-JP, also in en-US. Please see the attachment file. Is it better to send localize

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30.06.14 12:49, Kosuke Kaizuka wrote: > Hi Patrick, > > I have found several problems of locale files. > > 1. enigmail.dtd > > - enigmail.keyservers.sample does not include > pool.sks-keyservers.net Yes, we removed it. > - enigmail.amPrefTitl

Re: [Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Patrick, I have found several problems of locale files. 1. enigmail.dtd - - enigmail.keyservers.sample does not include pool.sks-keyservers.net - - enigmail.amPrefTitle.label "OpenPGP Options" should be "OpenPGP Security" - -- The title in the

[Enigmail] Request for Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Nico and I have finalized the strings for the next version of Enigmail. If you want to help translate the labels for all the new features, then please visit A few

[Enigmail] Request For Translation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I'm planning to release the next version of Enigmail in a couple of days. The new version adds quite a number of new strings to translate. Many translations are still not updated. Currently this is true for the following translations: Arabic Bulgari