What directory do I put background images in to use on the website?? sbbs/webv4/???? I created a custom.css in sbbs/webv4/root/css. Is this the
body {
background: url(background.jpg);
}
What directory do I put background images in to use on the website?? sbbs/webv4/???? I created a custom.css in sbbs/webv4/root/css. Is this the right tag if the name of the background is "background.jpg"??
Re: Webv4
By: HusTler to All on Tue May 28 2019 16:33:46
What directory do I put background images in to use on the website?? sbbs/webv4/???? I created a custom.css in sbbs/webv4/root/css. Is this
Anywhere you like, as long as it's publically accessible (the browser needs be able to source the image from there). I'll suggest:
sbbs/webv4/root/images/
body {
background: url(background.jpg);
}
I believe the URL needs to be quoted. If you create an "images" directory a put "background.jpg" there:
background: url("/images/background.jpg");
I also like more webv4 but with it I have not been able to put it in
LATIN-1. Here in Spain we use LATIN-1, which is ISO8859-1 (or -15). That
makes the tildes, eñes and umlauts come out well for all users in Spain. On
the other hand, the Runemaster website has been able to make the tildes,
eñes and umlauts come out well.
If you know how to put webv4 in iso8859-1 I will be very grateful :)
Thank you again
you're welcome, echicken may be able to help you with that better than, webv* is his baby :)
I also like more webv4 but with it I have not been able to put it in
LATIN-1. Here in Spain we use LATIN-1, which is ISO8859-1 (or -15). That
makes the tildes, eñes and umlauts come out well for all users in Spain. On
Echicken, can you help me on this? I would be very grateful :)
http_reply.header['charset'] = 'iso-8859-1';
If that doesn't work, you could try adding this, further down in the same file, inside the <head> element:
<meta charset="ISO-8859-1">
Let me know if one or both of those works for you, and I can add it as a configurable option.
The message come out with the Kudge CHRS: UTF-8 4. In golded, which doesnot have support for UTF-8,
they are not seen correctly. If they come out with CHRS: CP437 2 (which iswhat happened with the
old web) it seems that if the tildes and others are seen well, but withUTF-8 no. It must be
sbbsecho who puts the kludges.
I wish there was a field to choose the charset for each message area
or each group of message areas even if only sbbsecho used to
import/export messages. Maybe in the new versions :). I don't know
how difficult that would be.
I wish there was a field to choose the charset for each message area
or each group of message areas even if only sbbsecho used to
import/export messages. Maybe in the new versions :). I don't know
how difficult that would be.
each message area has a toggle to detect UTF-8 or not... perhaps that's what you're looking for? i think you'll have to set it for each area because it is not copied from the template area...
I might have misunderstood the problem that you're describing.
Are you saying that messages *posted* from webv4 aren't being displayed properly elsewhere?
Or are you having trouble *viewing* messages in webv4?
If the problem is with messages *posted* via webv4, you can try searching for "UTF-8 4" in webv4/lib/forum.js. You should find it twice in that file, and you could try replacing both with "CP437 2" or whatever value you think will work.
Hola Echicken!
15 Jul 20 22:32, echicken escribi¢ a Angel Ripoll:
I might have misunderstood the problem that you're describing.
Are you saying that messages *posted* from webv4 aren't being displayed properly elsewhere?
Or are you having trouble *viewing* messages in webv4?
I speak of the first, but the second also occurs.
If the problem is with messages *posted* via webv4, you can try searching for "UTF-8 4" in webv4/lib/forum.js. You should find it twice in that file, and you could try replacing both with "CP437 2" or whatever value you think will work.
Tried. It does not work.
I tell you what I see happening. I put CP437 or ISO-8859-1 in root / index.xjs, in the two sites you told me about. And I put the same in lib / forum.js. The web, when I write, detects that it is CP437, but when I write ticked aeiou, in lowercase and uppercase, as well as the u with umlaut and eñe, the PKT that it generates comes out with the kudge "CHSR: CP437 2" but the vowels come out in UTF-8 (the ticked a comes out as C3 A1 in Hex, the ticked e comes out as C3 A9, etc).
Hola Rampage!
16 Jul 20 07:57, Rampage escribi¢ a Angel Ripoll:
I wish there was a field to choose the charset for each message area
or each group of message areas even if only sbbsecho used to
import/export messages. Maybe in the new versions :). I don't know
how difficult that would be.
each message area has a toggle to detect UTF-8 or not... perhaps that's what you're looking for? i think you'll have to set it for each area because it is not copied from the template area...
I just tried and nothing. Still the same. It was disabled, I have enabled it and the same result.
It is not exactly what I am looking for. What I would like, I don't know how difficult it would be to implement, is that each area or each group of areas had a field in which to choose the character encoding.
The ideal would be for Golded, the most widely used fido reading and writing program in Europe, to have full UTF-8 support. UTF-8 is the best encoding and valid for all languages.
But that's not going to happen because it's not updating or at least I haven't seen updates for years
The Synchronet message base (and related programs, including SBBSecho) only support 3 character sets/encodings: - US-ASCII - CP437 - UTF-8
That's not practical. Not every message posted in a message group would be assured to use the same character set/encoding. If I login to your BBS with a CP437 terminal (i.e. most BBS terminals), it's impossible for me to post a message in CP870 or CP866 or even UTF-8. The character set and encoding of the characters in a stored message is partly a function of the terminal in use at the time of the message writing.
And similarly, when viewing messages, you can't change the terminal to magically support CP870 just because the user switch from a CP437 message group to a CP870 message group. Terminals don't work that way. The only solution is to use UTF-8.
The ideal would be for Golded, the most widely used fido reading and
writing program in Europe, to have full UTF-8 support. UTF-8 is the best
encoding and valid for all languages.
But that's not going to happen because it's not updating or at least I
haven't seen updates for years
It's open source. Update it or find some other interested user-developers to update it. It can be done.
I might have misunderstood the problem that you're describing.
Are you saying that messages *posted* from webv4 aren't being displayed properly elsewhere?
Or are you having trouble *viewing* messages in webv4?
Hola Digital!
16 Jul 20 21:32, Digital Man escribi¢ a Angel Ripoll:
That's not practical. Not every message posted in a message group would be assured to use the same character set/encoding. If I login to your BBS with a CP437 terminal (i.e. most BBS terminals), it's impossible for me to post a message in CP870 or CP866 or even UTF-8. The character set and encoding of the characters in a stored message is partly a function of the terminal in use at the time of the message writing.
I get it. Although I use the Mate terminal in linux and if it allows me to choose the charset I want, i understand that many terminals do not give that option.
And similarly, when viewing messages, you can't change the terminal to magically support CP870 just because the user switch from a CP437 message group to a CP870 message group. Terminals don't work that way. The only solution is to use UTF-8.
I know, UTF-8 is the best solution. I don't dispute that. But now it is not my choice because I am not a programmer and I cannot give golded UTF-8 support. I would like to.
The ideal would be for Golded, the most widely used fido reading and
writing program in Europe, to have full UTF-8 support. UTF-8 is the best
encoding and valid for all languages.
But that's not going to happen because it's not updating or at least I
haven't seen updates for years
It's open source. Update it or find some other interested user-developers to update it. It can be done.
I know it's open source. I asked a few months ago if full support for utf-8 was planned and the answer was a resounding no
I'd like to do it myself, but I wouldn't even know how to start.
Hola Digital!
16 Jul 20 21:26, Digital Man escribi¢ a Angel Ripoll:
The Synchronet message base (and related programs, including SBBSecho) only support 3 character sets/encodings: - US-ASCII - CP437 - UTF-8
Is it very difficult to also support Latin-1 (Latin-9) and CP866 for Russia and Ukraine? I'm not a programmer, so I don't know how difficult it can be.
Putty can. If CP866 support will be added into Synchronet on same conditions as CP437 I will became the beta-tester of this feature (and can spread wide this in Russia and Ukraine)
Hola Echicken!
15 Jul 20 22:32, echicken escribi¢ a Angel Ripoll:
I might have misunderstood the problem that you're describing.
Are you saying that messages *posted* from webv4 aren't being displayed properly elsewhere?
Or are you having trouble *viewing* messages in webv4?
I am doing more tests.
I write a message with the vowels marked in upper and lower case, as well as the eñe, umlauts and the euro symbol from the web, from the BBS by telnet and from golded using that golded can directly read the synchronet configuration.
For telnet I use the debian MATE terminal, which allows me to choose the charset and for golded I use it in the same terminal. At this terminals I choose iso-8859-15.
From the BBS and from golded the characters come out well. The PKT that synchronet generates is not generated in UTF-8, but it is in iso-8859-15 like the terminal.
On the other hand, when I do it from the web it is not like that. The test that I have done is to read the message that I have written in the BBS from the terminal that goes well. I go to the web, read it and chrome detects iso8859-15 and read it well. I reply to that message and it seems like I write it well, but when I save it, it looks bad. I change the encoding of the page to UTF-8 and it reads perfect while the original message misread. I see the PKT that will have that answer and i see that it is in UTF-8.
That is, according to these tests, if I write directly to the BBS by telnet or directly in the golded area, it works, but if I do it on the web, somehow, when it reaches the message area, it does it in UTF- 8.
Putty can. If CP866 support will be added into Synchronet on same
conditions as CP437 I will became the beta-tester of this feature (and can
spread wide this in Russia and Ukraine)
I'm interested in doing this and would need an active participant/user (like yourself). But you're writing your messages using GoldEd, which seems to imply that you're not even running Synchronet or not using it for reading/writing messages?
And that is all incorrect. If another user logins into your BBS and reads those messages using a common BBS terminal that assumes CP437 charset, those special characters are not going to be displayed to them as intended.
Sure, but your terminal can't dynamically switch which codepage/charset it's expecting depending on what message area you happen to be viewing. It doesn't work that way. With codepages, modal: it's all or nothing. With UTF-8, you get all the possible glyphs/characters displayable in a single mode (no codepage switch necessary).
Simple "tagging" content (messages) as being of some special arbitrary charset (not UTF-8) is not nearly enough. All the programs that display or modify that content then need to recoginize that special charset and handle the translations as appropriate, dynamically.
I'd like to do it myself, but I wouldn't even know how to start.
Then use a different program?
Hola Digital!
18 Jul 20 11:56, Digital Man escribi¢ a Angel Ripoll:
Putty can. If CP866 support will be added into Synchronet on same
conditions as CP437 I will became the beta-tester of this feature (and can
spread wide this in Russia and Ukraine)
I'm interested in doing this and would need an active participant/user (like yourself). But you're writing your messages using GoldEd, which seems to imply that you're not even running Synchronet or not using it for reading/writing messages?
My BBS with synchronet is operational 24x7 in bbs.zruspas.org
I have two fidonet nodes. 2:341/66 is on Binkd + HPT + Golded and 2:341/200 is on Synchronet.
I usually read netmails/echoamils from golded in 2:341/66, but I can test from one or the other or from one to the other.
I can be a beta tester if that's what you need.
I have not found any such program for linux that reads JAM message base and has full UTF-8 support. If you know it or someone knows it, it would be great.
Are you interested in testing CP866 (Cyrillic) or some other character set?
Hola Digital!
19 Jul 20 11:54, Digital Man escribi¢ a Angel Ripoll:
Are you interested in testing CP866 (Cyrillic) or some other character set?
ISO-8859-15 (Latin9) or ISO8859-1 (Latin1).
CP866 wouldn't even know to read it.
What's a JAM message base got to do with anything?
WOW, mat hat goes off to you and MLong for the Dark Mode option on webv4.
I am curious however, is there a way to make the dark mode default, and let the user switch it to light mode if wanted. That would be more in line
I am curious however, is there a way to make the dark mode default,
and let the user switch it to light mode if wanted. That would be
more in line
Not at the moment, but I'll add that as a config option; should be pretty simple.
That was a recently added feature of webv4. You could update your webv4 install if you want to go that route. https://github.com/echicken/synchronet-web-v4
Ttyl :-),
Al
ok so got the switch for light to dark now having problem with fTelnet it showing up small on the page
I have noticed on some of the websites using webv4 some of them have a switch from light to dark was wondering how do you get that??
ok so got the switch for light to dark now having problem with fTelnet it showing up small on the page
ok so got the switch for light to dark now having problem with fTelnet it showing up small on the page
--- SBBSecho 3.11-Win32
* Origin: Canadian Rebel (1:153/802)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
ok so got the switch for light to dark now having problem with fTelnet it showing up small on the page
Re: Webv4
By: Dave L to All on Sat Mar 06 2021 20:08:20
If this is your site:
http://canadianrebel.sytes.net:90/
it looks fine to me. fTelnet is the correct size.
If you're still having a problem, maybe post a screenshot somewhere so I can see what you're seeing - and let me know which browser & OS you're viewing it from.
---
echicken
electronic chicken bbs - bbs.electronicchicken.com
---
� Synchronet � electronic chicken bbs - bbs.electronicchicken.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
If you're still having a problem, maybe post a screenshot somewhere so I can see what you're seeing - and let me know which browser & OS you're viewing it from.
Yeah we fixed it thanks :)
I have noticed on some of the websites using webv4 some of
them have a switch from light to dark was wondering how do
you get that??
https://github.com/echicken/synchronet-web-v4
Thanks I tried the files and still not working don't see the switch
Nice site, btw, especially like Canadian Rebel Internet Radio page, blows my alleycat radio away :-)
I tried to send you an 'Email the SysOP' from your Ftelnet Login Matrix, but I was informed that I 'have sent too many emails today' :(
~mortifis
who is we
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 189:36:12 |
| Calls: | 2,004 |
| Calls today: | 1 |
| Files: | 11,114 |
| Messages: | 942,271 |
![http://yourbbs.com/pics/background.jpg"](http://yourbbs.com/pics/background.jpg"){kind=link}