FogBugz (Case [Issue]20313) Zinc - ZnEasy get fails with "ZnInvalidUTF8: Illegal leading byte for utf-8 encoding"

Classic

List

Threaded

♦

♦

Locked 1 message

Pharo Issue Tracker

Reply | Threaded

Open this post in threaded view

♦

♦

|

FogBugz (Case [Issue]20313) Zinc - ZnEasy get fails with "ZnInvalidUTF8: Illegal leading byte for utf-8 encoding"

Hwee-Boon Yar edited Case 20313: ZnEasy get fails with "ZnInvalidUTF8: Illegal leading byte for utf-8 encoding": Bug in  Zinc: 1. Pharo Image  •  You are subscribed to this case Thanks Sven. > But both curl and browsers seem to keep on loading the page. So I would translate your issue as a request to be optionally more lenient when UTF-8 decoding. Agreed ? > The question though is what to do in case of error ? The most flexible would probably be to allow the user to specify the custom behaviour. Right. I should also have mentioned my use case which should be helpful. I'm trying to scrape the web page using Soup which uses Zinc. So having a way to make it more forgiving (be it a flag or some other way to specify custom behaviour) would be great. In most cases web servers should be expected to be configured correctly, but unfortunately when web scraping, we clients have to make do. Priority: 4 – Would be nice Status: Work Needed Assigned to: Everyone Milestone: Later Go to Case No longer need updates? Unsubscribe from this case. Don't want FogBugz notifications anymore? Update your preferences. A FogBugz case was edited by Hwee-Boon Yar. Case ID: 20313 Title: ZnEasy get fails with "ZnInvalidUTF8: Illegal leading byte for utf-8 encoding" Status: Work Needed Category: Bug Project: Zinc Area: 1. Pharo Image Priority: 4 - Would be nice Milestone: Later Assigned To: Everyone URL: https://pharo.fogbugz.com/f/cases/20313 Thanks Sven. > But both curl and browsers seem to keep on loading the page. So I would translate your issue as a request to be optionally more lenient when UTF-8 decoding. Agreed ? > The question though is what to do in case of error ? The most flexible would probably be to allow the user to specify the custom behaviour. Right. I should also have mentioned my use case which should be helpful. I'm trying to scrape the web page using Soup which uses Zinc. So having a way to make it more forgiving (be it a flag or some other way to specify custom behaviour) would be great. In most cases web servers should be expected to be configured correctly, but unfortunately when web scraping, we clients have to make do. You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=20313) from this case. _______________________________________________ Pharo-bugtracker mailing list [hidden email] https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker