@@ -38,7 +38,7 @@ Very simply put, main part of the Unicode standart is just a giant table,
38
38
which assigns a number to every L<glyph|https://en.wikipedia.org/wiki/Glyph>,
39
39
would that be a letter, a punctuation, a diacritic and so on. Those numbers
40
40
are called I<code points> and normally a Unicode code point is referred to by
41
- writing I<U+> followed by its in number hexadecimal form. For example, B<U+0050>
41
+ writing I<U+> followed by its number in hexadecimal form. For example, B<U+0050>
42
42
refers to B<LATIN CAPITAL LETTER P>, and B<U+00A9> is the B<COPYRIGHT SIGN> etc.
43
43
44
44
But this giant table of code points itself yet has nothing to do with
@@ -70,9 +70,9 @@ right now, instead we'll show you possible solution to avoid this warning:
70
70
binmode FILEHANDLE, ":encoding(UTF-8)";
71
71
72
72
This command should be put before your printing statement and it will specify
73
- the encoding layer for desired FILEHANDLE. So, to be able to print to
74
- console FILEHANDLE should be STDOUT, which is the filehandle used by Perl's
75
- C<print> and C<say> functions by default.
73
+ the encoding layer for desired C< FILEHANDLE> . So, to be able to print to
74
+ console C< FILEHANDLE> should be C< STDOUT> , which is the filehandle used by
75
+ Perl's C<print> and C<say> functions by default.
76
76
77
77
=head2 Printing symbols
78
78
@@ -141,7 +141,7 @@ B<Hint>: use Unicode B<NOT SIGN>.
141
141
=head2 Unicode in your source
142
142
143
143
But you don't have to type code points or even their names everytime. You
144
- can use any Unicode symbol in source code, for example in you string
144
+ can use any Unicode symbol in source code, for example in your string
145
145
literals. All you have to do, is to use C<utf8> pragma and then to save your
146
146
script as UTF-8 text file. Watch this:
147
147
@@ -212,7 +212,7 @@ Decode you input data using L<Encode> module.
212
212
213
213
=item *
214
214
215
- Do some some stuff with you I<textual> data.
215
+ Do some some stuff with your I<textual> data.
216
216
217
217
=item *
218
218
@@ -242,7 +242,7 @@ This is obviously true for single-byte encodings, such as I<latin1>.
242
242
243
243
say length encode('latin1', '$'); # says 1
244
244
245
- But since Unicode now defines more then 1 million code points (1,114,112 to
245
+ But since Unicode now defines more then B< 1 million> code points (1,114,112 to
246
246
be precise) it's absolutely impossible to use one byte (which can take only
247
247
256 combinations of bits) to hold them all. That's where
248
248
L<UTF encodings|Encode::Unicode> step in.
0 commit comments