附属書1 HTML 4.01への変更点

Appendix A: Changes

参考  附属書1では,TR X 0033:2000の作成作業終了前後に,W3Cから1999年12月24日に発行されたHTML 4.01とTR X 0033:2000との間の変更点を示す。附属書1は,W3CによるHTML 4.01の原規定のAnnex Aから,TR X 0033:2000の附属書Aに含まれている部分を除いた,HTML 4.01への変更点の部分(A.1だけ)を翻訳したものである。なお,TR X 0033:2000作成時に見つけられ既にTRでは修正済みの誤り又は翻訳上目立たない誤りも混在している。これらのTR X 0033:2000には適用する必要のないものについては,参考によってそのことを明示する。

附1.1 TR X 0033:2000とHTML 4.01の1999年12月24日版との間での変更

A.1 Changes between 24 April 1998 HTML 4.0 and 24 December 1999 HTML 4.01 versions

附1.1では,HTML 4.01規定の1999年12月24日版がTR X 0033:2000(HTML 4.0規定の1998年4月24日版と同等)と異なる点を示す。

This section describes how the 24 December 1999 version of the HTML 4.01 specification differs from the 24 April 1998 version of the HTML 4.0 specification.

附1.1.1 規定への変更
Changes to the specification

一般的な変更
General changes
 

SGML及びHTML
On SGML and HTML
 

HTML文書表現
HTML Document Representation
 

基本HTMLデータ型
Basic HTML data types
 

HTML文書の大域的構造
Global structure of an HTML document
 

言語情報及びテキスト方向
Language information and text direction
 

Tables
 

リンク
Links
 

オブジェクト,画像及びアプレット
Objects, Images, and Applets
 

HTML文書におけるスタイルシート
Style Sheets in HTML Documents
 

フレーム
Frames
 

フォーム
Forms
 

SGML宣言
SGML Declaration
 

厳密DTD
Strict DTD
 

備考
Notes
 

文献
References
 

附1.1.2 HTML 4.01において修正済みの既知の誤り
Errors that were corrected

13.6.1
Section 13.6.1
"poly"を使用した画像マップの例は,閉じられた多角形を形成するように修正された。座標の最後の対は,多角形を閉じるために座標の最初の対と同じになっている。
Image map examples using "poly" have been fixed to form a closed polygon. Also, the last pair of coordinates is the same as the first to close the polygon.
14.4.1
Section 14.4.1
最後の例において,STYLE要素は,属性の割当て"media=screen, print"を欠いている。
In the final example, the STYLE element is missing the attribute assignment "media=screen, print".
15.2.1
Section 15.2.1
"mypar"を用いた例で,CSS規則は,次のとおりになるのが望ましい。
In the example with "mypar", the CSS rule should read
  P#mypar {font-style: italic; color: blue}

CSSでは,"#"はID名を参照し,"."はクラス名を参照する。この例は,"id"属性を取り扱っている。

In CSS, "#" refers to an ID name while the "." refers to a class name. This example is dealing with the "id" attribute.

16.2.2
Section 16.2.2
marginwidth及びmarginheightに対する値は,1画素以上ではなく0画素以上でなければならない。
Values for marginwidth and marginheight must be 0 pixels or more, not 1 pixel or more.
16.2.2
Section 16.2.2
FRAME要素は,target属性を取らない。
The FRAME element does not take the target attribute.
16.5
Section 16.5
IFRAME要素は,target属性を取らない。
The IFRAME element does not take the target attribute.
17.2.1
Section 17.2.1
"checkboxes"の記述において,"制御要素の選択された属性が設定される場合("when the control element's selected attribute is set)"の中の,"選択される(selected)"を"チェックされる(checked)"に変更する。
In the description of "checkboxes", change "selected" to "checked" in "when the control element's selected attribute is set."
17.6.1
Section 17.6.1
OPTGROUP要素に対する"他の箇所で定義される属性"の箇条において,onfocus属性,onblur属性及びonchange属性は存在しないほうがよい。
In the "Attributes defined elsewhere" section for the OPTGROUP element, the attributes onfocus, onblur, and onchange should not be there.
18.2.3
Section 18.2.3
onfocus及びonblurをとる要素のリストに対して,A及びAREAを追加する。
To the list of elements that take onfocus and onblur, add A and AREA.
20.
Section 20
HTML 4のためのSGML宣言は,16進の数値文字参照をサポートするために若干修正しなければならない。これを次に示す。
The SGML Declaration for HTML 4 must be modified slightly to support hexadecimal numeric character references. The lines:
        DELIM
               GENERAL SGMLREF
               SHORTREF SGMLREF

これらの行は,次のとおりに変更されなければならない。

must be changed to:

        DELIM
               GENERAL SGMLREF
               HCRO "&#x" -- 38 is the number for ampersand --
               SHORTREF SGMLREF

さらに,最初の<!SGML "ISO 8879:1986"は,<!SGML "ISO 8879:1986 (WWW)"に変更されなければならない。

