This appendix is normative.
The following are notes about implementation requirements corresponding to various features in the SVG language.
There are various scenarios where an SVG document fragment is technically in error:
A document can go in and out of error over time. For example, document changes from the SVG DOM or from animation can cause a document to become in error and a further change can cause the document to become correct again.
The following error processing shall occur when a document is in error:
Because of situations where a block of scripting changes might cause a given SVG document fragment to go into and out of error, error processing shall occur only at times when document presentation (e.g., rendering to the display device) is updated. In particular, error processing shall be disabled whenever redraw has been suspended via DOM calls to suspendRedraw.
Here we previously required SVG user agents to check the PUBLIC identifier in a DOCTYPE declaration or the "version" of the SVG language as represented by the namespace to verify that it understands the version of SVG the document was authored against. It also had wording about not needing to render future specification's elements, and for a UA to alert the user if it encounters a version it doesn't recognise. This should all be replaced with some wording about how to process elements the UA recognises and those that it doesn't, without any reference to versions of the specification.
Some numeric attribute and property values have restricted ranges, such as color component values. When out-of-range values are provided, the user agent shall defer any error checking until after presentation time, as composited actions might produce intermediate values which are out-of-range but final values which are within range.
Color values are not in error if they are out-of-range, even if final computations produce an out-of-range color value at presentation time. It is recommended that user agents clamp color values to the nearest color value (possibly determined by simple clipping) which the system can process as late as possible (e.g., presentation time), although it is acceptable for user agents to clamp color values as early as parse time. Thus, implementation dependencies might preclude consistent behavior across different systems when out-of-range color values are used.
Opacity values out-of-range are not in error and should be clamped to the range 0 to 1 at the time which opacity values have to be processed (e.g., at presentation time or when it is necessary to perform intermediate filter effect calculations).
We should move all of this into the relevant chapters, rather than having it hidden here in an appendix.
A conforming SVG user agent must implement path rendering as follows:
stroke-linecap
’ has a value of
round or
square.(newx1, newy1) = (curx - (oldx2 - curx), cury - (oldy2 - cury)) = (2*curx - oldx2, 2*cury - oldy2)
An elliptical arc is a particular path command. As such, it is described by the following parameters in order:
(x_{1}, y_{1}) are the absolute coordinates of the current point on the path, obtained from the last two parameters of the previous path command.
r_{x} and r_{y} are the radii of the ellipse (also known as its semi-major and semi-minor axes).
φ is the angle from the x-axis of the current coordinate system to the x-axis of the ellipse.
f_{A} is the large arc flag, and is 0 if an arc spanning less than or equal to 180 degrees is chosen, or 1 if an arc spanning greater than 180 degrees is chosen.
f_{S} is the sweep flag, and is 0 if the line joining center to arc sweeps through decreasing angles, or 1 if it sweeps through increasing angles.
(x_{2}, y_{2}) are the absolute coordinates of the final point of the arc.
This parameterization of elliptical arcs will be referred to as endpoint parameterization. One of the advantages of endpoint parameterization is that it permits a consistent path syntax in which all path commands end in the coordinates of the new "current point". The following notes give rules and formulas to help implementers deal with endpoint parameterization.
Arbitrary numerical values are permitted for all elliptical arc parameters, but where these values are invalid or out-of-range, an implementation must make sense of them as follows:
If the endpoints (x_{1}, y_{1}) and (x_{2}, y_{2}) are identical, then this is equivalent to omitting the elliptical arc segment entirely.
If r_{x} = 0 or r_{y} = 0 then this arc is treated as a straight line segment (a "lineto") joining the endpoints.
If r_{x} or r_{y} have negative signs, these are dropped; the absolute value is used instead.
If r_{x}, r_{y} and φ are such that there is no solution (basically, the ellipse is not big enough to reach from (x_{1}, y_{1}) to (x_{2}, y_{2})) then the ellipse is scaled up uniformly until there is exactly one solution (until the ellipse is just big enough).
φ is taken mod 360 degrees.
Any nonzero value for either of the flags f_{A} or f_{S} is taken to mean the value 1.
This forgiving yet consistent treatment of out-of-range values ensures that:
An arbitrary point (x, y) on the elliptical arc can be described by the 2-dimensional matrix equation:
$\left(\begin{array}{c}x\\ y\end{array}\right)=\left(\begin{array}{cc}\mathrm{cos}\phi & -\mathrm{sin}\phi \\ \mathrm{sin}\phi & \mathrm{cos}\phi \end{array}\right)\xb7\left(\begin{array}{c}{r}_{x}\mathrm{cos}\theta \\ {r}_{y}\mathrm{sin}\theta \end{array}\right)+\left(\begin{array}{c}{c}_{x}\\ {c}_{y}\end{array}\right)$ | (F.6.3.1) |
(c_{x}, c_{y}) are the coordinates of the center of the ellipse.
r_{x} and r_{y} are the radii of the ellipse (also known as its semi-major and semi-minor axes).
θ is the angle from the x-axis of the current coordinate system to the x-axis of the ellipse.
θ ranges from:
If one thinks of an ellipse as a circle that has been stretched and then rotated, then θ_{1}, θ_{2} and Δθ are the start angle, end angle and sweep angle, respectively of the arc prior to the stretch and rotate operations. This leads to an alternate parameterization which is common among graphics APIs, which will be referred to as center parameterization. In the next sections, formulas are given for mapping in both directions between center parameterization and endpoint parameterization.
Given the following variables:
c_{x} c_{y} r_{x} r_{y} φ θ_{1} Δθ
the task is to find:
x_{1} y_{1} x_{2} y_{2} f_{A} f_{S}
This can be achieved using the following formulas:
(F.6.4.1) | |
(F.6.4.2) | |
(F.6.4.3) | |
(F.6.4.4) |
Given the following variables:
x_{1} y_{1} x_{2} y_{2} f_{A} f_{S} r_{x} r_{y} φ
the task is to find:
c_{x} c_{y} θ_{1} Δθ
The equations simplify after a translation which places the origin at the midpoint of the line joining (x_{1}, y_{1}) to (x_{2}, y_{2}), followed by a rotation to line up the coordinate axes with the axes of the ellipse. All transformed coordinates will be written with primes. They are computed as intermediate values on the way toward finding the required center parameterization variables. This procedure consists of the following steps:
Step 1: Compute (x_{1}′, y_{1}′)
(F.6.5.1) |
Step 2: Compute (c_{x}′, c_{y}′)
(F.6.5.2) |
where the + sign is chosen if f_{A} ≠ f_{S}, and the − sign is chosen if f_{A} = f_{S}.
Step 3: Compute (c_{x}, c_{y}) from (c_{x}′, c_{y}′)
(F.6.5.3) |
Step 4: Compute θ_{1} and Δθ
In general, the angle between two vectors (u_{x}, u_{y}) and (v_{x}, v_{y}) can be computed as
(F.6.5.4) |
where the ± sign appearing here is the sign of u_{x} v_{y} − u_{y} v_{x}.
This angle function can be used to express θ_{1} and Δθ as follows:
(F.6.5.5) | |
(F.6.5.6) |
where θ_{1} is fixed in the range −360° < Δθ < 360° such that:
if f_{S} = 0, then Δθ < 0,
else if f_{S} = 1, then Δθ > 0.
In other words, if f_{S} = 0 and the right side of (F.6.5.6) is greater than 0, then subtract 360°, whereas if f_{S} = 1 and the right side of (F.6.5.6) is less than 0, then add 360°. In all other cases leave it as is.
This section formalizes the adjustments to out-of-range r_{x} and r_{y} mentioned in F.6.2. Algorithmically these adjustments consist of the following steps:
Step 1: Ensure radii are non-zero
If r_{x} = 0 or r_{y} = 0, then treat this as a straight line from (x_{1}, y_{1}) to (x_{2}, y_{2}) and stop. Otherwise,
Step 2: Ensure radii are positive
Take the absolute value of r_{x} and r_{y}:
(F.6.6.1) |
Step 3: Ensure radii are large enough
Using the primed coordinate values of equation (F.6.5.1), compute
(F.6.6.2) |
If the result of the above equation is less than or equal to 1, then no further change need be made to r_{x} and r_{y}. If the result of the above equation is greater than 1, then make the replacements
(F.6.6.3) |
Step 4: Proceed with computations
Proceed with the remaining elliptical arc computations, such as those in section F.6.5. Note: As a consequence of the radii corrections in this section, equation (F.6.5.2) for the center of the ellipse always has at least one solution (i.e. the radicand is never negative). In the case that the radii are scaled up using equation (F.6.6.3), the radicand of (F.6.5.2) is zero and there is exactly one solution for the center of the ellipse.
The following implementation notes describe the algorithm for deciding which characters are selected during a text selection operation.
As the text selection operation occurs (e.g., while the user clicks and drags the mouse to identify the selection), the user agent determines a start selection position and an end selection position, each of which represents a position in the text string between two characters. After determining start selection position and end selection position, the user agent selects the appropriate characters, where the resulting text selection consists of either:
On systems with pointer devices, to determine the start selection position, the SVG user agent determines which boundary between characters corresponding to rendered glyphs is the best target (e.g., closest) based on the current pointer location at the time of the event that initiates the selection operation (e.g., the mouse down event). The user agent then tracks the completion of the selection operation (e.g., the mouse drag, followed ultimately by the mouse up). At the end of the selection operation, the user agent determines which boundary between characters is the best target (e.g., closest) for the end selection position.
If no character reordering has occurred due to bidirectionality, then the selection consists of all characters between the start selection position and end selection position. For example, if a ‘text’ element contains the string "abcdef" and the start selection position and end selection positions are 0 and 3 respectively (assuming the left side of the "a" is position zero), then the selection will consist of "abc".
When the user agent is implementing selection of bidirectional text, and when the selection starts (or ends) between characters which are not contiguous in logical order, then there might be multiple potential combinations of characters that can be considered part of the selection. The algorithms to choose among the combinations of potential selection options shall choose the selection option which most closely matches the text string's visual rendering order.
When multiple characters map inseparably to a given set of one or more glyphs, the user agent can either disallow the selection to start in the middle of the glyph set or can attempt to allocate portions of the area taken up by the glyph set to the characters that correspond to the glyph.
For systems which support pointer devices such as a mouse, the user agent is required to provide a mechanism for selecting text even when the given text has associated event handlers or links, which might block text selection due to event processing precedence rules (see Pointer events). One implementation option: For platforms which support a pointer device such as a mouse, the user agent may provide for a small additional region around character cells which initiates text selection operations but does not initiate event handlers or links.
For user agents which support both zooming on display devices and printing, it is recommended that the default printing option produce printed output that reflects the display device's current view of the current SVG document fragment (assuming there is no media-specific styling), taking into account any zooming and panning done by the user, the current state of animation, and any document changes due to DOM and scripting. Thus, if the user zooms into a particular area of a map on the display device and then requests a hardcopy, the hardcopy should show the same view of the map as appears on the display device. If a user pauses an animation and prints, the hardcopy should show the same graphics as the currently paused picture on the display device. If scripting has added or removed elements from the document, then the hardcopy should reflect the same changes that would be reflected on the display.
When an SVG document is rendered on a static-only device such as a printer which does not support SVG's animation and scripting and facilities, then the user agent shall ignore any animation and scripting elements in the document and render the remaining graphics elements according to the rules in this specification.