John Doe 123456789

Bla great bla bla world bla bla empire bla bla color bla bla history bla bla forever. John Johnson

Depending on the width of the containing block, this may be rendered as: Bla great bla bla world bla bla empire bla bla color bla bla history bla bla forever. John Johnson However, this rendering is preferable: Bla great bla bla world bla bla empire bla bla color bla bla history bla bla forever. John Johnson If the name and number end up on different lines (e.g., in a narrow column), it may be formatted like this: John Doe.... ...123456789

NOTE-CSS-potential-19981210

List of suggested extensions to CSS

W3C Note 10 December 1998

This version:	http://www.w3.org/TR/1998/NOTE-CSS-potential-19981210
Latest version:	http://www.w3.org/TR/NOTE-CSS-potential
Previous version:	http://www.w3.org/TR/NOTE-CSS-potential-19970819
÷ 000D ÷ 000D ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] (CR) ÷ [2: ÷ eot] ÷ 000D × 000A ÷ # ÷ [1: sot ÷] (CR) × [3: CR × LF] (LF) ÷ [2: ÷ eot] ÷ 000D ÷ 0001 ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] (Control) ÷ [2: ÷ eot] ÷ 000D ÷ 0300 ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ 000D ÷ 1100 ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ 000D ÷ 1160 ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ 000D ÷ 11A8 ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ 000D ÷ AC00 ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ 000D ÷ AC01 ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ 000D ÷ 0020 ÷ # ÷ [1: sot ÷] (CR) ÷ [4: ( Control \| CR \| LF ) ÷] SPACE (Other) ÷ [2: ÷ eot] ÷ 000A ÷ 000D ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] (CR) ÷ [2: ÷ eot] ÷ 000A ÷ 000A ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] (LF) ÷ [2: ÷ eot] ÷ 000A ÷ 0001 ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] (Control) ÷ [2: ÷ eot] ÷ 000A ÷ 0300 ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ 000A ÷ 1100 ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ 000A ÷ 1160 ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ 000A ÷ 11A8 ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ 000A ÷ AC00 ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ 000A ÷ AC01 ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ 000A ÷ 0020 ÷ # ÷ [1: sot ÷] (LF) ÷ [4: ( Control \| CR \| LF ) ÷] SPACE (Other) ÷ [2: ÷ eot] ÷ 0001 ÷ 000D ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] (CR) ÷ [2: ÷ eot] ÷ 0001 ÷ 000A ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] (LF) ÷ [2: ÷ eot] ÷ 0001 ÷ 0001 ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] (Control) ÷ [2: ÷ eot] ÷ 0001 ÷ 0300 ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ 0001 ÷ 1100 ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ 0001 ÷ 1160 ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ 0001 ÷ 11A8 ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ 0001 ÷ AC00 ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ 0001 ÷ AC01 ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ 0001 ÷ 0020 ÷ # ÷ [1: sot ÷] (Control) ÷ [4: ( Control \| CR \| LF ) ÷] SPACE (Other) ÷ [2: ÷ eot] ÷ 0300 ÷ 000D ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [5: ÷ ( Control \| CR \| LF )] (CR) ÷ [2: ÷ eot] ÷ 0300 ÷ 000A ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [5: ÷ ( Control \| CR \| LF )] (LF) ÷ [2: ÷ eot] ÷ 0300 ÷ 0001 ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [5: ÷ ( Control \| CR \| LF )] (Control) ÷ [2: ÷ eot] ÷ 0300 × 0300 ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) × [9: × Extend] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ 0300 ÷ 1100 ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [10: Any ÷ Any] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ 0300 ÷ 1160 ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [10: Any ÷ Any] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ 0300 ÷ 11A8 ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [10: Any ÷ Any] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ 0300 ÷ AC00 ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ 0300 ÷ AC01 ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ 0300 ÷ 0020 ÷ # ÷ [1: sot ÷] COMBINING GRAVE ACCENT (Extend) ÷ [10: Any ÷ Any] SPACE (Other) ÷ [2: ÷ eot] ÷ 1100 ÷ 000D ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) ÷ [5: ÷ ( Control \| CR \| LF )] (CR) ÷ [2: ÷ eot] ÷ 1100 ÷ 000A ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) ÷ [5: ÷ ( Control \| CR \| LF )] (LF) ÷ [2: ÷ eot] ÷ 1100 ÷ 0001 ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) ÷ [5: ÷ ( Control \| CR \| LF )] (Control) ÷ [2: ÷ eot] ÷ 1100 × 0300 ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) × [9: × Extend] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ 1100 × 1100 ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) × [6: L × ( L \| V \| LV \| LVT )] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ 1100 × 1160 ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) × [6: L × ( L \| V \| LV \| LVT )] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ 1100 ÷ 11A8 ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) ÷ [10: Any ÷ Any] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ 1100 × AC00 ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) × [6: L × ( L \| V \| LV \| LVT )] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ 1100 × AC01 ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) × [6: L × ( L \| V \| LV \| LVT )] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ 1100 ÷ 0020 ÷ # ÷ [1: sot ÷] HANGUL CHOSEONG KIYEOK (L) ÷ [10: Any ÷ Any] SPACE (Other) ÷ [2: ÷ eot] ÷ 1160 ÷ 000D ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) ÷ [5: ÷ ( Control \| CR \| LF )] (CR) ÷ [2: ÷ eot] ÷ 1160 ÷ 000A ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) ÷ [5: ÷ ( Control \| CR \| LF )] (LF) ÷ [2: ÷ eot] ÷ 1160 ÷ 0001 ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) ÷ [5: ÷ ( Control \| CR \| LF )] (Control) ÷ [2: ÷ eot] ÷ 1160 × 0300 ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) × [9: × Extend] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ 1160 ÷ 1100 ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) ÷ [10: Any ÷ Any] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ 1160 × 1160 ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) × [7: ( LV \| V ) × ( V \| T )] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ 1160 × 11A8 ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) × [7: ( LV \| V ) × ( V \| T )] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ 1160 ÷ AC00 ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ 1160 ÷ AC01 ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ 1160 ÷ 0020 ÷ # ÷ [1: sot ÷] HANGUL JUNGSEONG FILLER (V) ÷ [10: Any ÷ Any] SPACE (Other) ÷ [2: ÷ eot] ÷ 11A8 ÷ 000D ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [5: ÷ ( Control \| CR \| LF )] (CR) ÷ [2: ÷ eot] ÷ 11A8 ÷ 000A ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [5: ÷ ( Control \| CR \| LF )] (LF) ÷ [2: ÷ eot] ÷ 11A8 ÷ 0001 ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [5: ÷ ( Control \| CR \| LF )] (Control) ÷ [2: ÷ eot] ÷ 11A8 × 0300 ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) × [9: × Extend] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ 11A8 ÷ 1100 ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [10: Any ÷ Any] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ 11A8 ÷ 1160 ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [10: Any ÷ Any] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ 11A8 × 11A8 ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) × [8: ( LVT \| T ) × T] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ 11A8 ÷ AC00 ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ 11A8 ÷ AC01 ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ 11A8 ÷ 0020 ÷ # ÷ [1: sot ÷] HANGUL JONGSEONG KIYEOK (T) ÷ [10: Any ÷ Any] SPACE (Other) ÷ [2: ÷ eot] ÷ AC00 ÷ 000D ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) ÷ [5: ÷ ( Control \| CR \| LF )] (CR) ÷ [2: ÷ eot] ÷ AC00 ÷ 000A ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) ÷ [5: ÷ ( Control \| CR \| LF )] (LF) ÷ [2: ÷ eot] ÷ AC00 ÷ 0001 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) ÷ [5: ÷ ( Control \| CR \| LF )] (Control) ÷ [2: ÷ eot] ÷ AC00 × 0300 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) × [9: × Extend] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ AC00 ÷ 1100 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) ÷ [10: Any ÷ Any] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ AC00 × 1160 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) × [7: ( LV \| V ) × ( V \| T )] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ AC00 × 11A8 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) × [7: ( LV \| V ) × ( V \| T )] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ AC00 ÷ AC00 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ AC00 ÷ AC01 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ AC00 ÷ 0020 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GA (LV) ÷ [10: Any ÷ Any] SPACE (Other) ÷ [2: ÷ eot] ÷ AC01 ÷ 000D ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) ÷ [5: ÷ ( Control \| CR \| LF )] (CR) ÷ [2: ÷ eot] ÷ AC01 ÷ 000A ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) ÷ [5: ÷ ( Control \| CR \| LF )] (LF) ÷ [2: ÷ eot] ÷ AC01 ÷ 0001 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) ÷ [5: ÷ ( Control \| CR \| LF )] (Control) ÷ [2: ÷ eot] ÷ AC01 × 0300 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) × [9: × Extend] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ AC01 ÷ 1100 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) ÷ [10: Any ÷ Any] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ AC01 ÷ 1160 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) ÷ [10: Any ÷ Any] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ AC01 × 11A8 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) × [8: ( LVT \| T ) × T] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ AC01 ÷ AC00 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ AC01 ÷ AC01 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ AC01 ÷ 0020 ÷ # ÷ [1: sot ÷] HANGUL SYLLABLE GAG (LVT) ÷ [10: Any ÷ Any] SPACE (Other) ÷ [2: ÷ eot] ÷ 0020 ÷ 000D ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [5: ÷ ( Control \| CR \| LF )] (CR) ÷ [2: ÷ eot] ÷ 0020 ÷ 000A ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [5: ÷ ( Control \| CR \| LF )] (LF) ÷ [2: ÷ eot] ÷ 0020 ÷ 0001 ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [5: ÷ ( Control \| CR \| LF )] (Control) ÷ [2: ÷ eot] ÷ 0020 × 0300 ÷ # ÷ [1: sot ÷] SPACE (Other) × [9: × Extend] COMBINING GRAVE ACCENT (Extend) ÷ [2: ÷ eot] ÷ 0020 ÷ 1100 ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [10: Any ÷ Any] HANGUL CHOSEONG KIYEOK (L) ÷ [2: ÷ eot] ÷ 0020 ÷ 1160 ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [10: Any ÷ Any] HANGUL JUNGSEONG FILLER (V) ÷ [2: ÷ eot] ÷ 0020 ÷ 11A8 ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [10: Any ÷ Any] HANGUL JONGSEONG KIYEOK (T) ÷ [2: ÷ eot] ÷ 0020 ÷ AC00 ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GA (LV) ÷ [2: ÷ eot] ÷ 0020 ÷ AC01 ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [10: Any ÷ Any] HANGUL SYLLABLE GAG (LVT) ÷ [2: ÷ eot] ÷ 0020 ÷ 0020 ÷ # ÷ [1: sot ÷] SPACE (Other) ÷ [10: Any ÷ Any] SPACE (Other) ÷ [2: ÷ eot] # Lines: 100:	Bert Bos (bert@w3.org)