And the initial <!SGML "ISO 8879:1986" must be changed to <!SGML "ISO 8879:1986 (WWW)".

21.
Section 21
HR要素は,lang属性及びdir属性もとることが望ましい。これらは,要素の定義において他の箇所で定義されるとして注意されるが,DTDには記載されないままとされた。
The HR element should also take the lang and dir attributes. These are noted as being defined elsewhere at the element's definition, but were left out of the DTDs.
21.
Section 21
OBJECT要素のarchive属性は,型%URIの値をとるとしてDTDで定義されている。これは正しくない。値は,(属性の定義において及びDTDの注釈において示されているとおり)URIのスペースで区切られたリストとなることができる。
The OBJECT element's archive attribute is defined in the DTD as taking a value of type %URI". This is incorrect: the value may be a space-separated list of URIs (as indicated in the definition of the attribute and in the DTD comment).
FORM要素のDTD素片は,要素の定義においてリストとされている,accept属性に対する定義を取り込むことが望ましい。その定義は,次によるのが望ましい。
The FORM element's DTD fragment should include a definition for the accept attribute, which is listed in the element's definition. The definition should be the following:
 accept  %ContentTypes;  #IMPLIED  -- list of MIME types for file upload --
B.4.1
Section B.4.1
箇条の最後の次の文,すなわち,"contentにおける語(のリスト)は,ALL,INDEX,NOFOLLOW,又はNOINDEXとする。name及びcontentの属性値は,大文字及び小文字を区別しない。(The list of terms in the content is ALL, INDEX, NOFOLLOW, NOINDEX. The name and the content attribute values are case-insensitive.)",は正しくない。実際,META定義は,name属性及びcontent属性に対する値は,大文字及び小文字を区別する,と指定する。
At the end of the section, the following sentences are incorrect: "The list of terms in the content is ALL, INDEX, NOFOLLOW, NOINDEX. The name and the content attribute values are case-insensitive." In fact, the META definition specifies that values for the name and content attributes are case-sensitive.
B.4.1の"robots.txtファイル"
Section B.4.1.1
規定は,"空行は認められない。(Blank lines are not permitted.)",と読める。空行は,robots.txtファイルの中では許されており,単に一つの"レコード"内では許されない。規定はレコードを定義していないことに注意。
The specification reads, "Blank lines are not permitted." Blank lines are permitted in the robots.txt file, just not within a single "record". Note that the specification doesn't define record.

さらに,規定は,"レコードごとに,ただ一つの"User-agent"フィールドが存在していなければならない。(There must be exactly one "User-agent" field per record.)"としている。実際には,robots.txtファイルの中では二つ以上のUser-Agentが存在可能であって,単にレコードごとには多くとも一つ存在できる。

Further down the page, the specification reads, "There must be exactly one "User-agent" field per record." In fact, there can be more than one User-Agent field in the robots.txt file, just not more than one per record.

検索ロボットについての情報は,例えば,次を参考にすること。

For information about search robots, please consult, for example:

文献
References
  • [URI]の参照は,1998年8月のRFC 2396に,次のとおりに,更新するのが望ましい。すなわち,"Uniform Resource Identifiers (URI): Generic Syntax", T. Berners-Lee, R. Fielding, L. Masinter, August 1998. RFC 2396は,[RFC1738]及び[RFC1808]を更新している。
    The [URI] reference should be updated to RFC 2396 as of August 1998. "Uniform Resource Identifiers (URI): Generic Syntax", T. Berners-Lee, R. Fielding, L. Masinter, August 1998. RFC 2396 updates [RFC1738] and [RFC1808].

附1.1.3 HTML 4.01において修正済みの些細な印刷上の誤り
Minor typographical errors that were corrected

2.1.1
Section 2.1.1
""/TR/REC-html4/"というパスでアクセスできる。(accessible via the path "/TR/REC-html4/")"という句は,"/TR/REC-html40/"となることが望ましい。
The phrase "accessible via the path "/TR/REC-html4/". should end with "/TR/REC-html40/".
2.1.3
Section 2.1.3
3番目の箇条記号("c)")における,語"applets"は"applet"となることが望ましい。
参考 TR X 0033:2000では,修正は不要。
In the third bullet, the word "applets" should be "applet".
3.3
Section 3.3
2番目の箇条記号("b)")において,文"Whether the element's end tag is optional."は,"Whether the element's tags are optional."となることが望ましい。
参考 TR X 0033:2000では,修正は不要。
In bullet two, the sentence "Whether the element's end tag is optional." should read "Whether the element's tags are optional."
3.2.1
Section 3.2.1
"SGMLの規格を参照されたい(Please consult the SGML standard)"がある文で始まる段落において,句"一つの終了タグは, マッチする開始タグ(7.5.1)まですべての省略された開始タグを閉じる[an end tag closes all omitted start tags up to the matching start tag (section 7.5.1)]"は,"一つの終了タグは, マッチする開始タグまで戻って,省略された終了タグをもつすべての閉じていない途中にある開始タグを閉じる(an end tag closes, back to the matching start tag, all unclosed intervening start tags with omitted end tags)"となるのが望ましい。
In the sentence beginning "Please consult the SGML standard", the phrase "an end tag closes all omitted start tags up to the matching start tag (section 7.5.1)" should read "an end tag closes, back to the matching start tag, all unclosed intervening start tags with omitted end tags".
3.2.2
Section 3.2.2
"Attribute names are always case-insensitive"には,最後にピリオドがない。
参考 TR X 0033:2000では,修正は不要。
"Attribute names are always case-insensitive" is missing a final period.
3.3.4の"論理属性"
Section 3.3.4.2
OPTION要素をもつ例は,不適格な終了タグをもっている。</OPTION>となることが望ましい。
The example with the OPTION element has an improper end tag; it should be </OPTION>.

