[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-dev] cruft in readAllStringHTML
- To: sc-dev@xxxxxxxxxxxxxxxx
- Subject: Re: [sc-dev] cruft in readAllStringHTML
- From: Dan Stowell <danstowell+sc3@xxxxxxxxx>
- Date: Thu, 17 Dec 2009 09:54:19 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=SZF2LYNjTzPIJfW5tQa83Fq2Csv4TnX9gIjHtpEdZs0=; b=ICbZ2sRgjbkQBT5ZJsKv//YFs8deM9ladMy8PI9vS6cA0YSM1N0p4SW5XOZzYFHAom yGZcn6pgBQWHFNmms2FTHfVRSS9DjbW5evvucYD/UnypG7XSV0Hnk4Sr81WQYmo4Y8Bb qp37kaZ64TUfz2L4GjWS64mD00uMvl2wTJSww=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=s0ekKo2oBKgFJb4FhrjpzEFzDtrmxb+Vex13G6cbq9hSLtdrdtgkf+UkgEHlyWbAFq tXZWwSbqM+3tCOgRNX9saYN2a37obe8Jgj6rs4jrzIL8JaL4Ggx7kVMOk2FwUog7+TNm VbjxPaNk0bZmC7tvgrjHLvMbBEyrLieYLPmUc=
- In-reply-to: <5AF3B82C-AB1C-466F-8754-E105E41BEE4E@xxxxxxxxxx>
- List-id: SuperCollider developers mailing list <sc-devel.create.ucsb.edu>
- References: <1EBEECD7-B889-4087-AAC0-79FDADF03D1F@xxxxxxxxxxxx> <5AF3B82C-AB1C-466F-8754-E105E41BEE4E@xxxxxxxxxx>
- Reply-to: sc-dev@xxxxxxxxxxxxxxxx
- Sender: owner-sc-dev@xxxxxxxxxxxxxxxx
2009/12/17 Scott Wilson <s.d.wilson.1@xxxxxxxxxx>:
>
> On 16 Dec 2009, at 21:06, ronald kuivila wrote:
>
> Hi all,
> If you run the following two lines you will see
>  
> in the resultant string.
> f = File("/Applications/SuperCollider3/build/Help/BinaryOps/absdif.html",
> "r");
>
> f.readAllStringHTML
>
> These appear in the HTML source as
>
> <span class="Apple-converted-space">  </span>
>
> Is there some easy fix for this or would it mean adding a special check in
> html2txt
>
> Yes I think so.
>
> or
>
> is this a flaw in the HTML generation?
No, this is a classic case of garbage-in-garbage-out. Someone put a
"gremlin" character into that particular file (possibly via alt+space?
that has a tendency to catch people out) and cocoa faithfully included
that gremlin into the stored document; then sc happens to render it.
We just need to remove the gremlin.
Dan
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/