Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
This bug is important to me and to no-one else, so far as I know, on this list. It is something that I have not the knowledge to do for myself. So could I pay the project? Can someone spare the time? If so, would it be affordable? Yes, another subjective word.
I don't want to have to abandon KMail. I'd rather try and solve this problem.
Lisi
On Wednesday 06 May 2015 12:23:58 Lisi Reisz wrote:
Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
This bug is important to me and to no-one else, so far as I know, on this list. It is something that I have not the knowledge to do for myself. So could I pay the project? Can someone spare the time? If so, would it be affordable? Yes, another subjective word.
I don't want to have to abandon KMail. I'd rather try and solve this problem.
Lisi
Sorry, should ahve included the URL. http://bugs.pearsoncomputing.net/show_bug.cgi?id=2440
Lisi
On Wednesday 06 May 2015, Lisi Reisz wrote:
On Wednesday 06 May 2015 12:23:58 Lisi Reisz wrote:
Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
This bug is important to me and to no-one else, so far as I know, on this list. It is something that I have not the knowledge to do for myself. So could I pay the project? Can someone spare the time? If so, would it be affordable? Yes, another subjective word.
I don't want to have to abandon KMail. I'd rather try and solve this problem.
Lisi
Sorry, should ahve included the URL. http://bugs.pearsoncomputing.net/show_bug.cgi?id=2440
Lisi,
I don't get your point (maybe because I'm not a native speaker?!). For me, Kmail always shows HTML Mails as rendered text and I have explicitely switch to HTNL view if wished. Seems to be a setting but I have not found it yet in settings dialog of Kmail.
Maybe someone else have an idea about where to switch to non-HTML view as default behavior but I definitively don't see this as a bug.
regards Gerhard
On Wednesday 06 May 2015 13:50:19 Gerhard Zintel wrote:
I don't get your point (maybe because I'm not a native speaker?!). For me, Kmail always shows HTML Mails as rendered text and I have explicitely switch to HTNL view if wished. Seems to be a setting but I have not found it yet in settings dialog of Kmail. Gerhard
You have the choice with Kmail : HTML or text.
And what happens with the bug about "tdm-trinity" ? (very difficult to log in the desktop tde-trinity...).
Waiting, I use the desktop "openbox" or "mate", but not so good than tde-trinity.
Is it possible to come back to the tde 14.0.0 version and avoid this bug ? If yes, how to do ?
André
On Wednesday 06 May 2015 13:42:43 andre_debian@numericable.fr wrote:
You have the choice with Kmail : HTML or text.
No, you don't. You can have the text, only in a plain text email or a correct multipart one. An HTML email can be shown as rendered HTML, which I can't read, or the underlying HTML source code. Which I can't read.
Lisi
On Wed May 6 2015 06:46:34 Lisi Reisz wrote:
An HTML email can be shown as rendered HTML, which I can't read, or the underlying HTML source code.
Hi Lisi,
I'm guessing maybe bad color contrast or fonts too small, but I'd like to know for sure.
So that techies can better understand the issues, can you give us some insight into the problems of reading the rendered HTML?
--Mike
On Wednesday 06 May 2015 16:51:43 Mike Bird wrote:
On Wed May 6 2015 06:46:34 Lisi Reisz wrote:
An HTML email can be shown as rendered HTML, which I can't read, or the underlying HTML source code.
Hi Lisi,
I'm guessing maybe bad color contrast or fonts too small, but I'd like to know for sure.
So that techies can better understand the issues, can you give us some insight into the problems of reading the rendered HTML?
Hi, Mike,
You've hit the nail right on the head! Except that, in addition, the fonts are apt to be chosen for "prettiness" rather than clarity. The exact font can make an enormous difference.
I did ask my power supplier the other day whether it was selling pictures or electricity. (It likes small writing in pale green on pale yellow. How on earth do even completely sighted people manage to read that??)
Thanks very much. Lisi
On Wednesday 06 May 2015, Lisi Reisz wrote:
On Wednesday 06 May 2015 12:23:58 Lisi Reisz wrote:
Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
This bug is important to me and to no-one else, so far as I know, on this list. It is something that I have not the knowledge to do for myself. So could I pay the project? Can someone spare the time? If so, would it be affordable? Yes, another subjective word.
I don't want to have to abandon KMail. I'd rather try and solve this problem.
Lisi
Sorry, should ahve included the URL. http://bugs.pearsoncomputing.net/show_bug.cgi?id=2440
now I found something in settings dialog. Have you un-checked "Prefer HTML to plain text" item in Kmail->Settings->Securitry on tab Reading?
Gerhard
Am Mittwoch, 6. Mai 2015 schrieb Lisi Reisz:
On Wednesday 06 May 2015 12:23:58 Lisi Reisz wrote:
Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
This bug is important to me and to no-one else, so far as I know, on this list. It is something that I have not the knowledge to do for myself. So could I pay the project? Can someone spare the time? If so, would it be affordable? Yes, another subjective word.
I don't want to have to abandon KMail. I'd rather try and solve this problem.
Lisi
Sorry, should ahve included the URL. http://bugs.pearsoncomputing.net/show_bug.cgi?id=2440
Lisi
Hi Lisi!
That problem is why I enabled "prefer HTML" in kmail. I've added a small program to #2440 that acts as a filter. If "somebody" (sorry it's not me, I'm still stuck at getting tdelibs working on FreeBSD) finds the time to add pipe the message through that filter and then display the resulting text plus attachments instead of using kmails filer, things would be fine. Despite the fackt that these custom filters would allow interesting things :-)
Nik
On Wednesday 06 May 2015 13:48:38 Dr. Nikolaus Klepp wrote:
Am Mittwoch, 6. Mai 2015 schrieb Lisi Reisz:
On Wednesday 06 May 2015 12:23:58 Lisi Reisz wrote:
Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
This bug is important to me and to no-one else, so far as I know, on this list. It is something that I have not the knowledge to do for myself. So could I pay the project? Can someone spare the time? If so, would it be affordable? Yes, another subjective word.
I don't want to have to abandon KMail. I'd rather try and solve this problem.
Lisi
Sorry, should ahve included the URL. http://bugs.pearsoncomputing.net/show_bug.cgi?id=2440
Lisi
Hi Lisi!
That problem is why I enabled "prefer HTML" in kmail. I've added a small program to #2440 that acts as a filter. If "somebody" (sorry it's not me, I'm still stuck at getting tdelibs working on FreeBSD) finds the time to add pipe the message through that filter and then display the resulting text plus attachments instead of using kmails filer, things would be fine. Despite the fackt that these custom filters would allow interesting things :-)
Hi, Nik :-)
Thanks, and good to hear from you. I'm sorry that tdelibs is still proving intractable.
Lisi
On Wed, 6 May 2015 12:23:58 +0100 Lisi Reisz lisi.reisz@gmail.com wrote:
Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
This bug is important to me and to no-one else, so far as I know, on this list. It is something that I have not the knowledge to do for myself. So could I pay the project? Can someone spare the time? If so, would it be affordable? Yes, another subjective word.
I don't want to have to abandon KMail. I'd rather try and solve this problem.
I dont use kmail and dont know how it renders messages, but if using external helpers is not a problem rendering html as plain text is as easy as calling lynx -dump (or whatever lynx variant you prefer).
On Wed, May 06, 2015 at 12:23:58PM +0100, Lisi Reisz wrote:
Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
Here is the bug report again:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=2440
Unfortunately, for some reason I can't view the screen shot, but I think I know what you are referring to.
I think you mean that Kmail displays HTML emails as raw HTML code, like the "View Source" in a web browser, full of < > tags and other formatting information. Is that what you mean?
I must say I've never noticed that when I was using Kmail, but I'm currently using mutt almost exclusively.
It might be helpful to mention how mutt deals with HTML mail. Of course, being mutt, nearly everything is configurable, but this is how I have it set up: when an email contains both a plain text version of the message and a html version of the message, mutt will display the plain text version.
But if the email only has a html version, mutt calls out to the "links" text-based web browser, and gets it to dump the html message to a plain text version. links knows how to extract the message content, ignoring irrelevant tags and formatting information. "lynx" is another text-only browser capable of a similar html-to-text dump. In either case, all you see is the plain text, with no <tags>.
Is that what you are after?
My own feeling is that any graphical email client should show the plain text message (when available), and if not available, you should have a choice between showing the html message either formatted and rendered in all it's glory (or horror), or as plain text with the formatting removed.
On Wednesday 06 May 2015 13:26:10 Steven D'Aprano wrote:
On Wed, May 06, 2015 at 12:23:58PM +0100, Lisi Reisz wrote:
Yesterday I filed a wish-bug. I am very conscious of what is involved and of how precious the developer effort and time is. The person who told me to ask said that it would be quick and easy, but quick and easy are both very subjective words.
Here is the bug report again:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=2440
Unfortunately, for some reason I can't view the screen shot, but I think I know what you are referring to.
I think you mean that Kmail displays HTML emails as raw HTML code, like the "View Source" in a web browser, full of < > tags and other formatting information. Is that what you mean?
Yes, that is exactly what I mean.
I must say I've never noticed that when I was using Kmail, but I'm currently using mutt almost exclusively.
It might be helpful to mention how mutt deals with HTML mail. Of course, being mutt, nearly everything is configurable, but this is how I have it set up: when an email contains both a plain text version of the message and a html version of the message, mutt will display the plain text version.
I have KMail set to do that, but even then I sometimes get gobbledy-gook. Here is a short extract from teh _plain_ _text_ part of a multipart email from a local supermarket:
"Morrisonsbody { width: 100%; } /* Outlook link fix */ #outlook a {padding:0;} /* Hotmail background & line height fixes */ .ExternalClass {width:100% !important;} .ExternalClass, .ExternalClass p, .ExternalClass b, .ExternalClass span, .ExternalClass font, .ExternalClass td, .ExternalClass div, .ExternalClass br {line-height: 100%;} /* Image "
But if the email only has a html version, mutt calls out to the "links" text-based web browser, and gets it to dump the html message to a plain text version. links knows how to extract the message content, ignoring irrelevant tags and formatting information. "lynx" is another text-only browser capable of a similar html-to-text dump. In either case, all you see is the plain text, with no <tags>.
Is that what you are after?
YES!!!! I hadn't realised taht it could be done.
My own feeling is that any graphical email client should show the plain text message (when available), and if not available, you should have a choice between showing the html message either formatted and rendered in all it's glory (or horror), or as plain text with the formatting removed.
That would be GREAT!!! That is what I would like for KMail, now I know that it can be done. That exactly is what I am requesting in my wish-bug.
Lisi
This is one way to convert an HTML-only email to a text-only email. It is a last resort for when no safer and easier solution can be found.
WARNING: Converting HTML to text is error prone. You may lose the content of the email. If the email is at all important COPY it to another mail folder and then try the conversion on that copy.
NOTE: These instructions assume you have not previously used any mail filters. If you have already used mail filters it's up to you to figure out how to create a new mail filter instead of following these instructions. These instructions convert the default "<unknown>" no-op mail filter to an UnHTML filter.
1. Settings / Configure Filters.
2. At left rename <unknown> to UnHTML.
3. In General tab select filter action "Pipe Through".
4. Copy/paste the following in the white box all on one line.
perl -e '$h=1;while(<>){print;if($h&&$_ eq "\n"){$h=0;open(STDOUT,"| lynx -stdin -dump")}}close(STDOUT);'
5. In Advanced tab uncheck all, except check only "Add this filter to the Apply Filter menu" and "Additionally add this filter to the toolbar".
6. OK
You should now have a blue gear wheel in your toolbar and the tooltip for it should say "Filter UnHTML".
Select the message you want to convert (or for safety a copy of it) and click the blue gear wheel. The message should disappear and then reappear without HTML a few seconds later.
WARNING: If you lose information it's your fault for not making enough backups.
Good luck!
--Mike
On Fri May 8 2015 12:14:25 Mike Bird wrote:
This is one way to convert an HTML-only email to a text-only email. It is a last resort for when no safer and easier solution can be found.
This requires the perl executable which in Debian Wheezy is in the perl-base package.
This requires the lynx executable which in Debian Wheezy is in the lynx-cur package.
--Mike
On Friday 08 May 2015 20:14:25 Mike Bird wrote:
This is one way to convert an HTML-only email to a text-only email. It is a last resort for when no safer and easier solution can be found.
WARNING: Converting HTML to text is error prone. You may lose the content of the email. If the email is at all important COPY it to another mail folder and then try the conversion on that copy.
NOTE: These instructions assume you have not previously used any mail filters. If you have already used mail filters it's up to you to figure out how to create a new mail filter instead of following these instructions. These instructions convert the default "<unknown>" no-op mail filter to an UnHTML filter.
Settings / Configure Filters.
At left rename <unknown> to UnHTML.
In General tab select filter action "Pipe Through".
Copy/paste the following in the white box all on one line.
perl -e '$h=1;while(<>){print;if($h&&$_ eq "\n"){$h=0;open(STDOUT,"| lynx -stdin -dump")}}close(STDOUT);'
- In Advanced tab uncheck all, except check only "Add this filter
to the Apply Filter menu" and "Additionally add this filter to the toolbar".
- OK
You should now have a blue gear wheel in your toolbar and the tooltip for it should say "Filter UnHTML".
Select the message you want to convert (or for safety a copy of it) and click the blue gear wheel. The message should disappear and then reappear without HTML a few seconds later.
WARNING: If you lose information it's your fault for not making enough backups.
Good luck!
Thanks, Mike!
Lisi
-
andre_debian＠numericable.fr -
Dr. Nikolaus Klepp -
Gerhard Zintel -
Lisi Reisz -
Mike Bird -
Nick Koretsky -
Steven D'Aprano