箇条の後の方の,"Authors should be aware than"で始まる文は,代わりに,"aware that"となることが望ましい。
参考 TR X 0033:2000では,修正は不要。

Later in the section, the sentence that begins "Authors should be aware than" should say "aware that" instead.

5.2.2
Section 5.2.2
"ASCII文字(ASCII characters)"を"ASCII値のバイト(ASCII-valued bytes)"に変更する。
Change "ASCII characters" to ASCII-valued bytes".
5.3.1
Section 5.3.1
2番目の箇条記号の"where H is an hexadecimal number"における"an"の代わりに"a"となることが望ましい。
参考 TR X 0033:2000では,修正は不要。
The second bullet should read "a" instead of "an" in "where H is an hexadecimal number".
6.5.1
Section 6.5.1
最初の文は,語"document"の前に不定冠詞の"a"を必要とする。
参考 TR X 0033:2000では,修正は不要。
The first sentence needs the indefinite article "a" before the word "document".
6.10
Section 6.10
最初の文は,語"single"の前に不定冠詞の"a"を必要とする。
参考 TR X 0033:2000では,修正は不要。
The first sentence needs the indefinite article "a" before the word "single".
6.12
Section 6.12
"Next"の下の"in an linear"は,代わりに,"in a linear"となることが望ましい。
参考 TR X 0033:2000では,修正は不要。
Under "Next", "in an linear" should read "in a linear" instead.
6.16
Section 6.16
"cancelling"を"canceling"に変更する。
参考 TR X 0033:2000では,修正は不要。
Change "cancelling" to "canceling".
7.4.4の"メタデータのプロファイル"
Section 7.4.4.3
"scheme属性によって...(The scheme attribute allows...)"で始まる段落において,"Month-Date-Year"を"Month-Day-Year"に置き換える。
参考 TR X 0033:2000では,修正は不要。
In the paragraph beginning "The scheme attribute allows...", replace "Month-Date-Year" with "Month-Day-Year".
7.5.4
Section 7.5.4
例の後の文において,"declaration"を複数にする。
参考 TR X 0033:2000では,修正は不要。
In the sentence after the example, make "declaration" plural.
7.5.6
Section 7.5.6
ADDRESS要素に対する,"他の箇所で定義される属性(Attributes defined elsewhere)"の箇条において,style及びtitleが抜けている。
For the ADDRESS element, in the section "Attributes defined elsewhere", style and title are missing.

また,"他の箇所で定義される属性(Attributes defined elsewhere)"の箇条の後の,"contact information for document"において,"document"の前に"a"を置く。
参考 TR X 0033:2000では,修正は不要。

Also, after the section on "Attributes defined elsewhere", in "contact information for document", put "a" before "document".

