Оглавление

Ответственность составителей документа
Введение
Предоставление лицензии
Структура документа
Общее описание
Номера версий
Кодировщик
Декодировщик
Совместимость
Рекомендации
Таблицы цветов
Основные и дополнительные блоки, а также границы их действия
Размер блока
Использование формата GIF в составе более общего протокола
Субблоки данных
Блок-терминатор
Заголовок
Дескриптор логического экрана
Глобальная таблица цветов
Дескриптор изображения
Локальная таблица цветов
Кодирование изображений методом таблиц
Дополнительный блок управления изображением
Дополнительный блок комментария
Дополнительный блок с простым текстом
Дополнительный блок приложений
Завершающий блок

Читать далее →

A metafile for the Windows operating system consists of a collection of graphics  device interface (GDI) functions  that describe an image. Because metafiles take up less space and are more device- independent than bitmaps, they  provide convenient storage for images that appear repeatedly in an application or  need to be moved from one  application to another. To generate a metafile, a Windows application creates a special device context that sends GDI commands to a file or memory for storage. The application can later play back the metafile and display the image. During playback, Windows breaks the metafile down into records and identifies  each object with an index to a handle table. Читать далее →

Also Known As: WMF, Enhanced Metafile, EMF, APM

Type Metafile
Colors 24-bit
Compression None
Maximum Image Size NA
Multiple Images Per File Yes
Numerical Format Little-endian
Originator Microsoft Corporation
Platform Microsoft Windows
Supporting Applications Numerous Microsoft Windows-based graphics applications
Usage Storage of vector drawings and bitmaps. Читать далее →

Disclaimer
Although PKWARE will attempt to supply current and accurate information relating to its file formats, algorithms, and the subject programs, the possibility of error can not be eliminated. PKWARE therefore expressly disclaims any warranty that the information contained in the associated materials relating to the subject programs and/or the format of the files created or accessed by the subject programs and/or the algorithms used by the subject programs, or any other matter, is current, correct or accurate as delivered.  Any risk of damage due to any possible inaccurate information is assumed by the user of the information. Furthermore, the information relating to the subject programs and/or the file formats created or accessed by the subject programs and/or the algorithms used by the subject programs is subject to change without notice.

General Format of a ZIP file  Files stored in arbitrary order.  Large zipfiles can span multiple diskette media. Читать далее →

*.CSV (Comma Seperated Value) format is mostly self-explanatory ASCII text format. If you export a file from a database in CSV format and look at it you will find that it is simply a list of entries seperated by commas:

<CSV_file> ::= { <CSV_line> }
<CSV_line> ::= <value> { "," <value> } <spaces_and_tabs>
<CRLF>
<value> ::= <spaces_and_tabs>
        (
          { <any_text_except_quotas_and_commas_and_smth_else>
}
        | <single_or_double_quote>
          <any_text_save_CRLF_with_corresponding_doubled_quotas>
          <the_same_quote>
        )

That’s all I think… and there is some problem with this format: different database systems have different definitions of the term <any_text_except_quotas_and_commas_and_smth_else> Also Paradox version approx.4 has the bug. When converting to .CSV, it always writes values surrounded by «s — but if in the source database file we have a field containing «s, them will not be doubled in CSV.
E.g.: abc»dfg will be translated to «abc»dfg» instead of «abc»»dfg».