The Official Xanjax Blog

Ugly Fonts In Windows

April 6th, 2008 by chappo, in Xanjax Chat

Just discovered after doing the first actual test of Xanjax in Windows XP for about a year (yes that’s how long since I last used Windows for anything!) that there’s no anti-aliasing by default and various fonts/sizes on Xanjax website look terrible! Supposedly you can turn Clear-Type on (or some such feature) but that won’t make things look any better for W2K, W98 users, or anyone else without Clear-Type. Do you actually get it in XP home anyway?

Us Linux Gnome Desktop users have had font anti-aliasing since at least W98 days! I really forgot how terrible older versions of Windows look.

Please, if anyone can tell me what’s the reliable way to get halfway decent looking fonts in Windows in IE without clear-type, I would like to know. Is it necessary to choose specific fonts and sizes, avoid italics; what?

You may have noticed that Xanjax website scales to fit the window size of the browser, font size too. This looks just great in Linux, even in Internet Explorer in Linux, but not in Windows.

This is just a Windows anti-aliasing issue, nothing to do with Xanjax, I’d love to hear about a good solution.

No Comments »

Xanjax Known Issues

April 6th, 2008 by chappo, in Broken Stuff

Naturally there are some issues, especially so early in the release cycle!

If you find more, please add comments with details.

Opera is not supported yet supported as of 20080410 with addition of cancel bubble code.

Konqueror is not supported yet.

Safari in not tested at all yet and may or may not work.

Classes in IE. This one I hadn’t noticed during development. CSS classes don’t work in any version of Internet Explorer. This is actually due to a well known bug in IE with setAttribute. Ugly hack for know is to use object loads for any page needing classes. I hope we can get around this one!

Navigation Bug in IE. This is minor. If you navigate all the way back out of Xanjax, back in and all the way forward out again, then back in again, the last page will be correct but location bar reads entry page rather than the exit page.

Navigation Bug. When entering a new hash location while in Xanjax location bar stays on this hash until navigating out of Xanjax and back in again. Navigation still works. This is caused by browser behaviour and may not be fixable. It’s not that common for people to type into the address bar after having arrived at a site, so this is not considered to be all that serious.

Navigation Bug. Presently, typing a hash while in Xanjax will not work unless the hash is already known, such as in the menu or the content being viewed. This is because a dynamic algorithm is being used to create anchors. I’ll probably revert to static, or better to a combination if people think this matters. Please note that all inward links using either an ordinary *.html path or a #hash path work.

Query Strings.  Presently, query strings are not working in internal pages, but work fine from external inward links. This is due due an oversight in the hash creation algorithm and will be fixed.

No Comments »

footer