8.2.3
Section 8.2.3
"Authors may also use special Unicode characters to achieve multiply"において,最後は,"multiple"に変更する。
参考 TR X 0033:2000では,修正は不要。
In "Authors may also use special Unicode characters to achieve multiply" change to "multiple" at the end.
11.2.4の"COLGROUP 要素"
Section 11.2.4.1
文"The first COL element refers to the first 39 columns (doing nothing special to them) and the second one assigns an id value to the fortieth columns so that style sheets may refer to it."は,代わりに,"fortieth column"とする。
参考 TR X 0033:2000では,修正は不要。
The sentence "The first COL element refers to the first 39 columns (doing nothing special to them) and the second one assigns an id value to the fortieth columns so that style sheets may refer to it." should have "fortieth column" instead.
11.2.5
Section 11.2.5
TR要素に対する,"他の箇所で定義される属性(Attributes defined elsewhere)"の箇条において,bgcolorが抜けている。
For the TR element, in the section "Attributes defined elsewhere", bgcolor is missing.
11.2.6
Section 11.2.6
TH要素及びTD要素に対して,width属性height属性の型を,百分率値を許すために,"%Pixels;"から"%Length;"へと変更する。
For the TH and TD elements, the type of the width and height attributes is changed from "%Pixels;" to "%Length;" to allow for percentage values.
11.3.1
Section 11.3.1
frame属性定義の最初の文で,"that surrounds"の代わりに"surrounding"を使用する。
参考 TR X 0033:2000では,修正は不要。
In the first sentence of the frame attribute definition, use "surrounding" instead of "that surrounds".
11.4.1
Section 11.4.1
最初の箇条記号の3番目の文,"Note that its not always possible"は,代わりに,"it's"をもつ。
参考 TR X 0033:2000では,修正は不要。
First bullet, third sentence. "Note that its not always possible" should have "it's" instead.
12.1.2
Section 12.1.2
最後の文は,"Further information is given below on using links for..."となるのが望ましい。すなわち,"of"を"on"に変更する。この文は,その閉じの句読点も抜けている。
参考 TR X 0033:2000では,修正は不要。
The last sentence should read "Further information is given below on using links for..." (change "of" to "on"). This sentence is also missing its closing punctuation.
12.2.2
Section 12.2.2
最後の段落は,"Since the DTD defines the LINK element to be empty..."となるのが望ましい。すなわち,"LINK"の前に定冠詞の"the"を挿入する。
参考 TR X 0033:2000では,修正は不要。
The last paragraph should read "Since the DTD defines the LINK element to be empty..." (insert definite article "the" before "LINK").
12.2.3
Section 12.2.3
12.2.4の直前の3番目の箇条項目。"richer anchors names"は"richer anchor names"とするのが望ましい。
参考 TR X 0033:2000では,修正は不要。
Just before section 12.2.4, the third bullet. "richer anchors names" should read "richer anchor names".
13.3.4
Section 13.3.4
"次の例は,...(In the following example...)"で始まる段落において,句"cause it so be instantiated"は"cause it to be instantiated"に変更されるのが望ましい。すなわち,"so"を"to"に変更する。
参考 TR X 0033:2000では,修正は不要。
In the paragraph that begins "In the following example...", the phrase "cause it so be instantiated" should be changed to cause it to be instantiated" (change "so" to "to").
13.4
Section 13.4
推奨しない例の直後,文"This example may be rewritten as follows with OBJECT as follows:"は,"This example may be rewritten with OBJECT as follows:"となるのが望ましい。
参考 TR X 0033:2000では,修正は不要。
Just after the deprecated example, the sentence "This example may be rewritten as follows with OBJECT as follows:" should say "This example may be rewritten with OBJECT as follows:".
13.6.1
Section 13.6.1
"coords"属性の下,語"and"を,語"a"に対して置き換えるのが望ましい。そこで,文は,"この属性は,画面上の位置及び形状を指定する。(This attribute specifies the position and shape on the screen.)",となる。
Under the "coords" attribute, the word "and" should be substituted for the word "a" so the sentence reads, "This attribute specifies the position and shape on the screen."
13.7.1
Section 13.7.1
height属性の定義に対して,句"Image and object override"は,"Image and object height override"となるのが望ましい。
参考 TR X 0033:2000では,修正は不要。
In the definition of the height attribute, the phrase "Image and object override" should read "Image and object height override".
15.1.3の"オブジェクトの浮動"
Section 15.1.3.1
下位見出し"オブジェクトの浮動(Float an object)"の下,最初の段落の,語"object"の最初の使用は,"objects"となるのが望ましい。
参考 TR X 0033:2000では,修正は不要。
Under the subheading "Float an object", in the first paragraph, the first use of the word "object" should be "objects".
15.1.3の"オブジェクト周囲のテキストの浮動"
Section 15.1.3.2
"推奨しない(Deprecated)"例における最初の文は,"If the clear attribute is set to left or all, the next line will appear as follows:"となるのが望ましい。すなわち,"next line"の前に"the"を挿入する。
参考 TR X 0033:2000では,修正は不要。
In the "Deprecated" example, the first sentence should read "If the clear attribute is set to left or all, the next line will appear as follows:" ("the" before "next line").
15.3
Section 15.3
HRalign属性は,他の箇所では定義されていない。
The align attribute for HR is not defined elsewhere.
16.1
Section 16.1
最初の段落の最後の文において,語"though"は"through"となるのが望ましい。
参考 TR X 0033:2000では,修正は不要。
In the last sentence of the first paragraph, the word "though" should be "through".
16.3.1
Section 16.3.1
2番目の文において,語"factorizing"は"factoring"となるのが望ましい。
参考 TR X 0033:2000では,修正は不要。
In the second sentence, the word "factorizing" should be "factoring".
16.4.1
Section 16.4.1
"他の箇所で定義される属性(attributes defined elsewhere)"のリストが,不用意にも,NOFRAMESの定義の後に省略されていた。これら属性は,次のとおり。class属性,id属性,lang属性,dir属性,title属性,style属性,及び%events;属性。
The list of "attributes defined elsewhere" was inadvertently omitted after the definition of NOFRAMES. These attributes are: class, id, lang, dir, title, style, and the %events; attributes.
17.1
Section 17.1
"(entering text, selecting menu items, etc.)"において,"text"の後に","を追加する。
参考 TR X 0033:2000では,修正は不要。
In "(entering text, selecting menu items, etc.)", add the "," after "text".
17.5
Section 17.5
"Visual user agents may render..."で開始する段落において,不定冠詞の"a"を,語"flat"の前から取り除くのが望ましい。
参考 TR X 0033:2000では,修正は不要。
In the paragraph that begins "Visual user agents may render...", the indefinite article "a" should be removed from before the word "flat".
17.12.1
Section 17.12.1
"disabled"属性をサポートする要素のリストの中のBUTTONINPUTとの間に一つのコンマを追加することが望ましい。
A comma should be added between BUTTON and INPUT in the list of elements that support the "disabled" attribute.
17.13.4の"multipart/form-data"
Section 17.13.4.2
箇条の最後の例で,"Content-Disposition: attachment"を"Content-Disposition: file"に変更する。さらに,その前の方の例で,"server.dom"を"server.com"に変更する。
In the examples at the end of the section, change "Content-Disposition: attachment" to "Content-Disposition: file". Also, in an earlier example, change "server.dom" to "server.com".
18.2.2の"デフォルトスクリプト言語"
Section 18.2.2.1
最初の例の後,"content-type"の前の不定冠詞は,"an"ではなく"a"が必要である。同じことが,次の段落の"content-type"にも適用される。
参考 TR X 0033:2000では,修正は不要。
After the first example, the indefinite article before "content-type" needs to be "a", not "an". The same applies to "content-type" in the next paragraph.

