Hola All!, saludo cordial

I compiled Linux version and it works fine, issue I have is basically when accessing from windows SecureCRT or Putty, I cannot seem to find the right emulation setting or terminal mode.

Does anyone have any experience running Golded rmeotely and showing up properly?

Thanks

--
Saludos/Kind Regards
David
- SysOp SkyNet BBS
- telnet://bbs.skynet.com:20023
SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30 50 700 SEEN-BY: 203/0 220/90 221/0 6 226/18 44 50 229/426 240/1120 5832 280/464 5003 SEEN-BY: 280/5006 5555 292/854 8125 301/1 310/31 341/66 234 396/45 423/120 SEEN-BY: 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26 930/1 SEEN-BY: 2320/105 3634/12 5020/400

Hi David,

On 2024-11-19 12:00:30, you wrote to All:

I compiled Linux version and it works fine, issue I have is basically
when accessing from windows SecureCRT or Putty, I cannot seem to find
the right emulation setting or terminal mode.

Does anyone have any experience running Golded rmeotely and showing up properly?

Can you do a rescan of this area (about 300 messages back will do)? In Februari and March I had a long thread with a few other people to get this right on my linux konsole, and remotely with Putty. Maybe it contains some useful clues for you...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello David!

19 Nov 24 12:00, you wrote to all:

I compiled Linux version and it works fine, issue I have is basically

[...]

--
Saludos/Kind Regards
David
- SysOp SkyNet BBS
- telnet://bbs.skynet.com:20023
SEEN-BY: 4/0 90/0 103/705 124/5016 153/757 154/10 30 203/0 221/0

It actually isn't working fine. There is no Origin or Tear lines on all of your messages.



Stephen


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

Hola Stephen!, saludo cordial

20 Nov 24 09:53, tu escribi(ste) a ti:

Erm ok, I noticed, but no idea why it happens when I use a TPL file looking into that, and this is windows version LoL

Hello David!

19 Nov 24 12:00, you wrote to all:

I compiled Linux version and it works fine, issue I have is
basically

[...]

--
Saludos/Kind Regards
David
- SysOp SkyNet BBS
- telnet://bbs.skynet.com:20023
SEEN-BY: 4/0 90/0 103/705 124/5016 153/757 154/10 30 203/0 221/0

It actually isn't working fine. There is no Origin or Tear lines on
all of your messages.

Stephen

--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30 50 700 SEEN-BY: 203/0 220/90 221/0 6 226/18 44 50 229/426 240/1120 5832 280/464 5003 SEEN-BY: 280/5006 5555 292/854 8125 301/1 310/31 341/66 234 396/45 423/120 SEEN-BY: 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26 930/1 SEEN-BY: 2320/105 3634/12 5020/400

Hello David,

On Wed, Nov 20 2024 07:38:50 -0600, you wrote:

Erm ok, I noticed, but no idea why it happens when I use a TPL file
looking into that, and this is windows version LoL

Because it's not part of the template file. It's something you need to define in your config file.

TEARLINE <tearline>
ORIGIN <origin>

Do a search for GOLD_REF.TXT, as I said on a couple of occasions already, it will be your best friend (and tell you every option available to you, with descriptions on what they do).

SEEN-BY: 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26 930/1 SEEN-BY: 2320/105 3634/12 5020/400

While they don't seem to show up in Golded (Golded must still filter this), I'm seeing your SEEN-BYs in every message you post, too. These don't look like they start with a CTRL character to be a proper kludge, either.

Are trying to invalidate these in your Golded config by removing the "@" or something?

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hi Nicholas,

On 2024-11-20 19:38:57, you wrote to David Gonzalez:

SEEN-BY: 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26
930/1
SEEN-BY: 2320/105 3634/12 5020/400

While they don't seem to show up in Golded (Golded must still filter this),
I'm seeing your SEEN-BYs in every message you post, too. These don't look like
they start with a CTRL character to be a proper kludge, either.

Are trying to invalidate these in your Golded config by removing the "@" or
something?

His seen-bys look fine here? Maybe your reader gets confused when the origin line is missing?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Thu, Nov 21 2024 05:32:21 -0600, you wrote:

While they don't seem to show up in Golded (Golded must still filter this),
I'm seeing your SEEN-BYs in every message you post, too. These don't look like
they start with a CTRL character to be a proper kludge, either.

Are trying to invalidate these in your Golded config by removing the "@" or
something?

His seen-bys look fine here? Maybe your reader gets confused when the origin line is missing?

I just got done saying it works fine in Golded, which is what you're using.. so it would look fine there.

