Word 2007 can’t print

Okay, so maybe I spoke too soon.

Its inter­face is won­der­fully improved, its type­set­ting now is vastly more tol­er­a­ble, and it’s still full of bugs.

I just tried to print a doc­u­ment and it failed to include one image out of thir­teen. I tried to print to a PDF file (using Acro­bat, because the inbuilt PDF plu­gin is crap and won’t respect the Word mul­ti­ple sheets/page set­ting), in case it was just the printer being lame — it wasn’t.

Who thought it might be a good idea to release a word proces­sor that can’t print?

Obvi­ously they scrapped their beta test­ing pro­gramme so they could afford to give it away for $75 to peo­ple who’d oth­er­wise pirate it any­way *rolls eyes*

# by Josh on March 8th, 2007 Tags:
| 1 Comment »

Office 2007

Please stop me if I am mak­ing a fool of myself by over­flow­ing with gush­ing praise for this thing, but, seri­ously, the best $75 I ever spent on soft­ware. (Yes, you can get the lat­est Office Ulti­mate for $75 if you’re a stu­dent. Legit.)

The new ver­sion of Word is a thing of beauty. It just works, and makes sense, and is gen­er­ally a usabil­ity won­der. I’m sure some­one will pub­lish a study to the con­trary in the next week, but I don’t care — it is per­fectly intu­itive to a non-Office lit­er­ate user. Yes, that is myself – I’ve bat­tled with OO.org for years, and am utterly con­vinced it sucks. I have occa­sion­ally fought with MS Office prod­ucts in this time, and bat­tled slightly less, but still it’s felt like I’m doing things the slow way. Every essay I’ve writ­ten over the last eigh­teen months is stored in LyX (LaTeX) for­mat: I’ve basi­cally not used a word proces­sor for any­thing seri­ous in at least that long. And I haven’t used a Microsoft word proces­sor at home for three years (on a hor­ri­ble lap­top), and not on my pri­mary desk­top com­puter for four, or pos­si­bly five. His­tor­i­cal per­spec­tive: I started using Win­dows when I was 7, stopped when I was 15 or 16, and returned at 18 ½ — Microsoft have got good rea­son to be try­ing to bring me back into the fam­ily, because I’ve been away for a long time.

I am as upset as the next web devel­oper about the Out­look team’s brain-dead deci­sion to switch back to Word as the pri­mary rich email ren­der­ing engine, but will wax lyri­cal about the new cal­en­dar­ing fea­tures in Out­look!! For they are greatly beau­ti­ful. Observe my three cal­en­dars (Organ­ised into: Per­sonal & Work; Uni; Church) lay­ered together here:

Outlook 2007 week calendars layered

Groove makes me shrug enor­mously, it does noth­ing use­ful for me. Unless it’s like Share­point only… good. But even then, I’ve never dug that whole Intranet col­lab­o­ra­tive thang. Really, if I were going to run bloat-inducing col­lab­o­ra­tive soft­ware, I should start with Adobe’s Ver­sion Cue. But I don’t use it because… too many apps in my tray annoys me, and Fire­fox eats all my mem­ory as is (screeny from yes­ter­day… it peaked at about 1GB but I couldn’t be both­ered tak­ing another):

Firefox using the better part of 1GB of RAM

The only rea­son I still use that bloody browser is its exten­sions sup­port: Fire­bug has stolen my heart where Office 2007 hasn’t yet. Here’s its asset down­load gra­phy thingamijig:

Firebug in Net inspector action

It’s even bet­ter than Chris Pederick’s tool­bar. But oh how I’d love to switch to Opera (or even, shock, IE) full time now. Fire­fox really isn’t doing it for me with its bloat these days.

Speak­ing of bloat, Office 2007 is one 500MB down­load. It doesn’t down­load a 500MB stub and then install the rest — no, that includes Word, Out­look, Pow­er­point, Excel, Pub­lisher, … and all the other ran­dom crap I installed but will prob­a­bly never use. Fantastic.

Every­thing is pretty fast (but it emphat­i­cally encour­ages you to install Win­dows Live Desk­top, and see­ing as I’m a beta tester for other Live stuff pretty will­ingly, I fig­ured I may as well, and when you first install that index­ing makes every­thing chug) which is excel­lent — but I’m still look­ing to buy a new dual core 939 some­time soon. Graph­ics are fine because I have no inten­tion of upgrad­ing to Vista (read: need­ing DirectX 10 and a $1000 graph­ics card) in the next 18 months at least, but… well, another 2GB of RAM would go down nicely. Shame it’s still rel­a­tively expen­sive, though.

Microsoft, I wasn’t going to pirate your soft­ware because it’s not that good, but thanks for the dis­count, anyway!

Part 2: Web design in schools

The last post on this sub­ject gen­er­ated a bit of inter­est, so I thought I’d share some more thoughts on the same. Who are you call­ing attention-seeker? Seri­ously, though — this time, I’m aim­ing to share some more con­struc­tive thoughts on how to improve the situation.

First up, a response to some of the com­ments. I think that there’s a very def­i­nite need for the teach­ing of web design in any gen­eral IT course in schools or other insti­tu­tions. Con­sid­er­ing they’ve been teach­ing progam­ming in these since the begin­ning of time, a lit­tle markup is hardly too much to ask.

You don’t learn web design in year nine, the bur­den isn’t on a year nine com­put­ing syllabus/teacher to teach web design to any great level of competency…

Clearly, they believe you do. “Any great level of com­pe­tency”, here, is appar­ently none at all. Exist­ing courses do not ren­der stu­dents pro­fi­cient in web design, but rather in use of a word proces­sor to cre­ate unprint­able doc­u­ments. I would sug­gest that if they elect to teach any­thing resem­bling web design, the first aspect of the course should be to exam­ine a basic doc­u­ment struc­ture — first a doc­u­ment type dec­la­ra­tion (DTD), then doc­u­ment meta data (header infor­ma­tion, links to archives, stylesheets, alter­nate doc­u­ment for­mats, etc.), then con­tent using seman­tic markup.

Only after this should design be explored, in terms of using CSS to adjust posi­tion­ing, typog­ra­phy, and graph­i­cal ele­ments of design.

All insti­tu­tions seem to teach the WYSIWYG model — but I have stopped grip­ing over it — mainly because I know that most peo­ple in these “intro” classes won’t make it very far in Web design — and if they do — they will even­tu­ally learn the right way to do things.

I’d argue against this pas­siv­ity. I note the point, but would sug­gest that the rea­son given ignores web design train­ing as an ancil­lary thing — that is, peo­ple do these courses not as graphic design­ers look­ing to shift or expand their focus, or peo­ple look­ing to move into web design as a career, but rather as a part of their reg­u­lar employ­ment. An exam­ple has already been given by Steve in his arti­cle and com­ments — his friend wasn’t being edu­cated in order to advise oth­ers in web design, but rather as an ancil­lary part of her job, much like prepar­ing printed hand­outs. Sim­i­larly, many other pro­fes­sions also require a degree of web literacy.

Hav­ing said that, I’d agree that adding your own “two cents” to these courses is counter-productive: at least, per­haps, the atten­dees will achieve a smat­ter­ing of design knowl­edge. More to the point, these courses should be changed at an edu­ca­tion level, not as a stu­dent or attendee!

I’d also don’t think that print expe­ri­ence is irrel­e­vant or unhelp­ful — quite the oppo­site. The CSS Zen Gar­den project attests to this, in that it is pri­mar­ily about design. Print and web design are not mutu­ally exclu­sive, and, in many cases, are com­ple­men­tary. There’s also noth­ing inher­ently wrong with learn­ing to use Pho­to­shop (or sim­i­lar util­ity) to splice images for web pro­duc­tion — this is a valid tech­nique for cre­at­ing graph­i­cal lay­outs with CSS, too — although I per­son­ally don’t use this method, oth­ers do, and, pro­vided they’re not using tables for their dis­play and are includ­ing mean­ing­ful alter­na­tive tex­tual descrip­tions (alt text) where applic­a­ble, there’s absolutely noth­ing to be said against this.

Regret­tably, an under­stand­ing of graphic design for a print medium often instills a false con­fi­dence in authors — it is the role of edu­ca­tors to ensure that the dif­fer­ences between web and print design are made clear where they are respon­si­ble for the dis­sem­i­na­tion of design prac­tice knowl­edge, and there is much that may still be done in this area.

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.3

In response to a request from some­one on the Word­Press forums, I’ve added a heap of char­ac­ters processed by CurlyEnc. It also now processes using an array, which would be mar­gin­ally faster, I’d imag­ine. In this ver­sion, chances are if your word proces­sor can gen­er­ate a char­ac­ter, this will parse it into its cor­re­spond­ing entity.

As always, two ver­sions — plain text and PHPS syntax-highlighted.

# by Josh on June 4th, 2005 Tags:
| 5 Comments »