Tcl Source Code

View Ticket
Login
Ticket UUID: 1227201
Title: does not translate computer names
Type: Bug Created on: 2005-06-24 19:05:56
Submitter: nobody Assigned to: patthoyts
Subsystem: 27. Channel Types Severity:
Priority: 5 Medium Last modified: 2026-10-22 17:19:30
Status: Closed Closed by: serhiy.storchaka
Resolution: Fixed Closed on: 2026-10-21 10:03:37
Version: obsolete: 8.4.10
Description:
The "socket" command  when running in windows 
DOES NOT use a "wide" version of the socket calles or 
translate the uft-8 encode string to local code page 
before making a call to (say) "gethostbyname"
User Comments:
hobbs added on 2005-10-06 01:15:15:
Logged In: YES 
user_id=72656

Dave - does this make sense to you?

davygrvy added on 2005-10-06 06:21:33:
Logged In: YES 
user_id=7549

unfortunetly, I'm a bit busy with stuff unrelated to Tcl so
I can't much more than commenting.  It does make sense if
(..from memory..) Tcl_UtfToWinTchar() call isn't done on the
buffer prior to giving it to gethostbyname().  IIRC,
gethostbyname() is limited to 7-bit ansi.  Legality of
character encodings through gethostbyname() is worth
checking.  Conversion from utf to local code page doesn't
sound appropriate to me unless the winsock flavor of
gethostbyname() has implicit conversions internally.

dgp added on 2007-10-31 23:49:29:
Logged In: YES 
user_id=80530
Originator: NO


See also 1823552

dkf added on 2012-05-18 06:47:52:
Did this get affected by the changes due to adding IPv6 support?

serhiy.storchaka added on 2026-10-21 10:03:37:

Since 8.6.0 (IPv6 rewrite, [3f8b48b6b6]) the host name is converted to the system encoding before getaddrinfo() is called. Please reopen if a non-ASCII host name still fails with 8.6.18 or 9.0.