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
|
Description: spelling fixes
Origin: vendor
Author: gregor herrmann <gregoa@debian.org>
Last-Update: 2018-07-29
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=125958
Bug: https://rt.cpan.org/Ticket/Display.html?id=125958
--- a/lib/Tickit/Debug.pm
+++ b/lib/Tickit/Debug.pm
@@ -33,7 +33,7 @@
=head1 FLAGS
-Each flag name starts with a upper-case letters indiciating the subsystem it
+Each flag name starts with a upper-case letters indicating the subsystem it
relates to, then lower-case letters to indicate the particular kind of event
or message.
@@ -77,7 +77,7 @@
=head3 Wh
-Heirarchy changes on Windows (creates, deletes, re-orderings)
+Hierarchy changes on Windows (creates, deletes, re-orderings)
=head3 Ws
--- a/lib/Tickit/Pen.pm
+++ b/lib/Tickit/Pen.pm
@@ -81,7 +81,7 @@
Applications wishing to use this attribute should be aware that the majority
of terminal drivers will not be able to support it, and so should make sure to
-set an approriate regular colour index as well. Some terminals using the
+set an appropriate regular colour index as well. Some terminals using the
F<xterm> driver may make use of it, however, and therefore ignore the index
version.
--- a/lib/Tickit/RenderBuffer.pm
+++ b/lib/Tickit/RenderBuffer.pm
@@ -335,7 +335,7 @@
is a saved state on the stack it will be merged with the rendering pen of the
most recent saved state.
-This method may be preferrable to passing pens into multiple C<text> or
+This method may be preferable to passing pens into multiple C<text> or
C<erase> calls as it may be more efficient than merging the same pen on every
call. If the original pen is still required afterwards, the C<savepen> /
C<restore> pair may be useful.
@@ -509,7 +509,7 @@
the entire body of the cell and stop at the boundary. By default line segments
will start and end at the centre of the cells, so that horizontal and vertical
lines meeting in a cell will form a neat corner. When drawing isolated lines
-such as horizontal or vertical rules, it is preferrable that the line go right
+such as horizontal or vertical rules, it is preferable that the line go right
through the cells at the start and end. To control this behaviour, the
C<$caps> bitmask is used. C<CAP_START> and C<CAP_END> state that the line
should consume the whole of the start or end cell, respectively; C<CAP_BOTH>
--- a/lib/Tickit/StringPos.pm
+++ b/lib/Tickit/StringPos.pm
@@ -38,7 +38,7 @@
The C<codepoints> member counts individual Unicode codepoints.
-The C<graphemes> member counts whole composed grahical clusters of codepoints,
+The C<graphemes> member counts whole composed graphical clusters of codepoints,
where combining accents which count as individual codepoints do not count as
separate graphemes. For example, the codepoint sequence U+0065 U+0301 would
increment the C<codepoint> counter by 2 and the C<graphemes> counter by 1.
--- a/lib/Tickit/Term.pm
+++ b/lib/Tickit/Term.pm
@@ -229,7 +229,7 @@
$id = $term->bind_event( $ev, $flags, $code, $data )
-The C<$code> argument may optionally be preceeded by an integer of flag
+The C<$code> argument may optionally be preceded by an integer of flag
values. This should be zero to apply default semantics, or a bitmask of one or
more of the following constants:
--- a/lib/Tickit/Window.pm
+++ b/lib/Tickit/Window.pm
@@ -208,7 +208,7 @@
$id = $win->bind_event( $ev, $flags, $code, $data )
-The C<$code> argument may optionally be preceeded by an integer of flag
+The C<$code> argument may optionally be preceded by an integer of flag
values. This should be zero to apply default semantics, or a bitmask of
constants. The constants are documented in
L<Tickit::Term/bind_event (with flags)>.
|