Register - Login
Views: 99412648
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-24-22 11:54:08 PM
Jul - Posts by IIMarckus
Pages: 1 2 3 4 5 6
IIMarckus
Member
Level: 25


Posts: 61/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 10-26-10 03:14:13 AM, in Link’s Awakening confirmed for 3DS Virtual Console Link

Also Super Mario Land. Both games will have a new 3D mode.



____________________
iimarck.us
IIMarckus
Member
Level: 25


Posts: 62/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 10-31-10 03:56:54 AM, in The Internet used to be so different. Link

Please be patient — This Page is Under Construction!



____________________
iimarck.us
IIMarckus
Member
Level: 25


Posts: 63/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-21-10 03:13:13 AM, in Text encoding Link
I saw some talk about text encoding in this forum, and I’d like to clear up some misconceptions. I work with this stuff a lot.

What text encodings are there?
  • ASCII
  • ISO-8859-1
  • win1252
  • UTF-8

ASCII


Pros:
  • It’s everywhere. Sticking to it means your text will be fine wherever you post it.
Cons:
  • Limited to 128 characters: a–z, A–Z, 0–9, and a little punctuation. Absolutely no internationalization (the A stands for American, after all).

ISO-8859-1


AKA Latin-1. Standardized way back when. An okay choice but not the best.

Pros:
  • It’s in lots of places. Lots of programs default to it.
  • ASCII-compatible. It encompasses all of ASCII.
  • More characters than ASCII. Adds accents (àáâä)
Cons:
  • Limited to 256 characters, which isn’t very many considering. No extra internationalization outside of Europe/Americas.
  • Just one of many ISO-8859 encodings; there are 16, and they’re all incompatible except for the ASCII part.

win1252


Microsoft’s bastardized ISO-8859-1. Don’t ever use this. Seriously, don’t.

Pros:
  • Nothing that ISO-8859-1 doesn’t do better.
Cons:
  • Non-standard. Windows-only.
  • Limited to 256 characters.

UTF-8


The one true encoding. Supports Unicode, which means approximately one zillion characters.

Pros:
  • Backwards-compatible with ASCII.
  • Widely used; there are more UTF-8 webpages than ASCII webpages, and than ISO-8859-1 webpages.1
  • Lots and lots of characters!
Cons:
  • It’s not the only encoding out there, so sometimes ISO-8859-1 will be interpreted as UTF-8 (Pokémon → Pokémon) or vice-versa (Pokémon → Pok�on)


What about Shift-JIS?

Don’t use it unless you’re actually a Japanese person living in Japan. (Even then, UTF-8 is probably better, but it’s hard to go against the flow.) If you’re an English speaker working with Japanese text, always use UTF-8—it’s the only one in the list that supports Asian characters!


What about those HTML entities like é and ☺?

When you’re not sure of what encoding the page uses, these are pretty safe, and they let you use any Unicode character. Just be aware that they’re HTML, which means you can’t use them except on your own pages or boards that support HTML (like Jul). This is probably the safest way to use special characters on Jul.‡


What about UTF-16/UTF-32/other Unicode encodings?

They’re not ASCII-compatible and as a result are worthless. (UTF-16 is built into Java, unfortunately, but you can and should avoid it elsewhere.)


What encoding should I use for my new site?

UTF-8, no question about it. It is widely used, widely supported, widely compatible, and its only cons are when working with legacy content (i.e. unimportant when you’re starting anew).


How do I send my HTML/PHP pages as UTF-8?

Send an HTTP header:
Content-Type: text/html; charset=utf-8

In PHP, you can do this with:
header('Content-Type: text/html; charset=utf-8');

If you use .htaccess, put:
AddDefaultCharset UTF-8

If you don’t have access to either of these, HTML can almost do it, but this will always be overwritten by the HTTP header if there is one. Try to do one of the above instead.
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">


Of course, the files you send must be in UTF-8 and not another encoding. Any good text editor can make them this way (not Notepad; Notepad++ can).


Should I convert my database-driven website to UTF-8?

That depends. Maybe. But make a backup beforehand; MySQL is unbelievably stupid when it comes to converting character sets. (Seriously, there is no excuse for silent truncation in this day and age.) It’s better to make sure it uses UTF-8 from the beginning.


