In typography and computing, characters per line (CPL) or terminal width refers to the maximal number of monospaced characters that may appear on a single line. It is similar to line length in typesetting.
History
editThe limit of the line length in 70–80 characters may well have originated from various technical limitations of various equipment. The American teletypewriters could type only 72 CPL, while the British ones even less, 70 CPL.[1] In the era of typewriters, most designs of the typewriter carriage were limited to 80–90 CPL. Standard paper sizes, such as the international standard A4, also impose limitations on line length: using the US standard Letter paper size (8.5×11"), it is only possible to print a maximum of 85 or 102 characters (with the font size either 10 or 12 characters per inch) without margins on the typewriter. With various margins – usually from 1–1.5 inches (25–38?mm) for each side, but there is no strict standard – these numbers may shrink to 55–78 CPL.
In computer technology, a line of an IBM punched card consisted of 80 characters. Widespread computer terminals such as DEC's VT52 and VT100 mostly followed this standard, showing 80 CPL and 24 lines. This line length was carried over into the original 80×25 text mode of the IBM PC, along with its clones and successors. To this day, virtual terminals most often display 80×24 characters.
The "long" line of 132 CPL comes from mainframes' line printers.[2][3][4] However, some printers or printing terminals could print as many as 216 CPL, given certain extra-wide paper sizes and/or extra-narrow font sizes.[5]
In modern computing
editWith the advent of desktop computing and publishing, and technologies such as TrueType used in word processing and web browsing, a uniform CPL has been made mostly obsolete. HTML (and some other modern text presentation formats) uses dynamic word wrapping which is more flexible than characters per line restriction and may produce a text block with non-rectangular shape, just like in paper typesetting.
Many plain text documents still conform to 72 CPL out of tradition (e.g., RFC?678).
In programming
editMany style guides for computer programming define the maximum or desirable number of characters in a line of source code:
| Characters per line | Programming style |
|---|---|
| 72 | |
| 79 | |
| 80 | |
| 88 |
|
| 90 | |
| 100 | |
| 102 | |
| 120 | |
| 132 | |
| 140 | |
| 180 | |
| undefined |
|
With the increasing common use of larger widescreen monitors, some of these limits have been relaxed, as in the Linux kernel[39] and FreeBSD.[40]
See also
edit- IBM 80-column punched card format
- Common text modes
- Apple 80-Column Text Card
- Column (typography)
- Line length (the equivalent concept for non-monospaced text)
References
edit- ^ Department of the Army, ed. (1947). Teletypewriter Circuits and Equipment (fundamentals). Washington: US Government Printing Office. p.?69.
- ^ Pomerantz, Ori; Vander Weele, Barbara; Nelson, Mark; et?al., eds. (2008). Mainframe Basics for Security Professionals. IBM Press. ISBN?9780132704342.
- ^ Wells, April J. (2003). Oracle 11i E-Business Suite from the Front Lines. CRC Press. p.?168. ISBN?9780203508961.
- ^ "Difference between..LRECL = 133 and LRECL = 132". IBMMAINFRAMES.com - IBM Mainframe Support Forums. 2004.
- ^ "Appendix K. Traditional Terminals and Printers". Terminals & Printers Handbook 1983–84. Digital. 1983.
- ^ Ada 95 Quality and Style Guide
- ^ agda/agda-stdlib: Style guide for the standard library
- ^ PEP 8 Style Guide for Python Code
- ^ Style Guide for Python Code
- ^ Google C++ Style Guide
- ^ Chromium Objective-C and Objective-C++ style guide
- ^ Google Python Style Guide
- ^ Google's R Style Guide
- ^ Google JavaScript Style Guide
- ^ "4.1. Line length". Java Code Conventions (PDF). Sun Microsystems, Inc. 1997. p.?5.
- ^ "Linux kernel code style as of June 2020". git.kernel.org. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
- ^ "Object Pascal Style Guide". Archived from the original on 2025-08-14. Retrieved 2025-08-14.
- ^ "style(9) - OpenBSD manual pages". Archived from the original on 2025-08-14. Retrieved 2025-08-14.
All code should fit in 80 columns.
- ^ Conway, Damian (2005). Perl Best Practices: Standards and Styles for Developing Maintainable Code. O'Reilly. p.?40. ISBN?978-0-596-55502-3.
- ^ a b PSR-2: Coding Style Guide
- ^ The Ruby Style Guide
- ^ OCaml Programming Guidelines
- ^ GCC Coding Conventions
- ^ "The Black code style - Black (stable) documentation". black.readthedocs.io. Retrieved 2025-08-14.
- ^ CCM4 self-imposed limit
- ^ Android Code Style Guidelines for Contributors
- ^ Common Lisp Style Guide
- ^ Google Common Lisp Style Guide
- ^ Google Java Style
- ^ rustfmt Documentation
- ^ How to Program Racket: a Style Guide
- ^ FORTRAN 90
- ^ Reid, John (2025-08-14), The new features of Fortran 202x (PDF)
- ^ Blink Coding Style Guidelines
- ^ Moodle Coding Style
- ^ Leach, Parker. "The Puppet language style guide". puppet.com. Retrieved 2025-08-14.
- ^ Mono Coding Guidelines
- ^ Effective Go
- ^ "The Linux Kernel Deprecates The 80 Character Line Coding Style". www.phoronix.com. Retrieved 2025-08-14.
- ^ "? D30255 style: Relax 80 column rule". reviews.freebsd.org. Retrieved 2025-08-14.