From: Mike Gran <spk121@yahoo.com>
To: "Julian Graham" <joolean@gmail.com>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: More explicit support for Unicode title case
Date: Mon, 21 Dec 2009 23:16:22 -0800 (PST) [thread overview]
Message-ID: <366328.13621.qm@web37904.mail.mud.yahoo.com> (raw)
In-Reply-To: <2bc5f8210912212137m132f0d2ag44d39b827a146050@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
> >> +SCM_API scm_t_wchar scm_c_titlecase (scm_t_wchar c);
> >
> > I think it should be documented in the manual.
>
> Actually, I'm going to hold off on this, since documenting this would
> require at least some explanation of scm_t_wchar, which seems to me to
> be outside the scope of this patch. I'm happy to add documentation
> for this (as well as the other wchar functions), although some context
> from the originator of that typedef (`git blame' says it was Mike
> Gran) would be useful.
I wonder if these should be API. It is probably too late to change them,
since they've existed as API since the late 1990s, but, as far as I can
tell, no one has ever used them (I checked codesearch.google.com
and koders.com). They've also never been documented.
But, a patch for documenting these is attached.
Thanks,
Mike
[-- Attachment #2: api-data-case.patch --]
[-- Type: application/octet-stream, Size: 769 bytes --]
--- doc/ref/api-data.texi.0 2009-12-21 22:40:16.226406152 -0800
+++ doc/ref/api-data.texi 2009-12-21 23:07:43.902405881 -0800
@@ -1901,6 +1901,17 @@
Return the lowercase character version of @var{chr}.
@end deffn
+@tindex scm_t_wchar
+@deftypefn {C Function} scm_t_wchar scm_c_upcase (scm_t_wchar @var{c})
+@deftypefnx {C Function} scm_t_wchar scm_c_downcase (scm_t_wchar @var{c})
+@deftypefnx {C Function} scm_t_wchar scm_c_titlecase (scm_t_wchar @var{c})
+
+These C functions take an integer representation of a Unicode
+codepoint and return the codepoint corresponding to its uppercase,
+lowercase, and titlecase forms respectively. The type
+@code{scm_t_wchar} is a signed, 32-bit integer.
+@end deftypefn
+
@node Character Sets
@subsection Character Sets
next prev parent reply other threads:[~2009-12-22 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 14:02 More explicit support for Unicode title case Julian Graham
2009-12-21 20:17 ` Ludovic Courtès
2009-12-22 5:37 ` Julian Graham
2009-12-22 7:16 ` Mike Gran [this message]
2009-12-28 22:28 ` Ludovic Courtès
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=366328.13621.qm@web37904.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=joolean@gmail.com \
--cc=ludo@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).