对方未开通空间| 　| 　 |
| 　　| 　　| |
| 　| 　 | 　 | 　　| 　　　|
| 　 | 　 |
| 　| 　 | 　 |
| 　 | 　| 　|
2014年-2015年
2010年-2013年
1990年-2009年
2014年-2015年
2010年-2013年
1990年-2009年
2013年-2015年
2010年-2012年
1990年-2009年
2014年-2015年
2010年-2013年
1990年-2009年
2014年-2015年
2010年-2013年
1990年-2009年
2013年-2015年
2010年-2012年
1990年-2009年
2014年-2015年
2010年-2013年
1990年-2009年
2010年-2015年
2001年-2009年
1990年-2000年
随着创意流失和快餐化，暴雪似乎脱离了轨道，当某一天暴雪宣布新作的时候，你还期待么？
当时间背叛了你
穿梭在银河的未来战士
幽默的策略小品
有多少江湖可以重来
日前，台湾的四人团队AJB喷射熊用虚幻4打造了一款动作冒险游戏《奥罗伦：天授神权》，其战斗模式正是致敬骑砍。
《爆笑魔兽》第24集闪亮登场！为何99%成功率的航海任务也能失败？船只失事之后抓紧时间自拍？请看最新一期《爆笑魔兽》。
FIFA Online 3 的全新职业联赛已经远远超出了以往正常电竞联赛的制作规格，视觉上首先做到了一个高水准电竞联赛的规格。
最新单机游戏
近期看点精选
国产山寨主机“OUYE坦克电视游戏机”传到了外国玩家眼中，来看看他们怎么对这一事件评价的吧。
《GTA5》的剧情DLC无疑仍在制作当中，近日，两位《GTA5》的配音演员再次放出暗示，为该DLC再添迷雾。
在迪士尼的D23博览会上，官方宣布《王国之心3》中会加入“超能陆战队”，同时迪士尼官方还发布了新宣传视频。
ESRB公布了《变形金刚：毁灭》的评级描述，因游戏含有幻想暴力元素而被评级为“T（Teen青少年级）”。
早在《羞辱2》公布之初我们看到，本作主角将换成前作的小女孩艾米丽，近日B社公开了艾米丽的介绍视频。
《合金装备5：幻痛》将于今年9月1日发售，现在来看，似乎玩家们可以更早的玩到这款3A巨制了。
近期上市大作
萌系剑士战邪神
武林风云起 孤胆侠客行
廿年情怀 缘起仙剑
老爷归来 再战阿甘
游戏发售表
日前，台湾的四人团队AJB喷射熊用虚幻4打造了一款动作冒险游戏《奥罗伦：天授神权》，其战斗模式正是致敬骑砍。
《爆笑魔兽》第24集闪亮登场！为何99%成功率的航海任务也能失败？船只失事之后抓紧时间自拍？请看最新一期《爆笑魔兽》。
FIFA OL3的全新职业联赛已经超出了以往正常电竞联赛的制作，视觉上首先做到了一个高水准电竞联赛的规格。
《剑灵》在2015年Season2比武会上公布了游戏的第九大职业，用现场的特效视频来将这个能发冲击波的拳师推介出来。
射击·RPG·单机IP
奇幻·道具·腾讯游戏
动作射击·电竞·暴雪
XIBA·战棋·火焰纹章
射击·科幻·开放世界
国产动画《雏蜂》的日语版在YoTuBe上面向日本网友播放了，2CH上的日本网友认为《雏蜂》就是在山寨日本动画并没有什么中国风格。
C88今天最后一天了，那么在这展会即结束之际，小编给大家总结了一些这三天以来，会场上那些惊人的COS以及一些奇葩的事情。
还记得C88上的那个7米长的抱枕吗？有人竟然拿着这只抱枕满场“乱跑”，然而这个场面被网友拍摄了下来，的确能够联想到国内的舞狮或者舞龙的活动。
外传开启全新故事
特技神作不服来战
就是这么爱把妹
吃饭也高潮
学生vs老师
少年岁拯救世界
吐槽的正确姿势
4月最燃新番
校园恋爱最麻烦
手游排行榜
热爱游戏的你，现在多大了呢？
45岁及以上
热游排行榜
新游期待榜
网游测试表
开放性测试
不删档首测
不删档内测
不删档测试
不删档首测
友情链接：ASCII codes, Latin character set, ANSI Standard (X3.64) Control Sequences,
VT100 commands, Mime Encode format, Mac Binary format
ASCII codes
Compiled by
August 1995
----------------------------------------------------------------------------
NUL (Null)
ENQ (Answerback)
BEL (Bell)
(Backspace)
(Linefeed)
(Carriage Return)
DC3 (Xoff)
CAN (Cancel)
ESC (Escape)
DEL (Delete)
Latin 1 character set
The following is the "official" Latin I Character set. In particular,
these characters can be included in HTML documents by enclosing them
as &#__;. For precise details view the source of this file.
Non-breaking space
Inverted exclamation
Pound sterling
General currency sign
Broken vertical bar
Section sign
Umlaut (dieresis)
Feminine ordinal
Left angle quote, guillemotleft
Soft hyphen
Registered trademark
Macron accent
Degree sign
Plus or minus
Superscript two
Superscript three
Acute accent
Micro sign
Paragraph sign
Middle dot
Superscript one
Masculine ordinal
Right angle quote, guillemotright
Fraction one-fourth
Fraction one-half
Fraction three-fourths
Inverted question mark
Capital A, grave accent ("&A")
Capital A, acute accent ("&A")
Capital A, circumflex accent ("&A")
Capital A, tilde ("&A")
Capital A, dieresis or umlaut mark ("&A")
Capital A, ring ("&A")
Capital AE dipthong (ligature) ("&AE")
Capital C, cedilla ("&C")
Capital E, grave accent ("&E")
Capital E, acute accent ("&E")
Capital E, circumflex accent ("&E")
Capital E, dieresis or umlaut mark ("&E")
Capital I, grave accent ("&I")
Capital I, acute accent ("&I")
Capital I, circumflex accent ("&I")
Capital I, dieresis or umlaut mark ("&I")
Capital Eth, Icelandic ("Ð")
Capital N, tilde ("&N")
Capital O, grave accent ("&O")
Capital O, acute accent ("&O")
Capital O, circumflex accent ("&O")
Capital O, tilde ("&O")
Capital O, dieresis or umlaut mark ("&O")
Multiply sign
Capital O, slash ("&O")
Capital U, grave accent ("&U")
Capital U, acute accent ("&U")
Capital U, circumflex accent ("&U")
Capital U, dieresis or umlaut mark ("&U")
Capital Y, acute accent ("&Y")
Capital THORN, Icelandic ("Þ")
Small sharp s, German (sz ligature) ("&")
Small a, grave accent ("&")
Small a, acute accent ("&")
Small a, circumflex accent ("&")
Small a, tilde ("&")
Small a, dieresis or umlaut mark ("&")
Small a, ring ("&")
Small ae dipthong (ligature) ("&")
Small c, cedilla ("&")
Small e, grave accent ("&")
Small e, acute accent ("&")
Small e, circumflex accent ("&")
Small e, dieresis or umlaut mark ("&")
Small i, grave accent ("&")
Small i, acute accent ("&")
Small i, circumflex accent ("&")
Small i, dieresis or umlaut mark ("&")
Small eth, Icelandic ("&")
Small n, tilde ("&")
Small o, grave accent ("&")
Small o, acute accent ("&")
Small o, circumflex accent ("&")
Small o, tilde ("&")
Small o, dieresis or umlaut mark ("&")
Division sign
Small o, slash ("&")
Small u, grave accent ("&")
Small u, acute accent ("&")
Small u, circumflex accent ("&")
Small u, dieresis or umlaut mark ("&")
Small y, acute accent ("&")
Small thorn, Icelandic ("&")
Small y, dieresis or umlaut mark ("&")
ANSI Standard (X3.64) Control Sequences for Video Terminals and Peripherals in alphabetic order by mnemonic
Compiled by
March 1989
Ps and Pn are parameters expressed in ASCII.
Numeric parameters are given in decimal radix.
Abbreviations are explained in detail at end.
Spaces used in this table for clarity are not used in the actual codes.
---------------------------------------------------------------------------
Applicatn Program Command Esc Fe
Cursor Backward Tab
Esc [ Pn Z
Cancel Previous Character Esc T
Cursor Horzntal Absolute
Esc [ Pn G
Cursor Horizontal Tab
Esc [ Pn I
Cursor Next Line
Esc [ Pn E
Cursor Preceding Line
Esc [ Pn F
Cursor Position Report
Esc [ P Pn R
Control Sequence Intro
Cursor Tab Control
Esc [ Ps W
Cursor Backward
Esc [ Pn D
Cursor Down
Esc [ Pn B
Cursor Forward
Esc [ Pn C
Cursor Position
Esc [ P Pn H
Esc [ Pn A
Cursor Vertical Tab
Esc [ Pn Y
Device Attributes
Esc [ Pn c
Define Area Qualification Esc [ Ps o
Delete Character
Esc [ Pn P
Device Control String
Delete Line
Esc [ Pn M
Disable Manual Input
Device Status Report
Esc [ Ps n
Erase in Area
Esc [ Ps O
Erase Character
Esc [ Pn X
Erase in Display
Esc [ Ps J
Erase in Field
Esc [ Ps N
Erase in Line
Esc [ Ps K
Enable Manual Input
End of Protected Area
End of Selected Area
Font Selection
Esc [ P Pn Space D
Graphic Size Modify
Esc [ P Pn Space B
Graphic Size Selection
Esc [ Pn Space C
Horz Position Absolute
Esc [ Pn `
Horz Position Relative
Esc [ Pn a
Horz Tab w/Justification
Horizontal Tab Set
Horz & Vertical Position
Esc [ P Pn f
Insert Character
Esc [ Pn @
Insert Line
Esc [ Pn L
Esc [ P ... ; Ps Space F
Media Copy
Esc [ Ps i
Message Waiting
Esc [ Pn U
Operating System Command
Partial Line Down
Partial Line Up
Privacy Message
Preceding Page
Esc [ Pn V
Private Use 1
Private Use 2
QUAD Typographic Quadding
Esc [ Ps Space H
Repeat Char or Control
Esc [ Pn b
Reverse Index
Reset to Initial State
Reset Mode
Esc [ Ps l
Scroll Down
Esc [ Pn T
Select Edit Extent Mode
Esc [ Ps Q
Select Graphic Rendition
Esc [ Ps m
Scroll Left
Esc [ Pn Space @
Select Mode
Esc [ Ps h
Start of Protected Area
Spacing Increment
Esc [ P Pn Space G
Scroll Right
Esc [ Pn Space A
Single Shift 2 (G2 set)
Single Shift 3 (G3 set)
Start of Selected Area
String Terminator
Set Transmit State
Esc [ Pn S
Esc [ Ps g
Thin Space Specification
Esc [ Pn Space E
Vert Position Absolute
Esc [ Pn d
Vert Position Relative
Esc [ Pn e
Vertical Tabulation Set
Abbreviations:
an Introducer of some kind the normal 7-bit
X3.64 Control Sequence Introducer is the two characters "Escape ["
a Delimiter
identifies a character by position in the ASCII table (column/row)
editor function (see explanation)
format effector (see explanation)
is a Final character in
an Escape sequence (F from 3/0 to 7/14 in the ASCII table)
a control sequence (F from 4/0 to 7/14)
is a graphic character appearing in strings (Gs ranges from
2/0 to 7/14) in the ASCII table
is a control represented as a single bit combination in the C1 set
of controls in an 8-bit character set
the familiar set of 7-bit ASCII control characters
roughly, the set of control characters available only in 8-bit systems.
This is too complicated to explain fully here, so read Jim Fleming's
article in the February 1983 BYTE, especially pages 214 through 224.
is a Final character of a 2-character Escape sequence that has an
equivalent representation in an 8-bit environment as a Ce-type
(Fe ranges from 4/0 to 5/15)
is a Final character of a 2-character Escape sequence that is
standardized internationally with identical representation in 7-bit
and 8-bit environments and is independent of the currently
designated C0 and C1 control sets (Fs ranges from 6/0 to 7/14)
is an Intermediate character from 2/0 to 2/15 (inclusive) in the
ASCII table
is a parameter character from 3/0 to 3/15 (inclusive) in the ASCII
is a numeric parameter in a control sequence, a string of zero or
more characters ranging from 3/0 to 3/9 in the ASCII table
is a variable number of selective parameters in a control sequence
with each selective parameter separated from the other by the code
3/11 (which usually represents a semicolon); Ps ranges from
3/0 to 3/9 and includes 3/11
Format Effectors versus Editor Functions
A format effector specifies how the final output is to be created.
An editor function allows you to modify the specification.
For instance, a format effector that moves the "active position" (the
cursor or equvalent) one space to the left would be useful when you want to
create an overstrike, a compound character made of two standard characters
overlaid. Control-H, the Backspace character, is actually supposed to be a
format effector, so you can do this. But many systems use it in a
nonstandard fashion, as an editor function, deleting the character to the
left of the cursor and moving the cursor left. When Control-H is assumed to
be an editor function, you cannot predict whether its use will create an
overstrike unless you also know whether the output device is in an "insert
mode" or an "overwrite mode". When Control-H is used as a format effector,
its effect can always be predicted. The familiar characters carriage
return, linefeed, formfeed, etc., are defined as format effectors.
ANSI X3.64 Mode-Changing Parameters for use with the Select Mode (SM) and Reset Mode (RM) functions
Mode Function
Characters
----------------------------------------------------------------------------
an error condition
guarded-area transfer mode
keyboard action mode
control representation mode
insertion/replacement mode
status-reporting transfer mode
erasure mode
vertical editing mode
reserved for future standardization
reserved for future standardization
reserved separator for parameters
Standard separator for parameters
reserved for private (experimental) use
reserved for private (experimental) use
horizontal editing mode
positioning unit mode
send/receive mode
format effector action mode
format effector transfer mode
multiple area transfer mode
transfer termination mode
selected area transfer mode
tabulation stop mode
editing boundary mode
reserved separator for parameters
Standard separator for parameters
error condition--unspecified recovery
error condition--unspecified recovery
linefeed/newline mode (not in ISO 6429)
reserved for future standardization
reserved for private (experimental) use
NOTES ON THE DEC VT100 IMPLEMENTATION
In the case of the popular DEC VT100 video-terminal implementation,
the only mode that may be altered is the linefeed/newline (LNM) mode.
Other modes are considered permanently set, reset, or not applicable
as follows:
Reset: CRM, EBM, FEAM, FETM, IRM, KAM, PUM, SRTM, TSM
GATM, HEM, MATM, SATM, TTM, VEM
Control sequences implemented in the VT100 are as follows:
CPR, CUB, CUD, CUF, CUP, CUU, DA, DSR, ED, EL, HTS, HVP, IND,
LNM, NEL, RI, RIS, RM, SGR, SM, TBC
plus several private DEC commands.
Erasing parts of the display (EL and ED) in the VT100 is performed thus:
Erase from cursor to end of line
or Esc [ K
Erase from beginning of line to cursor
Erase line containing cursor
Erase from cursor to end of screen
or Esc [ J
Erase from beginning of screen to cursor
Erase entire screen
The VT100 responds to receiving the DA (Device Attributes) control
(or Esc [ 0 c)
by transmitting the sequence
Esc [ ? Ps c
where Ps is a character that describes installed options.
The VT100's cursor location can be read with the DSR (Device Status
Report) control
The VT100 reports by transmitting the CPR sequence
Esc [ P Pc R
where Pl is the line number and Pc is the column number (in decimal).
The complete document describing the standard,
"ANSI X3.64-1979:
Additional Controls for Use with the American National Standard
Code for Information Interchange," can be ordered for $13.50 (plus
$4 postage) from
Standards Sales Department
American National Standards Institute
1430 Broadway
New York, NY 10018
212/354-3300
It's best to read the full standard before using it. It also helps
to have copies of the related standards "X3.4-1977: American
National Standard Code for Information Interchange" (the ASCII
standard) and "X3.41.1974: Code-Extension Techniques for Use with
the 7-Bit Coded Character Set of American National Standard for
Information Interchange."
See also the chapter "Using Extended Screens and Keyboard Control"
in the IBM PC-DOS manuals (versions 2.0, 2.1, and 3.0), especially
for the coding for character attributes.
The specification for the DEC VT100 is document EK-VT100-UG-003,
available for $13.00 prepaid from:
Digital Equipment Corporation
Accessories and Supplies Group
POB CS-2008
Nashua, NH 03061
Copyright 1984 BYTE Publications, subsidiary of McGraw-Hill Inc.
Permission granted to reproduce for noncommercial uses.
This file prepared by Richard S. Shuford.
VT100 commands and control sequences
the VT100 commands as
Digital VT101 Video Terminal User Guide
(EK-VT101-UG-003).
asterik (*)
beside the function indicate that it is
supported.
A plus (+) means the function is trapped and ignored.
Scrolling Functions:
ESC [ pb r
set scroll region
ESC [ ? 6 h
turn on region - origin mode
ESC [ ? 6 l
turn off region - full screen mode
Cursor Functions:
ESC [ pn A
cursor up pn times - stop at top
ESC [ pn B
cursor down pn times - stop at bottom
ESC [ pn C
cursor right pn times - stop at far right
ESC [ pn D
cursor left pn times - stop at far left
ESC [ pc H
set cursor position - pl Line, pc Column
set cursor home
ESC [ pc f
set cursor position - pl Line, pc Column
set cursor home
cursor down - at bottom of region, scroll up
cursor up - at top of region, scroll down
next line (same as CR LF)
save cursor position(char attr,char set,org)
restore position (char attr,char set,origin)
Applications / Normal Mode:
ESC [ ? 1 h
cursor keys in applications mode
ESC [ ? 1 l
cursor keys in cursor positioning mode
keypad keys in applications mode
keypad keys in numeric mode
Character Sets:
UK char set as G0
US char set as G0
line char set as G0
UK char set as G1
US char set as G1
line char set as G1
select G2 set for next character only
select G3 set for next character only
Character Attributes:
turn off attributes - normal video
turn off attributes - normal video
turn on underline mode
turn on inverse video mode
On color systems underlined characters are displayed in blue
Line Attributes:
double high (top half) - double wide
double high (bottom half) - double wide
single wide - single height
double wide - single height
erase to end of line (inclusive)
erase to end of line (inclusive)
erase to beginning of line (inclusive)
erase entire line (cursor doesn't move)
erase to end of screen (inclusive)
erase to end of screen (inclusive)
erase to beginning of screen (inclusive)
erase entire screen (cursor doesn't move)
Tabulation:
set tab in current position
clear tab stop in current position
clear tab stop in current position
clear all tab stops
print page
print page
print line
ESC [ ? 4 i
auto print off
ESC [ ? 5 i
auto print on
print controller off
print controller on
Requests / Reports:
request for terminal status
report - no malfunction
request for cursor position report
report - cursor at line pl, & column pc
ESC [ ? 1 5 n
request printer status
ESC [ ? 1 0 n
report - printer ready
request to identify terminal type
request to identify terminal type
request to identify terminal type
ESC [ ? 1;0 c
report - type VT100
Initialization / Tests:
reset to initial state
ESC [ 2 ; 1 y
power up test
ESC [ 2 ; 2 y
loop back test
ESC [ 2 ; 9 y
power up test till failure or power down
ESC [ 2 ; 10 y
loop back test till failure or power down
video alignment test-fill screen with E's
Setup Functions:
ESC [ ? 2 l
enter VT52 mode
exit VT52 mode
ESC [ ? 3 h
132 column mode
ESC [ ? 3 l
80 column mode
ESC [ ? 4 h
smooth scroll
ESC [ ? 4 l
jump scroll
ESC [ ? 5 h
black characters on white screen mode
ESC [ ? 5 l
white characters on black screen mode
ESC [ ? 7 h
auto wrap to new line
ESC [ ? 7 l
auto wrap off
ESC [ ? 8 h
keyboard auto repeat mode on
ESC [ ? 8 l
keyboard auto repeat mode off
ESC [ ? 9 h
480 scan line mode
ESC [ ? 9 l
240 scan line mode
ESC [ ? 1 8 h
print form feed on
ESC [ ? 1 8 l
print form feed off
ESC [ ? 1 9 h
print whole screen
ESC [ ? 1 9 l
print only scroll region
ESC [ 2 0 h
newline mode LF, FF, VT, CR = CR/LF)
ESC [ 2 0 l
line feed mode (LF, FF, VT = LF ; CR = CR)
LED Functions:
turn off LED 1-4
turn on LED #1
turn on LED #2
turn on LED #3
turn on LED #4
The bottom line of the screen is used as a status line by the
VT100 emulation.
The information on the bottom line is:
the status of the four VT100 LED's
of the numeric
(application mode /normal mode)
the cursor
(application mode/normal
Interpreted Control Characters:
- selects G0 character set
shift out - selects G1 character set
VT100 KEYBOARD MAP
The following table describes the special function keys of the
VT100 and shows the transmitted sequences.
It also shows the key
key sequence required to produce this function on the
VT100 has four function keys PF1 - PF4,
four arrow
keys, and a numeric keypad with 0-9,
RETURN and
The numeric
the arrow keys may be in standard
applications mode as set by the host computer.
Sequences will be
sent as follows:
Press Key on
Applications
IBM Keypad
=====================================================
NUMLOK - On
* (on PrtSc key)
NUMLOK - Off
Note that either set of keys may be used to send VT100 arrow keys.
The Alt 9,0,-, and = do not require NumLok to be off.
Functions:
PF1 - Gold
PF2 - Help
PF3 - Next
PF4 - DelBrk ESC O S
Please note that the backspace key transmits an ascii DEL
(character 127) while in VT100 emulation.
To get a true ascii
backspace (character 8) you must press control-backspace.
mmencode/mmdecode
Written by
man mmencode states
"mimencode - Translate to and from mail-oriented encoding
Description
The mimencode program simply converts a byte stream into (or
out of) one of the standard mail encoding formats defined by
MIME, the proposed standard for internet multimedia mail
Such an encoding is necessary because binary data
cannot be sent through the mail.
The encodings understood
by mimencode are preferable to the use of the
uuencode/uudecode programs, for use in mail, in several
respects that were important to the authors of MIME.
The man pages don't tell you how it does it, this is the discussion of
this short note
mmencode by default uses a system previously known as "base64".
Basically, consider the bytes of a file lines up
one after the
other in a long stream. Now move along this stream taking 6 bits at a
time and encode them using some "dictionary" of printable characters.
The only trick now is to know what dictionary mmencode actually uses.
It is given below.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/
For example if the current 6 bits happen to be 000001 then the letter B
is written to the mmencoded file.
If 111110 is encountered then + is written to the mmencoded file.
There are a number of way of encoding binary file into text only
files for various restrictive transmission channels. Generally
they are all very similar except for the bit length they use and the
dictionary that maps whatever number of bits to a printable character.
The two most common alternative formats are hqx which is generally
used on Macintosh systems, and uuencode which is used on UNIX.
MacBinary format
Originally by Peter Olson
Compiled by
November 1990
Introduction
MacBinary is a binary (non-text) format that encodes Macintosh files so that they can be safely stored or transfered through non-Macintosh systems.
MacBinary combines the two forks of a Mac file, together with the file information (Name, Creator Application, File Type, etc) into a single binary data stream, suitable for storage on non-Mac systems.
This serves a similar purpose to BinHex, except that BinHex takes things even further and stores the file using only text characters, so that the file will be preserved on almost any system, and can be sent through Email or USENET News without loss or corruption.
MacBinary II is the current standard for the MacBinary format.
I have further extended the format to allow the encoding of folder hierarchies into a single MacBinary II+ file.
But be warned, currently no one else implements this extension, and it may well be that no one else ever will, so the only program you can use to decode folders stored in MacBinary II+ format is this one.
Note that this does not affect files stored in MacBinary II format, since files use the MacBinary II format without the new extensions, so any MacBinary decoder should work happily.
Specification
This is a preliminary specification of an extension to the MacBinary II
Standard to allow MacBinary to incorporate a directory tree in a similar
way to a unix tar file.
This is done by a fairly simple extension to
the standard (which is documented separately, and which you should be
familiar with before reading this), basically, I defined a 128 byte
block that marks the start of a folder, and another one that marks the
end of the folder, and then set it up like this:
start block for folder "Folder1"
file1 - standard macbinary format
start block for "Folder2"
While the end block doesn't actually need to contain any information, its
format is similar to the header block for consistency.
Start Block:
Offset 000-version 1 - this is incompatible with previous decoders.
Offset 001-Byte, Length of foldername (must be in the range 1-63)
Offset 002-1 to 63 chars, foldername (only "length" bytes are significant,
the rest should be zero).
Offset 065-Long Word, file type - 'fold'
Offset 069-Long Word, file creator - $FFFFFFFF
Offset 073-Byte, original Finder flags of folder (high byte)
Offset 074-Byte, zero fill, must be zero for compatibility
Offset 075-Word, folder's vertical position within its window.
Offset 077-Word, folder's horizontal position within its window.
Offset 079-Word, folder's window or folder ID.
Offset 081-Byte, "Protected" flag (in low order bit).
Offset 082-Byte, zero fill, must be zero for compatibility
Offset 083-Long Word, Data Fork length 0
Offset 087-Long Word, Resource Fork length 0
Offset 091-Long Word, Folder's creation date
Offset 095-Long Word, Folder's "last modified" date.
Offset 099-Word, length of Get Info comment to be sent after the resource
fork (if implemented, see below).
*Offset 101-Byte, Finder Flags, bits 0-7. (Bits 8-15 are already in byte 73)
*Offset 116-Long Word, Length of total files when packed files are unpacked.
This may be zero to avoid having to preparse the folder when
creating the MacBinary file.
*Offset 120-Word, Length of a secondary header.
If this is non-zero,
Skip this many bytes (rounded up to the next multiple of 128)
This is for future expansion only, when sending files with
MacBinary, this word should be zero.
*Offset 122-Byte, Version number of Macbinary II - 130
*Offset 123-Byte, Minimum MacBinary II version needed to read this file - 130
*Offset 124-Word, CRC of previous 124 bytes
The secondary header length MAY be non-zero, and if so, the secondary
header immediately follows the Start Block, padded to a multiple of 128 bytes
The comment length MAY be non-zero, and if so, the comment immediately
follows the Start Block or secondary header, padded to a multiple of 128
bytes as usual.
End Block:
Offset 000-version 1 - this is incompatible with previous decoders.
Offset 065-Long Word, file type - 'fold'
Offset 069-Long Word, file creator - $FFFFFFFE
*Offset 116-Long Word, Length of total files when packed files are unpacked.
This may be zero.
*Offset 120-Word, Length of a secondary header.
If this is non-zero,
Skip this many bytes (rounded up to the next multiple of 128)
This is for future expansion only, when sending files with
MacBinary, this word should be zero.
*Offset 122-Byte, Version number of Macbinary II - 130
*Offset 123-Byte, Minimum MacBinary II version needed to read this file - 130
*Offset 124-Word, CRC of previous 124 bytes
This block is static except for the total length field, which may be
zero as well, in which case its totally static.
You should recognize the Start and End blocks by the version, file type and
creator fields.
Decoders MUST NOT rely on ANY other fields in the End Block
being valid.
Encoders MAY fill them out to look like a start block, or may
zero-fill them.
Encoders SHOULD zero-fill any bytes not explicitly set -
this applies to all header blocks and all padding.
All internal files should have version 0, MacBinary II version 129,129.
An extended MacBinary file MUST start with a Start Block.
MacBinary II+ file is either:
1) A MacBinary II file encoding a single file, OR
2) A MacBinary II+ file encoding a single folder.
Revised standard
These are the new changes to the MacBinary Standard, as generally agreed
upon in the MacBinary II Conference 6/21/87, and as changed in the followup
conference 6/28/87.
Revised 7/24/87 to reflect suggestions and clarifications
that came later, and to include all necessary information needed from the
original MacBinary standard document to implement MacBinary II.
The new standard will be very similar to the original MacBinary standard as
described in [MacBinary Standard].
(Reading the original standard is
recommended for a full understanding of implementation and philosophy
behind the MacBinary I and II formats.)
The binary format consists of a
128-byte header containing all the information necessary to reproduce the
document's directory entry on the receiving M followed by the
document's Data Fork (if it has one), padded with nulls to a multiple of
128 bytes (if necessary); followed by the document's Resource Fork (again,
padded if necessary). The lengths of these forks (either or both of which
may be zero) are contained in the header.
Header format
Offset 000-Byte, old version number, must be kept at zero for compatibility
Offset 001-Byte, Length of filename (must be in the range 1-63)
Offset 002-1 to 63 chars, filename (only "length" bytes are significant).
Offset 065-Long Word, file type (normally expressed as four characters)
Offset 069-Long Word, file creator (normally expressed as four characters)
Offset 073-Byte, original Finder flags
Bit 7 - Locked.
Bit 6 - Invisible.
Bit 5 - Bundle.
Bit 4 - System.
Bit 3 - Bozo.
Bit 2 - Busy.
Bit 1 - Changed.
Bit 0 - Inited.
Offset 074-Byte, zero fill, must be zero for compatibility
Offset 075-Word, file's vertical position within its window.
Offset 077-Word, file's horizontal position within its window.
Offset 079-Word, file's window or folder ID.
Offset 081-Byte, "Protected" flag (in low order bit).
Offset 082-Byte, zero fill, must be zero for compatibility
Offset 083-Long Word, Data Fork length (bytes, zero if no Data Fork).
Offset 087-Long Word, Resource Fork length (bytes, zero if no R.F.).
Offset 091-Long Word, File's creation date
Offset 095-Long Word, File's "last modified" date.
Offset 099-Word, length of Get Info comment to be sent after the resource
fork (if implemented, see below).
*Offset 101-Byte, Finder Flags, bits 0-7. (Bits 8-15 are already in byte 73)
*Offset 116-Long Word, Length of total files when packed files are unpacked.
This is only used by programs that pack and unpack on the fly,
mimicking a standalone utility such as PackIt.
A program that is
uploading a single file must zero this location when sending a
Programs that do not unpack/uncompress files when
downloading may ignore this value.
*Offset 120-Word, Length of a secondary header.
If this is non-zero,
Skip this many bytes (rounded up to the next multiple of 128)
This is for future expansion only, when sending files with
MacBinary, this word should be zero.
*Offset 122-Byte, Version number of Macbinary II that the uploading program
is written for (the version begins at 129)
*Offset 123-Byte, Minimum MacBinary II version needed to read this file
(start this value at 129 129)
*Offset 124-Word, CRC of previous 124 bytes
* This is newly defined for MacBinary II.
All values are stored in normal 68000 order, with Most Significant Byte
appearing first then the file.
Any bytes in the header not defined above
should be set to zero.
The original MacBinary format was amended to include the sending of the FCMT
(Get Info comment) after the resource fork was sent, if the length for such
comment, given in offset 99, is not zero.
To the best of our knowledge, no
program has implemented this feature, due to Apple's stated position that no
program should read or write these comments.
The definition remains in
MacBinary II, so that should Apple ever provide a documented way of reading and
writing these comments, terminal programs will be able to take advantage of
this feature.
All Finder flags and information would be uploaded, however, a downloading
program should clear the Finder flag bits of
0 - Set if file/folder is on the desktop (Finder 5.0 and later)
1 - bFOwnAppl (used internally)
8 - Inited (seen by Finder)
9 - Changed (used internally by Finder)
10 - Busy (copied from File System busy bit)
Also, fdLocation and fdFldr should be zeroed
To determine if a header is a valid
MacBinary header, check bytes 0 and 74 to
be both zero.
If they are both zero, either (a) the CRC should match, which
means it is a MB II file, or (b) byte 82 is zero, which means it may be a MB I
(Note that, at the current version level, byte 82 is kept zero to
maintain compatibility with MacBinary I. If at some point the MacBinary
versions change sufficiently that it is necessary to keep MacBinary I programs
from downloading these files, we can change byte 82 to non-zero.)
If the header is a MB II header, the program will check the minimum version
byte, to see if it knows enough to decode the file.
If the minimum version in
the header is greater than the version that the terminal program was written
for, it will download the file as pure XModem (creating a "TEXT" file) and
notify the user that conversion is needed because the MacBinary version was too
If the header does NOT represent a valid MB II header, the program must at
minimum check byte 82 to be zero--if it is not zero, the file is not a MB I
It is possible to write a much more robust routine, by checking the
following:
Offsets 101-125, Byte, should all be 0.
Offset 2, Byte, (the length of the file name) should be in the range of 1-63.
Offsets 83 and 87, Long Word, (the length of the forks) should be in the
range of 0-$007F FFFF.
If any of these tests fail, the file is not a valid MacBinary file.
still be desirable to distinguish between text files and foreign binary files
(for stripping line feeds or similar helpful acts).
Some tests that would
prove useful include:
A quantity of bytes in the first block with the high bit set would point to
a binary file (though this could be fooled by files with many extended
ascii characters, such as generated by the option key on a Mac).
A large quantity of zero bytes (nulls) would also point to a binary file.
CSV - Comma Separated Value
Written by
April 2000
The CSV (Comma Separated Value) format is a straightforward (mostly) way
of transfering data between programs. It is typically used for spreadsheet
and database applications because it is suited to data arranged in a table,
that is, made up of rows and columns.
In it's simplest form a CSV file consists of records and fields. The records
are separated by any combination of linefeeds, carriage control, or a carriage
control linefeed pairs. Fields are separated by commas and any leading or trailing
spaces are removed from fields.
For example the following has two records each with four fields.
1,tree,december,1999
5,bush,january, 2000
The above begs the question, "What if my field contains leading or trailing
spaces, commas, linefeeds,
or carriage control characters?". The answer is to enclose fields in double quotes.
Note that this means that records can span lines.
The following example has two records each with three fields.
1," tree","december, 1999"
5,bush,"january, 2000"
So what about fields that contain double quotes? These are represented by two
double quotes, the field itself must also be enclosed in double quotes. For example
the first field in the following becomes
I said "stop".
"I said ""stop""","January 2000","5pm"
In the vast majority of cases CSV is used to transfer human readable ascii
data, however there is no reason why it can't be used for more general binary