From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Help with sxml simple parser for the quicklisp importer
Date: Wed, 23 Jan 2019 10:55:21 -0600 [thread overview]
Message-ID: <87h8dzco06.fsf@gmail.com> (raw)
In-Reply-To: <87womv5psn.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 23 Jan 2019 16:58:32 +0100")
Ricardo Wurmus <rekado@elephly.net> writes:
> swedebugia <swedebugia@riseup.net> writes:
>
>>> The second “link” tag opens but is never closed. This may be valid
>>> HTML, but it is not valid XML, which is what xml->sxml expects.
>>
>> Thanks for the quick answer!
>> I will try to remove this line before handling over to the parser.
>
> I would recommend looking for a better source of package information.
> Parsing HTML is not fun and is often brittle.
The package information in quickdocs is accessed[1] via the API of
whatever is hosting the sourcecode. We could try doing the same.
Alternatively, it is good practice for CL systems defined in .asd files
to contain a `:description`, and even a `:long-description` field. We could
take the stance that package information simply comes from there as
technically this is the actual package's (i.e. system's) description.
And as CL is a lisp, it should be relatively easy to parse this out. The
only caveat is that I think it's possible for these fields to contain
sexps which read in other files, in which case we should do the same.
I hope this helps.
[1] - https://github.com/quickdocs/quickdocs-updater/blob/a64a41df9e5f1a3721ab68f9f02189ecbb54513b/src/repos.lisp
--
Katherine
prev parent reply other threads:[~2019-01-23 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 12:35 Help with sxml simple parser for the quicklisp importer swedebugia
2019-01-23 14:22 ` Ricardo Wurmus
2019-01-23 16:03 ` swedebugia
2019-01-23 15:58 ` Ricardo Wurmus
2019-01-23 16:32 ` swedebugia
2019-01-23 16:41 ` Ricardo Wurmus
2019-01-23 18:58 ` Pierre Neidhardt
2019-01-23 21:21 ` swedebugia
2019-01-23 16:55 ` Katherine Cox-Buday [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8dzco06.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).