Talk:TextEdit (API)

Apple Inc. Stub‑class

	This article is within the scope of WikiProject Apple Inc., a collaborative effort to improve the coverage of Apple, Mac, iOS and related topics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Apple Inc.Wikipedia:WikiProject Apple Inc.Template:WikiProject Apple Inc.Apple Inc.
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool based on the length of the article. Please ensure the assessment is correct before removing the `\|auto=` parameter.

On TextEdit Limitations

When listing the limitations of TextEdit, the article says that it only provides support for 8-bit character sets. But TextEdit actually allowed the use of any WorldScript text encoding, not just pure 8-bit encodings like MacRoman, but also multibyte encodings like MacJapanese, which could be defined as a mixture of single-byte and double-byte characters. TextEdit gained this ability shortly prior to the advent of System 7.0 (see Mac OS history), when the commercial moniker "WorldScript" hadn't been coined yet, but some of the Script Manager APIs were already available.

Also, in the System 7.x years, the 32K limit on text length was so felt by users and developers alike that when the first version of the WASTE text engine became available, it was soon widely adopted. Dhcmrlchtdj 08:43, 27 July 2007 (UTC)[reply]

ATSUI

The article states that "TextEdit ... has been superseded by numerous other solutions including ATSUI in Carbon ..." but ATSUI provides typography and layout services, whereas the Multilingual Text Engine (MLTE) provides editing features (see http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/TextArchitecture/Concepts/CocoaAndATSUI.html)