- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 21 Feb 2012 14:12:07 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-break
In directory hutz:/tmp/cvs-serv32721
Modified Files:
Overview.html Overview.src.html
Log Message:
Fix links
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-break/Overview.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- Overview.html 21 Feb 2012 14:05:27 -0000 1.21
+++ Overview.html 21 Feb 2012 14:12:05 -0000 1.22
@@ -142,10 +142,10 @@
<li><a href="#fragmentation-model"><span class=secno>2. </span>
Fragmentation Model and Terminology</a>
- <li><a href="#controlling-breaks"><span class=secno>3. </span> Controlling
+ <li><a href="#breaking-controls"><span class=secno>3. </span> Controlling
Breaks</a>
<ul class=toc>
- <li><a href="#break-controls"><span class=secno>3.1. </span> Forced
+ <li><a href="#break-properties"><span class=secno>3.1. </span> Forced
breaks and keep-together: the ‘<code
class=property>break-before</code>’, ‘<code
class=property>break-after</code>’, ‘<code
@@ -156,7 +156,7 @@
‘<code class=property>widows</code>’</a>
</ul>
- <li><a href="#break-rules"><span class=secno>4. </span> Rules for
+ <li><a href="#breaking-rules"><span class=secno>4. </span> Rules for
Breaking</a>
<ul class=toc>
<li><a href="#possible-breaks"><span class=secno>4.1. </span> Possible
@@ -231,12 +231,12 @@
<p> In paged media (e.g., paper, transparencies, photo album pages, pages
displayed on computer screens as printed output simulations), as opposed
- to <a href="/TR/CSS2/media.html#continuous-media-group"> continuous
- media</a>, the content of the document is split into one or more discrete
- display surfaces. In order to avoid awkward breaks (such as halfway
- through a line of text), the layout engine must be able to shift around
- content that would fall across the page break. This process is called <dfn
- id=pagination>pagination</dfn>.
+ to <a href="http://www.w3.org/TR/CSS2/media.html#continuous-media-group">
+ continuous media</a>, the content of the document is split into one or
+ more discrete display surfaces. In order to avoid awkward breaks (such as
+ halfway through a line of text), the layout engine must be able to shift
+ around content that would fall across the page break. This process is
+ called <dfn id=pagination>pagination</dfn>.
<p> In CSS, in addition to paged media, certain layout features such as <a
href="http://www.w3.org/TR/css3-regions/">regions</a> <a
@@ -347,7 +347,7 @@
class=property>box-decoration-break</code>’ property in
[[CSS3BACKGROUND]].
- <h2 id=controlling-breaks><span class=secno>3. </span> Controlling Breaks</h2>
+ <h2 id=breaking-controls><span class=secno>3. </span> Controlling Breaks</h2>
<p> The following sections explain how breaks are controlled in a
fragmented flow. Five properties indicate where the user agent may or
@@ -356,7 +356,7 @@
href="http://www.w3.org/TR/css3-page/#left-right-first">left or right</a>)
the subsequent content should resume.
- <h3 id=break-controls><span class=secno>3.1. </span> Forced breaks and
+ <h3 id=break-properties><span class=secno>3.1. </span> Forced breaks and
keep-together: the ‘<a href="#break-before"><code
class=property>break-before</code></a>’, ‘<a
href="#break-after"><code class=property>break-after</code></a>’,
@@ -677,7 +677,7 @@
property specifies the minimum number of line boxes of a block container
that must be left in a <a href="#fragment"><i>fragment</i></a> after a
break. Examples of how they are used to control fragmentation breaks are
- given <a href=widows-orphans-example>below</a>.
+ given <a href="#widows-orphans-example">below</a>.
<p> Only positive integers are allowed as values of ‘<a
href="#orphans"><code class=property>orphans</code></a>’ and
@@ -690,7 +690,7 @@
href="#orphans"><code class=property>orphans</code></a>’, the rule
simply becomes that all lines in the block must be kept together.
- <h2 id=break-rules><span class=secno>4. </span> Rules for Breaking</h2>
+ <h2 id=breaking-rules><span class=secno>4. </span> Rules for Breaking</h2>
<p> A fragmented flow may be broken across fragmenters at a number of <a
href="#possible-breaks">possible break points</a>. In the case of <a
@@ -820,8 +820,8 @@
the latest element in the flow wins.
<p class=note> A page break must also occur at <a
- href="#brk-btw-blocks">(1)</a> if the last line box above this margin and
- the first one below it do not have the same value for ‘<code
+ href="#btw-blocks">(1)</a> if the last line box above this margin and the
+ first one below it do not have the same value for ‘<code
class=property>page</code>’. See <a href="#CSS3PAGE"
rel=biblioentry>[CSS3PAGE]<!--{{!CSS3PAGE}}--></a>
@@ -829,7 +829,7 @@
<p> While <a href="#breaking-controls">breaking controls</a> can force
breaks, they can also discourage them. The following rules control whether
- breaking at a <a href="#posible-breaks">possible break point</a> is
+ breaking at a <a href="#possible-breaks">possible break point</a> is
allowed:
<dl>
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-break/Overview.src.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- Overview.src.html 21 Feb 2012 14:05:27 -0000 1.22
+++ Overview.src.html 21 Feb 2012 14:12:05 -0000 1.23
@@ -65,7 +65,7 @@
<p>
In paged media (e.g., paper, transparencies, photo album pages, pages
displayed on computer screens as printed output simulations), as
- opposed to <a href="/TR/CSS2/media.html#continuous-media-group">
+ opposed to <a href="http://www.w3.org/TR/CSS2/media.html#continuous-media-group">
continuous media</a>, the content of the document is split into one or
more discrete display surfaces. In order to avoid awkward breaks
(such as halfway through a line of text), the layout engine must be
@@ -176,7 +176,7 @@
the 'box-decoration-break' property in [[CSS3BACKGROUND]].
</p>
-<h2 id="controlling-breaks">
+<h2 id="breaking-controls">
Controlling Breaks</h2>
<p>
@@ -187,7 +187,7 @@
the subsequent content should resume.
</p>
-<h3 id="break-controls">
+<h3 id="break-properties">
Forced breaks and keep-together: the 'break-before', 'break-after', 'break-inside'
properties</h3>
@@ -445,7 +445,7 @@
of line boxes of a block container that must be left in a
<i>fragment</i> after a break. Examples of how they are used to
control fragmentation breaks are given
- <a href="widows-orphans-example">below</a>.
+ <a href="#widows-orphans-example">below</a>.
</p>
<p>
Only positive integers are allowed as values of 'orphans' and 'widows'. Negative
@@ -457,7 +457,7 @@
simply becomes that all lines in the block must be kept together.
</p>
-<h2 id="break-rules">
+<h2 id="breaking-rules">
Rules for Breaking</h2>
<p>
@@ -590,7 +590,7 @@
latest element in the flow wins.
</p>
<p class="note">
- A page break must also occur at <a href="#brk-btw-blocks">(1)</a>
+ A page break must also occur at <a href="#btw-blocks">(1)</a>
if the last line box above this margin and the first one below it do not have the
same value for 'page'. See [[!CSS3PAGE]]
</p>
@@ -601,7 +601,7 @@
<p>
While <a href="#breaking-controls">breaking controls</a> can force breaks,
they can also discourage them. The following rules control whether breaking
- at a <a href="#posible-breaks">possible break point</a> is allowed:
+ at a <a href="#possible-breaks">possible break point</a> is allowed:
</p>
<dl>
<dt>Rule A</dt>
Received on Tuesday, 21 February 2012 14:12:09 UTC