The virtues of Elinks

I had writ­ten a post prais­ing Elinks’ capa­bil­i­ties, fea­tur­ing not only HTTPS and FTP sup­port, but also tabbed brows­ing and more-than-respectable ren­der­ing of table-based pages — heck, it even works well with Gmail, albeit in plain HTML mode. But then I acci­den­tally hit the wrong arrow key. And it ate my post. So now I feel less like say­ing nice things about it than before.

Nev­er­the­less, impres­sive con­sid­er­ing the lim­i­ta­tions of the medium. I used it to down­load Breezy from iiNet’s FTP (because ISP.net.au still doesn’t have the ISOs), and aver­aged about 750KB/s — which is about a third again of what I was get­ting from ISP.net.au, so I think I’ll change the sources.list to that. It’s a shame Telstra’s files.bigpond.com is so useless/HTTP-only/slow to respond to new releases, because I’d love — and I’m sure they’d save some bandwidth/peering expen­di­ture — to be able to get quota-free down­loads of this stuff. I prob­a­bly could have got Breezy from there, albeit via HTTP, albeit in a few days time when­ever they get stuff up there (haven’t checked, might be there already, but gen­er­ally they’re pretty slug­gish), but it’s just so much eas­ier this way.

Any­way, I’ve burnt it to CD now (no, Elinks doesn’t do that too) and will hope­fully be up and run­ning again soon.

Posted from Elinks

# by Josh on October 15th, 2005 Tags: , ,
| 2 Comments »

To do: Learn JavaScript properly

I read an arti­cle today on using JavaScript for image pre­view­ing with­out any extra markup, and was, need­less to say, suit­ably impressed. And slightly scared that if I were locked in a room with a com­puter and no access to the Inter­net, I couldn’t pos­si­bly write some­thing like that. I can hack bits of JavaScript together and come out with some­thing that works (heaven help any­one who has to com­pre­hend it or, worse still, sub­se­quently extend it), but it prob­a­bly isn’t Doing Things Prop­erly — ironic, because Doing Things Prop­erly is what the whole CSS/(X)HTML web stan­dards groupies thing is about. I’m vaguely ashamed that I can be pas­sion­ate about pre­sen­ta­tion and con­tent but com­pletely fail to “get” the behav­iour layer of things.

As AJAX becomes more preva­lent, there’s less and less excuse (or scope, whilst remain­ing in the indus­try!) for fail­ing to com­pre­hend these things. And that scares me a lit­tle, whilst being incred­i­bly exciting.

# by Josh on September 25th, 2005 Tags: , ,
| No Comments »

WordPress comments and numeric entity codes

I received an email from Matt Thommes (matthom) today, regard­ing his com­ments on a post not show­ing up as he’d com­mented a few days back. I thought that was odd, because I don’t think I’ve ever mod­er­ated one of his com­ments — they’re per­pet­u­ally rel­e­vant and on topic, or just said in good fun with taste –, and peo­ple who have posted here pre­vi­ously should be auto­mat­i­cally authen­ti­cated and allowed to post.

