perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "tr_TR.UTF-8",
LC_MONETARY = "tr_TR.UTF-8",
LC_ADDRESS = "tr_TR.UTF-8",
LC_TELEPHONE = "tr_TR.UTF-8",
LC_NAME = "tr_TR.UTF-8",
LC_MEASUREMENT = "tr_TR.UTF-8",
LC_IDENTIFICATION = "tr_TR.UTF-8",
LC_NUMERIC = "tr_TR.UTF-8",
LC_PAPER = "tr_TR.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
1 definitions retrieved:
The Free On-line Dictionary of Computing (18 March 2015):
character encoding scheme
(Or "character encoding scheme") A mapping of
binary values to code positions and back; generally a 1:1
In the case of ASCII, this is generally a f(x)=x mapping:
code point 65 maps to the byte value 65, and vice versa. This
is possible because ASCII uses only code positions
representable as single bytes, i.e., values between 0 and 255,
at most. (US-ASCII only uses values 0 to 127, in fact.)
Unicode and many CJKcoded character sets use many more
than 255 positions, requiring more complex mappings: sometimes
the characters are mapped onto pairs of bytes (see DBCS).
In many cases, this breaks programs that assume a one-to-one
mapping of bytes to characters, and so, for example, treat any
occurrance of the byte value 13 as a carriage return. To
avoid this problem, character encodings such as UTF-8 were