Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!tudelft.nl!txtfeed1.tudelft.nl!dedekind.zen.co.uk!zen.net.uk!hamilton.zen.co.uk!shaftesbury.zen.co.uk.POSTED!not-for-mail From: Nobody Subject: Re: unicode by default Date: Sat, 14 May 2011 09:34:54 +0100 User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Message-Id: Newsgroups: comp.lang.python References: <874o50k1eb.fsf@benfinney.id.au> <3ae7c960dc8cf622fcf95aa48ed9df40.squirrel@webmail.lexicon.net> <492f8500-fd53-4b52-bd7b-cd90a3118d38@k16g2000yqm.googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Lines: 31 Organization: Zen Internet NNTP-Posting-Host: a6194155.news.zen.co.uk X-Trace: DXC=Le[D=BBU>[_c8@`lPX:2J[nok4Z\3cB^f=ZQOMCU8L]ShW2KaT5_L The unicode consortium is very careful to make sure that thousands > of symbols have a unique code point (that's great !) but how do these > thousands of symbols actually get displayed if there is no font > consortium? Are there collections of 'standard' fonts for unicode that I > am not aware? Is there a unix linux package that can be installed that > drops at least 'one' default standard font that will be able to render all > or 'most' (whatever I mean by that) code points in unicode? Using the original meaning of "font" (US) or "fount" (commonwealth), you can't have a single font cover the whole of Unicode. A font isn't a random set of glyphs, but a set of glyphs in a common style, which can only practically be achieved for a specific alphabet. You can bundle multiple fonts covering multiple repertoires into a single TTF (etc) file, but there's not much point. In software, the term "font" is commonly used to refer to some ad-hoc mapping between codepoints and glyphs. This typically works by either associating each specific font with a specific repertoire (set of codepoints), or by simply trying each font in order until one is found with the correct glyph. This is a sufficiently common problem that the FontConfig library exists to simplify a large part of it. > Is this a Python issue at all? No.