cvtenc(1) [debian man page]

CVTENC(1)						       GNUstep System Manual							 CVTENC(1)

NAME

       cvtenc - file encoding converter

SYNOPSIS

       cvtenc [-Encoding encoding] [-EscapeIn yes|NO] [-EscapeOut yes|NO]
	filename

DESCRIPTION

       Converts  a file encoded in a specified or default non-unicode encoding to unicode (UTF16), or, if the file is already in unicode, converts
       it to a specified or default non-unicode encoding.  The converted text is printed to standard out.  If the filename is a hyphen	then  this
       tool reads from standard input.

OPTIONS

       -Encoding  encoding
	   Specify  non-unicode encoding to be used.  The direction of conversion depends on whether the file given as input is recognized as uni-
	   code (from the higher order bytes).	To get a list of available encodings, enter "list" for the encoding.  If this  is  not	specified,
	   the default encoding for the current locale is used.

       -EscapeIn YES|NO
	   Specify '-EscapeIn YES' (the default is 'NO') to parse the input for u escape sequences (as in property lists).

       -EscapeOut YES|NO
	   Specify  '-EscapeOut YES' (the default is 'NO') to generate u escape sequences (as in property lists) in the output.  Note, this might
	   produce unexpected results for some encodings.

       -Unicode IN|OUT
	   Specify '-Unicode IN' (or '-Unicode OUT') to control the direction of conversion rather than having the tool guess it on the  basis	of
	   the	content  it  reads.  Using '-Unicode IN' means that the tool reads UTF16 data and writes C-String data, while using '-Unicode OUT'
	   merans that the tool reads C-String data and writes UTF16 data.

HISTORY

       Written in 2002.  Minr update in 2010.

       This manual page first appeared in gnustep-base 1.9.2 (March 2004).

AUTHORS

       cvtenc was written by Richard Frith-Macdonald <rfm@gnu.org>

GNUstep 							   February 2004							 CVTENC(1)

encoding(n)						       Tcl Built-In Commands						       encoding(n)

__________________________________________________________________________________________________________________________________________________

NAME

       encoding - Manipulate encodings

SYNOPSIS

       encoding option ?arg arg ...?
_________________________________________________________________

INTRODUCTION

       Strings	in Tcl are encoded using 16-bit Unicode characters.  Different operating system interfaces or applications may generate strings in
       other encodings such as Shift-JIS.  The encoding command helps to bridge the gap between Unicode and these other formats.

DESCRIPTION

       Performs one of several encoding related operations, depending on option.  The legal options are:

       encoding convertfrom ?encoding? data
	      Convert data to Unicode from the specified encoding.  The characters in data are treated as binary data where the  lower	8-bits	of
	      each  character  is  taken  as a single byte.  The resulting sequence of bytes is treated as a string in the specified encoding.	If
	      encoding is not specified, the current system encoding is used.

       encoding convertto ?encoding? string
	      Convert string from Unicode to the specified encoding.  The result is a sequence of bytes  that  represents  the	converted  string.
	      Each byte is stored in the lower 8-bits of a Unicode character.  If encoding is not specified, the current system encoding is used.

       encoding names
	      Returns a list containing the names of all of the encodings that are currently available.

       encoding system ?encoding?
	      Set the system encoding to encoding. If encoding is omitted then the command returns the current system encoding.  The system encod-
	      ing is used whenever Tcl passes strings to system calls.

EXAMPLE

       It is common practice to write script files using a text editor that produces output in the euc-jp encoding,  which  represents	the  ASCII
       characters  as  singe bytes and Japanese characters as two bytes.  This makes it easy to embed literal strings that correspond to non-ASCII
       characters by simply typing the strings in place in the script.	However, because the source command always reads files using the ISO8859-1
       encoding, Tcl will treat each byte in the file as a separate character that maps to the 00 page in Unicode.  The resulting Tcl strings will
       not contain the expected Japanese characters.  Instead, they will contain a sequence of Latin-1 characters that correspond to the bytes	of
       the original string.  The encoding command can be used to convert this string to the expected Japanese Unicode characters.  For example,
		set s [encoding convertfrom euc-jp "xA4xCF"]
       would return the Unicode string "u306F", which is the Hiragana letter HA.

SEE ALSO

       Tcl_GetEncoding(3)

KEYWORDS

       encoding

Tcl									8.1							       encoding(n)