Jacob Santos

Two fascinating problems came up. One with Unicode and the other with Apache. Completely mind boggling and the solution is equally frustrating. If I had the choice, in my magic circle, I would rather be stabbed countless times.

Unicode’s a bitch

Or more accurately, placing Unicode in an ASCII file is a pain. I remember vaguely having a similar problem many many years ago. I must have blocked that memory out, because of the pain. I think the solution (and I’m just making this up) was to completely start over.

I found the solution of changing the ‘charset’ in the HTML meta tag does often solve many of the problems. Saving all of the files either Unicode or ASCII will also solve the problem. That can bring up another problem.

The Unicode BOM is another bitch. I know you should have it, so that file editors and readers can tell what the file is, however WTF does it cause the characters to show up as Unicode? The Unicode BOM should just like a newline or space character. It exists, but it shouldn’t ever display.

Interesting. Very Interesting. However, next time I’ll be ready and Unicode won’t stand a chance.

It’s Magic

What documentation says that something will happen and it doesn’t happen, what does that say? That I suck or does the application suck? Now, I know Apache doesn’t suck because it has been used for years and developed and tested. I think a few “Gotchas” found their way into conf -> .htaccess file handling. Where it hates you.

I’ve come across a few solutions and mechanics that seem almost like magic. Some things, you just have to do trial and error (which I hate profusely).

Possibly Related Posts:

• Game Engine Development and Open Source
• Plans for Base CMS
• Project Plans
• Calibre Improvements Part 2
• Usability Testing Software Development