From: taylanbayirli@gmail.com (Taylan Ulrich B.)
To: Dmitry Bogatov <KAction@gnu.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Guile parsing html and htmlprag.
Date: Wed, 24 Jul 2013 15:52:34 +0200 [thread overview]
Message-ID: <87li4wawv1.fsf@taylan.uni.cx> (raw)
In-Reply-To: <87a9lcw1mj.fsf@gnu.org> (Dmitry Bogatov's message of "Wed, 24 Jul 2013 17:04:04 +0400")
Dmitry Bogatov <KAction@gnu.org> writes:
> Hello!
>
> Beeing in need to parse html(not xml) with Guile, I discovered that we
> have no one-true-way solution, like python's Beautiful Soup. The best we
> have is htmlprag-0.16. It works for me, good documented(even in
> TexInfo), but it is dropped by it's author. I think it would get more
> love as part of official Guile modules tree (personally, I always prefer
> standard modules to something-that-even-have-no-git-repository).
>
> If you agree with proposition, I will start work on patch.
>
> --
> Best regards, Dmitry Bogatov <KAction@gnu.org>,
> Free Software supporter and netiquette guardian.
> git clone git://gitorious.org/illusionoflife-read-only/rc-files.git --depth 1
> GPG: 54B7F00D
> Html mail and proprietary format attachments are forwarded to /dev/null.
If I'm not mistaken, having a nontrivial amount of code (e.g. whole
module) become part of the official Guile distribution requires the
copyright of the code (and subsequent contributions) to be assigned to
the FSF. So both you and all original authors of htmlprag would need to
officially assign their copyright. (This might be implausible if there
have been a dozen contributors.)
Otherwise, might want to look into guildhall.
Taylan
next prev parent reply other threads:[~2013-07-24 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 13:04 Guile parsing html and htmlprag Dmitry Bogatov
2013-07-24 13:52 ` Taylan Ulrich B. [this message]
2013-07-24 14:09 ` [guile] " Dmitry Bogatov
2013-07-26 21:23 ` Mark H Weaver
2013-07-27 13:31 ` [guile] " Dmitry Bogatov
2013-08-17 12:28 ` Ludovic Courtès
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=87li4wawv1.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=KAction@gnu.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).