Copyright © 1998 W3C (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.

÷ 0061 × 0027 × 0301 × 0308 × 0061 ÷ 002C × 0301 × 0308 ÷ 0061 ÷ ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0027 ÷ 0061 ÷ 002C × 0301 × 0308 ÷ 0061 ÷ ÷ 0027 ÷ 0031 ÷ 003A ÷ # ÷ [1: sot ÷] APOSTROPHE (MidLetter) ÷ [14: Any ÷ Any] DIGIT ONE (Numeric) ÷ [14: Any ÷ Any] COLON (MidLetter) ÷ [2: ÷ eot] ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0031 ÷ 003A × 0301 × 0308 ÷ 0061 ÷ ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0027 ÷ 0031 ÷ 003A × 0301 × 0308 ÷ 0061 ÷ ÷ 0027 ÷ 0031 ÷ 0027 ÷ # ÷ [1: sot ÷] APOSTROPHE (MidLetter) ÷ [14: Any ÷ Any] DIGIT ONE (Numeric) ÷ [14: Any ÷ Any] APOSTROPHE (MidLetter) ÷ [2: ÷ eot] ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0031 ÷ 0027 × 0301 × 0308 ÷ 0061 ÷ ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0027 ÷ 0031 ÷ 0027 × 0301 × 0308 ÷ 0061 ÷ ÷ 0027 ÷ 0031 ÷ 002C ÷ # ÷ [1: sot ÷] APOSTROPHE (MidLetter) ÷ [14: Any ÷ Any] DIGIT ONE (Numeric) ÷ [14: Any ÷ Any] COMMA (MidNum) ÷ [2: ÷ eot] ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0031 ÷ 002C × 0301 × 0308 ÷ 0061 ÷ ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0027 ÷ 0031 ÷ 002C × 0301 × 0308 ÷ 0061 ÷ ÷ 0027 ÷ 0031 ÷ 002E × 2060 ÷ # ÷ [1: sot ÷] APOSTROPHE (MidLetter) ÷ [14: Any ÷ Any] DIGIT ONE (Numeric) ÷ [14: Any ÷ Any] FULL STOP (MidNum) × [4: X Format* -> X] WORD JOINER (Format) ÷ [2: ÷ eot] ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0031 ÷ 002E × 2060 ÷ 0301 × 0308 ÷ 0061 ÷ ÷ 0061 ÷ 0027 × 0301 × 0308 ÷ 0027 ÷ 0031 ÷ 002E × 2060 ÷ 0301 × 0308 ÷ 0061 ÷ ÷ 002C × 00AD ÷ # ÷ [1: sot ÷] COMMA (MidNum) × [4: X Format* -> X] SOFT HYPHEN (Format) ÷ [2: ÷ eot] ÷ 0061 ÷ 002C × 0301 × 0308 × 00AD ÷ 0301 × 0308 ÷ 0061 ÷ ÷ 0061 ÷ 002C × 0301 × 0308 ÷ 0027 × 00AD ÷ 0301 × 0308 ÷ 0061 ÷ ÷ 002C ÷ 3031 ÷ # ÷ [1: sot ÷] COMMA (MidNum) ÷ [14: Any ÷ Any] VERTICAL KANA REPEAT MARK (Katakana) ÷ [2: ÷ eot]

Status of this document

This document is a NOTE issued by the Cascading Style Sheets and Formatting Properties Working Group (CSS & FP WG). It is provided for information only, and does not represent a W3C-endorsed specification. Features described here may or may not become part of a W3C Recommendation or other specification, and they may change considerably in the process. The features should therefore not be implemented, except as experiments, clearly labeled as experimental. Such experiments are welcomed, and may provide valuable information about the development (or not) of these features, but the fact that a feature has been implemented (or implemented in a certain way), will by itself not be an argument to adopt the feature in CSS (or adopt it in this particular form).

A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR/.

Abstract

This Note attempts to document all the features that have been suggested for CSS, and that are not part of CSS2. The fact that a feature has been listed here does not mean it will be in some future version of CSS; some of the suggestions do not fit in CSS or are better handled elsewhere (e.g., in HTML, SMIL, or RDF). The purpose of the list is to make sure suggestions are neither forgotten nor suggested over and over again.

Many suggestions are just listed without further comment. If the CSS working group has discussed a feature, some remarks may be added.

Comments on this draft are welcome and should be sent to the www-style@w3.org mailing list (recommended) or the CSS & FP WG (only for W3C members), or to the editors if neither of the above is suitable.

Please, give feedback before the 5th of February 1999.

Acknowledgements

Ian Hickson <exxieh@bath.ac.uk> for suggesting this document, and maintaining one independently.

Feedback

Please, give your evaluation of each of the listed items, by filling in the form. You don't have to fill in the whole form at once. You can submit multiple times, and new evaluations will be added to any old ones, or override them, if you rate the same item twice. However, that is the only use we make of the sender's e-mail address. When we publish the results, the e-mail addresses will not be published.

Please indicate your support for the feature, not for the suggested solutions. For example, if you want columns very much, but don't like the particular properties proposed, choose option 5: "strongly in favor." (And then send what you think of the solution to www-style.)

Each item can be rated on a scale from 1 to 5:

Strongly opposed
Mildly opposed
Neutral
Mildly in favor
Strongly in favor

If you already sent in a form, then the "I skipped this question" button means that whatever you said last time, will remain in the database unchanged.

The form will be active until 5 February 1999.

To discuss this note, please subscribe to the www-style@w3.org mailing list.

www-css-potential-19981210-vote@w3.org" style="margin: 0; padding: 0;">

1. Columns

Especially for printing, but also possibly on wide screens, text is often displayed in columns (also known as newspaper columns, or snaking columns).

Desirable features are:

a way to specify the (approximate or min/max) width of a column, and let the actual number of columns depend on the width of the containing block.
a way to make floating boxes float to the edge of a particular column, or even span columns.
specify whether columns are balanced, or have a particular height (the page height, e.g.)
make columns as high as the viewport, necessitating horizontal scrolling only (useful, e.g., for spreadsheet-like displays)
specify rules and gaps between columns

One concrete proposal is as follows:

Three properties ('column-number', 'column-width', 'column-gap') and one shorthand property ('columns') set either the number of columns, the width(s) of the columns, or both. They are not inherited. For example:

DIV.main { column-number: 2; column-width: auto; column-gap: 1em }

formats the DIV as two balanced columns, each of nearly half the width of the element.

Properties 'column-rule-style', 'column-rule-width', 'column-rule-color' and the shorthand 'column-rule' determine the style of the vertical rules between the columns. These properties are inherited.

For a similar idea, see e-mail by e-mail by David Baron.

For more details see Chris Wilson' proposal [member-only link].

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

2. Swash letters and other glyph substitutions

CSS2 can specify fonts, but if a font contains multiple glyphs for the same character, there is no way to get them (other than by creating a new font with the alternate glyph and the default swapped...) Maybe CSS should have a way of indicating which glyph to use for each character in the source. Problem is, of course, that there are no standard names for glyphs. The index number of a glyph inside a font file is unreliable as well.

Somewhat related: control over ligatures. In Latin scripts, the rule is simple enough to leave to the UA: always use all that the font provide. Occasionally a writer may have to insert a zero-width-space between two letters where tradition forbids a ligature, but otherwise the use of ligatures is seldomly a style question. In Arabic, things are different. Varying the amount and complexity of the ligatures is a common device to distinguish different types of documents.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

3. Running headers and footers

At the top and bottom (but maybe not only there) of a document that is split over several pages, you often find things like page numbers, author, title, date, current section, keywords, etc.

Robert Stevahn is collecting requirements. [member-only link]

We must support an arbitrary number of 'objects' in the header/footer areas.
We must be able to align these objects arbitrarily with respect to the boundaries of the header/footer areas.
We must be able to support running headers/footers. For example, we must be able to include the current page and chapter number in the header/footer without knowing this information a priori.
We must support two kinds of generated running information: page-based (i.e. page numbers, footnotes & some figure numbers) and document-based (i.e. chapter numbers).
We must be able to insert the current date/time into the header/footer area.
We must be able to extract data from the document for inclusion in the header/footer area. For example, if H1 elements define chapter titles, we must be able to extract the contents of these elements for running headers/footers.
We must be able to suppress the display of this extracted information in the body of the document. For example, a confidentiality clause that is pulled out into the footer area does not need to be repeated in the body of the document. However, you would want to display it in place when using a non-print medium.
We must be able to style portions of header/footer content at an appropriate level of granularity.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

4. Cross-references

If you print a document with hyperlinks to parts of itself, you might want to print them as "see page 17" or "(section 5.1, page 53)" or "list item 4", See Daniel Glazman's e-mail.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

5. Vertical text

Vertical text for the whole document, but also mixing vertical and horizontal, within a line, or on a page. For example, in vertical text in Japanese, it is quite common to put small numbers (2 or 3 digits) horizontally.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

6. Ruby

Example of ruby Ruby are small annotations, usually written on top of a character in Japanese or Chinese, that either give the pronunciation or the meaning of the characters under them.

See Microsoft's proposal. [member-only link]

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

7. Diagonal text & text along a path

SVG will probably provide means to do the complex things, but a diagonal header above a table column might be possible without SVG. See also e-mail by Jeffrey Veen. [member-only link]

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

8. Style properties for embedded 2D graphics

When you embed a PNG or GIF, you can only adapt the colors of the text to the graphic, but with SVG, you should be able to do it the other way round: if your page is red, then the graphic should be drawn in red lines as well. You could specify the style for the text and the style for the graphic in a single style sheet, and when the SVG is embedded/linked from an HTML page, it could inherit the style sheet. This needs cooperation with SVG [member-only link]

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

9. Hyphenation control

Properties for turning hyphenation on/off or settings in between: highly undesirable, avoid two hyphenated lines in a row, no restrictions...

Maybe also a way to list hyphenation exceptions (difficult words) in the style sheet.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

10. Image filters

Primitive (raster-) image operations, which can be applied to either the foreground, or both the foreground and background of an element, and which can be chained in sequence to create more complex effects.

Examples: convolution matrices.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

11. Rendering objects for forms

Including control over look of interaction objects in their various states. Keyword 'normal' or something similar to revert to normal look for user's platform.

Note: only the look is set with CSS. You can make an element look like a native button, and you can maybe even cause it to change its look when the user clicks or otherwise selects it, but it won't affect anything outside itself, or send anything to a server, unless it also has the semantics of a button, over which CSS has no control.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

12. A pseudo-element for the URL #fragment-id

Some URLs refer to a location within a resource. This kind of URL ends with "#" followed by an anchor identifier (called the fragment identifier). URLs with fragment identifiers link to a certain element within the document, known as the target element. For instance, here is a URI pointing to an anchor named "section_2":

http://somesite.com/html/top.html#section_2

The target element could be styled with a :target pseudo-class:

:target { color: red }

If the URI that has been followed has no fragment identifier, the rule above will have no effect.

This idea was first suggested by Russell O'Connor, in an e-email to www-style@w3.org, March 1998.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

13. Floating boxes to top & bottom of a page

In paged media, elements are often floated to the bottom or top of the (next) page, because leaving them inline would cause ugly page breaks, and they are too wide to float to the side.

A simple solution is to add 'top' and 'bottom' to the 'float' property, and possibly introduce additional properties to configure how many floats can accumulate at the top of a page, or how far from its original location an element can float.

There is a connection with footnotes here. See also numbered floats below.

If you want to give feedback, please tick the appropriate field:
1: Strongly opposed
2: Mildly opposed
3: Neutral
4: Mildly in favor
5: Strongly in favor
or: I skipped this question

14. Footnotes

Footnotes are somewhat like floats that go to the bottom of the page, but they also leave a footnote marker behind. Therefore they might need special treatment. Endnotes should be just a stylistic variant of footnotes, but how do you indicate where the endnotes go?

A footnote is also like a hyperlink, so maybe it should be possible to render the target of a hyperlink in a footnote to the source of the hyperlink.

End of form

...

A sentence consists of words [3]. ...

[3] Most often. When shown in a legacy browser, the content of the element will be shown as a clickable link to an endnote. When printed according to this specification, there will be a footnote: A sentence consists of words¹. ¹ Most often.

Weirdopedia says: "Weird" http://weirdopedia.posterous.com/bla-great-bla-bla-world John Doe 123456789 Bla great bla bla world bla bla empire bla bla color bla bla history bla bla forever. John Johnson Depending on the width of the containing block, this may be rendered as: Bla great bla bla world bla bla empire bla bla color bla bla history bla bla forever. John Johnson However, ...

Washinton Jongurt

Tuesday, August 16, 2011

Bla great bla bla world

List of suggested extensions to CSS

W3C Note 10 December 1998

Status of this document

Abstract

Table of contents

Acknowledgements

Feedback

1. Columns

2. Swash letters and other glyph substitutions

3. Running headers and footers

4. Cross-references

5. Vertical text

6. Ruby

7. Diagonal text & text along a path

8. Style properties for embedded 2D graphics

9. Hyphenation control

10. Image filters

11. Rendering objects for forms

12. A pseudo-element for the URL #fragment-id

13. Floating boxes to top & bottom of a page

14. Footnotes

End of form

No comments:

Post a Comment

Popular Posts

Blog Archive

Followers