JargonFile/original/html/F/frogging.html
2014-03-27 18:54:56 +00:00

13 lines
2.4 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>frogging</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../F.html" title="F"/><link rel="previous" href="frog.html" title="frog"/><link rel="next" href="front-end.html" title="front end"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">frogging</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="frog.html">Prev</a> </td><th width="60%" align="center">F</th><td width="20%" align="right"> <a accesskey="n" href="front-end.html">Next</a></td></tr></table><hr/></div><dt><a id="frogging"/><dt xmlns="" id="frogging"><b>frogging</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">v.</span></dt></dt><dd><p> 1. Partial corruption of a text file or input stream by some bug or
consistent glitch, as opposed to random events like line noise or media
failures. Might occur, for example, if one bit of each incoming character
on a tty were stuck, so that some characters were correct and others were
not. See <a href="../D/dread-high-bit-disease.html"><i class="glossterm">dread high-bit disease</i></a>. </p></dd><dd><p> 2. By extension, accidental display of text in a mode where the
output device emits special symbols or mnemonics rather than conventional
ASCII. This often happens, for example, when using a terminal or comm
program on a device like an IBM PC with a special &#8216;high-half&#8217;
character set and with the bit-parity assumption wrong. A hacker
sufficiently familiar with ASCII bit patterns might be able to read the
display anyway.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="frog.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../F.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="front-end.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">frog </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> front end</td></tr></table></div></body></html>