An application should be able to produce and consume data from
multiple formats. These often include proprietary binary formats
and should also include some standard formats, such as Rich Text
Format (RTF) or HTML. The following table lists some formats
that can contain ink. |Binary||Applications should use ink
serialized format (ISF) to encode ink into their binary
formats.| |HTML||A HTML format is highly recommended for the
representation of heterogeneous content. Applications should use
fortified GIFs to encode ink into their HTML documents. For more
information about fortified GIFs, see Building Blocks.|
|Image||For applications for which there is no other
intersection of compatibility, an ink-enabled application should
move bitmap and metafile formatted images to the Clipboard.|
|Ink Serialized Format (ISF)||ISF is the most compact persistent
representation of ink. Although it often contains only ink data,
ISF is extensible. Applications can set custom attributes
(identified by a globally unique identifi