From owner-freebsd-questions@FreeBSD.ORG Tue May 2 20:39:43 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 E12B816A401 for ; Tue, 2 May 2006 20:39:43 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DA6F43D45 for ; Tue, 2 May 2006 20:39:43 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by nz-out-0102.google.com with SMTP id n1so11984nzf for ; Tue, 02 May 2006 13:39:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FhJ+BosajCQijGQ4oxCSOMaZSohdAgCdW5G0WqZ7iF32SAbGAyNE9c3w/a/0+eULxyO3vcBjNSY/v5bQgNTg1e8CTAQoHO8oGk+4XUAQ3xvFoXe0l+Qe1EGp/UVwCYWEsKFCpvsZ+wc90Oyo6g34qPUEMC7RN+brnoMYbn+UN0E= Received: by 10.36.108.18 with SMTP id g18mr1792704nzc; Tue, 02 May 2006 13:39:43 -0700 (PDT) Received: by 10.37.22.74 with HTTP; Tue, 2 May 2006 13:39:43 -0700 (PDT) Message-ID: Date: Wed, 3 May 2006 00:39:43 +0400 From: "Andrew Pantyukhin" To: "Rostislav Krasny" In-Reply-To: <20060414050026.e96c6b05.rosti.bsd@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060414050026.e96c6b05.rosti.bsd@gmail.com> 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: Tue, 02 May 2006 20:39:44 -0000 On 4/14/06, Rostislav Krasny wrote: > > 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. > xterm-213 seems to fix it all. Yeeehaa.