From owner-freebsd-questions@FreeBSD.ORG Fri Apr 14 02:00:33 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 900F816A404 for ; Fri, 14 Apr 2006 02:00:33 +0000 (UTC) (envelope-from rosti.bsd@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8BDC43D49 for ; Fri, 14 Apr 2006 02:00:32 +0000 (GMT) (envelope-from rosti.bsd@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so1207667ugc for ; Thu, 13 Apr 2006 19:00:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:x-mailer:mime-version:content-type:content-transfer-encoding; b=VXvQqyZ5fNOa38o7qEgYgFt2WM2oEO3Dn5Cof2iCmwgPiYrG4xigxjWdOf8PvmEnneTgJPN4oabOk89YMCzYADzftlJOQdxPb211gBch0qDEDDhf14+zaTVhmz1nX3GHm6XQjpFiYKphi6CiPb9W4R4zkRSZsnW0u/o7e2dVG6M= Received: by 10.66.224.19 with SMTP id w19mr452888ugg; Thu, 13 Apr 2006 19:00:31 -0700 (PDT) Received: from saturn.lan ( [212.143.154.227]) by mx.gmail.com with ESMTP id y7sm998371ugc.2006.04.13.19.00.29; Thu, 13 Apr 2006 19:00:30 -0700 (PDT) Date: Fri, 14 Apr 2006 05:00:26 +0300 From: Rostislav Krasny To: "Andrew Pantyukhin" Message-Id: <20060414050026.e96c6b05.rosti.bsd@gmail.com> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: questions@freebsd.org Subject: Re: X11/xterm Unicode woes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 02:00:33 -0000 > About a month ago UTF-8 locale stopped working in my xterm. I experience the same problem after the xterm port had been updated from 206 to 210 version. As a workaround you can either: downgrade to xterm-206 or use uxterm. I'm suspecting following change of xterm-209: amend change for loading utf8Fonts resource from patch #204 to allow an ISO-8859-1 "normal" font to be combined with an ISO-10646 font if the latter is given via the -fw option or its corresponding resource value. But I'm not sure. I've already contacted with Thomas Dickey , the xterm author, and sent him a trace file of manually built xterm-212. I hope he will localize and fix the bug before the next xterm release.