From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: New Proposed Xconq Web Site Online
Date: Sun, 03 Oct 2004 23:55:00 -0000 [thread overview]
Message-ID: <416049AE.1020801@phy.cmich.edu> (raw)
In-Reply-To: <200410031836.i93IaX021511@panix5.panix.com>
Jim Kingdon wrote:
>>Unless there is multi-platform, lightweight rendering API that can
>>take a list of Pango glyphs (which I am led to believe is what comes
>>out of the far end of the Pango pipeline) and actually draw them on
>>the display, I am not sure how much use it would be to us.
>
> It is possible that http://sdlpango.sourceforge.net/ is such a thing.
> Although that page seemed to describe lots of issues, without quite
> saying just what SDL_Pango does.
I looked at their code example. It appears to be just what I had in
mind. It takes a Pango context (containing the glyphs) and draws it onto
a SDL surface. Perfect. Case closed.
>>Possibly. But, I have previously mentioned the possibility of writing
>>labels in runic alphabets (both historical and fictitious):
>
> It is the kind of thing which wouldn't be off the shelf. But using
> Unicode's private character numbers and writing yourself a font which
> the usual UTF-8 tools can process might be just as easy as doing
> everything from scratch.
Ah, I forgot about the private character numbers in Unicode. I think
that this solves the abovementioned problem. Good thought.
> Of course the real point of using something like Pango would be if we
> want to deal with arabic, thai, bidirectional, and the other
> complicated cases.
Sure.
Based on the info you just provided, it looks like we can cover both the
internationalization issue (for people who want to use SDL Xconq in a
language other than en_US), and the game designer-specified labels issue.
Thanks,
Eric
next prev parent reply other threads:[~2004-10-03 18:49 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
2004-10-03 18:36 ` Eric McDonald
2004-10-03 18:49 ` Jim Kingdon
2004-10-03 23:55 ` Eric McDonald [this message]
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=416049AE.1020801@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=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).