Revision as of 17:33, 15 October 2007 edit Jonathan de Boyne Pollard (talk \| contribs) Extended confirmed users 2,025 edits Fixed the text to match what the reference (which isn't a Unicode standard, note) actually says. The 2nd (unsourced) paragraph was obviously wrong, given the source. The rest was implied by "any". ← Previous edit		Revision as of 04:41, 16 October 2007 edit undo BenRG (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 7,373 edits Rewrite. This is not a Unicode-specific term. Legacy encodings are legacy encodings. It's like having an article about brown cows. Next edit →
Line 1: In computing, a '''legacy encoding''' is a [[character encoding]] that continues to be used despite being obsoleted by another encoding. An encoding considered legacy in one context may remain the preferred encoding in another. Today the term is most commonly used in the context of [[Unicode\|Unicodification]], where it refers to encodings that do not cover all Unicode code points. Even encodings which postdate the first Unicode standard, such as [[ISO-8859-15]], may be considered legacy encodings in this usage. In computing, a '''legacy encoding''' is, according to Basis Technology Corporation, "any [[character encoding]] that was in use prior to the advent of the Unicode standard", and legacy encodings "include national, international and vendor encoding standards".<ref>{{cite web\|url=http://www.ibm.com/developerworks/library/unicode-db-process/\|title=Processing database information using Unicode, a case study\|work=[[IBM]] developmentWorks\|date=[[1999-09-01]]\|publisher=Basis Technology Corporation\|author=Brian Carr and Karen Watts}}</ref> ~~== References ==~~ ~~<references/>~~ ==See also==

Legacy encoding: Difference between revisions