Maybe it is my reader, I don't know. It also displays these SEEN-BYs on my BBS, which does indeed know what FTN kludges are, and shouldn't matter if there is an origin line or not.

I checked in Golded as well, and the "@" (which I think is just a translation of a CTRL character) was missing before all SEEN-BY lines, yet Golded still hides them (which is great for Golded, but my current reader and BBS software is treating it like regular text, because there is no CTRL character before it, as far as I can tell.

So I can only guess that something is stripping the CTRL character before that specific kludge, as that "@" character is still there on all the other kludges of his message (and I don't see any of those in my reader, either), and it doesn't happen with anyone else that I've read in the past few weeks.

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hi Nicholas,

On 2024-11-21 16:05:45, you wrote to me:

While they don't seem to show up in Golded (Golded must still

filter
this),

I'm seeing your SEEN-BYs in every message you post, too. These don't

look like

they start with a CTRL character to be a proper kludge, either.

Are trying to invalidate these in your Golded config by removing the

"@" or

something?

His seen-bys look fine here? Maybe your reader gets confused when the origin
line is missing?

I just got done saying it works fine in Golded, which is what you're using..
so it would look fine there.

Maybe it is my reader, I don't know. It also displays these SEEN-BYs on my BBS, which does indeed know what FTN kludges are, and shouldn't matter if there is an origin line or not.

I checked in Golded as well, and the "@" (which I think is just a translation
of a CTRL character) was missing before all SEEN-BY lines, yet Golded still
hides them (which is great for Golded, but my current reader and BBS software
is treating it like regular text, because there is no CTRL character before
it, as far as I can tell.

SEEN+BY lines normally don't have a CTRL character in front of them!

So I can only guess that something is stripping the CTRL character
before that specific kludge, as that "@" character is still there on
all the other kludges of his message (and I don't see any of those in
my reader, either), and it doesn't happen with anyone else that I've
read in the past few weeks.

So I still think the SEEN-BY lines in this case are treated as normal text, because the origin line is missing...

They will only be treated special if they come after the origin line, which normally is the last readable line in a message, so it triggers your reader, to hide the lines comming after the origin line (my guess).

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Thu, Nov 21 2024 16:26:44 -0600, you wrote:

SEEN+BY lines normally don't have a CTRL character in front of them!

Ok.

So I still think the SEEN-BY lines in this case are treated as normal
text, because the origin line is missing...

Maybe.

They will only be treated special if they come after the origin line,
which normally is the last readable line in a message, so it triggers
your reader, to hide the lines comming after the origin line (my
guess).

I've let Rob know, as this reader is just accessing my Synchronet message bases via NNTP, and those SEEN-BYs are also displayed when logged into the BBS via telnet, so it's not just this reader.

Granted, if there was an origin line, I probably would have never seen this issue.

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Re: Re: Linux golded
By: Nicholas Boel to Wilfred van Velzen on Thu Nov 21 2024 04:46 pm

I've let Rob know, as this reader is just accessing my Synchronet message bases via NNTP, and those SEEN-BYs are also displayed when logged into the BBS via telnet, so it's not just this reader.

SBBSecho requires a tear line and/or an origin line in the message text before it'll start parsing SEEN-BYs and placing them in the message header (where FTN seen-bys are properly stored in a Synchronet Message Base). That's by design.
--
digital man (rob)

Steven Wright quote #33:
Everyone has a photographic memory; some just don't have film.
Norco, CA WX: 77.8øF, 11.0% humidity, 2 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Rob,

On Thu, Nov 21 2024 17:07:00 -0600, you wrote:

I've let Rob know, as this reader is just accessing my Synchronet message bases via NNTP, and those SEEN-BYs are also displayed when logged into the BBS via telnet, so it's not just this reader.

SBBSecho requires a tear line and/or an origin line in the message
text before it'll start parsing SEEN-BYs and placing them in the
message header (where FTN seen-bys are properly stored in a Synchronet Message Base). That's by design.

Ok. Thanks for the response!

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hola David!

19 Nov 24 12:00, David Gonzalez dijo a All:

Hola All!, saludo cordial

I compiled Linux version and it works fine, issue I have is basically when accessing from windows SecureCRT or Putty, I cannot seem to find the right emulation setting or terminal mode.

Does anyone have any experience running Golded rmeotely and showing up properly?

I do. I use this line:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx -Cpath_to_cfg

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hello Angel!

24 Nov 24 15:12, you wrote to me:

Hola David!

19 Nov 24 12:00, David Gonzalez dijo a All:

Hola All!, saludo cordial

I compiled Linux version and it works fine, issue I have is
basically when accessing from windows SecureCRT or Putty, I
cannot seem to find the right emulation setting or terminal mode.

Does anyone have any experience running Golded rmeotely and
showing up properly?

I do. I use this line:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx -Cpath_to_cfg

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

Thanks Angel, I tried your suggestion and Fernando Toledo's sample config with no luck my golded still looks like this:

Pick New Area: lqAreaqDescriptionqqqqqqqqqqqMsgsqqqqNewqqEchoIDqqqqqqqqGqkxqqqqqqGrupo de Echomailsqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq x 1 Area de pruebas 0 ESP.PRUEBAS 27 0 ESP.PRUEBAS F

x 2 REGION93 0 REGION93 F
x 3 ZONA4.GENERAL 0 ZONA4.GENERAL F
xqqqqqqGrupo etmailsqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq x 4 Bad-fido 0 0 Bad-fido N
x 5 Netmail-fido 23 0 Netmail-fido N
x 6+ ESP.COLOMBIA 9 2 ESP.COLOMBIA S xqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
Wird thing Synchronet's scfg and echocfg look just fine, meaning lineas and that stuff.

I also tried enabling and disabling lines no luck, ,y golded.cfg looks like this, for reference

// incluir el archivo de areas que genera crashexport
include areas.golded

// includes de paths de archivos de config de la instalacion
// tengan en cuenta que por defecto se instala en /usr/local
// y si estos includes no estan el golded no inicia
;include ./golded-plus/cfgs/colorset/gedcol02.cfg
;xlatpath ./golded-plus/cfgs/charset
;include ./golded-plus/cfgs/config/charsets.cfg

// algunas configs para converir los charsets
// posiblemente alguien en fido me paso estas opciones
// y veo bien las tildes y demas caracters
;xlatimport ibmpc
;xlatcharset ibmpc latin-1 ibm_iso.chs
;xlatcharset latin-1 ibmpc iso_ibm.chs
;xlatcharset latin-1 latin-1 iso_iso.chs
;xlatcharset ibmpc ibmpc ibm_ibm.chs

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx -Cpath_to_cfg

// configuracion de los paths para los nodelists
NODEPATH /home/sbbs/fido/filebox/nodelist/
NODEPATHFD /home/sbbs/fido/filebox/nodelist/
NODEPATHIM /home/sbbs/fido/filebox/nodelist/
NODEPATHV7 /home/sbbs/fido/filebox/nodelist/
NODELIST NODELIST.099
NODELISTWARN yes

// Mostrar las lineas ocultas de los mensajes (kludges desconocidos). VIEWHIDDEN YES
// Mostrar kludges conocidos. (Los que estan definidos e incluidos en la opci¢n KLUDGE).
VIEWKLUDGE YES
// Iniciar con la vista de listado de mensajes.
MSGLISTFIRST yes

// otras opciones comunes, (ver docu de golded)
areascan *
ADDRESSBOOKADD ALWAYS
MSGLISTFAST YEs
MSGLISTHEADER yes
showdeleted no

; opciones para ver agrupadas las areas segun la letra de grupo
; que nos exporta el crashmail al archivo areas.golded
AREALISTSORT G
AREASEP !N "Grupo Netmails" N Net
AREASEP !D "Grupo de Echomails" D Echo


David
SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30 50 700 SEEN-BY: 203/0 220/20 90 221/0 6 226/18 44 50 229/426 240/1120 5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1 310/31 341/66 234 396/45 SEEN-BY: 423/120 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 SEEN-BY: 902/26 930/1 2320/105 3634/12 5020/400

Hello David,

On Sun, Nov 24 2024 16:42:24 -0600, you wrote ..

Thanks Angel, I tried your suggestion and Fernando Toledo's sample
config with no luck my golded still looks like this:

You should probably start over with your config. Start as minimal as you possibly can (I think someone posted a command line option to create a
very basic golded.conf).

"LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx -Cpath_to_cfg"

Definitely does NOT go in your golded.conf. That's something you type on
the Linux console in order to run Golded.

With that said, I'd be willing to guess you don't have 'luit' installed, either.

Are you new to Linux? If so, you should probably mention that so people
can be a lot lighter on their explanations to you, which you currently
aren't seeming to understand any of. It also seems like you're
completely missing a lot of the help people are already trying to give you.

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello David!

24 Nov 24 17:42, you wrote to Angel Ripoll:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

I believe that this line has no use as source and target encoding is the same for my installation (I use Fidian for GoldEd through ttyd and tmux), I have a export TERM=screen.xterm-256color

where you can start that like (in a bin/bash script like) TERM=screen.xterm-256color /usr/bin/golded -T600

without that I have similar like you. Ie, if you run it directly in a shell
you possible have the incorrect encoding.

The 'lining' does have have really (imho) something to do withe the encoding for the characters in
messages ..


Dennis


... Why document it? I'll be here forever.
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Deputy Nodelist Police (2:280/2060)

Hello Nicholas!

24 Nov 24 17:33, you wrote to me:

Hello David,

On Sun, Nov 24 2024 16:42:24 -0600, you wrote ..

Thanks Angel, I tried your suggestion and Fernando Toledo's sample
config with no luck my golded still looks like this:

You should probably start over with your config. Start as minimal as
you possibly can (I think someone posted a command line option to
create a very basic golded.conf).

"LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx -Cpath_to_cfg"

Definitely does NOT go in your golded.conf. That's something you type
on the Linux console in order to run Golded.

yeah, well overlooked...

With that said, I'd be willing to guess you don't have 'luit'
installed, either.

Guessing I do not, why?, well I based my install on the Git repo instructions

Are you new to Linux? If so, you should probably mention that so
people can be a lot lighter on their explanations to you, which you currently aren't seeming to understand any of. It also seems like
you're completely missing a lot of the help people are already trying
to give you.

New... well, I don't consider myself new but I'm a self-proclaimed expert, so yeah I might be missing some concepts.

And normally if I'm going say LANG=es_ES TERM=linux or the like I'd have said start the program with, maybe *assumming* is problematic, but not going to trash, would there be another more basic are where I could ask?.

Thanls for your advice.

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
(1:154/700)

SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30 50 700 SEEN-BY: 203/0 220/20 90 221/0 6 226/18 44 50 229/426 240/1120 5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1 310/31 341/66 234 396/45 SEEN-BY: 423/120 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 SEEN-BY: 902/26 930/1 2320/105 3634/12 5020/400

Hello Dennis!

25 Nov 24 07:27, you wrote to me:

Hello David!

24 Nov 24 17:42, you wrote to Angel Ripoll:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

I believe that this line has no use as source and target encoding is
the same for my installation (I use Fidian for GoldEd through ttyd and tmux), I have a export TERM=screen.xterm-256color

yes, that might be, my TERM is TERM=linux

where you can start that like (in a bin/bash script like) TERM=screen.xterm-256color /usr/bin/golded -T600

I'm definitely going to try that as a bash startup script.

without that I have similar like you. Ie, if you run it directly in a shell you possible have the incorrect encoding.

The 'lining' does have have really (imho) something to do withe the encoding for the characters in messages ..

many thanks, I was thinking it was eitehr encoding or terminal type but it's been a long time coming back to Linux.

Dennis

... Why document it? I'll be here forever.
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Deputy Nodelist Police (2:280/2060)

SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30 50 700 SEEN-BY: 203/0 220/20 90 221/0 6 226/18 44 50 229/426 240/1120 5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1 310/31 341/66 234 396/45 SEEN-BY: 423/120 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 SEEN-BY: 902/26 930/1 2320/105 3634/12 5020/400

Hola Dennis!

25 Nov 24 07:27, Dennis Slagers dijo a David Gonzalez:

Hello David!

24 Nov 24 17:42, you wrote to Angel Ripoll:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

I believe that this line has no use as source and target encoding is the same for my installation (I use Fidian for GoldEd through ttyd and tmux), I have a export TERM=screen.xterm-256color

I have my system in UTF8 and I use ISO8859-1 with golded. That's why I use that line. Before using this I had to manually change the encoding of my terminal to see the golded screen correctly. If I didn't make that change, I saw more or less the screen as David says.

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hello David!

25 Nov 24 07:44, you wrote to Dennis Slagers:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

I believe that this line has no use as source and target encoding
is the same for my installation (I use Fidian for GoldEd through
ttyd and tmux), I have a export TERM=screen.xterm-256color

In my case (using specific czech codepage):

1) How to start golded:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3
LANG=cs_CZ.ISO8859-2 luit -encoding 'ISO-8859-2' ./gedlnx -f

2) In .bash_profile:

