unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: gettext-0.14.2 is released
Date: Sat, 26 Feb 2005 10:14:07 +1100	[thread overview]
Message-ID: <87vf8ggrls.fsf@zip.com.au> (raw)
In-Reply-To: <200502251331.44912.bruno@clisp.org> (Bruno Haible's message of "Fri, 25 Feb 2005 13:31:44 +0100")

Bruno Haible <bruno@clisp.org> writes:
>
>   - messages can be marked as "scheme-format", denoting 'format' strings.

I noticed a couple of forms that provoke errors,

	(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 ~?

Nosing around format-scheme.c (if that's the right code) I noticed ~!
described as a clisp call, in format.scm ~! is an output flush (no
parameters or args), though it doesn't seem to cause an error.

I added a bit to "Formatted Output" in the guile cvs reference manual
based on my understanding of what format.scm is supposed to do.
There's only a few differences from CL.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2005-02-25 23:14 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 [this message]
2005-02-26 16:52   ` Bruno Haible
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=87vf8ggrls.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --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).