Talk:YEnc

This article is massively POV and does not adequately explain how yEnc actually works. References to uudecode and it's design deficiencies would perhaps be better understood if the principles were more adequately explained. What does structured vs. unstructured fields mean? Of what relevance is innaccuracies of reporting yEnc uptake on the website? I'd also suggest that the parenthesised segways were footnoted, or re-written to be presented after the main content. -- Jon Dowland 10:22, 25 November 2005 (UTC)

Hi, i have read yEnc specification. I was even trying to implement something based on it, but reading it all, i can say that whole yEnc is just a joke, it have many obvious (and many non-obvious) bugs, and it is useless as any kind of standard. Just stay away from it (unless it is at least fixed to being properly specified). And regarding previous comment above - wikipedia cannot tell how yEnc actually works, becuase specification on yEnc website do not tell either. To know how it works one needs to do some reverse-enginering and search in examples to try understand what-author-have-on-their-mind. --87.239.216.2 (talk) 03:19, 27 July 2010 (UTC)

Thunderbird

The current stable version of Mozilla Thunderbird directly supports YEnc. So I am removing the Mozilla reference in the paragraph about major newsreaders that do not support YEnc.—Preceding unsigned comment added by 216.99.213.82 (talk • contribs), July 27, 2006

This is correct, some less than ideal sourcing here and I have tried it with the current version of Thunderbird. If you add a yEnc attachment to a mail or news message, eg a photo, Thunderbird will decode it, whereas in Outlook Express etc it will be rendered as ASCII text gobbledegook. However, Thunderbird will not handle NZB files, or multipart binaries requiring RAR and PAR operations to extract the files. This means that Thunderbird's yEnc support is at best partial, although it will decode individual files.--♦IanMacM♦ ^{(talk to me)} 09:07, 5 February 2012 (UTC)