Date: Mon, 1 Sep 2008 00:42:54 +0400 From: "Alexander Churanov" <alexanderchuranov@gmail.com> To: "Peter Jeremy" <peterjeremy@optushome.com.au> Cc: freebsd-current@freebsd.org Subject: Re: Unicode-based FreeBSD Message-ID: <3cb459ed0808311342x2f96e5a6oc04f97cf1362823b@mail.gmail.com> In-Reply-To: <20080830115559.GM86609@server.vk2pj.dyndns.org> References: <3cb459ed0808250952j572dfc35j2feb852a73de5ace@mail.gmail.com> <200808281718.m7SHISGL067492@lurza.secnetix.de> <3cb459ed0808290636r5eb389c8y6d4aafae1b8001cf@mail.gmail.com> <e7db6d980808291134h50bb71aaud1f4b8da7f61a174@mail.gmail.com> <3cb459ed0808291708l581422c1pdb2e3cb2913ecaa7@mail.gmail.com> <20080830083901.GA2183@medusa.sysfault.org> <20080830115559.GM86609@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/8/30 Peter Jeremy <peterjeremy@optushome.com.au> > IMHO, unless we want to embed the equivalent of pango in the kernel, > the only realistic solution is to count unicode codepoints. That's exactly what I want to implement. > It would be useful to know how other implementations work because I > can't see how to avoid some degree of broken-ness without a complete > CTF implementation. If we aim syscons at sysadmins then a degree of > misbehaviour may be acceptable. You are reading my thoughts! > The fonts are available in ports. I'm not sure if there are existing > bit-mapped fonts but a TTF or similar font can be converted to a > bitmap without major effort. Antialiasing would help with legibility. > Also agree. Alexander Churanov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3cb459ed0808311342x2f96e5a6oc04f97cf1362823b>