export TERM=vt220

3) In putty:

UTF8

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Hello David,

On Mon, Nov 25 2024 06:39:16 -0600, you wrote ..

With that said, I'd be willing to guess you don't have 'luit'
installed, either.

Guessing I do not, why?, well I based my install on the Git repo
instructions

Because if you are putting something you would normally run on the
command line in your Golded configuration file, people here should
probably be aware you're not very knowledgeable in Linux so they can
slow down a bit and explain things much more specific so you understand.
You seem to be missing a LOT of valuable information, as well as where
you should be looking for answers to most, if not all of your questions.

New... well, I don't consider myself new but I'm a self-proclaimed
expert, so yeah I might be missing some concepts.

Thank you for letting the people trying to help you know that.

SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30
50 700 SEEN-BY: 203/0 220/20 90 221/0 6 226/18 44 50 229/426
240/1120 5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1
310/31 341/66 234 396/45 SEEN-BY: 423/120 460/58 467/888 633/280
712/848 770/1 900/0 102 106 902/0 19 SEEN-BY: 902/26 930/1 2320/105
3634/12 5020/400

You've also missed the fact that multiple people, including myself, have
asked you multiple times to add a tearline and origin line via your
config file in networked messages, so that the above lines don't display
(ie they shouldn't, and wouldn't if you had the lines necessary).