"Documents that do not specify..."で始まる文において,不定冠詞の"a"が,"default scripting language information"の前から取り除かれることが望ましい。
参考 TR X 0033:2000では,修正は不要。

In the sentence beginning "Documents that do not specify...", the indefinite article "a" needs to be removed from before "default scripting language information".

18.2.3
Section 18.2.3
最初の備考の最初の文において,語"realm"の前に定冠詞"the"を置くのが望ましい。
参考 TR X 0033:2000では,修正は不要。
In the first sentence of the first note, the word "realm" should be preceded by the definite article "the".
18.3.1
Section 18.3.1
最初の段落の2番目の文において,語"be"が,語"only"と語"rendered"との間に挿入される必要がある。
参考 TR X 0033:2000では,修正は不要。
In the second sentence of the first paragraph, the word "be" needs to be inserted between the words "only" and "rendered".
21.
Section 21
  • COLGROUP要素の下のすべてのDTDにおいて,内容モデルは,"col"ではなく"COL"を示すのが望ましい。
    In all DTDs, under the COLGROUP element, the content model should indicate "COL", not "col".
  • %Scope実体についての注釈において,"axes"属性を"headers"属性に変更する。
    In the comment about the %Scope entity, change "axes" to "headers" attribute.
24.2.1
Section 24.2.1
"thorn"の定義の最後において,迷子になっている最後の語("with")を取り除く。
At end of definition of "thorn", remove stray final word.
24.4
Section 24.4
"cp-1252"を"CP-1252"に変更する。
Change "cp-1252" to "CP-1252".
A.1.7
Appendix: Changes for tables
COLGROUP要素に関する段落において,最後の文は次のとおりとするのが望ましい。"The semantics of COLGROUP have been clarified over previous drafts, and rules="basic" has been replaced by rules="groups"."
参考 TR X 0033:2000では,修正は不要。
In the paragraph on the COLGROUP element, the last sentence should read: "The semantics of COLGROUP have been clarified over previous drafts, and rules="basic" has been replaced by rules="groups"."
A.1.1
Changes to elements
非推奨の要素のリストは,Sを含むのが望ましい。
The list of deprecated elements should include S.
B.3.2
Section B.3.2
"区切りに名前文字([a-zA-Z])が続く(delimiter followed by a name character)"は,"区切りに名前開始文字([a-zA-Z])が続く(delimiter followed by a name start character)"に変更する。
In "delimiter followed by a name character", change to delimiter followed by a name start character".
B.4
Section B.4
"キーワード及び記述の提供(Provide keywords and descriptions)"の下の,文"この標準情報(TR)は,検索属性によって検索されるname属性の値を定義しない。(The value of the name attribute sought by a search attribute is not defined by this specification.)"の中央の辺りの"検索属性"は"検索エンジン(search engine)"となるのがよい。
Under "Provide keywords and descriptions", the middle of the sentence "The value of the name attribute sought by a search attribute is not defined by this specification." should read "search engine" instead.
B.4
Section B.4
"集まりの先頭の指示"の例の中のrel="begin"rel="start"に置き換える。
In the example to indicate the beginning of a collection replace rel="begin" with rel="start".
B.4.1
Section B.4.1
"name及びcontentの属性値は,大文字及び小文字を区別しない。(The name and the content attribute values are case-insensitive.)"を取り除く。
Remove "The name and the content attribute values are case-insensitive."
B.5.1の"増加的ディスプレイ"
Section B.5.1.2
最後の段落の最後の文は,閉じ括弧が抜けている。
参考 TR X 0033:2000では,修正は不要。
The last sentence of the last paragraph is missing a closing parenthesis.
B.7.1の"スクリプトマクロの現状の実施"
Section B.7.1.1
次の推奨しない例について。
In the deprecated example:
<BODY bgcolor='&{randomrgb};'>

