From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: More i18n
Date: Sun, 31 Dec 2006 16:54:36 +0000 [thread overview]
Message-ID: <87wt489far.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <878xhczmbp.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 13 Dec 2006 11:11:38 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> (i) add a reference to where charsets are documented further
>
> If only there was a decent central bit in the gnu manuals :-(.
> Running "iconv -l" is the only way I know to even see a full list.
It wasn't a list that I was looking for, just some idea of what a
charset is.
I've read just enough about this area to know that there is a lot of
terminology describing similar but subtly different concepts, like
locales, charsets, code pages; chars, code points, glyphs; encodings,
etc.
If it's a case of Guile's "charset" mapping exactly to some
well-known external definition of "charset", all I'm asking for is a
reference to that external definition.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-12-31 16:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 15:04 More i18n Ludovic Courtès
2006-12-11 19:42 ` Neil Jerram
2006-12-12 9:09 ` Ludovic Courtès
2006-12-12 19:48 ` Kevin Ryde
2006-12-31 16:23 ` Neil Jerram
2006-12-31 16:22 ` Neil Jerram
2006-12-13 0:11 ` Kevin Ryde
2006-12-31 16:54 ` Neil Jerram [this message]
2006-12-11 23:26 ` Kevin Ryde
2006-12-12 9:36 ` Ludovic Courtès
2006-12-12 19:43 ` Kevin Ryde
2006-12-12 19:19 ` Kevin Ryde
2006-12-31 16:15 ` Neil Jerram
2007-01-01 22:32 ` Kevin Ryde
2007-01-16 21:46 ` Ludovic Courtès
2007-01-16 22:08 ` Ludovic Courtès
2007-01-23 0:49 ` Kevin Ryde
2007-01-23 0:46 ` Kevin Ryde
2007-01-23 23:44 ` Ludovic Courtès
2007-01-24 20:58 ` Kevin Ryde
2007-01-31 21:13 ` Ludovic Courtès
2007-01-31 22:06 ` Kevin Ryde
2007-01-25 1:05 ` 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wt489far.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
/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).