From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-devel@gnu.org, Han-Wen Nienhuys <hanwen@cs.uu.nl>
Subject: Re: i18n patch ok?
Date: Wed, 22 Sep 2004 17:13:01 +0200 [thread overview]
Message-ID: <87r7ou5oci.fsf@peder.flower> (raw)
In-Reply-To: <877jqnteq1.fsf@zagadka.ping.de> (Marius Vollmer's message of "Wed, 22 Sep 2004 00:54:46 +0200")
Marius Vollmer writes:
> Yes, nice work, thanks! I have included it in my local working copy.
Ok. Please check with Han-Wen, he was working to include this too.
> I see that the FSF has sufficient papers from you, but Bruno has not,
> as far as I can see. So I need to known which portions were written
> by Bruno before I can commit the patch. Could you tell me this?
That would already be a bit of work; we both enhanched each-others
versions twice. My guess would be that Bruno wrote about half of it,
so we should ask Bruno about his papers.
> Also, we need documentation for the new functions, but it is not in
> the patch. Could you post a patch for the documentation also?
Where should I look for inspiration? It was my impression that docs
were generated from the code.
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-09-22 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 19:00 i18n patch ok? Jan Nieuwenhuizen
2004-09-21 22:54 ` Marius Vollmer
2004-09-21 23:58 ` Marius Vollmer
2004-09-22 15:13 ` Jan Nieuwenhuizen [this message]
2004-09-22 15:38 ` Han-Wen Nienhuys
2004-09-22 20:25 ` Marius Vollmer
2004-09-22 20:51 ` Jan Nieuwenhuizen
2004-09-23 19:04 ` Marius Vollmer
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 15:48 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=87r7ou5oci.fsf@peder.flower \
--to=janneke@gnu.org \
--cc=guile-devel@gnu.org \
--cc=hanwen@cs.uu.nl \
/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).