語"randomrbg"は,"randomrgb"となるのが望ましい。

The word "randomrbg" should be "randomrgb".

附1.1.4 明確化
Clarifications

3.2.1
Section 3.2.1
7番目の段落において,"back to the matching start tag"を追加して,"(e.g., they must be properly nested, an end tag closes, back to the matching start tag, all unclosed intervening start tags with omitted end tags (section 7.5.1), etc.)"とした。
In seventh paragraph, added "back to the matching start tag" to "(e.g., they must be properly nested, an end tag closes, back to the matching start tag, all unclosed intervening start tags with omitted end tags (section 7.5.1), etc.)."
3.2.4
Section 3.2.4
注釈はマーク付けとする,という文を追加した。
Added a statement that comments are markup.
3.3.3
Section 3.3.3
2番目のリスト項目において,"Whether the element's end tag"を"Whether the element's tags"に変更する。
In the second list item, change "Whether the element's end tag" to "Whether the element's tags".
3.3.3の"内容モデル定義"
Section 3.3.3.1
内容モデル定義において,"A"は,"A"が一度及びただ一度だけ出現しなければならない、を意味する。さらに,"+(A)"及び"-(A)"を内容モデル構文の箇条に追加した。
In a content model definition, "A" means that "A" must occur one time and only one time. Also, added "+(A)" and "-(A)" to the section on content model syntax.
7.4.2
Section 7.4.2
TITLEは,注釈を含むことは許されない,と明確化した。
Clarified that TITLE may not include comments.
10.3
Section 10.3
この箇条及びその下位の箇条における"cracker"を"hacker"に置き換える。さらに,"hacker"及び"nerd"の定義を"The Hacker's Dictionary"から採用する。
All uses of "cracker" in this section and its subsections are replaced with "hacker". Also, definitions of "hacker" and "nerd" taken from "The Hacker's Dictionary".
13.7.2
Section 13.7.2
hspace属性及びvspace属性は,推奨しない。
The hspace and vspace attributes are deprecated.
13.7.4
Section 13.7.4
align属性は,IMGOBJECT及びAPPLETに対して,推奨しない。
The align attribute is deprecated for IMG, OBJECT, and APPLET.

附1.1.5 既知のブラウザの問題点
Known Browser problems

以下の節は,TR X 0033:2000の附属書Aと同じなので,省略する。

A.2 Changes between 18 December 1997 and 24 April 1998 versions

This section describes how the 24 April 1998 version of the HTML 4.0 specification differs from the 18 December 1997 version.

A.2.1 Errors that were corrected

