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: Mon, 28 Feb 2005 09:06:42 +1100	[thread overview]
Message-ID: <87zmxpwtcd.fsf@zip.com.au> (raw)
In-Reply-To: <200502261752.54673.bruno@clisp.org> (Bruno Haible's message of "Sat, 26 Feb 2005 17:52:54 +0100")

Bruno Haible <bruno@clisp.org> writes:
>
>   - For guile, the code and doc regarding FORMAT in SLIB are not relevant
>     any more?

Oh, well, if it's withdrawn from slib then there's nothing for guile
to stay compatible with.

>   - 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 ~_)?

Yes, basically, I think.  There's some things missing though, like ~< ~>.

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

Yep.  I think there's some doubtful treatment of digits in some of the
floating point output, that's the sort of thing that really ought to
be the same as CL.

>   - The reference to which I can point translators is the node
>     "Formatted Output" in the guile documentation?

For guile, yes.  What other schemes are doing is another matter.

srfi-28 and srfi-48 specify versions of format too.  In the latter ~t
is different, and ~h is an addition.


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


  reply	other threads:[~2005-02-27 22:06 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
2005-02-27 22:06     ` Kevin Ryde [this message]
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=87zmxpwtcd.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).