Kevin Ryde wrote:
> Bruno Haible <[EMAIL PROTECTED]> 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"
Bruno Haible <[EMAIL PROTECTED]> writes:
>
> Also a problem is that some programs might be using the simple-format, but
> xgettext doesn't know about this (since the function name is still 'format'),
> and when the translator puts in translations with ~:* and the like, the
> simple-format will not
Kevin Ryde wrote:
> > - 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,
> >
Bruno Haible <[EMAIL PROTECTED]> 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 FO
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 de
Bruno Haible <[EMAIL PROTECTED]> 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
