Author Topic: View NFO & Binsearch  (Read 5680 times)

Offline Hecks

  • Global Moderator
  • *****
  • Posts: 1973
  • naughty cop
View NFO & Binsearch
« on: April 06, 2008, 12:11:56 PM »
Formatting of NFOs from Binsearch is broken.  Also <pre></pre> tags showing up in Newzleech NFOs too.
« Last Edit: April 18, 2008, 09:53:50 AM by Hecks »

Offline Hecks

  • Global Moderator
  • *****
  • Posts: 1973
  • naughty cop
Re: View NFO & Binsearch
« Reply #1 on: April 18, 2008, 09:54:31 AM »
Sorry, this seems to be a problem with how the site is now encoding NFOs rather than Alt.Binz.

Offline therealjoeblow

  • Contributor
  • ***
  • Posts: 60
Re: View NFO & Binsearch
« Reply #2 on: April 25, 2008, 04:18:57 PM »
I don't think it's Binsearch - I just viewed the same nfo in Alt.Binz and from my browser on the Binsearch site, and the formatting/ASCII art is perfect in the browser, but full of jibberish in Alt.Binz

If <ctrl-a> copy all of the text from the Alt.Binz nfo viewer, and paste it into a blank text file verbatim, and rename that file to xxx.htm and view it in my browser, it's perfect.

So it looks to me like Alt.Binz's viewer is broken.

It would be nice if this could be fixed as it makes internal nfo viewing nearly impossible.

Cheers,
The REAL Joe

Offline Hecks

  • Global Moderator
  • *****
  • Posts: 1973
  • naughty cop
Re: View NFO & Binsearch
« Reply #3 on: April 25, 2008, 04:45:22 PM »
Nope, I'm still seeing bad encoding on the Binsearch site as well as Alt.Binz - the difference being that Alt.Binz shows the html codes of the incorrectly coded characters ... if you know what I mean, lol.

For instance, Binsearch shows this:

Code: [Select]
                                          ßÛÛÛÛÛß 

 ÜÜÜ°ÛßßÛÛÛ²ÛÛÛÛ°ÜÜÛ°Ü  Ü ÜÜ    Proudly Presents    ÜÜ Ü  Ü°ÛÜÜ°ÛÛÛÛ²ÛÛÛßßÛ°ÜÜÜ
  ²ÛÛÛÜÛÛ²²Û²ßßß߲۲ߠ ß°ß²þßÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜßþ²ß°ß  ß²Û²ßßßß²Û²²ÛÛÜÛÛÛ²
  ±ß²ÛÛ±²ß±                                                          ±ß²±Û۲߱
  ° ÞÛ²²± °                                                          ° ±²²ÛÝ °
  Ü  ²ÛÝ°                                                              °ÞÛ²  Ü
 ß²ß ÞÛ        Release Type.....: HDTV                                   ÛÝ ß²ß

Alt.Binz shows this:

Code: [Select]
&Uuml;&Uuml;&Uuml;&deg;&Ucirc;&szlig;&szlig;&Ucirc;&Ucirc;&Ucirc;&sup2;&Ucirc;&Ucirc;&Ucirc;&Ucirc;&deg;&Uuml;&Uuml;&Ucirc;&deg;&Uuml;  &Uuml; &Uuml;&Uuml;    Proudly Presents    &Uuml;&Uuml; &Uuml;  &Uuml;&deg;&Ucirc;&Uuml;&Uuml;&deg;&Ucirc;&Ucirc;&Ucirc;&Ucirc;&sup2;&Ucirc;&Ucirc;&Ucirc;&szlig;&szlig;&Ucirc;&deg;&Uuml;&Uuml;&Uuml;
  &sup2;&Ucirc;&Ucirc;&Ucirc;&Uuml;&Ucirc;&Ucirc;&sup2;&sup2;&Ucirc;&sup2;&szlig;&szlig;&szlig;&szlig;&sup2;&Ucirc;&sup2;&szlig;  &szlig;&deg;&szlig;&sup2;&thorn;&szlig;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&Uuml;&szlig;&thorn;&sup2;&szlig;&deg;&szlig;  &szlig;&sup2;&Ucirc;&sup2;&szlig;&szlig;&szlig;&szlig;&sup2;&Ucirc;&sup2;&sup2;&Ucirc;&Ucirc;&Uuml;&Ucirc;&Ucirc;&Ucirc;&sup2;
  &plusmn;&szlig;&sup2;&Ucirc;&Ucirc;&plusmn;&sup2;&szlig;&plusmn;                                                          &plusmn;&szlig;&sup2;&plusmn;&Ucirc;&Ucirc;&sup2;&szlig;&plusmn;
  &deg; &THORN;&Ucirc;&sup2;&sup2;&plusmn; &deg;                                                          &deg; &plusmn;&sup2;&sup2;&Ucirc;&Yacute; &deg;
  &Uuml;  &sup2;&Ucirc;&Yacute;&deg;                                                              &deg;&THORN;&Ucirc;&sup2;  &Uuml;
 &szlig;&sup2;&szlig; &THORN;&Ucirc;        Release Type.....: HDTV                                   &Ucirc;&Yacute; &szlig;&sup2;&szlig;

But it should look like this (-ish):

Code: [Select]
▄▄▄░█▀▀███▓████░▄▄█░▄  ▄ ▄▄    Proudly Presents    ▄▄ ▄  ▄░█▄▄░████▓███▀▀█░▄▄▄
 ▓███▄██▓▓█▓▀▀▀▀▓█▓▀  ▀░▀▓■▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀■▓▀░▀  ▀▓█▓▀▀▀▀▓█▓▓██▄███▓
 ▒▀▓██▒▓▀▒                                                          ▒▀▓▒██▓▀▒
 ░ Ì█▓▓▒ ░                                                          ░ ▒▓▓█¦ ░
 ▄  ▓█¦░                                                              ░Ì█▓  ▄
▀▓▀ Ì█        Release Type.....: HDTV                                   █¦ ▀▓▀
« Last Edit: April 25, 2008, 04:49:04 PM by Hecks »

Offline therealjoeblow

  • Contributor
  • ***
  • Posts: 60
Re: View NFO & Binsearch
« Reply #4 on: April 26, 2008, 07:27:31 AM »
The first example of those 3 is just being displayed in an incorrect font that doesn't have the extended ascii character set.  The characters themselves are correct.

If I copy and paste that text into my text editor (MetaPad) which uses NetTerm OEM font to display NFO files, it looks exactly like your 3rd example.  If I switch the font to standard Courier, then it looks like your first example.  This is the correct behavior of extended ascii wordart that has been standard for over 10 years.

It's just a font display problem, nothing encoded incorrectly.

Cheers,
The REAL Joe

Offline Hecks

  • Global Moderator
  • *****
  • Posts: 1973
  • naughty cop
Re: View NFO & Binsearch
« Reply #5 on: April 26, 2008, 10:32:22 AM »
Well ...

The same NFO displays absolutely fine when grabbed from the Newzleech site and shown in a cmd window with Terminal (OEM/DOS) font, but not when grabbed from Binsearch, when this has worked perfectly well until recently.  I'm not sure what else to add.

Edit: at my end, it seems to be down to a problem with Binsearch sending html codes, which I assume is what's borking Alt.Binz too.

Edit 2: Yep, if I do a [System.Web.HttpUtility]::HtmlDecode on the Binsearch output it displays fine.
« Last Edit: April 26, 2008, 11:34:00 AM by Hecks »

Offline Rdl

  • Administrator
  • *****
  • Posts: 3090
Re: View NFO & Binsearch
« Reply #6 on: May 06, 2008, 04:55:58 PM »
Newzleech is now fixed (parsing nfo link was also broken)

Offline Rdl

  • Administrator
  • *****
  • Posts: 3090
Re: View NFO & Binsearch
« Reply #7 on: May 06, 2008, 05:13:13 PM »
Binsearch NFO pre/formating fixed