diff options
| author | Kenichi Handa | 2003-05-06 12:29:02 +0000 |
|---|---|---|
| committer | Kenichi Handa | 2003-05-06 12:29:02 +0000 |
| commit | 0ea1a6ca28aa172454d2b4b4a46df2af69459b15 (patch) | |
| tree | 4367a30a4e61cee00445fc98cf4f945458ee92bd | |
| parent | b49a1807a984553f0bb9c1e2d3d16d306c2d13d0 (diff) | |
| download | emacs-0ea1a6ca28aa172454d2b4b4a46df2af69459b15.tar.gz emacs-0ea1a6ca28aa172454d2b4b4a46df2af69459b15.zip | |
(define-coding-system): Fix docstring about :bom and :endian.
| -rw-r--r-- | lisp/international/mule.el | 18 |
1 files changed, 14 insertions, 4 deletions
diff --git a/lisp/international/mule.el b/lisp/international/mule.el index df3455ab4d0..1be00688428 100644 --- a/lisp/international/mule.el +++ b/lisp/international/mule.el | |||
| @@ -439,9 +439,6 @@ of ASCII. | |||
| 439 | If `use-oldjis' is specified, JIS0208-1976 is designated instead of | 439 | If `use-oldjis' is specified, JIS0208-1976 is designated instead of |
| 440 | JIS0208-1983.") | 440 | JIS0208-1983.") |
| 441 | 441 | ||
| 442 | ;; Fixme: Are translation tables still relevant? (Not currently | ||
| 443 | ;; implemented, anyway.) | ||
| 444 | ;; Fixme: What does cons :bom mean? Explanation of :endian. | ||
| 445 | (defun define-coding-system (name docstring &rest props) | 442 | (defun define-coding-system (name docstring &rest props) |
| 446 | "Define NAME (a symbol) as a coding system with DOCSTRING and attributes. | 443 | "Define NAME (a symbol) as a coding system with DOCSTRING and attributes. |
| 447 | The remaining arguments must come in pairs ATTRIBUTE VALUE. ATTRIBUTE | 444 | The remaining arguments must come in pairs ATTRIBUTE VALUE. ATTRIBUTE |
| @@ -559,11 +556,24 @@ This attributes specifies whether the coding system uses a `byte order | |||
| 559 | mark'. VALUE must nil, t, or cons of coding systems whose | 556 | mark'. VALUE must nil, t, or cons of coding systems whose |
| 560 | `:coding-type' is `utf-16'. | 557 | `:coding-type' is `utf-16'. |
| 561 | 558 | ||
| 559 | If the value is nil, on decoding, don't treat the first two-byte as | ||
| 560 | BOM, and on encoding, don't produce BOM bytes. | ||
| 561 | |||
| 562 | If the value is t, on decoding, skip the first two-byte as BOM, and on | ||
| 563 | encoding, produce BOM bytes accoding to the value of `:endian'. | ||
| 564 | |||
| 565 | If the value is cons, on decoding, check the first two-byte. If theyq | ||
| 566 | are 0xFE 0xFF, use the car part coding system of the value. If they | ||
| 567 | are 0xFF 0xFE, use the car part coding system of the value. | ||
| 568 | Otherwise, treat them as bytes for a normal character. On encoding, | ||
| 569 | produce BOM bytes accoding to the value of `:endian'. | ||
| 570 | |||
| 562 | This attribute has a meaning only when `:coding-type' is `utf-16'. | 571 | This attribute has a meaning only when `:coding-type' is `utf-16'. |
| 563 | 572 | ||
| 564 | `:endian' | 573 | `:endian' |
| 565 | 574 | ||
| 566 | VALUE must be t or nil. See the above description for the detail. | 575 | VALUE must be `big' or `little' specifying big-endian and |
| 576 | little-endian respectively. The default value is `big'. | ||
| 567 | 577 | ||
| 568 | This attribute has a meaning only when `:coding-type' is `utf-16'. | 578 | This attribute has a meaning only when `:coding-type' is `utf-16'. |
| 569 | 579 | ||