‡I say this because Tauwasser’s post showed up fine for me, even though other people were seeing garbage. That’s because Jul doesn’t send an encoding in its HTTP headers, so browsers have to guess. Mine and Tauwasser’s are apparently guessing UTF-8, while other people’s were incorrectly guessing ISO-8859-1. HTML entities will never be misinterpreted by a browser.

That said, I’ve used raw UTF-8 in most of my previous posts here and nobody complained, so I’m assuming they showed up correctly for everybody. So again, it’s inconsistent, and HTML entities are Safer Here™.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 64/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-21-10 04:08:52 AM, in Text encoding (last edited by IIMarckus at 11-21-10 01:14 AM) Link
Originally posted by Aoi
Did the kanji in my post show up correctly, for you?

Yes, your kanji and Tauwasser’s kanji showed up correctly in my browser (Firefox). Our browsers are autodetecting to UTF-8.
Originally posted by Aoi
(For everyone reading this, do these two lines show up correctly? Just a test of me using my IME, rather than cutting and pasting from my Japanese WP, as I did in the original post. Oops.)

No, they’re garbage here unless I set the encoding to UTF-8.

Both of the threads use UTF-8, but even for me one is correctly autodetected as UTF-8 while the other autodetects to ISO-8859-1. This is why leaving things up to autodetect is bad.

Originally posted by Imajin
Originally posted by Aoi
Did the kanji in my post show up correctly, for you?

(For everyone reading this, do these two lines show up correctly? Just a test of me using my IME, rather than cutting and pasting from my Japanese WP, as I did in the original post. Oops.)

私の名前は、葵。
テスト


It only works for me when the codepage on the browser is set to UTF-8... which I'm told is inaccurate for Jul,

This isn’t quite true. It’s not that Jul doesn’t support UTF-8, it’s that Jul doesn’t support any encoding (i.e., it doesn’t tell browsers to detect it as anything), while simultaneously “supporting” all of them (i.e., it lets anyone enter any encoding they want).

This means that if John Doe’s browser defaults to UTF-8 and he talks about Pokémon, Jane Smith (whose browser defaults to ISO-8859-1) will see Pokémon. Then when she posts about Pokémon, John will see his Pokémon and her Pok�on, and she will see her Pokémon and his Pokémon. On the same page.

If I were to give my opinion (with the understanding that it gets either followed or ignored—that kinda goes without saying), it would be that there are two options:
  1. Leave the board the way it is, rely on autodetect, tell people to not enter UTF-8 and use HTML entities instead. No copying and pasting from Wikipedia.
  2. Add UTF-8 to the HTTP headers (a one-line change). This lets people copy and paste Japanese from Wikipedia, disables autodetect so everyone sees the same thing, and triggers everybody’s browser to enter the same encoding. Of course, existing ISO-8859-1 content will look messed up, but since I’ve used UTF-8 a lot on this board (and I’ve checked, it wasn’t converted to HTML entities) and haven’t seen any garbled content, I doubt there’s much.
(There is a third option, to try to convert the whole board at the database level to UTF-8. This is a bad idea, it will never happen, and I won’t talk about it anymore.)

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 65/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-21-10 04:11:50 AM, in Unused Pokemon Ruby/Sapphire text. Different contest system? Debug sound test? You got it! And more Link
Full text dump here. Bear in mind that there’s still a ton of crap left over from romjuice.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 66/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-21-10 04:18:18 AM, in Text encoding Link
Originally posted by Xkeeper
Originally posted by IIMarckus
(There is a third option, to try to convert the whole board at the database level to UTF-8. This is a bad idea, it will never happen, and I won’t talk about it anymore.)

I actually have plans to do just that, if you can believe it. It can be done (and will be, at some point). It can be done, obviously.


Interestingly, I think that my browser (Opera) picks encodings based on whatever it encounters first. This thread is read as utf-8, while other threads are windows-1251.


Ah well.

Cool. By “a bad idea” I meant “a bad idea without motivation and lots of backups,” of course.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 67/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-21-10 04:31:41 AM, in Text encoding Link
Originally posted by Xkeeper
Until then, I should seriously add a tag to force the encoding to windows-1251; that's the DB's native format (latin1) and I'm sure UTF-8 is likely to break with the change.
Better than the status quo I suppose.

