Re:Readability-inspired Wikipedia Beautifier for Chrome
by acabal on Tuesday March 22, 2011 @11:09PM
(#2357781)
On a side note I'm really happy that they included screenshots and a description in the repo. There are so many github links that go straight to source code and have nothing in the wiki, as if I have the time to read, download, compile, and execute code just to see what it looks like/does. Whenever I reach a repo like that I usually end up just closing the tab.
Re:Readability-inspired Wikipedia Beautifier for Chrome
by kmfrk on Tuesday March 22, 2011 @07:57PM
(#2357164)
It uses justification and hyphenation, which is a deal-breaker for me (and presumably people with dyslexia, too). But I guess that's why it's on GitHub. :)
Re:Readability-inspired Wikipedia Beautifier for Chrome
by unwind on Wednesday March 23, 2011 @07:19AM
(#2358892)
I think it would be interesting if you were to expand a bit on this, it's not obvious to me why either justification or hyphenation makes it harder for you.
Making more people aware of such "side effects" of visual design might make help designs improve. I'm thinking a bit about the "awareness" of color blindness as being related, here.
Re:Readability-inspired Wikipedia Beautifier for Chrome
by Groxx on Wednesday March 23, 2011 @01:15PM
(#2360283)
My reasoning is as follows:
Ragged-edges make lines easier to distinguish. You don't lose your vertical location as easily, and it aids in remembering the physical location of words because every paragraph looks different. I seem to have very good location memory with what I read, though, so I may be abnormal in that part.
Varying space width means variation in reading words. Less variation is less cognitive cost.
Hyphenation means breaking a word in half, so you have to hold an incomplete word in your memory until you resume the next line. Useful to prevent huge gaps in paragraphs, but more = higher cognitive cost.
In summary: they're bad for my speed-reading. Very bad.
Don't have Git installed, so I can't delete the hyphenator.js file, but there ya go :) Delete it when you download it, and load it as an unpacked extension.
Re:Readability-inspired Wikipedia Beautifier for Chrome
by cookiecaper on Tuesday March 22, 2011 @11:14PM
(#2357788)
Interesting. I took a different approach: http://www.deserettechnology.com/journal/wm-read-bookmarklet... . As a frequent reader of articles on Wikimedia, I get really annoyed when there is a big chunk of wasted screen space while I attempt to read. It becomes distracting pretty quickly in long articles.
Re:Readability-inspired Wikipedia Beautifier for Chrome
by bdhe on Tuesday March 22, 2011 @08:02PM
(#2357182)
A good rule of thumb is to use sans-serif when possible for lots of text. Displays that are lower resolution will render serifs poorly, or just subtly bad enough to make reading difficult.
You could give the user to switch between serif and sans-serif. That would make the extension even better.
Re:Readability-inspired Wikipedia Beautifier for Chrome
by awj on Tuesday March 22, 2011 @08:36PM
(#2357306)
What are your thoughts on an option/setting for partial fade on the navigation elements? I like the general thrust of the idea, but removing them entirely puts navigating wikipedia a little too close to mystery meat.
Not as nice as the extension linked but much better than default wikipedia.
Hides navigation panel on the left when not hovering and introduces max-width making long texts readable. A border added to make the change in width more natural. Change font to whatever you want, i apparently found verdana to be easy on the eyes last time i edited this but with the new font renderer in firefox 4 i think there are better choices today.
Re:Readability-inspired Wikipedia Beautifier for Chrome
by idonthack on Tuesday March 22, 2011 @10:32PM
(#2357668)
They've gone farther than that. Take a look at the screenshots. There's an extra 300px of horizontal margin (150px on each side), after accounting for the space taken up by the hidden sidebar.
Re:Readability-inspired Wikipedia Beautifier for Chrome
by wheels on Tuesday March 22, 2011 @11:29PM
(#2357830)
There's a reason text is usually put into columns of a limited width when being laid out – it's much easier for the eyes to follow. (You'll see this nearly universally in print.) In fact, the current columns there are still way too wide by conventional standards, but Wikipedia's content isn't structured in such a way as to make even narrower columns tenable.
The Readability plugin, for example, uses a larger font and a 700px wide div for the text.
Re:Readability-inspired Wikipedia Beautifier for Chrome
by carussell on Friday March 25, 2011 @11:59AM
(#2369027)
++
Here's my PSA: if you're reading Wikipedia from a fullscreen or maximized window on what is typical for a widescreen display by today's standards (desktop or notebook, even), you're doing yourself a disservice for this very reason.
Making more people aware of such "side effects" of visual design might make help designs improve. I'm thinking a bit about the "awareness" of color blindness as being related, here.
Ragged-edges make lines easier to distinguish. You don't lose your vertical location as easily, and it aids in remembering the physical location of words because every paragraph looks different. I seem to have very good location memory with what I read, though, so I may be abnormal in that part.
Varying space width means variation in reading words. Less variation is less cognitive cost.
Hyphenation means breaking a word in half, so you have to hold an incomplete word in your memory until you resume the next line. Useful to prevent huge gaps in paragraphs, but more = higher cognitive cost.
In summary: they're bad for my speed-reading. Very bad.
Don't have Git installed, so I can't delete the hyphenator.js file, but there ya go :) Delete it when you download it, and load it as an unpacked extension.
news.yc reddit.com wikipedia.org reader.google.com
As well as readability available for most blogs.
I wonder if this is a trend or a temporary thing?
Also, does anyone have a Firefox port of this?
For Reddit, I've only added Reddit Reveal: Chrome: https://chrome.google.com/webstore/detail/ccjhmanjcinnojaidg... Firefox: https://addons.mozilla.org/en-US/firefox/addon/reddit-reveal... Userscript: http://userscripts.org/scripts/show/66698
[0] https://chrome.google.com/webstore/detail/jbhkdhkngalchoobjf...
You could give the user to switch between serif and sans-serif. That would make the extension even better.
Almost everything I've read on the issue advises the contrary, with an acknowledgment of the caveat for "low resolution" displays.
What qualifies as a "low resolution" display? Anything worse than the iPhone 4?
I wouldn't be opposed to merging in a setting if someone else wants to create it. (Same goes for justification / hyphenation and serif / sans-serif.)
Ideally, both options should be available.
Edit: Added a note above the large screenshot to reinforce that (though it was in the bullet points as well)
Hides navigation panel on the left when not hovering and introduces max-width making long texts readable. A border added to make the change in width more natural. Change font to whatever you want, i apparently found verdana to be easy on the eyes last time i edited this but with the new font renderer in firefox 4 i think there are better choices today.
The Readability plugin, for example, uses a larger font and a 700px wide div for the text.
Here's my PSA: if you're reading Wikipedia from a fullscreen or maximized window on what is typical for a widescreen display by today's standards (desktop or notebook, even), you're doing yourself a disservice for this very reason.