unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Linas Vepstas <linasvepstas@gmail.com>
To: 21221@debbugs.gnu.org
Subject: bug#21221: guile-2.2 socket ports used with display does not send utf8 !
Date: Sat, 8 Aug 2015 21:20:54 -0500	[thread overview]
Message-ID: <CAHrUA36i0jA6U57dVGzDEv9J5wJTzAUYOs42qZdb9gKEE_FfFQ@mail.gmail.com> (raw)

The following simple client-server program fails for me.
For simplicity, for the server, just use netcat listening on port 7777:

$ nc -l 7777

In a guile shell, try this:
(setlocale LC_ALL "")
(define sss (socket PF_INET SOCK_STREAM 0))
(set-port-encoding! sss "utf-8")
(connect sss AF_INET (inet-pton AF_INET "127.0.0.1") 7777)
(set-port-encoding! sss "utf-8")
(display "SmålandSmåland\n" sss)
(close-port sss)


The SmålandSmåland gets corrupted:  nc receives Sm?landSm?land

Some types of utf8 do go through, so e.g. (display "Ćićolina\n" sss)
seems to work fine.  This finish/norweign thing, though, fails,
vietnamese too.
(display "Hòa Phú Phú Tân Hiệp An  Tương Bình Hiệp Định Hòa\n" sss)

I suppose the answer is "don't use display for sending strings on a
socket", but I'm stumped as to why there should even be an encoding
error, why its not utf8 end-to-end.

This is for guile-2.2 from a recent git pull of the master source from
about June 2015, but I believe the problem occurs on guile-2.0 as
well.

guile --version
guile (GNU Guile) 2.1.0.305-e7097-dirty

this is on ubuntu 14.04 aka ubuntu trusty

-- Linas Vepstas





             reply	other threads:[~2015-08-09  2:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09  2:20 Linas Vepstas [this message]
2015-10-29 23:11 ` bug#21221: guile-2.2 socket ports used with display does not send utf8 ! Ludovic Courtès
2016-06-20 15:55 ` Andy Wingo
     [not found] ` <handler.21221.D21221.146643814711185.notifdone@debbugs.gnu.org>
2016-06-21 13:31   ` bug#21221: closed (Re: bug#21221: guile-2.2 socket ports used with display does not send utf8 !) Linas Vepstas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHrUA36i0jA6U57dVGzDEv9J5wJTzAUYOs42qZdb9gKEE_FfFQ@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --cc=21221@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).