1962 Vintage IBM Typewriter Training Film IBM Selectric Proper Typing Procedures, w/ Bud McDole by [[Computer History Archives Project]]

Right at the Typewriter. 16 mm. San Francisco, CA: KQED, 1962. https://www.youtube.com/watch?v=sPfHAW_OfGo.

On manual typewriters one "snaps" the keys while on an electric keyboard one "taps" the keys for maximum speed and accuracy.

Overview of functionality of an IBM typewriter.

To add longevity to one's carbon papers they should be rotated both top to bottom and front to back within one's packs.

Use plastic type cleaner, meant for cleaning type slugs, to clean the excess ink from a typewriter. Form it into a point and press it to the letter to erase several times. Then erase with eraser shield and eraser.

To type to the very bottom of the page, particularly with a carbon pack, to prevent slippage at the bottom, insert a "trailer sheet" about halfway down the first page. Insert it at the back of the pack just behind the original and between the first carbon sheet.

For typing small sheets of paper (index cards) fold a pleat into a regular sheet of paper and use the lip to hold the smaller sheet you're typing on.

To more quickly type envelopes, do the first then reverse the platen so that only about an inch of the top of the envelope is visible. Then insert the next envelope behind the first and continue reversing the platen. This will allow the finished envelopes to stack at the paper table and speed the threading and typing of envelopes in rapid succession.

Use of the divots on the typing guide for making horizontal or vertical lines while moving the carriage or rotating the platen respectively.

How to change the typeball and the ribbon cartridge on the IBM selectric.

I think this should be performance.

Page formatting is broken in several places and makes the formulas unreadable.

The HTML encoding of this document contains several errors, some of which substantially affect the way it's read. This fixes one of those problems in Appendix II:

javascript ([ ...document.querySelectorAll("op") ]).reverse().forEach((op) => { let f = document.createDocumentFragment(); f.append(document.createTextNode("<OP>"), ...op.childNodes); op.parentElement.replaceChild(f, op); })

The problem show be apparent on what is, at the time of this writing, line 4437:

html <code>IF ?w THEN ?x<OP>?y ELSE ?z<OP>?y</code>

(The angle brackets around the occurrences of "OP" should be encoded as HTML entities. Because they aren't they end up getting parsed as HTML op elements (which isn't a thing) and screwing up the document tree.)

only partial match: the most important thing is the information (more than presentation/formatting)

https://sharegpt.com/

<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Hypothesis</span> in Liquid Margins 38: The rise of ChatGPT and how to work with and around it : Hypothesis (<time class='dt-published'>02/09/2023 16:11:54</time>)</cite></small>

just noting a link here

formating issue on pull quote

call out box is hard to read!

Nice. Is there a way we could put this at the top, or make a quick link to it?

Ideally, this would have the ratings/rankings/predictions show up first on the page, as some sort of table (and also metadata if we dare to dream),

important

https://lucybellwood.com/never-again/

BRO...

I am semi-legitimately angry I am just now finding out about this.

Here's an example that actually works!

https://gist.github.com/extratone/36c6ceeb48ab2eefd77256afa80a54c3#file-extratext-csv-L329

https://archivaldecolonist.com/2020/05/07/indigenous-referencing-prototype-non-indigenous-authored-works/

A great resource for better referencing indigenous knowledge in non-Indigenous works.

Markdown issue

We should comment out any headers that we don't actually want showing up in the rendered doc

Typo here in formatting citation

remove bold

add space

Capitalize and spell together for consistency

add space

add space

add space

add space

maybe put in bold as terminology

lower case and either use quotation marks on the full word for none at all

remove

add space

add space

add space

remove bold

add space

add space

add space

remove

add space

add space

space

Remove or create a #4

Argdown. (n.d.). Retrieved July 2, 2020, from https://argdown.org/

This is hideous formatting. Walmart web techs need to make this much larger and more legible since we older folk can't always read so well.

Free-form text formatting has its pros and its cons.

Pros: It's very flexible. Since it's free-form, you can ad hoc make any new system you want, and designate, say, bold or blue to mean whatever you want it to.

Cons: No way to enforce the rules you made for yourself. In fact, it may be hard to even remember the rules you made for yourself. You may have to create a key/legend for yourself to be safe.

This is like why I dislike software where the only way to change font is to manually choose a font. I like it better when you can define a style/class (I think Word can do this, IIRC; and obviously HTML/CSS can), choose how that class should be formatted (font, etc.) and then can style any text with that class. This is a better way to go because classes have semantic meaning. This is the same dilemma I remember facing ~10 years ago when WYM editor was fairly new: It let you select use semantic classes/elements, whereas WYSIWIG editors were the norm (probably still are) and only let you do manual free-form formatting, with no semantic meaning conveyed.

