Mark Christian's dashboard

I did check that first thing, and FF font is set to Arial. With Google Sites, and pretty much every wiki I've used in the past, there is a default font that is independent of the browser's default font. – Hugh, 6 days ago

Jeez, so sorry to upset you, Guy.
I might have interpreted the original question differently (why is font defaulting to Lucida?) and I don't know for sure if I understand your answer, isn't it waaay out of context? I reacted to some of your statements which in my belief aren't true, to me 'automatically' and 'specific' are contradictory by nature, you do have a conveniently way of quoting urselves and making it hard for me to understand your logic. Let's be friends, OK?

This discussion is really about the WYSIWYG editor and its peculiar behavior, in this case not expanding the chosen formatting to inserted links or table rows.
And I have to disappoint you here, I don't know how to solve this, I barely use the editor, dive directly into source mode, whatever our dear friend, the Vu Man, may think of that.
Lately, on another platform, I have been using other editors which have a built-in way of applying pre-defined div & span to page-elements. PBwiki 3.0?

However, maybe the person asking the original question is better off applying some general CSS styling in his/her Sidebar, telling the wiki to display everything in Arial? Or do it page level, by putting everything into a div with styling (in source mode and then don't touch those formatting buttons no more ..)?

Segoe is the default user interface font for Windows Vista (http://en.wikipedia.org/wiki/Segoe_UI). Lucida Grande is the default user interface font for Mac OS X (http://en.wikipedia.org/wiki/Lucida_Grande). – Mark Christian, 7 days ago

Tim,
Make sure you get "fresh" code straight from del.icio.us when you try Vu Nguyen's suggestion above. My mistake was I was trying to use the code after it got mangled. Once I got original code and tried it again, it worked.

I'm still not having any luck.

This did not work for me? – Tim, 8 days ago

That does not work. That's what I tried. – Tim, 8 days ago

I have a similar problem, however my feed will not work with blogger, however it will work with google reader

I tried adding jiglu to http://macewan.pbwiki.com , but it doesn't seem to know how to index PBwiki pages very well. – Guy Fawkes, 15 days ago

i bumped into jiglu.com - they have a great tags-that-think tool
it uses a oneliner javascript
is it possible to validate a library of validated javascripts like jiglu's ?
best regards, Ron

I would recommend that the red and green colors not be used and perhaps the use of a bold style could bring attention to these areas. Also, the gray shading is hard to read and perhaps could be replaced with a border around the revised text area. Thanks for considering this.

Hi there;
I've taken a look at our notifications using Sim Daltonism (http://michelf.com/projects/sim-dalto...), a colour blindness simulator. For all but one type of monochromacy, things still seem to be quite visible.

How would you recommend we change the notifications to be clearer?

URLs get encoded using the standard PHP library (the urlencode function), which does it all according to common conventions. The vast majority of servers work just fine with this encoding -- in fact, this is the first instance of it not working that I've personally seen. For historical reasons, spaces get turned into pluses, which works perfectly most of the time.

That being said, there are alternative ways for us to encode URLs that might be better. I'm going to look into this and will post here if things change. In the meantime, Guy's recommendation to use TinyURL or a similar service is an excellent one.