minicom... problem!

Wed Nov 27 08:21:11 GMT 2019

 <EN>
Good morning Brolin, and the rest of the list:

He spent a lot of time trying to solve this problem.

I had always thought it was not a minicom problem ... and today I have finally found the culprit!

The problem is not of minicom, it is the configuration of "locales".

I explain:

1. All the machines we work with are configured by default with: LANG=es_ES.UTF-8.

2. Konsole always configures it to use the IBM850 charset.

3. I run (in Debian, in Ubuntu I have not tried):
# dpkg-reconfigure locales

4. I leave it like this:
[*] en_US ISO-8859-1
[*] en_US.ISO-8859-15 ISO-8859-15
[*] en_US.UTF-8 UTF-8
[*] es_ES ISO-8859-1
[*] es_ES.UTF-8 UTF-8
[*] es_ES at euro ISO-8859-15

5. The on-screen representation "fails" when execute these commands:
konsole -e minicom
konsole -e env LANG=en_US.UTF-8 minicom
konsole -e env LANG=es_ES.UTF-8 minicom

6. The on-screen representation is "correct" when execute these commands:
konsole -e env LANG=en_US minicom
konsole -e env LANG=en_US.ISO-8859-1 minicom
konsole -e env LANG=en_US.ISO-8859-15 minicom

konsole -e env LANG=es_ES minicom
konsole -e env LANG=es_ES.ISO-8859-1 minicom
konsole -e env LANG=es_ES at euro minicom
konsole -e env LANG=es_ES.ISO-8859-15 at euro minicom

konsole -e env LANG="NONE" minicom
konsole -e env LANG=* minicom

7. I have not tried more locales.
But I'm sure is a problem with the UTF-8 encoding!

8. I no longer know who should have directed my query! ;)
Can you do something about it?

9. It brings me to head that picocom always makes the representation correctly.
I do not understand why it is.

10. I will finally be able to update all machines with current versions of the operating system.

Well, sorry for the inconvenience, and thanks for listening!

Greetings from España!

Jose Avendaño.
</EN>

<ES>
Buenos dias Brolin, y al resto de la lista:

Levaba mucho tiempo intentando resolver este problema.

Siempre habia pensado que no era problema de minicom... y hoy por fin he dado con el culpable!

El problema no es de minicom, es de la configuracion de "locales".

Te explico:

1. Todas las maquinas con las que trabajamos estan configuradas por defecto con: LANG=es_ES.UTF-8.

2. Konsole lo configuro siempre para que utilice el charset IBM850.

3. Ejecuto (en Debian, en Ubuntu no he probado): 
# dpkg-reconfigure locales

4. Lo dejo asi:
[*] en_US ISO-8859-1
[*] en_US.ISO-8859-15 ISO-8859-15
[*] en_US.UTF-8 UTF-8
[*] es_ES ISO-8859-1
[*] es_ES.UTF-8 UTF-8
[*] es_ES at euro ISO-8859-15

5. La representacion en pantalla "falla" cuando ejecutas estos comandos:
konsole -e minicom
konsole -e env LANG=en_US.UTF-8 minicom
konsole -e env LANG=es_ES.UTF-8 minicom

6. La representacion en pantalla es "correcta", cuando ejecutas estos comandos:
konsole -e env LANG=en_US minicom
konsole -e env LANG=en_US.ISO-8859-1 minicom
konsole -e env LANG=en_US.ISO-8859-15 minicom

konsole -e env LANG=es_ES minicom
konsole -e env LANG=es_ES.ISO-8859-1 minicom
konsole -e env LANG=es_ES at euro minicom
konsole -e env LANG=es_ES.ISO-8859-15 at euro minicom

konsole -e env LANG="NONE" minicom
konsole -e env LANG=* minicom

7. No he probado mas locales.
Pero seguro que es problema con la codificacion UTF-8!

8. Ya no se a quien deberia haber dirijido mi consulta! ;)
Puedes hacer algo tu al respecto?

9. Me trae de cabeza que picocom siempre haga la representacion correctamente.
No entiendo a que se debe.

10. Por fin voy a poder actualizar todas las maquinas con versiones actuales del sistema operativo.

Bueno, disculpa por las molestias y gracias por escucharme!

Saludos desde España!

Jose Avendaño.
</ES>

     En lunes, 25 de noviembre de 2019 21:20:31 CET, Brolin Empey <brolin at brolin.be> escribió:  

 I meant have you tried to check out the source code for the master,
current development version of minicom from [1] and build it yourself
to see if it behaves the same as the minicom versions you have already
tried, which are apparently release versions?

[1] https://salsa.debian.org/minicom-team/minicom

