unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Jeffrey Stedfast <jestedfa@microsoft.com>,
	"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: RE: [PATCH] test: add known broken test for indexing html
Date: Sat, 18 Mar 2017 12:08:27 -0300	[thread overview]
Message-ID: <87tw6qlj10.fsf@tethera.net> (raw)
In-Reply-To: <MWHPR21MB06407AA016A715CEEAD9E6F1CF380@MWHPR21MB0640.namprd21.prod.outlook.com>

Jeffrey Stedfast <jestedfa@microsoft.com> writes:

> Base64 encoded inline image data is always within the src attribute
> value of an <img> tag and will always begin with "data:" followed by
> the mime-type and then followed by ";base64," so it's pretty easy to
> spot.
>
> While on this topic, why index HTML attribute values at all? Other
>than perhaps some known ones like perhaps the 'alt' value of <img>
>tags?
>
> I would argue that the only portion of any HTML that you should be
> indexing at all for searching is the character data between tags.
>

I should mention that we also have a fair amount of base64 gunk from
inline PGP signatures. I'm not sure if it's just ugly to look at when
dumping the database term, or if it actually makes a measurable
difference in time/space usage.

d

      parent reply	other threads:[~2017-03-18 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 13:25 [PATCH] test: add known broken test for indexing html David Bremner
2017-03-18 13:37 ` Jeffrey Stedfast
2017-03-18 15:04   ` David Bremner
2017-03-18 16:21     ` Jeffrey Stedfast
2017-03-18 18:14       ` David Bremner
2017-03-19 17:24         ` Jeffrey Stedfast
2017-03-18 15:08   ` David Bremner [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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tw6qlj10.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=jestedfa@microsoft.com \
    --cc=notmuch@notmuchmail.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. 
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.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).