Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Nov 2014 20:00:29 -0500
From:      Ed Maste <emaste@freebsd.org>
To:        Wendell Martins Borges <wendell@bsd.com.br>
Cc:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: CP437 in vt driver
Message-ID:  <CAPyFy2AziihmrBzTT0Jf4oBeVQG_rGy5uayt-YzdFjegikuG_Q@mail.gmail.com>
In-Reply-To: <CACwtQRdhC3=48ewWnoX%2Bt5O2JbYNMWirho6ZCun7H55f0DMb6A@mail.gmail.com>
References:  <CACwtQRdhC3=48ewWnoX%2Bt5O2JbYNMWirho6ZCun7H55f0DMb6A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10 November 2014 14:26, Wendell Martins Borges <wendell@bsd.com.br> wrote:
> I'm trying to use CP437 in vt driver in a RPi B+ with -CURRENT... I've
> already tried to use the default vt fonts, but none of them, recognize the
> specific char I want to use (for e.g. Cp437 - B3hex).

vt(4) is inherently Unicode & UTF-8, so you'll have to use the Unicode
code point for the character instead. CP437 0xB3 is Unicode U+2502, or
0xE2 0x94 0x82 as UTF-8. You should be able to confirm you can output
it with zsh/bash builtin printf: printf '\xe2\x94\x82'

Adding support for non-Unicode/UTF-8 mapping is on the vt(4) TODO list.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2AziihmrBzTT0Jf4oBeVQG_rGy5uayt-YzdFjegikuG_Q>