On Mon, 25 Nov 2019 at 09:09, JAC <xxjacs at yahoo.com> wrote:
>
> <EN>
> Good afternoon Brolin:
>
> Yes, I almost always use 16px monospace typography.
> And I always use the same IBM850 charset. If I change the charset some things are intelligible! ;)
> In production, I always launch minicom from konsole (kde).
> To do some test, I launch it from mate-terminal (mate).
>
>
> I use the packaged versions by default for each distro:
> Ubuntu 10.04: minicom version 2.4 (compiled Jan 25 2010).
> Ubuntu 14.04: minicom version 2.7 (compiled Nov 15 2018).
> Ubuntu 19.10: minicom version 2.7.1 (compiled May 3 2018).
> Debian 10...: minicom version 2.7.1 (compiled May 6 2018).
>
>
> Have you tried checking the current version (trunk or head?
> I do not understand what you mean.
>
>
> Joint with the previous mail, I sent the photos, I thought that the mail would be received by the current minicom program maintainer (Adam), I did not imagine that the mail was being sent to the Debian alioth list.
>
>
> You can see the photos here:
> http://avenca.org/minicom/minicom:konsole.minicom.png
> http://avenca.org/minicom/minicom:konsole.minicom.UBUNTU.14.04.png
> http://avenca.org/minicom/minicom:mate-terminal.minicom.png
> http://avenca.org/minicom/minicom:mate-terminal.minicom.UBUNTU.14.04.png
> http://avenca.org/minicom/picocom:konsole.picocom.png
> http://avenca.org/minicom/picocom:mate-terminal.picocom.png
>
>
> What I can't understand is:
> Why "picocom" always represent all characters correctly?
> And why minicom only do well on Ubuntu 10.04 and Ubuntu 14.04, and only when I launch it from Konsole?
>
>
> Thanks for responding and greetings!
> </EN>
>
>
>
> <ES>
> Buenas tardes Brolin:
>
> Si, uso casi siempre tipografia monospace 16px.
> Y siempre uso el mismo charset IBM850. Si cambio el charset algunas cosas son inteligibles! ;)
> En produccion lanzo siempre minicom desde konsole (kde).
> Para hacer alguna prueba, lo lanzo desde mate-terminal (mate).
>
>
> Utilizo las versiones empaquetadas por defecto para cada distro:
> Ubuntu 10.04: minicom version 2.4 (compilado Jan 25 2010).
> Ubuntu 14.04: minicom version 2.7 (compilado Nov 15 2018). ...debe ser una actualizacion reciente.
> Ubuntu 19.10: minicom version 2.7.1 (compilado May 3 2018).
> Debian 10. : minicom version 2.7.1 (compilado May 6 2018).
>
>
> ¿Has intentado verificar la versión actual (tronco o cabeza?
> No comprendo a que te refieres.
>
>
> Junto con el correo anterior, remiti las fotos, pensaba que el correo lo recibiria el actual mantenedor de minicom (Adam), no imaginaba que el correo lo estaba enviando a la lista alioth de Debian.
>
>
> Las fotos las puedes ver aqui:
> http://avenca.org/minicom/minicom:konsole.minicom.png
> http://avenca.org/minicom/minicom:konsole.minicom.UBUNTU.14.04.png
> http://avenca.org/minicom/minicom:mate-terminal.minicom.png
> http://avenca.org/minicom/minicom:mate-terminal.minicom.UBUNTU.14.04.png
> http://avenca.org/minicom/picocom:konsole.picocom.png
> http://avenca.org/minicom/picocom:mate-terminal.picocom.png
>
>
> Lo que no puedo entender es:
> Por que "picocom" siempre representa todos los caracteres correctamente?
> Y por que minicom solo lo hace bien en Ubuntu 10.04 y Ubuntu 14.04, y solo cuando lo lanzo desde konsole?
>
>
> Gracias por responder y un saludo!
> </ES>
>
>
> En sábado, 23 de noviembre de 2019 17:05:27 CET, Brolin Empey <brolin at brolin.be> escribió:
>
>
> Hello Jose,
>
> Your English is good but “España” (endonym) is usually called “Spain”
> (exonym) in English. ;-)
>
> Are you using the same font in all cases?
>
> Which version(s) of minicom are you using?  Have you tried checking
> out the current version (trunk or head?  Not certain about the
> specific terminology but not a release, which I guess is a tag.) from
> the version control system and building it yourself to see if it
> behaves the same as whichever version(s) you used for the screenshots
> you sent?  Because you did not say which version of minicom you are
> using, I guess you are using the version from the Debian/Ubuntu
> package.
>
> Greetings from Metro Vancouver, Canada.
>
> Brolin  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/minicom-devel/attachments/20191127/4529257c/attachment.html>