Retooling Slashdot with Web Standards 764
Joe Clark writes "Nearly a year after an interview with this correspondent highlighted a few problems with Slashdot's HTML, Daniel M. Frommelt and his posse have recoded a prototype of Slashdot that uses valid, semantic HTML and stylesheets. Frommelt projects four-figure bandwidth savings in the candidate redesign, were it adopted, not to mention better appearance in a wide range of browsers and improved accessibility. Next he needs volunteers to retool the Slashdot engine. And yes, he did it all with CmdrTaco's blessing." Slashdot has kept its HTML 3.2 design for a long time ("because it works"), but perhaps this effort will be a catalyst for change...
CTRL-R (Score:5, Funny)
On second thought, that could mean more time working. Scratch the idea.
Re:CTRL-R (Score:5, Funny)
Then again, this is slashdot, and we don't read articles.
Re:CTRL-R (Score:4, Funny)
Article (Score:5, Funny)
Many languages have two articles, which correspond to English "an" and "the". Many of those languages have multiple forms, called "allomorphs," for each article, determined by context; in English, "an" becomes "a" before a consonant and "some" before a mass or plural noun. Russian has no articles, their function having been replaced by sticking nouns before the verb (to imply "the"-itude) or after the verb (to imply "a"-ness).
Another meaning of "article" is any of the interesting pages linked to in the story at the top of a Slashdot article.pl page. In this case, Slashdot users would call this page [alistapart.com] "the article".
Re:Article (Score:3, Informative)
Re:Article (Score:3, Funny)
Hmmmm... well, normal people would call it "the article". Slashdot users would probably call it "a DoS target".
Re:RTFB (Score:3, Informative)
Re:RTFB (Score:3, Funny)
Re:RTFB (Score:3, Informative)
Also, the new design still allows the user to change the font size. Thank god for that. So many sites now use absolute pixel sizing in their stylesheets to apply their 12 pt. Times font.
Re:RTFB (Score:3, Interesting)
Lucky. On my iBook (which only goes to 1024x768) I get horizontal scrollbars unless I browse in fullscreen mode. I saw them and left the site immediately
This article is intended to be read by humans (Score:5, Insightful)
how about eliminating all of the completely wasteful, bandwidth and processor consuming, whitespace?
As you point out, XML, CSS, and ECMAScript, unlike Python, are not very sensitive to whitespace. Slashdot can mitigate whitespace's contribution to bandwidth in two ways: 1. mod_gzip (which Slashdot already uses), and 2. caching proxies that strip excess whitespace. But this article itself is intended to be read by developers, and clarity counts.
Re:F5 (Score:3, Insightful)
Whitespace isn't going to be your biggest bandwidth waster. So why not leave human readable.
actually wasting time (albeit a tiny amount, but nonetheless) parsing through it.
Why don't you measure it and compare it to other optimizations before you recommend that people spend their time changing it? "Premature optimization is the root of all evil", or something like that?
PHP and Smarty (Score:3, Insightful)
In development the filters are disabled, when it goes to production they strip white space and single line comments.
Combine that with Smarty caching and phpa and you get dynamic PHP pages that perform like static ones.
Re:F5 (Score:5, Insightful)
a) Totally guessing, but about 99.9999% of the pages served up are interpreted by "no one" other than the browser. It's more "readable" by the browser minus the whitespace.
b) Most pages, like this, is "mechanically generated" - What you see in the final results was rendered: It isn't the "source-code". As such there is absolutely no code maintenance issues.
What you're left with is the prospect that maybe one out of every million page hits is going to a Slashdot developer who's debugging that the rendered properly, though if it's XHTML transitional then a XML editor would be a great choice and would again make it irrelevant if it's clogged full of waste whitespace.
Re:F5 (Score:5, Informative)
http://www.greece.k12.ny.us/taylor/topics/doubles
http://desktoppub.about.com/cs/typespacing/a/onet
http://www.webword.com/reports/period.html [webword.com]
http://www.getitwriteonline.com/archive/011803.ht
Both the MLA and Chicago Manual of Style suggest one space after punctuation while using a compensatory font (ie, not-monospaced). Two spaces after a period is very out of style. Yeah I know - shocked the hell out of me when I learned it a couple years ago too.
Digital typography / spacing (Score:4, Informative)
In most well-designed typefaces, there is a certain amount of built-in space around punctuation glyphs, with the amounts chosen to match the other design characteristics of the characters to maximise reading ease. This gives you, amongst other things, a slightly wider space after a '.' (full stop/period) at the end of a sentence, which in turn gives a natural break while reading without being overly distracting. Note that in most typefaces, two full space characters after a full stop would give an excessively wide space, breaking the reading flow more than necessary, particularly where full justification is in use.
For the same reason, serious typography uses separate characters to represent full stops and (English) decimal place separators, and has another character for ellipses ('...'). If you used the normal full stop character singly as a decimal separator or thrice for ellipses, the spacing would be awkward.
Alas, this sort of detail is the bane of the typographer's life: they spend their days designing typefaces that are easy for you to read, without distracting artifacts, but most people will never appreciate the artistry involved, and only ever notice when they get it wrong.
Obviously, this can't apply when using a monospaced ("typewriter") typeface, because the designer doesn't have the luxury of fine-tuning the widths of characters. This partly explains why reading large blocks of text in a monospaced typeface is difficult for most people, and was also the reasoning behind using two full spaces in that context, although it's unnecessary with good proportionally spaced fonts.
If you'd like more information, you might try Microsoft's excellent Typography web site, or Donald Knuth's works on digital typography if you're really hardcore. There are excellent examples in each case of things that good typography will take into account to make for better readability, and of the distracting effects that can happen if you don't account for them. And as a bonus, once you've read Knuth, you'll know exactly how to typeset "e.g.," using TeX with perfect spacing. =:-)
*looks down* (Score:5, Funny)
Brr.
Re:*looks down* (Score:3, Funny)
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
X-Powered-By: ASP.NET
Date: Sat, 22 Nov 2003 07:09:02 GMT
Content-Type: text/html
Accept-Ranges: bytes
Last-Modified: Thu, 20 Nov 2003 20:38:43 GMT
ETag: "8036d049a6afc31:9a2"
Content-Length: 33923
Well, I never!
Re:*looks down* (Score:3, Funny)
Hell just froze over.
Brr.
Please, this isn't the proper thread to mention when you've got an erection.
Just another example of the Slashdot monopoly... (Score:5, Funny)
This isn't the first time this has happened. Remember when BBS's became popular, and Slashdot "integrated" one into their site to kill any competition? Or all the times that Slashdot has brought down "competing" sites by linking to them, thereby safeguarding their website monopoly?
It's a shame that the DoJ let them off for this....
Not complying with any HTML standard (Score:5, Informative)
That's not true [htmlhelp.com].
Re:Just another example of the Slashdot monopoly.. (Score:4, Insightful)
However, someone sufficiently motivated can rip it out and slap in something new. Sometimes people end up rewriting amazing portions of software when it's big enough. I'm not sure slashdot really does enough to warrant that kind of manhandling, it might be better to start entirely over.
But then, I've never looked into slashcode, because while slashdot is a fine site, I would never want to run it. I'll learn a lot more if I write my own code, and I don't have lofty goals for my website.
While you're at it (Score:5, Insightful)
Re:While you're at it (Score:3, Interesting)
I can confirm this. There was a case were I tried to view an 8 pages thread, and all the 8 pages came up as the same first page. Only as I changed from the threaded view to the flat view I was able to see some of the later postings. There are definitely bugs in the paging code.
Re:While you're at it (Score:3, Informative)
Re:While you're at it (Score:3, Informative)
It can be annoying, so I will agree on that argument; at least include an option to do pages beginning in a response nest.
My own method of cutting down on nesting-thread page repetititition is to set the display to 100 posts/page. (Which also cuts down on my need to click on the page numbers! Nifty!)
The one reason I can't give /. urls to friends (Score:4, Interesting)
is that the default comment view (i.e., when you don't have an account) is non-threaded, oldest first. Which is just stupid. People visiting are treated to pages of whatever the current first-post troll is these days.
Switch the default to threaded, highest scores first, and then if a visitor wants a more chaotic view, they can deliberately ask for it.
Re:The one reason I can't give /. urls to friends (Score:3, Informative)
http://developers.slashdot.org/article.pl?sid=03 /11/21/2223256
. NO. I don't think so. I think you'll send them a link. And *then*,you can add the appropriate parameter.Say:
http://developers.slashdot.org/article.pl?sid=03/1 1/21/2223256&mode=thread .
OMG. So incredibly difficult.
Re:While you're at it (Score:3, Informative)
It shows the last thread of the previous page. No idea why it does this, but that's what it's doing.
Re:While you're at it (Score:3, Interesting)
Easy: Leave the main page as it is and pipe the comments to NNTP.
Is it really just the advertisements that prevent this? Why not create alt.fan.slashdot and have the discussions a lot easier to read with your favorite newsreader?
Re:While you're at it (Score:3, Interesting)
Re:While you're at it (Score:3, Informative)
Basically when the site is redisgned with valid XHTML and CSS your WAP device will just dump the CSS file and you'll have your bare, structural (X)HTML which your WAP device will love. It's just one of the reasons why web stanards are so great.
Re:While you're at it (Score:4, Interesting)
If page 1 has: thread A with 14 subcomments, thread B with 22 subcomments, and thread C which has 17 subcomments, but...
there's only room (based on the max page length) to show A, B, and 13 of C's comments...
Page 2 will start over with the first comment of thread C. So you get to reread the first 13 of C's comments.
All hell breaks loose if thread C has more comments than can be shown in a single page...
Each page wants to start at the top of thread C again.
The problem is slash won't start page N in the middle of a comment thread. Any comment thread that was only partially displayed in the previous page is reshown in its entirety.
very annoying.
well (Score:5, Insightful)
How about a new look altogether?
I had a look at the new site, and while it does fix many problems and should certainly be used to replace the existing setup, why not go a little farther and retool the look of the site as well?
The look of slashdot has barely changed since the late 90's, and while the look certainly brings part of it's character, it's beginning to look dated. Perhaps it can be redesigned with a more effecient and cohesive interface while still retaining some of it's previous character?
Or is it just a pipe-dream...
Re:well (Score:5, Insightful)
Re:well (Score:5, Informative)
Re:well (Score:5, Insightful)
universal access (Score:5, Funny)
Re:universal access (Score:3, Interesting)
The prototype is slowing already (Score:5, Funny)
Re:The prototype is slowing already (Score:5, Funny)
Hallelujah! (Score:5, Insightful)
Now maybe I'll finally be able to change my
Re:Hallelujah! (Score:5, Interesting)
And do you do it with a reader that doesn't interface directly with IE's rendering engine rather than reading the HTML directly?
Despite running some very information-centric sites, I have yet to see a confirmed assistive technology surfing my site in the logs--yes, I know all about spoofing, which is why I ask...you'd think that some of them, given the Biblical proclamations about standards liberating the handicapped that come from ALA, would just be a HTML-slurpers that give a unique identifier to logs and simply break on IE-only sites.
So, any of you out there? Is the site unusable on JAWS or some such? I want real blind people who use it every day rather than somebody who once listened to JAWS read it in a lab or academic setting.
Re:Hallelujah! (Score:5, Informative)
Tidying posts (Score:5, Insightful)
I hope they implement ASAP.
But there is another challenge, and that's the posts people write. Anybody care about their code? For example, quoting, to do it properly, one should write: <blockquote><p>blah, blah</p></blockquote>. That's an awful lot of typing.
A page is not going to validate unless the posts are correct.
The way I have planned to do this on one of my sites, is to make sure that every time somebody clicks "Preview" or "Submit", the post is handled to Tidy [sourceforge.net] for sanity checks and conversion. By using preview, you can correct you're code, but you can never submit something that isn't well-formed.
I'm using Perl too, not Slashcode, but AxKit [axkit.org]. Nevertheless, a good Perl implementation of Tidy is still lacking. There is a HTML::Tidy [sourceforge.net] project page on Sourceforge, but it hasn't really gotten off the ground.
Does anybody else want to work on this, or do you have other ideas for cleaning up posts?
Re:Tidying posts (Score:3, Informative)
Re:Tidying posts (Score:3, Insightful)
. That's an awful lot of typing.
A page is not going to validate unless the posts are correct.
The balance problem is trivally corrected by actually parsing the HTML in the post, then inserting the proper closing tags at the end. No, the page will still not validate -- but no one is asking for slash pages+posts to validate, merely asking t
Re:Tidying posts (Score:3, Insightful)
Yes, that's true! But it is not simply the balance problem I'm addressing. People may for example use the BLOCKQUOTE element, but don't realize that it should be a P element within it. There are quite a lot of small things like that.
I do... :-)
The point is, tidy should be able to do that job easily, unless I'v
Agent sensing (Score:3, Insightful)
When the time comes, please add some code to switch to a light design when browsing with a PDA. I know right now you can select light mode, but it affects all browsers used from an account which isn't at all what I want...
Re:Agent sensing (Score:3, Informative)
Selecting based on user-agent is a Bad Thing. The preferred method to provide "light" style to a PDA is the @media rule [w3.org] in CSS, which would allow PDAs to get their style via an "@media handheld" rule in the stylesheet, or from a simple link like this:
The author of the ALA article used the same technique to provide "printer-friendly" layout via CSS, and it can work for a variety of other media as well.
Wow, slashdot is ugly... (Score:5, Funny)
About the author... (Score:5, Funny)
I like the guy already.
Teeny Bug (Score:5, Interesting)
Right now slashdot looks normal at any text zoom setting, but the version proposed in the article hides parts of words when I turn up my zoom to 200%. I don't often read with text that large, but I've done it before, and I'm sure there's users out there who do it regularily.
Re:Teeny Bug (Score:5, Informative)
I'm not really up on my css, but I would guess a solution would be to have the centre column floating next to the left column, or to define the distance from the left hand side in em units instead of pixels.
Re:Teeny Bug (Score:5, Insightful)
I'm not really up on my css, but I would guess a solution would be to have the centre column floating next to the left column, or to define the distance from the left hand side in em units instead of pixels.
Or the CSS property overflow [w3.org], which could be used in a variety of ways to make the text visible when it gets too large for the column.
The problem is the CVS (Score:5, Insightful)
It would be GREAT to see them finally, 3 or 4 years later, dump the old theme and streamline it with CSS and stuff. Is it going to happen anytime soon. Probably not.....
What about the graphic design (Score:4, Insightful)
Now that you've made slashdot standards compliant, why not make it look good? CSS has powerful leading, word spacing and font tools (all of them with relative measurements to look good across most browsers). If a browser doesn't like a text attribute, it won't display it, so you won't have to worry about the same unpredictability as you would with layers and div boxes. The one thing that sucks the most on slashdot is its typesetting. Type is the one thing web designers forget about, but doing it right drastically improves the appearance and readability of a site.
Re: Changing the look (Score:4, Insightful)
Things do look a bit dated, but maybe that is a good thing. The popularity of
Anyone that matters knows the site already. The content is the reason they return, not the pretty icons. Getting more impact through a more compelling rendering might matter to a few folks, but will the expense be worth it?
Maybe this is the wrong comparison... Take an established publication like the Times or WSJ. Do they make big changes often? No. The formula works and is a big part of their identity.
I think they keep things the way they are because they know change works against the needs of their readers; namely, access to relevant content easily.
Unless I am missing something, major changes to
Re: Changing the look (Score:3, Insightful)
It's been done before (unofficially) (Score:5, Informative)
You can view all the available CSS designs here [mezzoblue.com]. Same content, different stylesheet. Just shows off all the wonderful things that's possible with CSS standards-based page creation.
"HTML is dead." - Friedrich Nietzsche
What does it pay? (Score:3, Interesting)
Editor Queue enhancements? (Score:5, Insightful)
Not a flame.
If you're thinking of retooling the slash engine itself, I hope you consider some of the oft-complained areas for the most improvement. Things get mixed up in any random-access submission "queue" engine, but slash seems to suffer from these things often. Even editors have grumbled about not seeing other editors' status on various stories.
Re:Editor Queue enhancements? (Score:3, Insightful)
> allow meta-moderation of "overrated" and "underrated"
*rrated is abused far too often in my opinion.
Here [slashdot.org]'s an explanation from another
Also, it should not be possible to moderate *rrated on a post with no previous moderation. This would prevent troll moderators from immediately
Slashdot CSS Suggestions (Score:5, Insightful)
Good article, just a couple of suggestions...
In general, it's usually better to avoid giving layout-suggestive names to your div tags. In the example, the author calls the Login/Sections/Help div leftcolumn. It would probably be better to name it something that is more suggestive of it's content rather than it's location - this way, if in the future a new skin was added that moved the content to the right-side, or even bottom of the page, the div name wouldn't contradict it's location.
Another suggestion would be to disable all images in the print.css file. The author already went ahead and disabled the advertisement, the left and right columns, but he left those pesky story icons. I know that when I print an article, usually all I care about is the text. It's a simple way to make a page a little more printer friendly.
My last suggestion would be to move the content div tag, up near the top of the page. This way, as your browser downloads the information from the server, it will download the story information (important) before downloading the left/righthand content panes (unimportant). If someone stops loading their browser before the page download has been completed, at least the browser can attempt to render the story data. And with css, the layout will be preserved.
Re:Slashdot CSS Suggestions (Score:5, Insightful)
#advertisement { display: none; }
Comment removed (Score:5, Insightful)
Re:What about PNGs? (Score:3, Informative)
seconded! (Score:4, Informative)
Actually, you'll have to go back to stuff like Internet Explorer 1.5 and the like to find a browser that doesn't support the basics.
And for the record, PNGs are always smaller, except in a few very special cases which doesn't matter because the absolute size difference is next to nothing in those.
And yes, the PNG-writer in Adobe products is fucking broken last time I checked, and to top it off, many "webdesigners" doesn't understand that PNG supports truecolor, so they'll happily compare their paletted GIF and their GIF saved RGBA and explain the size difference not with "I'm an idiot" but "PNG sucks".
And as for animation.. that's a feature! Personally, I have animated GIFs disabled -- always -- but if you really want to animate pictures you'll use MNG which is animations made out of PNG-images
Re:What about PNGs? (Score:3, Informative)
That's typically attributed to the number of colors present in the image, and the addition of the alpha channel. If you have a PNG image with 256 colors compared to the same GIF image, the PNG will be smaller.
The very fact that you can have 16 million colors + alpha in a PNG is well worth the sacrifice you make in file size. The difference is typically on the order of 4-5 KB anyways.
Re:What about PNGs? (Score:3, Informative)
Canada (expires 7 July 2004)
the United Kingdom, France, Germany and Italy (expires 18 June 2004)
Japan (expires 20 June 2004)
So you're not free to use the LZW routines if you live in one of those countries. Please stop spreading misinformation.
Four simple feature requests (Score:4, Interesting)
1. When you click on your username, you see all of your comments, and next to your comments, you see the number of replies to your comments.
It would be really nice if this number would be clickable, so you could immediately read the replies to your comments. (It's quite complicated to get to the replies now, especially when you've put a high comment threshold in place)
2. Can story submissions be placed (more logically & more conveniently) on people's slashdot-homepages, instead of on the page that you get when you click on "submit story"?
3. It would be nice if you could see your own story submissions (not just the subject, but also the body & other details) when you click on them. Just to see them back.
4. Could the default comment-submission mode be changed to "plain old text" instead of "html-formatted"?
It is confusing that you have to write your own html in a text area on slashdot to get something as basic as newlines, where there is no other site that I can think of - not even a geeky one - that requires you to manually enter the BRs.
It's just not useful, not intuitive and not nice this way.
Sweet creepin' jesus! (Score:4, Funny)
I do ~90-100 gigs per MONTH and freak out at that.
I will never bitch about my bandwidth use again.
I will never bitch about my bandwidth use again.
I will never bitch about my bandwidth use again.
I will never bitch about my bandwidth use again.
I will never bitch about my bandwidth use again.
I will never bitch about my bandwidth use again.
Search Function (Score:4, Interesting)
ALA is ok but CSS is broken (Score:5, Interesting)
A reply to your complaints... (Score:4, Informative)
Following your identical post on ALA the following reply from Marshall Roch [exclupen.com]
Everything mentioned in these comments are fixable, including Andrew's "CSS tables."
Have a look at http://projects.exclupen.com/slashdot/ [exclupen.com] (does not work well in IE, but that is fixable if there is interest)
I'm also willing to help get /. up to speed. Where's the best place for interested parties to discuss this further? Please post replies on the ALA forum.
Re:ALA is ok but CSS is broken (Score:4, Insightful)
I don't know if this si a browser issue, or a problem with the CSS spec, but text overflow is a serious issue, one which breaks nearly every CSS page with complex layout in existance.
Yeah, you'd think somebody would come up with an " overflow [w3.org]" property and put it in the CSS spec to fix that, wouldn't you?
Snarky comments aside, most problems with layouts being broken by text magnification can be fixed with careful design. Yeah, it takes some work, but generally no more than what you'd put in nesting 800 tables...
If you understood.... (Score:4, Informative)
Re:ALA is ok but CSS is broken (Score:3, Insightful)
In most cases, one can replace tables with division tags, which work much better in general. The only caveat is that IE tends to break CSS based DIV tags if you use the wrong type of positioning. To be specific, if you use position: fixed; IE will NOT position this correctly, and really has trouble with multiple elements being f
Did anyone else notice? (Score:3, Informative)
some shortcomings (Score:3, Interesting)
XHTML or HTML 4.,01 Strict? (Score:5, Informative)
If XHTML, there are some things to consider:
It's important to note that using XHTML 1.1 requires you to send your documents as XML [w3.org]. This means the document should have an XML declaration above the doctype, and needs to be sent with an XML mime-type [w3.org], ideally application/xhtml+xml. This has a significant drawback; IE can't see it [w3.org].
A fairly well established workaround is to use mod_rewrite and munge the mime-type of a document [w3.org] based on what a user agent sends in its Accept header (To date, Mozilla is the only browser to include application/xhtml+xml in its Accept header). However, some would argue that this too has drawbacks. Since only Mozilla understands application/xhtml+xml, your documents will be sent as text/html, and XHTML does not validate as HTML.
The arguments around this issue have been summarized in the widely linked "Sending XHTML as text/html Considered Harmful [hixie.ch]"
Konqueror, Opera (Score:3, Informative)
Also, I seem to remember reading application/xhtml+xml pages just fine in Opera.
I used to serve all pages on my site as pure XHTML 1.1, with the correct MIME type and everything, until I realized that I'm one of three people I know who uses a non-IE browser.
You can't really hate Microsoft until you've gotten serious about standards. Then
Works much better... (Score:3, Informative)
The original version had lots of italics and the text flow wasn't great.
The updated version looked much better (except that the header of the first story was separated from the body by the section nav and poll and stuff)
Handspring Treo 600, blazer browser.
Now there's no reason to fix http://slashdot.org/palm [slashdot.org] (which doesn't seem to work) to be as good as http://www.wired.com/news_drop/palm [wired.com] looks on a handheld.
Maybe even make it automatic.
Sweet. i've been working on the same thing (Score:5, Informative)
For the last several months I've been working on the same project from a slightly different perspective. We have a working Slash-based site, currently in live beta, at http://www.news4neighbors.net [news4neighbors.net].
The site doesn't validate, but it's all structural XHTML with CSS for layout and style. This is much rougher than the beautiful markup presented here, but the difference is that nearly our entire site is running this template system. My work is based on the Openflows strict theme, released early this year at http://strict.openflows.org [openflows.org]. But not much of that theme is left, as their project and mine had very different goals. I've changed all of the 120-something templates, and much of the code that sends them data.
The site needs a lot of work, no doubt. But we're developing it rapidly, and have made much progress.
The biggest challenge is that Slash itself doesn't separate content from presentation from business logic. To change one set of tags you may have to rewrite a template, change a database variable, write some Perl, or a combination. This isn't a knock on Slash -- it's very powerful and I enjoy using it -- it's just that the presentation layer hasn't been their focus.
The end-goal for this project, Slash-wise, is to have a fully XHTML/CSS compliant theme that people can easily use on their sites.
If you want more information about it, send me email at randall -at- sonofhans.net
[ FYI, I also posted this in the ALA discussion ].
Handheld-friendly (Score:3, Insightful)
Actually, I like /. like it is (Score:3, Interesting)
There are bound to be issues with the multitude of browsers available, each rendering even CSS 1.0 in their own inimitable style (pun intended), because what Mac IE5 considers as a box, and what Windows IE5 consider as decent box or text attribute sometimes tend to be entirely different things.
If it works don't break it, I think. Rather fix the search engine.
YES (Score:3, Informative)
1) looks better
2) allows people to easily make custom
3) slashdot can have multiple css to choose from, especially for those of us blinded by games.slashdot.org. Also in Firebird users can switch between the different stylesheets with east
4) people can easily write XSLT stuffs to take slashdot and mix it up.
5) Maybe we can make an RSS that's a little bit better and more customizeable. Doesn't exactly have to do with it, but it's related somewhat.
Yes
for the love of pete... (Score:3, Interesting)
HTML is not a semantic web technology! here's the W3C Semantic Web page [w3.org]. Notice how (X)HTML isn't mentioned?
i don't know who to blame for the propagation of this usage of the word 'semantic,' but i think it might be Jeffrey Zeldman [zeldman.com]. i like the dude, but this has to stop...
Re:Not ANOTHER non-standard page... (Score:5, Insightful)
that's almost as standard as you can get.
Re:Not ANOTHER non-standard page... (Score:3, Informative)
For example, I can create a validated XHTML page with one paragraph inside it, and it will look different in Mozilla than what it does in MSIE. Even though Mozilla and MSIE support the standards used to render this one paragraph.
When I create a site, I use font sizes like xx-small, x-small, small, medium, large, x-large, xx-large. (Browser
I'm just happy it rendered properly in Firebird.. (Score:5, Interesting)
The bit that impresses me more is that the page rendered properly with Mozilla Firebird 0.7 on Win32. The real slashdot doesn't render particularly well at all with Firebird for me.
Re:Explains some stuff (Score:5, Informative)
It scans through the page and tries to match the character frequency against average character frequencies for various languages. If you're seeing Slashdot as Big5, then that means IE thought that the character frequency matched Big5 most closely.
Re:Explains some stuff (Score:5, Funny)
A sad testament to how bad Slashdot grammar is... Next time someone asks you how bad the writing is on Slashdot, you can tell them "It's so bad my browser thinks it's Chinese!"
Re:Sounds good (Score:4, Informative)
I'm not sure if this is settable in IE, but Mozilla, Safari, etc etc have these settings.
Personally, I use serif, and then my serif font is Georgia. It looks great to me. But feel free to use sans-serif and Comic Sans if it suits you.
Re:XML? (Score:3, Informative)
Re:XML?-Bag-pipes. (Score:3, Informative)
Simple, XML covers everything! But the idea i like is that if i want i could define my own XSL file for slashdot. Say take the XML code from the web site and format it on my machine so i can read it how i want. Also, this is great for little side bars that just want to summe
Re:XML?-Bag-pipes. (Score:3)
This is something I *really* want to know more about. I've searched for info on client side XSLT transforms, and haven't really found a lot. I've seen something on mozilla.org, and a tutorial for IE.
Is it possible to just send an XML doc to the client, along with a
Re:um... (Score:3, Interesting)
Certainly, caching CSS files locally would save a little in this scenario, but not nearly as much as they say.
Re:Blech... (Score:5, Insightful)
Er, 'fontface'? WTF is a 'fontface'?
As for CSS resizing automagically, resize in relation to what, pray tell? A box with width: 30%; resizes in relation to the viewport, a box with width: 15em; resizes in relation to font size, as of CSS 2.1 a box with float: left or float: right and no width resizes in relation to content (most browsers--including IE/Win--do this anyway) and table-layout will get you table-style layout with whatever tags you like. MS just didn't feel the need to support it in IE 5/Win or IE/Mac so people don't use it much. That's Microsoft's fault, not the W3C's
Ian Hickson [hixie.ch] edited the CSS2.1 spec, and he's been 'solving real world web design problems' since at least 1998 when I worked with him at the Web Stanards Project [webstandards.org]. Hakon Wium Lie [w3.org] edited CSS 1, 2 and 2.1 and has been working on Opera [opera.com] since 1999, earned an MS in Visual Studies from MIT and wrote his thesis on electronic display of newspapers. TantekCelik [tantek.com] is responsible for the widely-lauded Tasman rendering engine used in IE 5.x/Mac. These people do use this stuff in the real world, and if you don't like the directions they're taking your'e free to join the www-style [w3.org] discussion list and let them know.
One line of CSS is 'a bunch of work'? I suppose you find tying your own shoes a pretty onerous task as well?
Let me get this straight: you're hacked because the site doesn't use your settings for font size and face, but setting your browser to override the site's settings with your choices is 'undesirable'? Huh?
Re:Current /. is rubbish on a phone (Score:3, Insightful)