--On Mon, Mar 22, 1999 at 01:59:07AM -0600, Shaw Terwilliger wrote: > Return-Path: <owner-abiword-dev@abisource.com> > Received: (from majordomo@localhost) > by postman.abisource.com (8.8.7/8.8.7) id BAA31959 > for abiword-dev-outgoing; Mon, 22 Mar 1999 01:59:07 -0600 > Received: (from sterwill@localhost) > by postman.abisource.com (8.8.7/8.8.7) id BAA31954; > Mon, 22 Mar 1999 01:59:07 -0600 > Message-ID: <19990322015907.A31905@postman.abisource.com> > Date: Mon, 22 Mar 1999 01:59:07 -0600 > From: Shaw Terwilliger <sterwill@postman.abisource.com> > To: abiword-dev@postman.abisource.com > Subject: commit -- Unix font dialog string changes and encoding > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > X-Mailer: Mutt 0.91.1 > Sender: owner-abiword-dev@abisource.com > Precedence: bulk
> It seems like all I do these days is mess with that Unix font > dialog, doesn't it? :) I read Drazen Kacar's message about > encoding schemes and decided I should really put in a combo for it. > Right now it doesn't actually do anything, but it will soon, and > while I was messing around there I pulled out the strings to the common > strings table for xap stuff. > > Here's how I'm planning on doing the encoding selection, > so someone tell me if this either isn't going to work or > if there's a better way to do it. I'm planning on > simply pulling out the encoding field from the XLFDs > in the fonts.dir (that's what the field is for, anyway). > I guess I'll then just make user-friendly names for common > sets ("Latin 1", "Latin 2", "Cyrillic", "Greek", etc.). My > uncertainty is about mapping those user-friendly names > to actual encodings. Will there always be a 1:1 mapping > of, say, "Latin 1" to "iso-8859-1"? Will "Greek" always > fall into, say "iso-8859-5", or will there be different > flavors of local languages spread across different > ISO encodings? > > -- > Shaw Terwilliger
-- Eric W. Sink, Software Craftsman eric@abisource.com