Not Really TN: Blind wines, I swing and miss

p.s. For some reason, Dale, your post had no line breaks in it, so had lines much longer than 79 characters. I had to reformat your quoted text before I was allowed to post through the AIOE server. Weird!

Mark Lipton

"Bi!!" wrote in news: snipped-for-privacy@m20g2000prc.googlegroups.com:

I have had the luck to taste TR on a few occasions and I have been less than impressed with older bottles. It is mostly out of my budget anyway, but I rather buy a recent vintage than an older one.

Any of you has a track record with bottles older than -say- 20 years?

s.

Actually, Mark, this is up your alley. Or not entirely - this is due to the interplay of your TB settings with a subtle change in Dale's posting method. I suggest you set your TB to support format-flowed on both reading and writing. Unfortunately I don't know if it is in the same place in TB.3 - I was so disgusted by the "improvements" in it, that I promptly uninstalled it and went back to TB2. Here, in TB2, the settings are in about:config (Tools-> Options-> Advanced-> Config Editor), and should be mailnews.display.disable_format_flowed_support -> false mailnews.send_plaintext_flowed -> true As a matter of fact, Dale's post has hard-coded line breaks, which you can see by looking at the message source. The difference in his posting, which I suspect triggered the effect you observe, is that he changed his encoding from ISO-8859-1 to windows-1252, which made GoogleCrap switch the transfer encoding to quoted-printable. I'm not sure Dale is aware of any of these changes.

Aha! Thanks, Elk...er... Patok ;-) Suffice it to say that I would never have found that on my own. As I use a Mac (and TB 3.1.7), the about:config settings were accessed in Thunderbird-> Preferences-> Advanced-> General-> Config Editor. As expected, I found that the second variable was set to false and so changed it. (Dale's posts were being displayed correctly; it was only when I tried to reply that the line breaks got munged) Interestingly, when I look at the message source, I do see line breaks, but also = at the end of each line -- a windows-1252 thing?

Thanks again! Mark Lipton

You're more than welcome! And good detective work - how did you find out? I'm usually careful to separate them, even though I don't normally post stuff as one that I wouldn't as the other; it's just for fun. :) But it's been a long time since I was myself here, and I'm curious how you did it.

No, I think it is a quoted-printable artifact. However, I'm pretty sure it was triggered by the Windows-1252 charset change.

Oh, it's my usual nosey behavior. Back when we had a discussion here about the stereotypes of Bulgaria, I recalled a semi-regular poster who had a Bulgarian-sounding name. A bit of searching Google's archive and Googling the web made the connection, in part courtesy of umbc's website. The connection stuck in my mind owing to my long-standing interest in genetic algorithms, actually ;-)

Mark Lipton