bsef11a055 / mp-onlinevideos2

Automatically exported from code.google.com/p/mp-onlinevideos2
0 stars 1 forks source link

Incorrect charset at specific website #106

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
> What steps will reproduce the problem?
1. Add to list: "LineCinemaOrg" and "Kino-Dom.tv (TV Series)"
2. Open "LineCinemaOrg"  - incorrect charset
3. Open "Kino-Dom.tv (TV Series)" - shown correctly. 

> What is the expected output? What do you see instead?
> Please provide any additional information below.
Both sites are in fact identical, running the same engine.
The only differnce I could see on http://LineCinema.Org is additional META 
items in header before http-equiv="Content-Type", 3 lines of 
name="google-site-verification".

It looks like OnlineVideos just doesn't receive that 4th line of header, with 
correct charset=windows-1251, resulting the issue. 

Original issue reported on code.google.com by maxbal...@gmail.com on 28 Jul 2011 at 2:10

GoogleCodeExporter commented 9 years ago
OnlineVideos takes the encoding from the http headers, it will not analyze the 
content. I have seen server that don't set the encoding or set it wrong 
resulting in what you describe. You could fix it, if you have your own util and 
force an encoding on received data.

Original comment by bborgsd...@gmail.com on 28 Jul 2011 at 5:12

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Well... I hope, I see what you're talking about. And most probably you are 
right. There are just some strange circumstances which made me submitting this 
report:
- as I said, both mentioned sites are in fact identical (but surely I admit 
that servers settings could be different);
- that site LineCinemaOrg worked OK in OnlineVideos until they added those 
"verification" meta-data;
- yesterday, when I was creating regexps for another site, I faced the same 
problem, that site has "verification" meta as well and OnlineVideos using wrong 
charset; for that site "force UTF" settings is helpful, because that site is in 
UTF in fact, unlike the one in subject.
Hence this request for possible issue, I do not insist that it is really exists.

Original comment by maxbal...@gmail.com on 29 Jul 2011 at 8:18

GoogleCodeExporter commented 9 years ago
Is this issue resolved with the dll posted in issue 105?

Original comment by bborgsd...@gmail.com on 9 Aug 2011 at 1:05

GoogleCodeExporter commented 9 years ago
Is this issue resolved with the dll posted in issue 105?

Original comment by bborgsd...@gmail.com on 9 Aug 2011 at 1:05

GoogleCodeExporter commented 9 years ago
Yes, totally! Thank you! 

Original comment by maxbal...@gmail.com on 9 Aug 2011 at 1:19

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r1487.

Original comment by bborgsd...@gmail.com on 9 Aug 2011 at 2:25