From: Kevin Ryde <user42@zip.com.au>
To: guile-gtk@sources.redhat.com
Subject: GdkWChar (was: Added a bunch of GDK routines.)
Date: Fri, 06 Jun 2003 22:23:00 -0000 [thread overview]
Message-ID: <878yse3ky1.fsf@zip.com.au> (raw)
In-Reply-To: <m33cjyxi3p.fsf@lumo.pacujo.net>
Marko Rauhamaa <marko@pacujo.net> writes:
>
> - gdk-1.2.defs: Defined an alias GdkWChar for uint for
> gdk_draw_text_wc. (I trust uint to correspond to guint32 because
> currently there is no alternative.)
Presumably one day guile will get its own notion of chars bigger than
a byte. Probably no alternative to plain integers until then. I'm
thinking the words below can cover the present situation at least.
[General conventions:]
Strings
Gtk generally uses strings encoded in UTF-8. Guile (version 1.6)
has no direct notion of multi-byte characters in strings, so
applications will need to take care when in a non-ASCII or
non-Latin locale.
Converting to `GdkWChar' with `gdk-mbstowc' (*note Gdk Module::) is
one way to identify character boundaries at least.
[Gdk Module:]
`GdkWChar'
Currently `GdkWChar' values are represented as integers, and
`GdkWChar' strings as vectors of integers. So for instance
`gdk-mbstowc' returns such a vector (or `#f' if conversion fails).
Note that this representation might change in the future if Guile
gets its own notion of characters bigger than 8 bits.
next prev parent reply other threads:[~2003-06-06 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 1:25 Added a bunch of GDK routines Marko Rauhamaa
2003-05-11 23:28 ` Kevin Ryde
2003-05-12 18:06 ` Marko Rauhamaa
2003-05-12 18:56 ` Marko Rauhamaa
2003-06-06 22:23 ` Kevin Ryde [this message]
2003-06-14 23:58 ` gdk-gc-copy comments (was: Added a bunch of GDK routines.) Kevin Ryde
2003-06-20 23:54 ` sgtk_timestamp returns " Kevin Ryde
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=878yse3ky1.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-gtk@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).