🚀 go-pugleaf

In article <hotelca-0208950026390001@192.0.2.1>,
Hotel California <hotelca@cris.com> wrote:
>In article <3vlv30INN26h@keats.ugrad.cs.ubc.ca>, c2a192@ugrad.cs.ubc.ca
>(Kazimir Kylheku) wrote:
>
>> Really? Here at UBC you can get a job "babysitting" in the Mac lab. Why
>> is that job needed?
>> 
>> I say that you need training to make _effective_ use of any system.  I
>> mentioned this before:  I've met Mac users who would use spaces for
>> alignment in a word processing document, type in page numbers by
>> hand and use repeated carriage returns to cause a page break. 
>> That's the intuitive thing to do for an utter newbie who refuses
>> to read the manual.
>
>No, a newbie would see a command labeled "Insert Page Numbers" and say
>"gee, maybe that inserts page numbers" rather having to read a manual to

Get glasses. I said that I've met people who didn't find it that intuitive.
They weren't utter newbies either -- one lady used her Mac for several years.

A guy I know hired some woman with secretarial training to bang out
some documents about 40 pages long. She used spaces for alignment,
hit carriage returns to cause page breaks, and used underline characters
to create "blanks". He wanted to change the font, thinking it would
take "about a minute". Haha. We're talking about a person who had some
vocational training that included word processing, not someone who's
never sat in front of a computer.

>see if the command even exists.  And I make very effective use of my
>system, thank you, without the help of manuals.  Besides, I thought it was
>DOS and Unix people who used spaces to line things up with there awful
>monospaced fonts.

Fixed fonts are very appropriate for alignment in plain ASCII text
documents. You can't be serious in implying that typesetting is also
done using terminal fonts!


I once used this lame Mac program called ClarisWorks, and it would
actually change the alignment based on what magnification I was using to
work on the document.  At 80% scale, the tabs would look normal.  Then
I'd print the document, to discover that some text has shifted around.
I'd switch to 100% scale and see the same mistakes!

Later, I checked out a newer release of the same program at a computer
store. It did the same damn thing. This is not just some programming bug,
but a serious design flaw stemming from a failure to represent some
metrics within the document in a resolution-independent manner.

Is this the kind of  of "app" that's supposed to make you more productive?