:thumbsup:

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 68/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-21-10 03:03:26 PM, in Text encoding Link
Originally posted by Joe
Shift-JIS has one major advantage over Unicode: All characters will be mapped to Japanese glyphs. Thanks to Han unification, many obviously different characters are mapped to the same code point. (The same is true of other Asian text encodings.) Hopefully a resolution can be worked out, because UTF-8 is much more useful overall.
Han unification is more of a political problem than a technical one; it just shunts the font choice from the raw encoding to whatever’s rendering the text (e.g., the browser). If you’re that worried about it, just wrap your text in <span lang="ja">: 紀 紀

There are lots of good arguments for Han unification; one is that, e.g., Japanese books use Japanese fonts and not Chinese fonts when quoting Chinese text.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 69/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-21-10 05:50:08 PM, in Text encoding Link
Originally posted by Joe
Originally posted by IIMarckus
Han unification is more of a political problem than a technical one; it just shunts the font choice from the raw encoding to whatever’s rendering the text (e.g., the browser).
This is a problem when the browser chooses wrong. Say a website is Japanese and uses UTF-8 without specifying font or language. On Japanese systems, the browser will choose a Japanese font by default and so the website appears fine. On my computer, Opera chooses a Korean font by default and so the website appears with the Korean variants of some very common kanji.

社 (ko)

社 (ja)

Which brings us back to where we started: leaving things up to autodetect is bad, whether it’s for encoding (Content‑Type/charset) or for language (lang="").

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 70/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-23-10 01:56:13 AM, in Tron Legacy Link

Coming the 17th!

Counting down the days…

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 71/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-23-10 02:01:21 AM, in Optional Linebreaks (last edited by IIMarckus at 11-23-10 09:40 AM) Link
When working with HTML it would be nice to disable linebreak → <br> translation, with a checkbox like the one to disable smilies.

For example:

  • Item one

  • Item two

  • Item three

  • …



<ul>
<li>Item one</li>
<li>Item two</li>
<li>Item three</li>
<li>…</li>
</ul>

versus:
  • Item one
  • Item two
  • Item three
  • …


<ul><li>Item one</li><li>Item two</li><li>Item three</li><li>…</li></ul>

Looks better, but harder to read.


Edit:
Originally posted by Xkeeper
You also need to remove newlines from the style, because the board treats newlines as <br> tags.

This will be fixed at some point in the distant future.
Okay then. (Read threads first, then post new ones!)

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 72/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 01-29-11 07:47:23 PM, in Working with Mac OS X - For Web Developers (last edited by IIMarckus at 01-29-11 04:49 PM) Link

A minor note:

Originally posted by Kas
  • 'grep "test" /Users/Kas/Sites/test -Rn' in the Terminal uses grep to recursively search directory /Users/Kas/Sites/test for documents containing the string "test". This is immensely useful when asked to modify something in a project and you don't know where to begin looking.

Try to get in the habit of “grep -Rn "test" /Users/Kas/Sites/test”. Most UNIX command‐line tools are “<command> <flags> <arguments>”, not “<command> <arguments> <flags>”. Order doesn’t matter for the GNU versions of tools (such as the grep in OS X), but you’ll be in for a nasty surprise should you ever SSH into a server that doesn’t use GNU grep by default.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 73/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 02-10-11 05:03:30 AM, in gimme "MP3" player suggestions Link
Originally posted by Shadic
Sansa Fuze. $55 for 4GB, and can be easily expanded. You can put Rockbox on it, it can play video, it has FM radio AND a microphone, and it's pretty sleek. Sails and I both have one, my girlfriend does as well, and I've never had a real complaint on it. I've had it for over a year, and the battery will last around 24 hours playing music, regardless of how long it's been since you've last charged it. I love the damn thing.

Seriously, get this, and all of the sudden you have a 12GB MP3 player for $65. Forget all that overpriced Apple shit. This is shiny enough, why pay extra just to look hip?

Edit: Oh yes, it does play .ogg. :)

Thirding a Sansa Fuze. Matches your description, cheap and full‐featured. And it does support .ogg out of the box, even without Rockbox (but irritatingly, not when the file is named .oga, which is somewhat common for audio Ogg files).

FLAC is cool when you have lots of space. I rip all my CDs to FLAC. But for a portable player I would transcode to Ogg Vorbis for space reasons. And that’s easy to do. (Especially on Unix. CD to .wav: “cdio cdrip”, .wav to .flac: “flac *.wav”, .flac to .ogg: “oggenc *.flac”.) Ogg and FLAC also use the same metadata format.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 74/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 02-10-11 05:23:03 AM, in What Browser Do You Use? Link

