From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/18219 Path: news.gmane.org!not-for-mail From: =?UTF-8?Q?Elias_M=C3=A5rtenson?= Newsgroups: gmane.emacs.gnus.user Subject: Re: "Forward" in the standard way Date: Sat, 9 Apr 2016 11:38:57 +0800 Message-ID: References: <87a8m2f8ra.fsf@gmx.com> <87fuvut900.fsf@tullinup.koldfront.dk> <87d1qydsa3.fsf@gmx.com> <878u1mt8es.fsf@tullinup.koldfront.dk> <877fgbazv5.fsf@tullinup.koldfront.dk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6381669238462481339==" X-Trace: ger.gmane.org 1460173150 8294 80.91.229.3 (9 Apr 2016 03:39:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Apr 2016 03:39:10 +0000 (UTC) Cc: info-gnus-english@gnu.org To: =?UTF-8?Q?Adam_Sj=C3=B8gren?= Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Sat Apr 09 05:39:09 2016 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aojjm-00038h-Lj for gegu-info-gnus-english@m.gmane.org; Sat, 09 Apr 2016 05:39:06 +0200 Original-Received: from localhost ([::1]:59140 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aojji-0005Th-F6 for gegu-info-gnus-english@m.gmane.org; Fri, 08 Apr 2016 23:39:02 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33940) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aojjg-0005RX-6L for info-gnus-english@gnu.org; Fri, 08 Apr 2016 23:39:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aojje-0007Vo-TF for info-gnus-english@gnu.org; Fri, 08 Apr 2016 23:39:00 -0400 Original-Received: from mail-vk0-x235.google.com ([2607:f8b0:400c:c05::235]:33578) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aojje-0007VX-N0 for info-gnus-english@gnu.org; Fri, 08 Apr 2016 23:38:58 -0400 Original-Received: by mail-vk0-x235.google.com with SMTP id k1so159227477vkb.0 for ; Fri, 08 Apr 2016 20:38:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=wuGMgaLgBg/ABKHrejYt7X2KHVnLSuP2RCeA8Za9ofo=; b=LdhtPlvAh72x5fl6wiMHE6oSdfIhftUp7WzAblPqj8g8YZg+antot2745VG83al+xE 3bf6hwmK2o2ymUm/vTW7ZW1VH3El5g15WDYo9f06p3p7JCA+p5FpNLAUts5DV7+0JMs0 7m9X+4g7njLy7E4MDbQk9x98K3Ca3DUPq99UMB3fqk2/0bB8uUuPjVonmu1DBPSbvOku A8eCyAmAJwPARFJaOISjY1InkGCzJh26CnTOgvRjnCqetOt98pPdtooTd7bD8A8PFKYg A2gl0T7V5NvgHKARYXTPA1TYB2JOyjJN7V8HkSoqCd9ghADCadfzglFN69Yda9ScF69O 9AnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=wuGMgaLgBg/ABKHrejYt7X2KHVnLSuP2RCeA8Za9ofo=; b=kFnsXxPCxXBWn9nOcwfqHFTGoJCxLBiy1Bj45dANFjE5YOxdC/agexgeYHmXopvAWL xeYV9638xGdYGh6GxrQCu5Jg8q20g+GyNU6nWBUTLNjbSMr37Sll+2G270RZMgTdwp98 fw7CIndVhz/RonFJ2wFbBfTsXiNsgLoHM0fHuRbZJFKmpj5053u1bS2chmYbBddXUJtu ZsLRsNgqenTpzVHLeRZUfGecTigMCZcgvdU9dseXQqzIvn6cDprz/HhdgNaxJ4WD/ZGT r7HPxduyDiM1ilbUy0gJoPGZn+W5PAcwrZJE1Tsn/tJWB5Zph2wwh7HMw8TkGKlny3cX /B5Q== X-Gm-Message-State: AD7BkJJhpzFNA4SaY22bQx7FtD+utIxIq0/ga9PHkYjqIMlQIOHsh25hmQj+PSCTJVW173ok91Thvb6f6KDe3w== X-Received: by 10.31.56.151 with SMTP id f145mr6145491vka.107.1460173137852; Fri, 08 Apr 2016 20:38:57 -0700 (PDT) Original-Received: by 10.176.5.163 with HTTP; Fri, 8 Apr 2016 20:38:57 -0700 (PDT) In-Reply-To: <877fgbazv5.fsf@tullinup.koldfront.dk> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400c:c05::235 X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Original-Sender: "info-gnus-english" Xref: news.gmane.org gmane.emacs.gnus.user:18219 Archived-At: --===============6381669238462481339== Content-Type: multipart/alternative; boundary=001a1143f94831437b0530050d1b --001a1143f94831437b0530050d1b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 6 April 2016 at 16:46, Adam Sj=C3=B8gren wrote: * elide all "full-bottom-quoted" emails, preferably with a line for > each, togglable, > > or > > * reformat an email containing a thread of emails full-bottom-quoted > into the "correct" format (top quoted) > > I guess the latter isn't that useful, but sometimes I reformat threads > to make them understandable. > Fair enough (and yes, I'm aware of the fact that I made a mistake with my previous message). The first suggestion is what Gmail is doing, I believe, and it seems to work quite well. The second suggestion is not really workable. Anyone who has been working in an organisation that uses Outlook extensively (like where I work) knows that the chains become very long, and reformatting to put the entire message (or even message chain) on top would make it incredibly difficult to read. My tool does not address this at all. In fact, using shr to render the HTML Outlook emails works really well in almost all cases, and for the remaining ones all you need to do is to press K H to render it in a browser. My tool ensures that the reply chain is preserved when you reply. Believe it or not, but in many companies, when someone wants to inform another person of a previous discussion, he simply forwards the email to the recipient, and the entire chain is there for him. Thus, you need to make sure that no matter how you write your mails, you need to ensure that the previous chain is preserved, including inline images etc. That is what my tool does. I'm brining this up here, because I feel that this functionality should be part of Gnus. However, my tool is not suitable for this, due to the fact that it does the HTML rewriting using an external program. If there was an Elisp implementation of a parser that supports the HTML=E2=86=92DOM=E2=86= =92Edit=E2=86=92DOM=E2=86=92HTML workflow, I'd be happy to implement it. Regards, Elias --001a1143f94831437b0530050d1b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 6= April 2016 at 16:46, Adam Sj=C3=B8gren <asjo@koldfront.dk> = wrote:

=C2=A0* elide a= ll "full-bottom-quoted" emails, preferably with a line for
=C2=A0 =C2=A0each, togglable,

=C2=A0 =C2=A0 =C2=A0or

=C2=A0* reformat an email containing a thread of emails full-bottom-quoted<= br> =C2=A0 =C2=A0into the "correct" format (top quoted)

I guess the latter isn't that useful, but sometimes I reformat threads<= br> to make them understandable.

Fair enoug= h (and yes, I'm aware of the fact that I made a mistake with my previou= s message).

The first suggestion is what Gmail is = doing, I believe, and it seems to work quite well.

The second suggestion is not really workable. Anyone who has been working = in an organisation that uses Outlook extensively (like where I work) knows = that the chains become very long, and reformatting to put the entire messag= e (or even message chain) on top would make it incredibly difficult to read= .

My tool does not address this at all. In fact, u= sing shr to render the HTML Outlook emails works really well in almost all = cases, and for the remaining ones all you need to do is to press K H to ren= der it in a browser.

My tool ensures that the repl= y chain is preserved when you reply. Believe it or not, but in many compani= es, when someone wants to inform another person of a previous discussion, h= e simply forwards the email to the recipient, and the entire chain is there= for him. Thus, you need to make sure that no matter how you write your mai= ls, you need to ensure that the previous chain is preserved, including inli= ne images etc. That is what my tool does.

I'm = brining this up here, because I feel that this functionality should be part= of Gnus. However, my tool is not suitable for this, due to the fact that i= t does the HTML rewriting using an external program. If there was an Elisp = implementation of a parser that supports the HTML=E2=86=92DOM=E2=86=92Edit= =E2=86=92DOM=E2=86=92HTML workflow, I'd be happy to implement it.
=

Regards,
Elias
--001a1143f94831437b0530050d1b-- --===============6381669238462481339== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline