web/root/ecwebv3/ftelnet/ftelnet-resources connectansi.txt 1.3 1.4
Update of /cvsroot/sbbs/web/root/ecwebv3/ftelnet/ftelnet-resources
In directory cvs:/tmp/cvs-serv22886
Modified Files:
connectansi.txt
Log Message:
Synch. :O
Modified Files:
connectansi.txt
Log Message:
Synch. :O
That's cool, but the display problem remains. You can see an example of this problem at http://wd1cks.org :-(
That's cool, but the display problem remains. You can see an example of this problem at http://wd1cks.org :-(
Also, there are lingering issues with ecWebv3 when there is no "guest" account in the BBS's userbase.
Mine works! http://shodanscore.com/ smugsmug, but I kindda cheated and used ftelnet's new embedded system. You're suppoosed to be able to change
Re: web/root/ecwebv3/ftelnet/ftelnet-resources/connectansi.txt
By: Android8675 to Digital Man on Wed Jun 10 2015 09:13:17
Mine works! http://shodanscore.com/ smugsmug, but I kindda cheated and used ftelnet's new embedded system. You're suppoosed to be able to change
That would make things easier, but it would also mean that a fresh install of Synchronet (if ecweb was selected as the web interface) would rely on an external system for something. (A no-no in DM's book, and I can see why it's good as a general rule.)
I imagine this comes down to how the Synchronet webserver serves up the background file when ftelnet requests it. I changed the file's extension from .ans to .txt to avoid the ANSI web handler mangling it, but I don't know if the webserver does anything magical when it's serving up a .txt file
(specifying an encoding or something.) I believe the file itself was committed to CVS as binary and shouldn't have endured any translations during that part of the process.
It's not the file. If I copy the file from the (working) web/root/ftelnet/ftelnet-resources directory it has the same problem. So that's not it.
It's not the file. If I copy the file from the (working) web/root/ftelnet/ftelnet-resources directory it has the same problem. So that's not it.
It's not the file. If I copy the file from the (working) web/root/ftelnet/ftelnet-resources directory it has the same problem. So that's not it.
ecwebv3 is running an older version of fTelnet, so it's probably a bug I fixed at some point and I only updated the main folder on CVS.
I haven't worked on the old flash version in a couple years now...now that WebSockets have stabilized I'm only working on the HTML5 version, which I've been meaning to get on CVS for awhile now (I've always been too lazy to do the install/upgrade/upgrade/upgrade thing to get an up-to-date system to test with, but I see there's a new installer being tested so I'll have to give that a shot).
And the easiest way to get the new version on there is to use the embed method, which loads the javascript/css/etc resources from my server. I'm guessing you don't want to rely on external services though, so you'd prefer having a local install?
Re: web/root/ecwebv3/ftelnet/ftelnet-resources/connectansi.txt
By: Digital Man to echicken on Thu Jun 11 2015 23:30:21
It's not the file. If I copy the file from the (working) web/root/ftelnet/ftelnet-resources directory it has the same problem. So that's not it.
Flash likes to cache things, so you may need to use the utility on the following page, and possibly restart your browser, in order to force it to load a new copy of that file:
http://tinyurl.com/59gyz
If at that point you've copied a known-working copy of the file over and the problem goes away, then we can blame the file. Otherwise the problem is in fTelnet, the Synchronet web server, or ecWeb.
I think I've tried copying all the files from web/root/ftelnet to web/root/ecwebv3/ftelnet and the problem persists. It's been a
long-standing issue with ecwebv3. It's just cosmetic, I think, but it's annoying. :-(
I think I've tried copying all the files from web/root/ftelnet to web/root/ecwebv3/ftelnet and the problem persists. It's been a long-standing issue with ecwebv3. It's just cosmetic, I think, but it's annoying. :-(
So it works for you with the default theme, but not with ecwebv3?
I just
tried here and it looks garbled for both templates for me on my system.
I
just had a look at vert and it looks like you're not using connectansi.txt, which means the embedded ANSI gets displayed, and that works fine.
Further digging...
file -bi indicates the connectansi.txt is utf-8, and it looks like that's the problem.
I used a really convoluted method to create a new file (echo base64_encoded_ansi | base64 --decode > connectansi.bin), and file -bi indicates it is iso-8859-1, and it's now working fine for me.
From what I've read iconv should be able to do the conversion, but I couldn't get it to work for me.
file -bi indicates the connectansi.txt is utf-8, and it looks like
that's the problem.
It's not UTF-8, it's CP437 with ANSI X3.16 terminal escape sequences, what we BBS folk usually call an "ANSI file". It's possible that "file" can't tell the difference.
And the easiest way to get the new version on there is to use the embed method, which loads the javascript/css/etc resources from my server. I'm guessing you don't want to rely on external services though, so you'd prefer having a local install?
file -bi indicates the connectansi.txt is utf-8, and it looks like that's the problem.
It's not UTF-8, it's CP437 with ANSI X3.16 terminal escape sequences, what we BBS folk usually call an "ANSI file". It's possible that "file" can't tell the difference.
Could be that it's just mis-detecting it, but the file that works is almost half the size of the file that doesn't work, so there's definitely some difference. And the fact that utf-8 would need two bytes to store the high ascii explains the almost doubling in size, so I doubt it's mis-detecting.
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 136 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 08:08:54 |
| Calls: | 15,171 |
| Calls today: | 4 |
| Files: | 19,857 |
| D/L today: |
9 files (848K bytes) |
| Messages: | 1,691,487 |