 |
 |
|
 |
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Post a reply to this message
Attachments:
Download '=ybegin line=128 size=79710 name=TerminatorSide.png.dat' (81 KB)
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
hi,
Clarence1898 <dle### [at] comcast net> wrote:
> ...
Attachments:
Download '=ybegin line=128 size=79710 name=TerminatorSide.png.dat' (81 KB)
none of those three files download or display, for me, unsurprising perhaps
given the names ;-).
regards, jr.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Le 2025-08-21 à 10:47, Clarence1898 a écrit :
> No, not about Arnold. I have always liked to model odd things. This is
> from my early mainframe days. Control units were daisy chained on channel
> cables. This gadget was attached at the end to terminate the channel
> cable. I doubt that I will ever use it in a scene, but it was fun to
> model.
>
Please, do NOT use yEnc. Almost nobody can see your image. yEnc is
fatally broken. Let it die. Unless I have support for the exact same
version as you do, all I can see is strings of random garbage like this :
N***@�o��}
�������*zy�W|��J]XaXZm��***~�o��m������*|�����Jn���dJ\Z\_WZbW\ZJ\]d\]dZc�4z�������dJ�b`�`^W��W���4m�������dJ����J[Z4+p�**J*snk
~�����#�!i���"L��n�������X��B�f=M��`�70���0s�0�L�,-Tp��b��Na���*Q6���r=@���ȸT���~|�<o=[�f�����
��P9S���1pk
���M?O�#i�1�&q,****���/*****�6.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,
+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j
*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:
�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.
�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B
****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0
****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+
****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+****�j*0****�,+B****=J4.�****�U:�+**Z1��c(3*��5***�`"�Y�4
w�餜i(p`D7%��s*��*6**�cR����:
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Le 2025-08-21 à 11:03, jr a écrit :
> hi,
>
> Clarence1898 <dle### [at] comcast net> wrote:
>> ...
> Attachments:
> Download '=ybegin line=128 size=79710 name=TerminatorSide.png.dat' (81 KB)
>
> none of those three files download or display, for me, unsurprising perhaps
> given the names ;-).
>
>
> regards, jr.
>
Welcome to the nightmare that is yEnc encoding. A format that is
incompatible with pretty much all E-mail clients and web browsers. You
need a special yEnc E-mail client to view that.
Even better, clients from one source may not properly display a post
made with a client from another source.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
hi,
Alain Martel <kua### [at] videotron ca> wrote:
> > ...
> > none of those three files download or display, ...
>
> Welcome to the nightmare that is yEnc encoding. A format that is
> incompatible with pretty much all E-mail clients and web browsers. You
> need a special yEnc E-mail client to view that.
> Even better, clients from one source may not properly display a post
> made with a client from another source.
thanks for the heads-up, had not known of this abomination </grin>. Wikipedia
explains: The name yEncode is a wordplay on "Why encode?". quite..
regards, jr.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Clarence1898 <dle### [at] comcast net> wrote:
> No, not about Arnold. I have always liked to model odd things. This is
> from my early mainframe days. Control units were daisy chained on channel
> cables. This gadget was attached at the end to terminate the channel
> cable. I doubt that I will ever use it in a scene, but it was fun to
> model.
My apologies to everyone. I couldn't figure how to attach multiple files with
the povray web page. I tried a news reader program not realizing how it encoded
the files. How do I attach multiple files in a povray post?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Thu, 21 Aug 2025 18:16:34 EDT, Clarence1898 wrote:
> My apologies to everyone. I couldn't figure how to attach multiple
> files with the povray web page. I tried a news reader program not
> realizing how it encoded the files. How do I attach multiple files in a
> povray post?
Probably the best thing to do is use something like Thunderbird. The
version of Pan you tried is pretty old (the current version is 0.164, you
tried 0.149, which came out in 2021.
The current version doesn't include file attachments (that I can see).
FWIW, using Pan 0.163, I was able to see the images you uploaded just
fine, but the web interface hasn't implemented a decoder for it.
And, of course, Thunderbird doesn't understand it either. The yenc
website also appears to be offline at the moment, though it was active as
recently as June of this year.
--
"I learned long ago, never to wrestle with a pig. You get dirty, and
besides, the pig likes it." - George Bernard Shaw
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Thu, 21 Aug 2025 11:48:43 EDT, jr wrote:
> thanks for the heads-up, had not known of this abomination </grin>.
> Wikipedia explains: The name yEncode is a wordplay on "Why encode?".
> quite..
The Wikipedia author must have asked ChatGPT. :laughing:
Here's what the official site says (pulled from the Internet Archive as
the site seems to be offline):
"You might ask why the name of this thing is "yEnc" - yEncoding,
yDecoding.
Well - I did introduce the name "MyNews" for another project (in 1997)
long before everybody began to use My-Xxxx for his services or domain
names. When I designed the new encoding I needed any name for it. But as
all the 'MyXxxx' names were already in use (so I could not use MyEnc). I
wanted a new name - which is nearly unique on the Internet. The name
"yEncode" was never used - and the short form would be yEnc. The file-
extension *.ync would also be unique - so I found a short and good name."
https://web.archive.org/web/20240704064321/http://www.yenc.org/whatis.htm
--
"I learned long ago, never to wrestle with a pig. You get dirty, and
besides, the pig likes it." - George Bernard Shaw
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
hi,
Jim Henderson <nos### [at] nospam com> wrote:
> On Thu, 21 Aug 2025 11:48:43 EDT, jr wrote:
> ...
> > Wikipedia explains: The name yEncode is a wordplay on "Why encode?".
> > quite..
>
> The Wikipedia author must have asked ChatGPT. :laughing:
>
> Here's what the official site says (pulled from the Internet Archive as
> the site seems to be offline):
thank you for the explanation. I had wondered, seeing the file names, if
there'd been a "configuration issue". fwiw, the more "glib" version does sort
of sum it all up, neatly.
@Clarence1998
the web-ui is "clunky", but your previous posts were alright, so why not simply
"revert" to that method ?
regards, jr.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Le 2025-08-21 à 18:16, Clarence1898 a écrit :
> Clarence1898 <dle### [at] comcast net> wrote:
>> No, not about Arnold. I have always liked to model odd things. This is
>> from my early mainframe days. Control units were daisy chained on channel
>> cables. This gadget was attached at the end to terminate the channel
>> cable. I doubt that I will ever use it in a scene, but it was fun to
>> model.
>
> My apologies to everyone. I couldn't figure how to attach multiple files with
> the povray web page. I tried a news reader program not realizing how it encoded
> the files. How do I attach multiple files in a povray post?
>
From the web interface, you can only attach a single file.
You need to use a proper client. I recommend Thunderbird. In a pinch,
you may even use Outlook/Outlook Express.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|
 |