First sighting. First time I've seen a literal, non-whitespace character (┊) used to show indentation. Looks pretty nice. But breaks copy-and-pastability.

Don't waste space on whitespace, but keep your proposal readable. Double check on the formatting slack they they give you, but head your sections with bold, indented text but don't break the line afterwards. Give a few spaces or a colon and head into the paragraph

Don't be shy about numbering arguments in-paragraph, especially in the intellectual merit section. Listing several ideas in sequence makes your writing feel 'blippy' - moving too abruptly. By explicitly offsetting with numbers you implicitly prepare your reader for rapid topic switches. They also take up less space than "this, next, then, last, etc."

End your introduction with a one-sentence description of your project. Use italics to make in-paragraph text easy for your reviewer to pick out.

Can we revise the text color or format so that this section is easier to read and visually more manageable? Each beginning term, for example, could be formatted in this way:

"Participant data: Can help you determine if you're actually reaching the people you intend to reach."

In this explanatory subsection, can we perhaps format the text color or font so that the main point in each numbered section stands out visually? For example, a revised format might look something like this:

"1. Places a greater emphasis on determining unit of analysis. When conducting a content analysis, you'll want to first determine what your unit of analysis may be. . . ."

I would suggest that we begin a new paragraph with the sentence "These two categories..."

We may also want to very briefly reiterate the relevant topics. For example, the first sentence of the new paragraph might read something like "Idiographic and nomothetic research represent two different research categories existing at opposite extremes on a continuum."

just an observation - we may want to round the estimated reading times to the nearest half-minute. I think there's some potential for confusion among readers interpreting an estimated reading time such as "6.57" - this estimate is so specific that it might not seem at first glance like an estimated reading time. Rounding that number and changing the format - i,e., "6.57" [current] to "7 mins" [suggested] - might help students clearly understand what we are trying to communicate. I do think the estimated reading times are potentially very helpful for readers, though.

Numbering on these lines should be 22 and 23, respectively

This should start on a new line

Don't agree with this statement at all. Blogs are nothing but linear chronological structures.

Also, weirdly overstated. There were plenty of products and meta data even in 2009 that was available to determine provenance and iteration.

This statement seems to be fixed in traditional, old-school blogging (one idea = one post) and doesn't consider other forms that adapt/extend other ways to represent temporality/change/iteration.

As one example, live-blogging techniques which incorporate rapid updating of new information through chronological mini-posts, manual time-stamping of new material, etc. Also. plug-ins that allow annotation, image uploads, Google Docs with version control, etc.

Also, WP post/page formatting options with HTML, typography, etc., can augment re-ordering of information to designate change.

Hypothesis.is allows for annotation of various pages of a website. On this homepage, I have highlighted all text links to the other pages I have annotated.

The formatting of e-books on Internet Archive does not allow hypothesis.is users to annotate the books’ text. In annotating Hyde’s Love Songs of Connacht for the EN6009 Annotate-A-Thon, I have attached annotations to the text beneath the scanned images. Extracts and corresponding page numbers are placed at the beginning of each annotation, in order to properly contextualize my responses.

all-caps for emphasis

bold to strengthen the statement to highlight danger

using boldface to summarise view of conspiracists

Formatting issue

Formatting.

Double space this or try to do something to make more readable.

"to"

Include a space above this line, as per the previous bullets.

Remove new paragraph here.

Where is the footnote mark in the body of the text?

Is this wrapping from the second line? It's hard to read with only one line wrapping, so adjust if possible.

If this is a complete sentence - and it seems like it is - then both Malay and translation should have sentence punctuation. Same for other examples. If the Malay isn't a complete sentence, adjust the translation to make that clear.

Use same punctuation in first line of example as in third.

First line of example doesn't have same punctuation as the translation line.

First line of example doesn't have same punctuation as the translation line.

First line of example doesn't have same punctuation as the translation line.

I would move this whole part of the table to table 9.3, which would group all of the punya examples together in table 9.3 and the pu examples in table 9.3. As it is right now, it's not clear why you'd split the tables up the way you have.

Where is the footnote mark in the text body?

Use en-dash.

Use en-dash.

No spaces. Use en-dash.

No spaces. Use en-dash.

Should be (5j-5l) without spaces, but make the - an en-dash instead.

Is this supposed to be on the line above, with "mama..." on the next line? Same for all examples in (5). If not, I'm not following what structure you're trying to point out here.

Don't split an example across two pages.