Currently using Firefox. OpenBSD recently updated to Chrome 9, so I might try it out, but I’ve gotten a bit attached to HTTPS Everywhere.

Sometimes I use Netsurf, because it’s neat to see a browser that is reasonably small (the source code is 1.7MB; Chrome doesn’t even come close).

Originally posted by paulguy
There also should be some kind of daemon that runs and updates /etc/hosts with lists of ad sites so it's global and handled by the network stack, so it's not tied to 1 browser.

Sounds like Adsuck, minus the automatic download part.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 75/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 02-20-11 11:14:13 PM, in What Browser Do You Use? Link

I use Google. Google predominates the market, obviously, but occasionally I like to go to Yahoo just to give them some business.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 76/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 03-22-11 03:24:00 AM, in Ever donate blood? Link

I do it all the time. Probably three times a year.

Get a free shirt and cookies and juice every time.

A−.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 77/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 07-16-11 06:51:59 PM, in PHP proposes deprecating ext/mysql (last edited by IIMarckus at 07-16-11 03:55 PM) Link

link

Very interesting. Didn’t see it coming.

(Title should say: PHP proposes deprecating ext/mysql.)

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 78/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 11-27-11 10:34:43 PM, in Favorite Anime? Link
  • Serial Experiments Lain
  • Cowboy Bebop
  • Neon Genesis Evangelion
  • Higurashi no Naku Koro Ni
  • The Melancholy of Haruhi Suzumiya
  • Madoka Magica
  • Death Note
  • Now and Then, Here and There

Also, some movies:

  • 5 Centimeters Per Second, and other stuff by Makoto Shinkai
  • Operation: Return the Treasure (Lupin III TV special)
  • The Girl Who Leapt Through Time
  • My Neighbor Totoro, Spirited Away, and most other Studio Ghibli / Miyazaki stuff


____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 79/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 12-01-11 12:11:04 AM, in Adding new Pokemon in Generation I Link
Originally posted by Rena
Since generation 1 doesn't use a clock, you could convert it to use the MBC5 chip with very little effort. IIRC that gives you up to 4MB of ROM space.

Up to 8 MiB, actually. But you shouldn’t need it, because:

Originally posted by Keitaro
good to know, about the free space stuff. I hacked the GB Pokemon games extensively back in the day (my main focus is the GBA ones now) and I remember very much that Red had a lot of weird programming quirks, so I just assumed the free space was limited.

Space was limited in the Japanese Red and Green. They were counting bytes, and according to interviews only had enough space for Mew after removing debug stuff. The English versions, though, are doubled in size, so there are banks upon banks of free space. My (very) rough calculations show at least a quarter, and almost half, of Pokémon Red is free space.

____________________
[hax.]iimarck.us
IIMarckus
Member
Level: 25


Posts: 80/111
EXP: 82221
For next: 7399

Since: 10-11-08


Since last post: 3.0 years
Last activity: 1.7 years
Posted on 12-14-11 04:13:02 AM, in (Neopets) Let me know what you think of this website... Link

I started doing Neopets back in 1999; it was basically my introduction to the Internet. Owned a Nimmo named HealthFrog, and a Shoyru named NidoBarb (after Nidorino, because that’s the coolest Pokémon ever). Had a daily routine to try to get free stuff by the end—the Giving Tree, Jelly Land, and that prehistoric area, among others. Amazing how it all comes back.

I had stopped playing by 2003 or so, and I think I’m better off for it… it was nothing but a timesink.

____________________

[hax.]iimarck.us

Pokémon Red disassembly project
Pages: 1 2 3 4 5 6
Jul - Posts by IIMarckus


Rusted Logic
Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

