View source for E-text

{{Short description|Any document that is read in digital form}}
{{More citations needed|date=January 2013}}

'''e-text''' (from "''[[electronics|electronic]] text''"; sometimes written as '''etext''') is a general term for any [[Electronic document|document]] that is read in [[digital data|digital form]], and especially a document that is mainly text. For example, a computer-based book of art with minimal text, or a set of [[photograph]]s or [[Book scanning|scans of pages]], would not usually be called an "e-text".  An e-text may be a [[Binary file|binary]] or a [[plain text]] file, viewed with any [[open source]] or [[proprietary software]]. An e-text may have [[markup language|markup]] or other [[Formatted text|formatting]] information, or not. An e-text may be an electronic edition of a work originally composed or published in other media, or may be created in electronic form originally. The term is usually synonymous with [[e-book]].

==E-text origins==

E-texts, or [[electronic document]]s, have been around since long before the Internet, the Web, and specialized E-book reading hardware. [[Roberto Busa]] began developing an electronic edition of [[Aquinas]] in the 1940s, while large-scale electronic text editing, [[hypertext]], and online reading platforms such as [[NLS (computer system)|Augment]] and [[FRESS]] appeared in the 1960s. These early systems made extensive use of formatting, [[markup language|markup]], automatic tables of contents, [[hyperlinks]], and other information in their texts, as well as in some cases (such as FRESS) supporting not just text but also graphics.<ref>Reading and Writing the Electronic Book. Nicole Yankelovich, Norman Meyrowitz, and Andries van Dam. IEEE Computer 18(10), October 1985. http://dl.acm.org/citation.cfm?id=4407</ref>

=="Just plain text"==
{{Original research|section|date=April 2015}}
In some communities, "e-text" is used much more narrowly, to refer to electronic documents that are, so to speak, "plain [[Vanilla (computing)|vanilla]] [[ASCII]]". By this is meant not only that the document is a [[plain text]] file, but that it has no information beyond "the text itself"—no representation of bold or italics, paragraph, page, chapter, or footnote boundaries, etc. [[Michael S. Hart]],<ref>[https://web.archive.org/web/20060830193319/http://www.gutenberg.org/wiki/Gutenberg:The_History_and_Philosophy_of_Project_Gutenberg_by_Michael_Hart Michael S. Hart]</ref> for example, argued that this "is the only text mode that is easy on both the eyes and the computer". Hart made the correct{{According to whom|date=April 2015}} point that proprietary word-processor formats made texts grossly inaccessible; but that is irrelevant to standard, open data formats. The narrow sense of "e-text" is now uncommon, because the notion of "just vanilla ASCII" (attractive at first glance), has turned out to have serious difficulties:

First, this narrow type of "e-text" is limited to the English letters. Not even Spanish [[ñ]] or the accented vowels used in many European languages cannot be represented (unless awkwardly and ambiguously as "~n" "a'"). Asian, Slavic, Greek, and other writing systems are impossible.

Second, diagrams and pictures cannot be accommodated, and many books have at least some such material; often it is essential to the book.

Third, "e-texts" in this narrow sense have no reliable way to distinguish "the text" from other things that occur in a work. For example, page numbers, [[page header]]s, and [[footnote]]s might be omitted, or might simply appear as additional lines of text, perhaps with blank lines before and after (or not). An ornate separator line might be represented instead by a line of asterisks (or not).  Chapter and sections titles, likewise, are just additional lines of text: they might be detectable by capitalization if they were all caps in the original (or not). Even to discover what conventions (if any) were used, makes each book a new research or reverse-engineering project.

In consequence of this, such texts cannot be reliably re-formatted. A program cannot reliably tell where footnotes, headers or footers are, or perhaps even paragraphs, so it cannot re-arrange the text, for example to fit a narrower screen, or read it aloud for the visually impaired. Programs might apply [[heuristics]] to guess at the structure, but this can easily fail.

Fourth, and a perhaps surprisingly{{According to whom|date=April 2015}} important issue, a "plain-text" e-text affords no way to represent information ''about'' the work. For example, is it the first or the tenth edition? Who prepared it, and what rights do they reserve or grant to others? Is this the raw version straight off a scanner, or has it been proofread and corrected? [[Metadata]] relating to the text is sometimes included with an e-text, but there is by this definition no way to say whether or where it is preset. At best, the text of the title page might be included (or not), perhaps with centering imitated by indentation.

Fifth, texts with more complicated information cannot really be handled at all. A bilingual edition, or a [[critical edition]] with footnotes, commentary, critical apparatus, [[cross-references]], or even the simplest tables. This leads to endless practical problems: for example, if the computer cannot reliably distinguish footnotes, it cannot find a phrase that a footnote interrupts.

Even raw scanner [[Optical character recognition|OCR]] output usually produces more information than this, such as the use of bold and italic. If this information is not kept, it is expensive and time-consuming to reconstruct it; more sophisticated information such as what edition you have, may not be recoverable at all.

If actuality, even "plain text" uses some kind of "markup"—usually [[control character]]s, spaces, tabs, and the like: Spaces between words; two returns and 5 spaces for paragraph. The main difference from more formal markup is that "plain texts" use implicit, usually undocumented conventions, which are therefore inconsistent and difficult to recognize.<ref>{{cite journal|date=November 1987|title=Markup systems and the future of scholarly text processing|journal=[[Communications of the ACM]]|publisher=[[Association for Computing Machinery|ACM]]|volume=30|issue=11|pages=933–947|doi=10.1145/32206.32209|url=http://xml.coverpages.org/coombs.html|first1=James H.|last1=Coombs|first2=Allen H.|last2=Renear|first3=Steven J.|last3=DeRose|s2cid=59941802|doi-access=free|archive-date=2019-05-12|access-date=2012-07-19|archive-url=https://web.archive.org/web/20190512040939/http://xml.coverpages.org/coombs.html|url-status=dead}}</ref>

The narrow sense of e-text as "plain vanilla ASCII" has fallen out of favor.{{According to whom|date=April 2015}} Nevertheless, many such texts are freely available on the Web, perhaps as much because they are easily produced as because of any purported portability advantage. For many years [[Project Gutenberg]] strongly favored this model of text, but with time, has begun to develop and distribute more capable forms such as [[HTML]].

==See also==
*[[Text file]]
*[[e-book]]
*[[Electronic paper]]
*[[Digital library]]
*[[Online Books Page]]
*[[Distributed Proofreaders]]
*[[:fr:Association des bibliophiles universels|L'Association des Bibliophiles Universels]]

==References==
{{reflist}}

==External links==
* [http://info.lib.uh.edu/sepb/sepb.html ''Scholarly Electronic Publishing Bibliography''] {{Webarchive|url=https://web.archive.org/web/20050619083936/http://info.lib.uh.edu/sepb/sepb.html |date=2005-06-19 }}

[[Category:Books by type]]
[[Category:Electronic publishing]]
[[Category:Documents]]

[[ru:Электронная книга (документ)]]