Date: Fri, 23 Nov 2001 01:18:10 +0200 From: =?iso-8859-7?Q?=C1=ED=E1=F3=F4=E1=F3=DC=F4=EF=F2=20=C2=E1=F3=DF=EB=E5=E9=EF=F2?= <B.Anastasatos@MyRealBox.com> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: freebsd-i18n@FreeBSD.ORG Subject: Re: ACS (Alternate Character Set) support in ISO-8859-7 greek codepage Message-ID: <3BFD87B2.E9691603@MyRealBox.com> References: <20010727132229.B8030-300000@idemnia.ath.cx> <3BFCCE33.A73F605E@MyRealBox.com> <20011122153813.GA62978@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
"Andrey A. Chernov" wrote: > > ISO-8859-7 supports only 4 out of the 32 ACS characters. On > > the other hand, there are about 35 "unused" positions in > > ISO-7, more than enough if somebody wanted to add ACS glyphs > > to ISO-8859-7 console fonts. I noticed that this is exactly > > what happens in the FreeBSD implementation of ISO-8859-2. > No, fonts must conforms standards exactly. 8859-2 font must be > fixed instead. Otherwise it gives user wrong impression that ACS > characters present in standard, OK, what about creating _separate_ fonts and naming them in such a way that is obvious they don't conform _exactly_ to ISO-8859' series? Like el.iso07_with_ACS_enhancements.8x16.fnt. > so he start to use them and become incompatible with the rest of > the world. Of course people wouldn't use directly the enhancements, instead the would keep using the ncurses library interface as usual (cat /usr/include/curses.h | grep define | grep ACS | less). ncurses would then consult /etc/termcap to find out if and how ACS is implemented in the actual $TERM console. In this way no compatibility problems raise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BFD87B2.E9691603>