From: Bruno Haible <bruno@clisp.org>
Cc: guile-devel@gnu.org
Subject: Re: gettext-0.14.2 is released
Date: Sat, 26 Feb 2005 17:52:54 +0100 [thread overview]
Message-ID: <200502261752.54673.bruno@clisp.org> (raw)
In-Reply-To: <87vf8ggrls.fsf@zip.com.au>
Kevin Ryde wrote:
> > - messages can be marked as "scheme-format", denoting 'format' strings.
>
> I noticed a couple of forms that provoke errors,
Thanks for reporting this. I was confused through the situation in slib
and through the documentations: In SLIB, when I saw that Aubrey Jaffer
had deprecated FORMAT, I told him that FORMAT is essential for i18n (because
the SLIB PRINTF doesn't support reordering of arguments) and explained him
that some elements of his SLIB FAQ about FORMAT are simply wrong expectations.
About the documentation, I found that the older SLIB doc describes it as
"An almost complete implementation of Common LISP format description
according to the CL reference book @cite{Common LISP} from Guy L. Steele"
so I referred to that.
Now I see your message in
http://lists.gnu.org/archive/html/guile-devel/2004-07/msg00044.html
Is it correct to assume that
- For guile, the code and doc regarding FORMAT in SLIB are not relevant
any more?
- The guile FORMAT attempts to be an extension of Common Lisp FORMAT,
i.e. that all CL format directives are supported without changes
(except when documented otherwise, such as ~_)?
- Differences in behaviour between a valid CL format string and the
same string in guile (except when documented otherwise) are bugs in
format.scm that I should report?
- The reference to which I can point translators is the node
"Formatted Output" in the guile documentation?
> Nosing around format-scheme.c (if that's the right code) I noticed ~!
> described as a clisp call
Oops, that was a copy&paste artefact. I've now removed that.
> (format #f (gettext "~/"))
> (format #f (gettext "~q"))
> (format #f (gettext "~8,2i") 1+2i)
> (format #f (gettext "~65c"))
> (format #f (gettext "~4,3,'-t"))
> (format #f (gettext "~k") "fmtstr")
>
> ~q is a copyright message
> ~/ is a tab character (like ~| etc)
> ~i is complex number fixed-point (up to 5 params)
> ~c accepts a charnum param
> ~t accepts a pad char param
> ~k is an alias for ~?
OK, will be corrected in gettext.
Bruno
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-02-26 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 12:31 gettext-0.14.2 is released Bruno Haible
2005-02-25 23:14 ` Kevin Ryde
2005-02-26 16:52 ` Bruno Haible [this message]
2005-02-27 22:06 ` Kevin Ryde
2005-02-28 21:29 ` Bruno Haible
2005-02-28 22:29 ` Kevin Ryde
2005-03-15 14:18 ` Bruno Haible
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=200502261752.54673.bruno@clisp.org \
--to=bruno@clisp.org \
--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).