[simoncion]

I've seen that very same character sequence whenever a Slashcode site is asked to handle Unicode out of the ASCII range. If I had to bet, I'd say that textwrangler fucked up your document somehow, whether through poor design or improper operation. It's strange that you'd think that someone from Apache or Mozilla would:

a) Be randomly reading your online resume.

b) Think that the mojibake contained within was the fault of some software that they maintained.

Additionally, I've had occasion to work with many, many people. I've found that -regardless of brilliance and competency- folks with bad attitudes almost always make bad coworkers. :)

Anyway. I hope you come to understand why your declarations about your side projects tend to mystify people, and why your strongly held stances tend to not gain traction with others. All the best, man.

[MichaelCrawford]

Sorry I should have been more clear, I regard the mojibake in Ya Kazakh as a bug either in Apache or the web browsers.

[simoncion]

People believe all sorts of things that are incorrect.

Carefully inspect -in a good text editor- the files that you have asked your web server to serve. I suspect that you will discover that what is being delivered to the browser is exactly what is in the files on disk. :)

Or, view source on your personal page. (Notice that the page is served up as UTF-8, so that what is served up will be what was on disk.) Here is a snippet of what's served up, verbatim:

  <p>Español Mexicano, Español Castellano: "MEE-gə-LEET-oh".</p>

  <p>Por Favor?  Español Americano Centrale?  Español Americano del Sur? "mə-LEET-oh".
  "G" Silencio!</p>

  <p>Я name is Міша.  Я казах!</p>