-
Notifications
You must be signed in to change notification settings - Fork 791
Expand file tree
/
Copy pathOverview.src.html
More file actions
executable file
·676 lines (574 loc) · 24.6 KB
/
Overview.src.html
File metadata and controls
executable file
·676 lines (574 loc) · 24.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
<!DOCTYPE html public '-//W3C//DTD HTML 4.01//EN'
'http://www.w3.org/TR/html4/strict.dtd'>
<html lang="en">
<head profile="http://www.w3.org/2006/03/hcard">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>CSS Line Grid Module Level 1</title>
<link rel="stylesheet" type="text/css" href="../default.css">
<style type="text/css">
.sidenote-block {
border: 1px solid gray;
margin: auto;
text-align: left;
padding: 4pt;
position: relative;
max-width: 400pt;
}
.sidenote-body {
margin-left: 120pt;
font-size: 12pt;
line-height: 18pt;
}
.sidenote-note {
font-size: 10pt;
line-height: 18pt;
position: absolute; left: 4pt; top: 4pt;
width: 110pt;
}
</style>
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-ED.css">
</head>
<div class="head">
<!--logo-->
<h1>CSS Line Grid Module Level 1</h1>
<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
<dl>
<dt>This version:
<dd><a href="[VERSION]">
http://www.w3.org/TR/[YEAR]/[STATUS]-[SHORTNAME]-[CDATE]/</a>
<dt>Latest version:
<dd><a href="http://www.w3.org/TR/css-line-grid-1/">
http://www.w3.org/TR/css-line-grid-1/</a>
<!--
<dt>Previous version:
<dd><a href="http://www.w3.org/PreviousVersionURI">
http://www.w3.org/PreviousVersionURI</a>
-->
<dt>Editors:
<dd class=vcard><a href="http://fantasai.inkedblade.net/contact" class="fn url">Elika Etemad</a>,
<span class=org>Invited Expert</span>
<dd class=vcard><a href="mailto:kojiishi@gluesoft.co.jp" class="fn email">Koji Ishii</a>,
<span class=org>Invited Expert</span>
<dd class=vcard><a href="mailto:stearns@adobe.com" class="fn email">Alan Stearns</a>,
<span class=org>Adobe Systems, Inc.</span>
</dl>
<!--copyright-->
<hr title="Separator for header">
</div>
<h2 class="no-num no-toc" id=abstract>Abstract</h2>
<p>
<span class="p-summary">
This module contains CSS features for aligning content to a baseline grid.
</span>
<a href="http://www.w3.org/TR/CSS/">CSS</a> is a language for describing
the rendering of structured documents (such as HTML and XML) on screen, on
paper, in speech, etc.
<h2 class="no-num no-toc" id=status>Status of this document</h2>
<!--status-->
<p>The following features are at risk: …
<h2 class="no-num no-toc" id="contents">Table of contents</h2>
<!--toc-->
<h2>Introduction</h2>
<h3 id="context">Background</h3>
<p><em>This section is not normative.</em></p>
<p>This specification provides features to align lines and blocks
to invisible grids in the document.</p>
<p>Aligning lines and blocks to grids provides the following benefits:</p>
<ul>
<li>Vertical rhythm is kept for better readability.</li>
<li>Lines are aligned between columns in multi-column documents.</li>
<li>The top and the bottom margins of pictures are made equal,
while keeping the vertical rhythm of text before and after the pictures.</li>
<!--
<li>Aligning to grids can sometimes be turned off for objects like tables,
but then turned back on for the following text
to the same grids as the one for the text before the objects.</li>
-->
<li>Layout lines are at the same position on every page in paged media.
Keeping the position of the bottom line of a page has benefits for
design and readability.
This also improves the readability of duplex printing,
two pages spreads,
and displaying on slow display devices like e-ink.</li>
<li>East Asian layouts require vertical rhythm
more often than other scripts do,
even in single column, non-paged media documents,
as defined in [[JLREQ]].</li>
</ul>
<p>There are several types of objects in a document
that can break the vertical rhythm.
Examples include lines with different sizes of text, pictures, and tables.</p>
<div class="figure">
<img src="line-grid-multicol.png"
width="480" height="246"
alt="Vertical rhythm kept through pictures and different size of text in a multi-column document"
/>
<p class="caption">Vertical rhythm kept through pictures and different size of text in a multi-column document.</p>
</div>
<div class="example">
<div class="sidefigure">
<img src="line-grid-wrap.png"
width="276" height="244"
alt="Large text wraps within line grids"
/>
<p class="caption">Large text wraps within line grids.</p>
</div>
<p>When a different size of text, such as a headings, wraps,
it is usually aligned to grids as a block and
the lines within the block do not align.</p>
<br style="clear:both;"/>
</div>
<div id="ex-sidenote" class="figure">
<div class="sidenote-block">
<div class="sidenote-body">
Sidenotes (and footnotes for that matter) are often set
at a smaller size than the basic text.
This smaller text should still line up with the basic text.
Authors can achieve this effect
by calculating appropriate font-size, line-height,
and margins*.
</div>
<div class="sidenote-note">
Only if author controls everything.
It can easily be broken by user stylesheet, for instance.
</div>
</div>
<p class="caption">Sidenotes are set at a smaller size, but still line up with the basic text.</p>
</div>
<div id="ex-width" class="sidefigure">
<img src="width-multiple-of-em.png"
width="180" height="142"
alt="East Asian layouts may require width be a multiple of em without fractions"
/>
<p class="caption">East Asian layouts may require width
be a multiple of <em>em</em> without fractions.</p>
</div>
<p>East Asian layouts may require grid-like features
in inline progression direction as well.</p>
<p>It is often desirable in East Asian layouts
to make the line width
a multiple of <em>em</em> without fractions.
Because most East Asian characters have 1em advance
and most East Asian documents are justified,
this minimizes cases where justification needs to expand character spacing.</p>
<p>This module provides the following capabilities:</p>
<ul>
<li>Defining grids in the line progression direction.</li>
<li>Controling how lines and blocks align to the grids.</li>
</ul>
<p>It is important to control these capabilities independently,
so that, for example, aligning to grids can be turned off for tables,
but can then be turned back on for aligning the following text to the grids.
</p>
<h3 id="placement">Module Interactions</h3>
<p>This module extends the line box model defined in [[!CSS21]] sections
9.4.2 and 10.8.
<h3 id="values">Values</h3>
<p>This specification follows the
<a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
definition conventions</a> from [[!CSS21]]. Value types not defined in
this specification are defined in CSS Level 2 Revision 1 [[!CSS21]].
Other CSS modules may expand the definitions of these value types: for
example [[CSS3COLOR]], when combined with this module, expands the
definition of the <color> value type as used in this specification.</p>
<p>In addition to the property-specific values listed in their definitions,
all properties defined in this specification also accept the
<a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
keyword as their property value. For readability it has not been repeated
explicitly.
<h2 id=line-grid>
Defining a Line Grid: the 'line-grid' property</h2>
<table class=propdef>
<tr>
<th>Name:
<td><dfn>line-grid</dfn>
<tr>
<th><a href="#values">Value</a>:
<td>match-parent | create
<tr>
<th>Initial:
<td>match-parent
<tr>
<th>Applies to:
<td>block containers
<tr>
<th>Inherited:
<td>no
<tr>
<th>Animatable:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Media:
<td>visual
<tr>
<th>Computed value:
<td>specified value
<tr>
<th>Canonical order:
<td><abbr title="follows order of property value definition">per grammar<abbr>
</table>
<p>Specifies whether this box creates a new baseline grid for its descendants
or uses the same baseline grid as its parent.
(Each box always has an associated line grid.
However, whether a box or its contents snap to a line grid
is determined by ''line-snap'' and ''box-snap''.)
<dl>
<dt><dfn>''match-parent''</dfn>
<dd>Box assumes the line grid of its parent.
<dt><dfn>''create''</dfn>
<dd>Box creates a new line grid using its own font and line layout settings.
The line grid consists of a series of horizontal lines corresponding to
all the baselines (alphabetic, text-top, text-bottom, mathematic, central, hanging, etc.)
and to the line-over and line-under edges,
positioned where they would fall if the contents of this element consisted
entirely of line boxes filled with text (no sub-elements) using the first
available font.
If the box is paginated, the line grid is restarted on each page;
since line boxes cannot be fragmented,
no page begins with the bottom part of a line's grid.
</dl>
<p>
<p class="issue">The names of these values is currently up for debate.
Current suggestions for ''match-parent'' include ''match-parent'' and ''normal'';
those for ''create'' include ''create'' and ''new''.
<p class="note">The original proposal for line grids allowed an element
to create a named grid.
This property could still be extended to do this in the future.
<p class="issue"><a href="http://www.w3.org/mid/21262.26596.32230.32937@gargle.gargle.HOWL">Håkon points out</a> that
there might be a need to have line grids aligned
to the page box rather than the page content box.
The current proposal has no way to switch between the two.
<p class="note">There might need to be an offset for more complicated designs.
How to set this offset is problematic:
usually it's not a fixed length, but the distance to clear some header content.
This could be added to a later level of line-grid.
<h2>Snapping to a Grid</h2>
<h3 id=line-snap>
Snapping Line Boxes: the 'line-snap' property</h3>
<table class=propdef>
<tr>
<th>Name:
<td><dfn>line-snap</dfn>
<tr>
<th><a href="#values">Value</a>:
<td>none | baseline | contain
<tr>
<th>Initial:
<td>none
<tr>
<th>Applies to:
<td>all elements
<tr>
<th>Inherited:
<td>yes
<tr>
<th>Animatable:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Media:
<td>visual
<tr>
<th>Computed value:
<td>specified value
<tr>
<th>Canonical order:
<td><abbr title="follows order of property value definition">per grammar<abbr>
</table>
<p>This property applies to all the line boxes directly contained by
the element, and, when not ''none'', causes each line box to shift
downward (possibly by zero) until it snaps to the line grid specified
by 'line-grid'. (The unshifted position is the position that would be
determined by normal line stacking rules, with consideration of any
new controls defined by other modules such as [[CSS3LINE]].) Values
have the following meanings:
<dl>
<dt><dfn>''none''</dfn>
<dd>Line boxes do not snap to the grid; they stack normally.
<dt><dfn>''baseline''</dfn>
<dd>The dominant baseline snaps with the matching baseline on the
line grid applying to the element.
<dt><dfn>''contain''</dfn>
<dd>Two baselines are used to align the line box: the line box is
snapped so that its ''central'' baseline (halfway between the
''text-over'' and ''text-under'' baselines) is centered between
one of the line grid's ''text-over'' baselines and a subsequent
(but not necessarily consecutive) ''text-under'' baseline.
</dl>
<p>In some cases lines of equal line height will not align perfectly
to a baseline grid: this happens, for example, when fonts (of the same
size) with different baseline tables are mixed on a line.
For this reason, if shifting the line by the largest difference between
the smallest ascent and largest ascent of a single size used on the line
would result in a smaller shift, then the contents of the line box are
shifted up within the line box so as to allow the line to snap without
jumping downward to the next grid line.
<h3 id=box-snap>
Snapping Block Boxes: the 'box-snap' property</h3>
<p class="issue">
This is a rough draft of trying to solve the box-snapping problem.
<p class="issue">
Some optional box values (margin-box, border-box) could be added
to the before and after values
to allow snapping various box model edges to the line grid.
<p class="issue">
An 'auto' value could be useful - one that defaults to center,
but snaps to before if it's the first block in a fragment container,
and snaps to after if it's the last block in a fragment container.
<table class=propdef>
<tr>
<th>Name:
<td><dfn>box-snap</dfn>
<tr>
<th><a href="#values">Value</a>:
<td> none | before | after | center | first-baseline | last-baseline
<tr>
<th>Initial:
<td>none
<tr>
<th>Applies to:
<td>block-level boxes and internal table elements except table cells
<tr>
<th>Inherited:
<td>yes
<tr>
<th>Animatable:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Media:
<td>visual
<tr>
<th>Computed value:
<td>specified value
<tr>
<th>Canonical order:
<td><abbr title="follows order of property value definition">per grammar<abbr>
</table>
<p>Specifies how the block is snapped to the baseline grid.
Values have the following meanings:
<dl>
<dt><dfn>none</dfn>
<dd>The block is not snapped to any grid.</dd>
<dt><dfn>before</dfn>
<dd>The before edge is snapped to the nearest grid line.
<dt><dfn>after</dfn>
<dd>The after edge is snapped to the nearest grid line.
<dt><dfn>center</dfn>
<dd>The block is centered centered between
one of the baseline grid's ''text-over'' baselines and a subsequent
(but not necessarily consecutive) ''text-under'' baseline.
<dt><dfn>first-baseline</dfn>
<dd>The first line box's dominant baseline is snapped to the nearest grid line.
<dt><dfn>last-baseline</dfn>
<dd>The last line box's dominant baseline is snapped to the nearest grid line.
</dl>
<p>When snapping to baselines on a line grid, either the <i>text-over</i>
or <i>text-under</i> baseline is chosen: whichever one is on the matching
side of the central baseline. For example, when snapping the before edge
in horizontal writing mode, the <i>over</i> edge is chosen. In some
cases the <i>under</i> edge might be used instead for the before edge:
for example, when the writing mode of the line grid doesn't match that of
the affected element, or when due to the 'text-orientation' settings the
<i>under</i> side corresponds to the <i>after</i> edge.
<p>To snap a block-level element to a grid line, the effective margin is increased
at that edge. <!--To snap an after border-box or half-border edge to a grid
line, the effective content-box height is increased.-->
If, however, the box is an empty block that could be
<a href="http://www.w3.org/TR/CSS21/box.html">collapsed through</a>,
then this property has no effect. [[!CSS21]]
<p>When applied to table row group and table row boxes, 'box-snap' only
affects the before and after edges, and only if those edges are not at
the beginning or end of the table, respectively. To snap a before edge
on a table row or row group, the preceding row's height is increased.
To snap an after edge on a table row or row group, the affected row's
height is increased.
<p>When applied to table column group and table column boxes, 'box-snap'
only affects the start and end edges, and only if those edges are not at
the start or end of the table, respectively. How the space is redistributed
among columns to satisfy snapping constraints is not defined, however:
<ul>
<li>In an auto-sized table no column may be smaller than its minimum
content width.
<li>The resulting table must not exceed its original measure if it
had a non-''auto'' measure.
<li>The adjusted widths must not cause the table to overflow its
containing block any more than it would with ''box-snap: none''.
</ul>
<p>To satisfy these constraints, some column edges may remain unsnapped.
<!--
Line snapping for columnsis processed from start to end: column widths
are increased or decreased in order to snap the column edges.
By preference, the widths are increased.
However if the table has an explicit size or is auto-sized and the resulting
table overflows its containing block, then columns whose widths were
increased must, one by one, switch their snap to decreasing the column
width, until the table reaches its specified size or
-->
<!--
<p>For internal table elements in separated borders tables, ''margin-box''
represents the edge at the midpoint of the border spacing. For collapsed
tables, ''margin-box'' and ''border-box'' are treated as ''half-border''.
When two coinciding edges have conflicting snap values, the later value
wins.
-->
<h2 id="conformance">
Conformance</h2>
<h3 id="conventions">Document Conventions</h3>
<p>Conformance requirements are expressed with a combination of
descriptive assertions and RFC 2119 terminology. The key words “MUST”,
“MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
“RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
document are to be interpreted as described in RFC 2119.
However, for readability, these words do not appear in all uppercase
letters in this specification.
<p>All of the text of this specification is normative except sections
explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
<p>Examples in this specification are introduced with the words “for example”
or are set apart from the normative text with <code>class="example"</code>,
like this:
<div class="example">
<p>This is an example of an informative example.</p>
</div>
<p>Informative notes begin with the word “Note” and are set apart from the
normative text with <code>class="note"</code>, like this:
<p class="note">Note, this is an informative note.</p>
<h3 id="conformance-classes">
Conformance Classes</h3>
<p>Conformance to CSS Line Grid Level 1
is defined for three conformance classes:
<dl>
<dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
style sheet</a>.
<dt><dfn>renderer</dfn></dt>
<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
that interprets the semantics of a style sheet and renders
documents that use them.
<dt><dfn id="authoring-tool">authoring tool</dfn></dt>
<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
that writes a style sheet.
</dl>
<p>A style sheet is conformant to CSS Line Grid Level 1
if all of its declarations that use properties defined in this module
have values that are valid according to the generic CSS grammar and the
individual grammars of each property as given in this module.
<p>A renderer is conformant to CSS Line Grid Level 1
if, in addition to interpreting the style sheet as defined by the
appropriate specifications, it supports all the properties defined
by CSS Line Grid Level 1 by parsing them correctly
and rendering the document accordingly. However, the inability of a
UA to correctly render a document due to limitations of the device
does not make the UA non-conformant. (For example, a UA is not
required to render color on a monochrome monitor.)
<p>An authoring tool is conformant to CSS Line Grid Level 1
if it writes syntactically correct style sheets, according to the
generic CSS grammar and the individual grammars of each property in
this module.
<h3 id="partial">
Partial Implementations</h3>
<p>So that authors can exploit the forward-compatible parsing rules to
assign fallback values, CSS renderers <strong>must</strong>
treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
as appropriate</a>) any at-rules, properties, property values, keywords,
and other syntactic constructs for which they have no usable level of
support. In particular, user agents <strong>must not</strong> selectively
ignore unsupported component values and honor supported values in a single
multi-value property declaration: if any value is considered invalid
(as unsupported values must be), CSS requires that the entire declaration
be ignored.</p>
<h3 id="experimental">
Experimental Implementations</h3>
<p>To avoid clashes with future CSS features, the CSS specifications
reserve a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
syntax</a> for proprietary property and value extensions to CSS. The CSS
Working Group recommends that experimental implementations of features in
CSS Working Drafts also use vendor-prefixed property or value names. This
avoids any incompatibilities with future changes in the draft. Once a
specification reaches the Candidate Recommendation stage, implementors
should implement the non-prefixed syntax for any feature they consider to
be correctly implemented according to spec.</p>
<h3 id="cr-exit-criteria">
CR Exit Criteria</h3>
<p>
For this specification to be advanced to Proposed Recommendation,
there must be at least two independent, interoperable implementations
of each feature. Each feature may be implemented by a different set of
products, there is no requirement that all features be implemented by
a single product. For the purposes of this criterion, we define the
following terms:
<dl>
<dt>independent <dd>each implementation must be developed by a
different party and cannot share, reuse, or derive from code
used by another qualifying implementation. Sections of code that
have no bearing on the implementation of this specification are
exempt from this requirement.
<dt>interoperable <dd>passing the respective test case(s) in the
official CSS test suite, or, if the implementation is not a Web
browser, an equivalent test. Every relevant test in the test
suite should have an equivalent test created if such a user
agent (UA) is to be used to claim interoperability. In addition
if such a UA is to be used to claim interoperability, then there
must one or more additional UAs which can also pass those
equivalent tests in the same way for the purpose of
interoperability. The equivalent tests must be made publicly
available for the purposes of peer review.
<dt>implementation <dd>a user agent which:
<ol class=inline>
<li>implements the specification.
<li>is available to the general public. The implementation may
be a shipping product or other publicly available version
(i.e., beta version, preview release, or “nightly build”).
Non-shipping product releases must have implemented the
feature(s) for a period of at least one month in order to
demonstrate stability.
<li>is not experimental (i.e., a version specifically designed
to pass the test suite and is not intended for normal usage
going forward).
</ol>
</dl>
<p>The specification will remain Candidate Recommendation for at least
six months.
<h2 class=no-num id=acknowledgments>Acknowledgments</h2>
<p>This module was made possible by the advice and contributions of
…
<h2 class=no-num id=references>References</h2>
<h3 class="no-num" id="normative-references">Normative references</h3>
<!--normative-->
<h3 class="no-num" id="other-references">Other references</h3>
<!--informative-->
<h2 class="no-num" id="index">Index</h2>
<!--index-->
<h2 class="no-num" id="property-index">Property index</h2>
<!-- properties -->
</body>
</html>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-declaration:"~/SGML/HTML4.decl"
sgml-default-doctype-name:"html"
sgml-minimize-attributes:t
sgml-nofill-elements:("pre" "style" "br")
sgml-live-element-indicator:t
sgml-omittag:nil
sgml-shorttag:nil
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-always-quote-attributes:t
sgml-indent-step:nil
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->