39 database queries, 38 query cache hits.
Query execution time:  0.090751 seconds
Script execution time:  0.040600 seconds
Total render time:  0.131351 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 147 column 136 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 95 - Warning: unescaped & or unknown entity "&page"
line 149 column 128 - Warning: unescaped & or unknown entity "&page"
line 149 column 161 - Warning: unescaped & or unknown entity "&page"
line 149 column 196 - Warning: unescaped & or unknown entity "&page"
line 149 column 229 - Warning: unescaped & or unknown entity "&page"
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 264 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 182 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 184 column 9 - Warning: missing <tr>
line 202 column 13 - Warning: missing <tr>
line 208 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 210 column 9 - Warning: missing <tr>
line 228 column 13 - Warning: missing <tr>
line 297 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 299 column 9 - Warning: missing <tr>
line 317 column 13 - Warning: missing <tr>
line 343 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 345 column 9 - Warning: missing <tr>
line 363 column 13 - Warning: missing <tr>
line 369 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 371 column 9 - Warning: missing <tr>
line 389 column 13 - Warning: missing <tr>
line 403 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 405 column 9 - Warning: missing <tr>
line 423 column 13 - Warning: missing <tr>
line 431 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 433 column 9 - Warning: missing <tr>
line 451 column 13 - Warning: missing <tr>
line 459 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 461 column 9 - Warning: missing <tr>
line 479 column 13 - Warning: missing <tr>
line 490 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 492 column 9 - Warning: missing <tr>
line 510 column 13 - Warning: missing <tr>
line 513 column 174 - Warning: missing </a> before </li>
line 513 column 263 - Warning: inserting implicit <a>
line 513 column 263 - Warning: missing </a> before <a>
line 513 column 263 - Warning: inserting implicit <a>
line 513 column 263 - Warning: missing </a> before <a>
line 516 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 518 column 9 - Warning: missing <tr>
line 536 column 13 - Warning: missing <tr>
line 543 column 1 - Warning: missing <li>
line 544 column 1 - Warning: missing <li>
line 545 column 1 - Warning: missing <li>
line 546 column 1 - Warning: missing <li>
line 547 column 1 - Warning: missing <li>
line 569 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 571 column 9 - Warning: missing <tr>
line 589 column 13 - Warning: missing <tr>
line 595 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 597 column 9 - Warning: missing <tr>
line 615 column 13 - Warning: missing <tr>
line 618 column 245 - Warning: unescaped & or unknown entity "&qid"
line 618 column 260 - Warning: unescaped & or unknown entity "&sr"
line 620 column 829 - Warning: unescaped & or unknown entity "&ie"
line 620 column 837 - Warning: unescaped & or unknown entity "&qid"
line 620 column 852 - Warning: unescaped & or unknown entity "&sr"
line 625 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 627 column 9 - Warning: missing <tr>
line 645 column 13 - Warning: missing <tr>
line 651 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 653 column 9 - Warning: missing <tr>
line 671 column 13 - Warning: missing <tr>
line 677 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 679 column 9 - Warning: missing <tr>
line 697 column 13 - Warning: missing <tr>
line 703 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 705 column 9 - Warning: missing <tr>
line 723 column 13 - Warning: missing <tr>
line 726 column 119 - Warning: unescaped & or unknown entity "&m"
line 726 column 137 - Warning: unescaped & or unknown entity "&w"
line 729 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 731 column 9 - Warning: missing <tr>
line 749 column 13 - Warning: missing <tr>
line 755 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 757 column 9 - Warning: missing <tr>
line 775 column 13 - Warning: missing <tr>
line 781 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 783 column 9 - Warning: missing <tr>
line 801 column 13 - Warning: missing <tr>
line 807 column 17 - Warning: missing <tr>
line 807 column 17 - Warning: discarding unexpected <table>
line 810 column 35 - Warning: missing <tr>
line 810 column 95 - Warning: unescaped & or unknown entity "&page"
line 810 column 128 - Warning: unescaped & or unknown entity "&page"
line 810 column 161 - Warning: unescaped & or unknown entity "&page"
line 810 column 196 - Warning: unescaped & or unknown entity "&page"
line 810 column 229 - Warning: unescaped & or unknown entity "&page"
line 810 column 50 - Warning: missing </font> before </td>
line 810 column 264 - Warning: missing </font> before </table>
line 812 column 35 - Warning: missing <tr>
line 812 column 50 - Warning: missing </font> before </td>
line 812 column 136 - Warning: missing </font> before </table>
line 814 column 17 - Warning: discarding unexpected </textarea>
line 814 column 28 - Warning: discarding unexpected </form>
line 814 column 35 - Warning: discarding unexpected </embed>
line 814 column 43 - Warning: discarding unexpected </noembed>
line 814 column 53 - Warning: discarding unexpected </noscript>
line 814 column 64 - Warning: discarding unexpected </noembed>
line 814 column 74 - Warning: discarding unexpected </embed>
line 814 column 82 - Warning: discarding unexpected </table>
line 814 column 90 - Warning: discarding unexpected </table>
line 816 column 9 - Warning: missing </font> before <table>
line 828 column 25 - Warning: discarding unexpected </font>
line 837 column 58 - Warning: discarding unexpected </font>
line 815 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 161 column 22 - Warning: <img> lacks "alt" attribute
line 161 column 63 - Warning: <img> lacks "alt" attribute
line 161 column 112 - Warning: <img> lacks "alt" attribute
line 161 column 162 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 187 column 22 - Warning: <img> lacks "alt" attribute
line 187 column 63 - Warning: <img> lacks "alt" attribute
line 187 column 112 - Warning: <img> lacks "alt" attribute
line 187 column 162 - Warning: <img> lacks "alt" attribute
line 198 column 15 - Warning: <img> lacks "alt" attribute
line 213 column 22 - Warning: <img> lacks "alt" attribute
line 213 column 63 - Warning: <img> lacks "alt" attribute
line 213 column 112 - Warning: <img> lacks "alt" attribute
line 213 column 162 - Warning: <img> lacks "alt" attribute
line 224 column 15 - Warning: <img> lacks "alt" attribute
line 302 column 22 - Warning: <img> lacks "alt" attribute
line 302 column 63 - Warning: <img> lacks "alt" attribute
line 302 column 112 - Warning: <img> lacks "alt" attribute
line 302 column 162 - Warning: <img> lacks "alt" attribute
line 313 column 15 - Warning: <img> lacks "alt" attribute
line 348 column 22 - Warning: <img> lacks "alt" attribute
line 348 column 63 - Warning: <img> lacks "alt" attribute
line 348 column 112 - Warning: <img> lacks "alt" attribute
line 348 column 162 - Warning: <img> lacks "alt" attribute
line 359 column 15 - Warning: <img> lacks "alt" attribute
line 374 column 22 - Warning: <img> lacks "alt" attribute
line 374 column 63 - Warning: <img> lacks "alt" attribute
line 374 column 112 - Warning: <img> lacks "alt" attribute
line 374 column 162 - Warning: <img> lacks "alt" attribute
line 385 column 15 - Warning: <img> lacks "alt" attribute
line 408 column 22 - Warning: <img> lacks "alt" attribute
line 408 column 63 - Warning: <img> lacks "alt" attribute
line 408 column 112 - Warning: <img> lacks "alt" attribute
line 408 column 162 - Warning: <img> lacks "alt" attribute
line 419 column 15 - Warning: <img> lacks "alt" attribute
line 436 column 22 - Warning: <img> lacks "alt" attribute
line 436 column 63 - Warning: <img> lacks "alt" attribute
line 436 column 112 - Warning: <img> lacks "alt" attribute
line 436 column 162 - Warning: <img> lacks "alt" attribute
line 447 column 15 - Warning: <img> lacks "alt" attribute
line 464 column 22 - Warning: <img> lacks "alt" attribute
line 464 column 63 - Warning: <img> lacks "alt" attribute
line 464 column 112 - Warning: <img> lacks "alt" attribute
line 464 column 162 - Warning: <img> lacks "alt" attribute
line 475 column 15 - Warning: <img> lacks "alt" attribute
line 495 column 22 - Warning: <img> lacks "alt" attribute
line 495 column 63 - Warning: <img> lacks "alt" attribute
line 495 column 112 - Warning: <img> lacks "alt" attribute
line 495 column 162 - Warning: <img> lacks "alt" attribute
line 506 column 15 - Warning: <img> lacks "alt" attribute
line 521 column 22 - Warning: <img> lacks "alt" attribute
line 521 column 63 - Warning: <img> lacks "alt" attribute
line 521 column 112 - Warning: <img> lacks "alt" attribute
line 521 column 162 - Warning: <img> lacks "alt" attribute
line 532 column 15 - Warning: <img> lacks "alt" attribute
line 574 column 22 - Warning: <img> lacks "alt" attribute
line 574 column 63 - Warning: <img> lacks "alt" attribute
line 574 column 112 - Warning: <img> lacks "alt" attribute
line 574 column 162 - Warning: <img> lacks "alt" attribute
line 585 column 15 - Warning: <img> lacks "alt" attribute
line 600 column 22 - Warning: <img> lacks "alt" attribute
line 600 column 63 - Warning: <img> lacks "alt" attribute
line 600 column 112 - Warning: <img> lacks "alt" attribute
line 600 column 162 - Warning: <img> lacks "alt" attribute
line 611 column 15 - Warning: <img> lacks "alt" attribute
line 630 column 22 - Warning: <img> lacks "alt" attribute
line 630 column 63 - Warning: <img> lacks "alt" attribute
line 630 column 112 - Warning: <img> lacks "alt" attribute
line 630 column 162 - Warning: <img> lacks "alt" attribute
line 641 column 15 - Warning: <img> lacks "alt" attribute
line 656 column 22 - Warning: <img> lacks "alt" attribute
line 656 column 63 - Warning: <img> lacks "alt" attribute
line 656 column 112 - Warning: <img> lacks "alt" attribute
line 656 column 162 - Warning: <img> lacks "alt" attribute
line 667 column 15 - Warning: <img> lacks "alt" attribute
line 682 column 22 - Warning: <img> lacks "alt" attribute
line 682 column 63 - Warning: <img> lacks "alt" attribute
line 682 column 112 - Warning: <img> lacks "alt" attribute
line 682 column 162 - Warning: <img> lacks "alt" attribute
line 693 column 15 - Warning: <img> lacks "alt" attribute
line 708 column 22 - Warning: <img> lacks "alt" attribute
line 708 column 63 - Warning: <img> lacks "alt" attribute
line 708 column 112 - Warning: <img> lacks "alt" attribute
line 708 column 162 - Warning: <img> lacks "alt" attribute
line 719 column 15 - Warning: <img> lacks "alt" attribute
line 734 column 22 - Warning: <img> lacks "alt" attribute
line 734 column 63 - Warning: <img> lacks "alt" attribute
line 734 column 112 - Warning: <img> lacks "alt" attribute
line 734 column 162 - Warning: <img> lacks "alt" attribute
line 745 column 15 - Warning: <img> lacks "alt" attribute
line 760 column 22 - Warning: <img> lacks "alt" attribute
line 760 column 63 - Warning: <img> lacks "alt" attribute
line 760 column 112 - Warning: <img> lacks "alt" attribute
line 760 column 162 - Warning: <img> lacks "alt" attribute
line 771 column 15 - Warning: <img> lacks "alt" attribute
line 786 column 22 - Warning: <img> lacks "alt" attribute
line 786 column 63 - Warning: <img> lacks "alt" attribute
line 786 column 112 - Warning: <img> lacks "alt" attribute
line 786 column 162 - Warning: <img> lacks "alt" attribute
line 797 column 15 - Warning: <img> lacks "alt" attribute
line 822 column 25 - Warning: <img> lacks "alt" attribute
line 827 column 267 - Warning: <img> lacks "alt" attribute
line 147 column 136 - Warning: trimming empty <font>
line 149 column 264 - Warning: trimming empty <font>
line 807 column 17 - Warning: trimming empty <tr>
line 810 column 264 - Warning: trimming empty <font>
line 812 column 136 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 203 column 27 - Warning: <nobr> is not approved by W3C
line 229 column 27 - Warning: <nobr> is not approved by W3C
line 318 column 27 - Warning: <nobr> is not approved by W3C
line 364 column 27 - Warning: <nobr> is not approved by W3C
line 390 column 27 - Warning: <nobr> is not approved by W3C
line 424 column 27 - Warning: <nobr> is not approved by W3C
line 452 column 27 - Warning: <nobr> is not approved by W3C
line 480 column 27 - Warning: <nobr> is not approved by W3C
line 511 column 27 - Warning: <nobr> is not approved by W3C
line 537 column 27 - Warning: <nobr> is not approved by W3C
line 590 column 27 - Warning: <nobr> is not approved by W3C
line 616 column 27 - Warning: <nobr> is not approved by W3C
line 646 column 27 - Warning: <nobr> is not approved by W3C
line 672 column 27 - Warning: <nobr> is not approved by W3C
line 698 column 27 - Warning: <nobr> is not approved by W3C
line 724 column 27 - Warning: <nobr> is not approved by W3C
line 750 column 27 - Warning: <nobr> is not approved by W3C
line 776 column 27 - Warning: <nobr> is not approved by W3C
line 802 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 255 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md