From: Jim Kingdon <kingdon@panix.com>
To: xconq7@sources.redhat.com
Subject: Re: New Proposed Xconq Web Site Online
Date: Sun, 03 Oct 2004 17:48:00 -0000 [thread overview]
Message-ID: <200410031559.i93Fxag11465@panix5.panix.com> (raw)
In-Reply-To: <415E0BED.6080105@phy.cmich.edu> (message from Eric McDonald on Fri, 01 Oct 2004 20:01:17 -0600)
> I think that other font tables, similar to 'fonts.bmp' may need to be
> used for other languages, and the 'draw_string' code will probably
> have to be rewritten to dispatch to new functions such as
> 'draw_string_en_US', 'draw_string_eo' :-), etc... as appropriate.
Well, there is the easy way and the hard way. The easy way is to just
pick up one of the existing rendering packages, such as pango (
http://www.pango.org/ ) and existing sets of fonts. Something along
these lines is surely the way to go if we see it as a priority to
support a wide variety of modern languages with minimal effort on the
part of the game designer.
The hard way is more custom, and has as a goal having more of a
distinctive xconq look and/or a look specific to a particular xconq
game. One possible solution which passes the buck to the game
designer (or UI translator): rather than specify a unit name (or menu
item) as text, specify it as a bitmap (in how many sizes? etc). This
pushes all the rendering issues (bidirectional, combining glyphs in
languages like thai, arabic, etc) to design-time than runtime. This
doesn't help with cases in which humans enter text - the chat and "M"
(message) features of a multiplayer game are what spring to mind.
There's also "name a unit".
next prev parent reply other threads:[~2004-10-03 15:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 5:40 Feneric Brown
2004-10-01 6:10 ` Jim Kingdon
2004-10-02 2:14 ` Eric McDonald
2004-10-02 2:51 ` mskala
2004-10-02 3:04 ` Eric McDonald
2004-10-03 17:48 ` Jim Kingdon [this message]
2004-10-03 18:36 ` Eric McDonald
2004-10-03 18:49 ` Jim Kingdon
2004-10-03 23:55 ` Eric McDonald
2004-10-04 4:53 ` Antarcticonq Elijah Meeks
2004-10-05 3:50 ` Antarcticonq Eric McDonald
2004-10-06 2:01 ` Antarcticonq Elijah Meeks
2004-10-01 8:07 ` New Proposed Xconq Web Site Online Lincoln Peters
2004-10-01 18:07 ` Eric McDonald
-- strict thread matches above, loose matches on Subject: below --
2004-10-06 2:02 Feneric Brown
2004-10-01 18:35 Feneric Brown
2004-10-02 2:01 ` Eric McDonald
2004-10-01 18:23 Feneric Brown
2004-09-29 19:26 Feneric Brown
2004-09-30 0:36 ` Eric McDonald
2004-09-30 23:49 ` Jim Kingdon
2004-09-29 19:17 Eric W. Brown
2004-09-29 0:41 Eric W. Brown
2004-09-29 18:08 ` Jim Kingdon
2004-09-29 0:23 Feneric Brown
2004-09-28 21:34 Feneric Brown
2004-09-28 22:14 ` Elijah Meeks
2004-09-28 23:47 ` D. Cooper Stevenson
2004-09-29 15:00 ` Jim Kingdon
2004-09-29 18:16 ` Eric McDonald
2004-09-30 16:59 ` Jim Kingdon
2004-09-29 18:24 ` Eric McDonald
2004-09-30 17:07 ` Jim Kingdon
2004-09-27 18:44 D. Cooper Stevenson
2004-09-27 18:54 ` Elijah Meeks
2004-09-28 2:40 ` D. Cooper Stevenson
2004-09-28 3:25 ` Eric McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410031559.i93Fxag11465@panix5.panix.com \
--to=kingdon@panix.com \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).