SYLK
From Just Solve the File Format Problem
(Difference between revisions)
(→Links) |
|||
| Line 29: | Line 29: | ||
* [https://web.archive.org/web/20140330053022/http://office.microsoft.com/en-us/excel-help/excel-formatting-and-features-that-are-not-transferred-to-other-file-formats-HP010014105.aspx Excel formatting and features that are not transferred to other file formats] | * [https://web.archive.org/web/20140330053022/http://office.microsoft.com/en-us/excel-help/excel-formatting-and-features-that-are-not-transferred-to-other-file-formats-HP010014105.aspx Excel formatting and features that are not transferred to other file formats] | ||
* [https://outflank.nl/upload/sylksum.txt Summary of all currently used sylk fields.] | * [https://outflank.nl/upload/sylksum.txt Summary of all currently used sylk fields.] | ||
| + | * [https://archive.org/details/mac_Graphics_File_Formats_Second_Edition_1996/page/n595/mode/2up Graphics File Formats Book Definition] | ||
* [https://www.bitsavers.org/pdf/microsoft/cpm/Microsoft_Multiplan_for_CPM_1982.pdf#page=426 Multiplan definition of SLK file format] | * [https://www.bitsavers.org/pdf/microsoft/cpm/Microsoft_Multiplan_for_CPM_1982.pdf#page=426 Multiplan definition of SLK file format] | ||
[[Category:Microsoft]] | [[Category:Microsoft]] | ||
Revision as of 17:05, 9 November 2023
SYLK (Symbolic Link) is a format devised by Microsoft for data interchange between applications, primarily spreadsheets. It has nothing to do with the "symbolic links" or "symlinks" used to tie multiple file paths to a single file in some operating systems including Unix-type systems.
SYLK is text-based, and is encoded in the native Windows code page (such as Windows 1252) of the system they are created on (rather than in Unicode as modern applications use).
Some of the "boilerplate articles" on sites that claim to document file formats by extension refer to .sylk or .silk files, but the official extension of this format is .slk (still under the influence of old-timey DOS thinking where extensions had to be 3 characters or less).
Specifications
- The first record must be an ID record.
- The file must close with an E record.
- All record and field codes must be entered in upper-case letters.
- Record and field type are separated by a semicolon.
- Each record must be terminated by CR/LF.
- There must be no CR/LF characters within a record or field.
- D and G records always relate to the last C command.
- When using NE records, the file name must be defined beforehand using NU.
- The dimensions and subdivision of the window must be defined in logically ascending sequence.
