TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Hyphenation -- good research into reading speed and comprehension?
Subject:Hyphenation -- good research into reading speed and comprehension? From:JX Consulting <JX -at- jxconsulting -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 13 Nov 2009 22:17:04 -0800
Is there any good research into reading speed and comprehension of
unhyphenated English versus hyphenated English? I just mean
hyphenation due to end of line, not about words with naturally having
hyphens whereever they appear on the line :-)
I'm skeptical about hyphenation of technical documentation. Maybe I'm
wired differently than other folks, but it seems to hinder
comprehension and reading speed, as well as look distracting. Yeah, I
get it that lines can be more "full looking", but that's not even
necessarily more aesthetically pleasing. And for documentation, we're
optimizing for people actually reading it, especially quickly, and
learning quickly. And it doesn't seem worth it to me to hyphenate if
that's what we're going for.
From what I've read online**, the hyphenation of words for line
length was originally just an artifact of the physical limitations of
old moveable type presses, and just got carried over into the future
from there.
I want to know the facts on this. Is there any reputable research
about the actual reading of hyphenated English? I am curious about
various types of data: (1) neurotypical folks -- the general
population (2) dyslexic populations (3) and of course folks leaning
towards Aspergers - people more likely to be readers of our technical
docs. :-)
Thanks for any good tips!
-- JX Bell
Technical Communication Consultant
JX Consulting
*** According to wikipedia, "Prior to Gutenberg setting the first
lines printed in the Western world with movable type, there was no
need for hyphens or the justification of lines to equal length. The
Gutenberg printing press required words made up of individual letters
of type to be held in place by a surrounding non-printing rigid frame.
Gutenberg solved the problem of making each line the same length to
fit the frame by inserting a hyphen as the last element at the right
side margin. This interrupted the letters in the last word, requiring
the remaining letters be carried over to the start of the line
below..." http://en.wikipedia.org/wiki/Hyphenation
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help and Manual 5: The all-in-one help authoring tool. Full support for
team authoring with multi-user editing - both directly and in combination
with VSS-compatible source control systems. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-