His prob­lem arose, he says, when try­ing to include cer­tain char­ac­ter enti­ties, or when post­ing twice on the same topic. I think I’ve mis­proved the twice-on-same-comment thing, but the entity con­cern is valid — when using numeric entity codes. (Those are the ones that take the form &#xxxx; where xxxx is a number)

There’s not much doc­u­men­ta­tion on this, but it would appear it’s an inher­ent Word­Press anti-spam pro­ce­dure, lest spam­mers encode their entire mes­sage in this way (that would have neg­li­gi­ble SEO ben­e­fit, but care­fully crafted mes­sages can entice users, and the ease of dis­tri­b­u­tion means that the chance of some­one click­ing through makes it worth­while, for them) and thus avoid detection.

In fact, the only near-official word I could find on the mat­ter was this com­ment on Matt Mullenweg’s (WP lead devel­oper) weblog, in which he states:

I do block com­ments with numeric enti­ties lower than a cer­tain number.

Whether or not this holds true for the Word­Press plat­form as a whole, I can’t say con­clu­sively — though it seems that’s the symp­tom, here.

In Matthom’s case, the con­cern was mark­ing up an HTML tag for dis­play in a com­ment — using entity codes &#60; (<) and &#62; (>).

I usu­ally use &lt; and &gt; for this pur­pose, so I hadn’t noticed the prob­lem until now. That works fine, but I think Word­Press delet­ing this out­right is a lit­tle extreme… Not entirely sure what the prob­lem is here.

# by Josh on September 15th, 2005 Tags: , ,
| 3 Comments »

Abbreviated Human

Abbre­vi­ated Human (PDF, 157.3KB) was sub­mit­ted today. The PDF uses Type 1 fonts, and is hence best viewed on paper, but Acro­bat Reader does a fairly good job of ren­der­ing it nicely on screen. My rec­om­men­da­tion to the reader is to click “View” then “Page Lay­out” then select “Con­tin­u­ous — Fac­ing” in Acro­bat Reader, if your screen is suf­fi­ciently wide.

Fur­ther, if you want to print it, the best way to do this is as a double-sided doc­u­ment, as the page mar­gins alter­nate slightly to acco­mo­date for this.

The work is licensed under the Cre­ative Com­mons Attribution-NoDerivs License. Whilst the license per­mits repro­duc­tion for non-commerical pur­poses, I would per­son­ally pre­fer this did not occur exten­sively. A plain HTML ver­sion may be forth­com­ing at some point in the future.

Com­ments on this post are dis­abled for a rea­son — attempts to com­ment else­where will be deleted. I’m pub­lish­ing this work, not seek­ing feed­back. That stage has passed.

I’m using the Inter­net here as a uni­di­rec­tional medium because this work was never crafted as hyper­text, never meant to be part of an inter-related web of data rela­tion­ships, and has been trans­posed into this form inci­den­tally. I’m shar­ing this work, but not wish­ing for extrap­o­la­tion. Read what you will from it alone. I hope it is pow­er­ful and lucid enough to be appre­ci­ated as a piece of art, but I don’t wish to receive feed­back on it, be that crit­i­cism or praise. The work’s pur­pose was never that, and I hope it achieves some­thing greater than mere acknowl­edge­ment or a num­ber on a sheet of paper in a few months time.

# by Josh on August 24th, 2005 Tags: ,
| N/A

Web design in schools

Still… teach­ing… WYSIWYG design prin­ci­ples! My brother is on another com­puter here design­ing some web­page using a word proces­sor in HTML mode, and I’m furtively glanc­ing, wait­ing for the crush­ing moment when he dis­cov­ers that his pretty fonts aren’t going to dis­play like that in a real browser.

Acces­si­bil­ity issues aside, peo­ple don’t seem to under­stand that typog­ra­phy doesn’t work like print.

I’d like to go and rant to the teacher who set the project — not because they use redun­dant and dep­re­cated design prac­tices, but sim­ply in response to their role in per­pet­u­at­ing these. Edu­ca­tors have a greater bur­den of respon­si­bil­ity here, being a cat­a­lyst for the prac­tices of tomor­row. Admit­tedly, edu­ca­tion is not the only cat­a­lyst (I think most peo­ple my age who under­stand the notion of the seman­tic web can attest to this!), but that should not dimin­ish its poten­tial role in this.

I argue that, in their role as edu­ca­tors, they have failed — their influ­ence is a wholly neg­a­tive one in this aspect for sev­eral reasons.

Web design in this out­moded form, regard­less as to the WYSIWYG appli­ca­tion used to enact this, is not effec­tive in devel­op­ing an individual’s design skills.

Note that I don’t speak of web design gen­er­ally — I think, done prop­erly, it pro­vides an excel­lent ground­ing in design in a more flex­i­ble frame of mind (think­ing in terms of fluid lay­outs, for exam­ple, as opposed to sta­tic print lay­outs). My crit­i­cism is applied only to the pri­mary use of appli­ca­tions such as Front­page or Dreamweaver as sole design tools, and more so to word pro­cess­ing and DTP soft­ware that per­form a sec­ondary func­tion in being able to export HTML. Notably, use of graphic design tools is exempt from such a crit­i­cism (Pho­to­shop, Illus­tra­tor, Fire­works… and to a lesser extent Flash — lesser because it is not designed for the pri­mary pro­duc­tion of graph­i­cal ele­ments, rather for the imple­men­ta­tion of these in an inter­ac­tive and engag­ing framework) — these have value in the devel­op­ment of design skills, even if these skills are not directly applic­a­ble in an elec­tronic context.

The notion of markup is for­eign, even whilst the user recog­nises the pur­pose of an appli­ca­tion as being to cre­ate doc­u­ments in a markup lan­guage.

Clearly, such edu­ca­tion ignores the core tenet of the tech­nol­ogy on which it is based. Given the gen­eral pedan­ti­cism preva­lent in computing-related courses (I do not com­ment on the depth of edu­ca­tion, only the nature of that which is given), one would imag­ine that the fun­da­men­tal ele­ments, par­tic­u­larly in a “sim­ple”, uncom­piled lan­guage, would be addressed. Appar­ently not — per­haps it was too rel­e­vant for consideration?

WYSIWYG cre­ation rejects the notion of sep­a­ra­tion of markup (con­tent), pre­sen­ta­tion and behaviour.

The risks are three-fold.

Firstly, that pro­duc­tion of qual­ity con­tent should be hin­dered by the bun­dled nature of the medium — that is, peo­ple will focus on pre­sen­ta­tion at the expense of con­tent. The seman­tic web frees content-creators from this — their pur­pose is sim­ply that, with lay­out being dic­tated at the pre­sen­ta­tional layer. For a broader exam­ple of this, see gen­eral crit­i­cisms of Pow­er­Point as being a time-wasting and hol­low pre­sen­ta­tion form.

Sec­ondly, that the con­tent should be bound to pre­sen­ta­tion, and its longevity would be com­pro­mised by this link. This is a well-documented risk in rela­tion to the seman­tic web, and one of the core rea­sons com­monly given in sup­port of this. Ample evi­dence sup­port­ing this exists, so I won’t elab­o­rate further.

A third risk is the gen­eral acces­si­bil­ity of infor­ma­tion — also well doc­u­mented. The cre­ation of qual­ity con­tent is still pos­si­ble, but if this con­tent is acces­si­ble to no-one due to usabil­ity bar­ri­ers, it is redundant.

Pro­mo­tion of WYSIWYG devel­op­ment meth­ods is counter-productive in all areas — con­tent pro­duc­tion, gen­eral qual­ity of design, and cre­ation of an accessibility/usability cul­ture — and should cease imme­di­ately in all edu­ca­tional spheres presently sup­port­ing this practice.

*steps off soap box*

CurlyEnc 0.1

This is a sim­ple Word­Press plu­gin that allows you to copy and paste from word-processing soft­ware that automag­i­cally does smart quotes con­ver­sion (curly quotes). You can do this with­out using this plu­gin — but the char­ac­ters aren’t proper HTML enti­ties and it’s dirty. CurlyEnc con­verts curly quote char­ac­ters to their proper HTML entity codes — some­thing Word­Press does per­fectly fine with nor­mal quo­ta­tion marks, but not with these ones.

Sim­ply upload CurlyEnc into your plugins direc­tory and enable it from the Plu­g­ins sec­tion of your Word­Press admin­is­tra­tion panel, and it should* work.

* No guar­an­tees, no promises. If your weblog sprouts furry ears and starts chas­ing your mouse, so to speak, I accept no respon­si­bil­ity. Yada yada. Happy to try and help. More seri­ously, I don’t know that much about char­ac­ter encod­ing, so I wouldn’t be entirely sur­prised if my mag­i­cal char­ac­ter is some­thing of a dud on some instal­la­tions. I know it’s a good con­cept, and this is my best imple­men­ta­tion of it — if any­one else has a bet­ter idea as to how it should be done, please share!

On a related note, it’s released under the GNU GPL — you can have that five lines of code for free! Sorry, no steak knives.

View the PHP source, or down­load a plain text ver­sion.

Extension 1 presentation

At least one of these has to work okay with the school’s tech­nol­ogy…
Native OpenOf­fice
MS Pow­er­point

Macro­me­dia Flash
Adobe PDF

*Josh really really really hopes fonts embed­ding works properly*

Aaaannnddd the Flash ver­sion worked great, fonts and all! Thankyou, OpenOffice!

Full­text of the pre­sen­ta­tion, with slide cues, as promised. PDF, file­size: stu­pidly large (280KB). Don’t know what hap­pened there!

As for the con­tent of the thing, no jokes are required about me being unable to write an essay/speech with­out ref­er­ence to acces­si­bil­ity! It’s purely inci­den­tal, I promise! On a slightly more seri­ous note, if some of the sen­tences utterly suck, chances are I didn’t speak them that way… my paper ver­sion had a few pencilled-in cor­rec­tions, and then there was the inevitable “read but speak dif­fer­ently” fac­tor. The end.

Read on for a HTML ver­sion of the same. Read the rest of this entry »