451

(16 replies, posted in New versions)

{$SPACE} will let's you create spaces inside an argument wink

Gmail make some small modifications to inline message, like carriage returns, strange spaces and it's hard to get the original content to have a valid sign.

You have an another extention who conflict, it's impossible wink

454

(16 replies, posted in New versions)

Hum yes, I never think to that.

Wait for the next release, I will find a solution.

Ok, I will add a system who dectect the editor used and send mail in html only if the html editor is used.

Use openpgp/mime.

457

(11 replies, posted in Bugs & problems)

I will made test myself, thanks !

458

(4 replies, posted in Misc)

Hi,

Great wink

> Now I'm curious if the translations are "looking and reading good" in the AddOn and Website.

Next release will (probably) be here sunday or monday wink (I will sync the website too)

Regards,

459

(4 replies, posted in Requests)

http://bugs.getfiregpg.org/index.php?do … ask_id=210

460

(11 replies, posted in Bugs & problems)

Display the source of the mail (view originial)

If he is base64 encoded, we fix the problem.

If he is not, can you send us your message ?

Hum, I don't know...

Maybe you have an 64 bits xp ?

Try this too :

1) Check error in console, when you launch firegpg and then when you open firegpg's opens
2) Maybe check your Antivirus logs, he may doesn't like see the browser execute an application on your system (gnupg)
3) Try to install FireGPG on a clean profile. If it's works, give us the list of your installed addons

Ho, so it's was a missunderstanding, I was asking if FireFTP was installed wink

So uninstall it :]

Witch os ?

463

(3 replies, posted in Bugs & problems)

a) Error in console ?
b) Usage of the top or the bottom send button ? {bottom button is broken}

smile

Bug already reported for chose of key too, and the attachement with noname is normal (we have to respect standards wink)(try with enigmail, you will have one too)

Regards,

If you use the send button of the top of the page, any differences ?

And for the second problem it's connected to this one : http://bugs.getfiregpg.org/index.php?do … ;project=1

Regards,

466

(3 replies, posted in Bugs & problems)

Hum, non celui l

467

(3 replies, posted in Bugs & problems)

Bou,

Regardez la source du message: il il est encodé en base64, c'est normal.

Salutations,

FireFTP conflict with FireGPG, read messages wink

469

(7 replies, posted in Bugs & problems)

By never fail I mean 'never fail dues to this kind of problems' wink

You can easily truncate your message at 60 characters, I won't add a bar for that wink

Regards,

PS : Et si vous parlez français c'est mieux encore x]

470

(7 replies, posted in Bugs & problems)

No hmm

But notice using openpgp/mime sign will never fail, so you don't need to check them wink

471

(7 replies, posted in Bugs & problems)

You can't wink

Except by using the contextual menu

Regards,

472

(7 replies, posted in Bugs & problems)

We already truncate mail who are too long...

Use openpgp/mime wink

Regards,

FireFTP ?

474

(2 replies, posted in New versions)

It's not the same format for the mail. Inline sign your mail in the mail content, not inline (openpgp/mime) sign your mail with standarts, inside the mail data.

475

(15 replies, posted in Bugs & problems)

I didn't committed yet wink

Should be ok now !