Section 2.1.1
"http://www.w3.org/TR/PR-html4/cover.html" was said to designate the current HTML specification. The current HTML specification is actually at http://www.w3.org/TR/REC-html40.
Section 7.5.2
The hypertext link on name was incorrect. It now links to types.html#type-name.
Section 7.5.4
href was listed as an attribute of the DIV and SPAN elements. It is not.
Section 7.5.6
A P element was used in the example. It is invalid in ADDRESS.
Section 8.1
In the first example, which reads "Her super-powers were the result...", there was an extra double quote mark before the word "Her".
Section 9.3.4
The attribute width was not noted as deprecated.
Section 11.2.4, "Calculating the width of columns"
The sentence "We have set the value of the align attribute in the third column group to 'center'" read "second" instead of "third".
Section 11.2.6, "Cells that span several rows or columns"
The second paragraph read "In this table definition, we specify that the cell in row four, column two should span a total of three columns, including the current row." It now ends "...including the current column."
Section 13.2
The sentence beginning "User agents must render alternate text when they cannot support ..." read "next", instead of "text".
Section 13.6.2
The last sentence of the second paragraph applied to both the IMG and INPUT elements. However, the ismap attribute is not defined for INPUT. The sentence now only applies to IMG.
Section 14.2.3
The title attribute for the STYLE element was not listed as an attribute defined elsewhere.
Section 14.3.2
The second example set title="Compact". It now sets title="compact".
Section 15.1.2
The sentence ending "the align attribute." read "the align element."
Section 15.1.3.2
The CSS style rule "BR.mybr { clear: left }" was incorrect, since it refers to the class "mybr" and not the id value. The correct syntax is: "BR#mybr { clear: left }".
Section 16
All the examples containing a Document Type Declaration used something like "THE_LATEST_VERSION_/frameset.dtd" or "THE_LATEST_VERSION_" as the system identifier for the Frameset DTD. They now use the proper document type declaration indicated in Section 7.2
Section 16.3 and Section 16.3.1
The second example of 16.3 and the example of 16.3.1 used the wrong DTD; they now use the Transitional DTD.
Section 17.5
In "attributes defined elsewhere" for the BUTTON element, id, class, lang, dir, title, style, and tabindex were missing. Also, usemap has been removed.
Section 17.6/17.6.1
The "attributes defined elsewhere" for OPTION and OPTGROUP mistakenly listed onfocus, onblur, and onchange. The "attributes defined elsewhere" section was missing for the SELECT element (please see the DTD for the full list of attributes).
Section 17.9.1
The tabindex attribute was said to be defined for the LABEL element. It is not.
Section 17.12.2
The sentence "The following elements support the readonly attribute: INPUT and TEXTAREA." read "The following elements support the readonly attribute: INPUT, TEXT, PASSWORD, and TEXTAREA."
Section 18.2.2, "Local declaration of a scripting language"
The first paragraph read: "It is also possible to specify the scripting language in each SCRIPT element via the type attribute. In the absence of a default scripting language specification, this attribute must be set on each SCRIPT element." Since the type attribute is required for the SCRIPT element, this paragraph now reads: "The type attribute must be specified for each SCRIPT element instance in a document. The value of the type attribute for a SCRIPT element overrides the default scripting language for that element."
Section 21
Added note that the spec includes some syntactic constraints that cannot be expressed in the DTD.
Section 24.2.1 and file HTMLlat1.ent
The comment for the character reference "not" read "= discretionary hyphen". This has been removed.
The FPI in comment read "-//W3C//ENTITIES Full Latin 1//EN//HTML", instead this is now "-//W3C//ENTITIES Latin1//EN//HTML".
Section 24.3.1 and file HTMLsymbol.ent
The FPI in comment read "-//W3C//ENTITIES Symbolic//EN//HTML", instead this is now "-//W3C//ENTITIES Symbols//EN//HTML".
Section A.1.1, "New elements" (previously A.1.1) and Section A.1.1, "Deprecated elements" (previously A.1.2)
The S element which is deprecated was listed as part of the changes between HTML 3.2 and HTML 4.0. This element was not actually defined in HTML 3.2. It is now in the new elements list.
Section A.1.3 (previously A.3)
The longdesc attribute was said to be specified for tables. It is not. Instead, the summary attribute allows authors to give longer descriptions of tables.
Section B.4
The sentence "You may help search engines by using the LINK element with rel="start" along with the title attribute, ..." read "You may help search engines by using the LINK element with rel="begin" along with a TITLE, ..." The same stands for the companion example.
Section B.5.1
The sentence "This can be altered by setting the width attribute of the TABLE element." read "This can be altered by setting the width-TABLE attribute of the TABLE element."
Section B.5.2
The sentence "Rules for handling objects too large for a column apply when the explicit or implied alignment results in a situation where the data exceeds the assigned width of the column." read "too large for column". The meaning of the sentence was unclear since it referred to "rules" governing an error condition; user agent behavior in error conditions lies outside the scope of the specification.
Index of attributes
The href attribute for the BASE element was marked as deprecated. It is not. However, it is not defined in the Strict DTD either.

The language attribute for the SCRIPT element was not marked as deprecated. It is now, and it is no longer defined in the Strict DTD.

A.2.2 Minor typographical errors that were corrected

Section 2.1.3
"Relative URIs are resolved ..." was "Relative URIsare resolved ...".
Section 2.2.1
The second word "of" was missing in "Despite never receiving consensus in standards discussions, these drafts led to the adoption of a range of new features."
Section 3.3.3
The sentence "Element types that are designed to have no content are called empty elements." contained one too many "elements". The word "a" was missing in the sentence "A few HTML element types use an additional SGML feature to exclude elements from a content model".

Also, in list item two, a period was missing between "optional" and "Two".