So, please put these two lines in your Golded config file:

TEARLINE @longpid @version
ORIGIN "This is an example origin line."

In the quotes, you can put the name of your BBS or mailer, and maybe
even some kind of connection information to it, like mine below.

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello Karel!

25 Nov 24 21:06, you wrote to me:

Hello David!

25 Nov 24 07:44, you wrote to Dennis Slagers:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

I believe that this line has no use as source and target
encoding is the same for my installation (I use Fidian for
GoldEd through ttyd and tmux), I have a export
TERM=screen.xterm-256color

In my case (using specific czech codepage):

1) How to start golded:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3
LANG=cs_CZ.ISO8859-2 luit -encoding 'ISO-8859-2' ./gedlnx -f

2) In .bash_profile:

export TERM=vt220

3) In putty:

UTF8

I will try those, thanks.

It's wird but I'm still trying to put the pieces together.

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30 50 700 SEEN-BY: 203/0 220/20 90 221/0 6 226/18 44 50 229/426 240/1120 5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1 310/31 341/66 234 396/45 SEEN-BY: 423/120 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 SEEN-BY: 902/26 930/1 10 2320/105 3634/12 5020/400

Hola Angel!, saludo cordial

25 Nov 24 19:59, tu escribi(ste) a Dennis Slagers:

Hola Dennis!

25 Nov 24 07:27, Dennis Slagers dijo a David Gonzalez:

Hello David!

24 Nov 24 17:42, you wrote to Angel Ripoll:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

Tried this but Ubuntu reports luit not found, triued intalling it but no install candidate

I believe that this line has no use as source and target encoding
is the same for my installation (I use Fidian for GoldEd through
ttyd and tmux), I have a export TERM=screen.xterm-256color

I have my system in UTF8 and I use ISO8859-1 with golded. That's
why I use that line. Before using this I had to manually change the encoding of my terminal to see the golded screen correctly. If I
didn't make that change, I saw more or less the screen as David says.

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30 50 700 SEEN-BY: 203/0 220/20 90 221/0 6 226/18 44 50 229/426 240/1120 5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1 310/31 341/66 234 396/45 SEEN-BY: 423/120 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 SEEN-BY: 902/26 930/1 10 2320/105 3634/12 5020/400

Hi David,

On 2024-11-26 08:21:43, you wrote to Angel Ripoll:

Tried this but Ubuntu reports luit not found, triued intalling it but
no install candidate

# apt search luit
Sorting... Done
Full Text Search... Done
x11-utils/jammy,jammy,jammy,jammy 7.7+5build2 amd64
X11 utilities

xterm/jammy,jammy,jammy,jammy 372-1ubuntu1 amd64
X terminal emulator

# apt show x11-utils
Package: x11-utils
Version: 7.7+5build2
...
This package provides a miscellaneous assortment of X utilities
that ship with the X Window System, including:
- appres, editres, listres and viewres, which query the X resource database;
- luit, a filter that can be run between an arbitrary application and a
UTF-8 terminal emulator;
...
The luit program requires locale information from
the libx11-data package.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hola David!

26 Nov 24 08:21, David Gonzalez dijo a Angel Ripoll:

Hola Angel!, saludo cordial

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

Tried this but Ubuntu reports luit not found, triued intalling it but no install candidate

Package luit

oracular (24.10) (utils): locale and ISO 2022 support for Unicode terminals
2.0.20221028-1: amd64 arm64 armhf ppc64el riscv64 s390x
also provided by: luit
plucky (utils): locale and ISO 2022 support for Unicode terminals
2.0.20240910-1: amd64 arm64 armhf ppc64el riscv64 s390x
also provided by: luit

Luit is on Ubuntu 24.10

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)