Section 3.3.4
In the section on "Boolean attributes", the sentence that begins "In HTML, boolean attributes may appear in minimized ..." included a bogus word "be".
Section 6.3
The sentence beginning "For introductory information about attributes, ..." read "For introductory about attributes, ...".
Section 6.6
In the first sentence of the section on Pixels, "is an integer" read "is integer".
Section 7.4.1
The first word "The" was missing at the beginning of the section title.
Section 7.4.4
The last word "a" was missing in the sentence "The meaning of a property and the set of legal values for that property should be defined in a reference lexicon called profile."
Section 7.5.2
"Variable déclarée deux fois" read "Variable déclaré deux fois".
Section 9.2.2
The language of the quotations was "en" instead of "en-us", while in British English, the single quotation marks would delimit the outer quotation.
Section 9.3.2
In the first line, the sixth character of "&#x000A" was the letter 'O' instead of a zero.
Section 10.3.1
"(they are case-sensitive)" read "(the are case-sensitive)".
Section 12.1.1
In the sentence beginning "Note that the href attribute in each source ..." the space was missing between "href" and "attribute".
Section 12.1.2
The sentence "Links that express other types of relationships have one or more link types specified in their source anchors." read "Links that express other types of relationships have one or more link type specified in their source anchor."
Section 12.1.5
The second paragraph reads "the hreflang attribute provides user agents about the language of a ..." It should read "the hreflang attribute provides user agents with information about the language of a ..."
Section 13.3.2
In the sentence beginning "Any number of PARAM elements may appear in the content of an OBJECT or APPLET element, ..." a space was missing between "APPLET" and "element".
Section 14.2.2
There was a bogus word "style" at the beginning of the sentence "The style attribute specifies ..."
Section 17.2
In "Those controls for which name/value pairs are submitted are called successful controls" the word "for" was missing.
Section 17.10
There was a bogus word "/samp" just before section 17.11.
Section 17.11
The first sentence read, "In an HTML document, an element must receive focus from the user in order to become active and perform their tasks" (instead of "its" tasks).
Section 18.2.2
Just before section 18.2.3, the sentence that includes "a name attribute takes precedence over an id if both are set." read "over a id if both are set.".
Section 19.1
The section title read "document Document Validation". It now is "Document Validation".
Section 21
The FPI for the Transitional HTML 4.0 DTD was missing a closing double quote.
Section B.5.1/B.5.2
This sections referred to a non-existent cols attribute. This attribute is not part of HTML 4.0. Calculating the number of columns in a table is described in section Section 11.2.4.3, in the chapter on tables. In sections B.5.1 and B.5.2, occurrences of cols have been replaced by "the number of columns specified by the COL and COLGROUP elements".
Section B.5.2
In the sentence "The values for the frame attribute have been chosen to avoid clashes with the rules, align and valign attributes." a space was missing between "the" and "frame" and the last attribute was "valign-COLGROUP".
Section B.10.1
The last sentence read "Once a file is uploaded, the processing agent should process and store the it appropriately." "the it" was changed to "it".
Index of Elements
"strike-through" in the description of the S element read "sstrike-through".

A.3 Changes between HTML 3.2 and HTML 4.0 (18 December 1997)

This section describes how the 18 December 1997 specification of HTML 4.0 differs from HTML 3.2 ([HTML32]).

A.3.1 Changes to elements

New elements 

The new elements in HTML 4.0 are: ABBR, ACRONYM, BDO, BUTTON, COL, COLGROUP, DEL, FIELDSET, FRAME, FRAMESET, IFRAME, INS, LABEL, LEGEND, NOFRAMES, NOSCRIPT, OBJECT, OPTGROUP, PARAM, S (deprecated), SPAN, TBODY, TFOOT, THEAD, and Q.

Deprecated elements 

The following elements are deprecated: APPLET, BASEFONT, CENTER, DIR, FONT, ISINDEX, MENU, S, STRIKE, and U.

Obsolete elements 

The following elements are obsolete: LISTING, PLAINTEXT, and XMP. For all of them, authors should use the PRE element instead.

A.3.2 Changes to attributes

A.3.3 Changes for accessibility

HTML 4.0 features many changes to promote accessibility, including:

A.3.4 Changes for meta data

Authors may now specify profiles that provide explanations about meta data specified with the META or LINK elements.

A.3.5 Changes for text

A.3.6 Changes for links

A.3.7 Changes for tables

The HTML 4.0 table model has grown out of early work on HTML+ and the initial draft of HTML3.0. The earlier model has been extended in response to requests from information providers as follows:

The HTML 4.0 table model also satisfies requests for optional column-based defaults for alignment properties, more flexibility in specifying table frames and rules, and the ability to align on designated characters. It is expected, however, that style sheets will take over the task of rendering tables in the near future.

In addition, a major goal has been to provide backwards compatibility with the widely deployed Netscape implementation of tables. Another goal has been to simplify importing tables conforming to the SGML CALS model. The latest draft makes the align attribute compatible with the latest versions of the most popular browsers. Some clarifications have been made to the role of the dir attribute and recommended behavior when absolute and relative column widths are mixed.

A new element, COLGROUP, has been introduced to allow sets of columns to be grouped with different width and alignment properties specified by one or more COL elements. The semantics of COLGROUP have been clarified over previous drafts, and rules="basic" has been replaced by rules="groups".

The style attribute is included as a means for extending the properties associated with edges and interiors of groups of cells. For instance, the line style: dotted, double, thin/thick etc; the color/pattern fill for the interior; cell margins and font information. This will be the subject for a companion specification on style sheets.

The frame and rules attributes have been modified to avoid SGML name clashes with each other, and to avoid clashes with the align and valign attributes. These changes were additionally motivated by the desire to avoid future problems if this specification is extended to allow frame and rules attributes with other table elements.

A.3.8 Changes for images, objects, and image maps

A.3.9 Changes for forms

This specification introduces several new attributes and elements that affect forms:

A.3.10 Changes for style sheets

HTML 4.0 supports a larger set of media descriptors so that authors may write device-sensitive style sheets.

A.3.11 Changes for frames

HTML 4.0 supports frame documents and inline frames.

A.3.12 Changes for scripting

Many elements now feature event attributes that may be coupled with scripts; the script is executed when the event occurs (e.g., when a document is loaded, when the mouse is clicked, etc.).

A.3.13 Changes for internationalization

HTML 4.0 integrates the recommendations of [RFC2070] for the internationalization of HTML.

However, this specification and [RFC2070] differ as follows: