09-26-2009
Bash encoding, how to change
Hey guys.
The problem is :
i need to change encoding (to be more precise UTF-8) or change the language . You see , when i log in , manuals are shown in 'Some symbols' (being written in 'Not English') and its very confusing to work. Please Help
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi all,
how can i change my shell from BASH to C shell?
i am using cygwin. (3 Replies)
Discussion started by: npatwardhan
3 Replies
2. Shell Programming and Scripting
Hi,
I would like to change the font size in bash. I know how do it in ksh:
F_VDOBLE="\033#6"
print "${F_VDOBLE}Esto es..."
But in bash I don't know
Could you help me please?
Many thanks! (5 Replies)
Discussion started by: mierdatuti
5 Replies
3. Shell Programming and Scripting
It looks like,
user@hostname:/auto/home3/user$
Desired,
user@hostname$
I added following line in .bashrc, but still its same.
export PS1=" $ "
Please help me :confused: (13 Replies)
Discussion started by: admax
13 Replies
4. Shell Programming and Scripting
Hi,
I am beginner to Unix.
My requirement is to validate the encoding used in the incoming file(csv,txt).If it is encoded with UTF-8 format,then the file should remain as such otherwise i need to chnage the encoding to UTF-8.
Please advice me how to proceed on this. (7 Replies)
Discussion started by: cnraja
7 Replies
5. Shell Programming and Scripting
I have a variable in a bash script,
DISTANCE=`awk 'BEGIN {FS="\t"} {if (NR==2) print $3;}' $OUTFILE`
this is a real number taken from a file. The value are like,
0.334561754018
I am using this value in a file name,
'$NAME'_'$DISTANCE'.txt
I would like to shorten the number some to... (4 Replies)
Discussion started by: LMHmedchem
4 Replies
6. Shell Programming and Scripting
tenxun-glibc_code-x86-64-linux-20120713190049.root.tar.bz2
To
tenxun-glibc_code-x86-64-linux.root.tar.bz2 (3 Replies)
Discussion started by: yanglei_fage
3 Replies
7. Shell Programming and Scripting
Say you got a for loop where each execution has 0 dependence on the other. Thus ideally you'd like to executed them all concurrently rather than iteratively (if you had enough CPUs). We don't quite have that many CPUs but I would like to instead partition the iterations between them.
Or maybe... (10 Replies)
Discussion started by: stevensw
10 Replies
8. Shell Programming and Scripting
I have the below bash which runs great. Before I make a change I wanted to check with experts (as I am not one). After the perl code completes, I am going to display "annotation complete" then go into the remove function .
annovar() {
# combine id and position files
cd... (2 Replies)
Discussion started by: cmccabe
2 Replies
9. Solaris
Hi all!!
I´m using command file -i myfile.xml to validate XML file encoding, but it is just saying regular file . I´m expecting / looking an output as UTF8 or ANSI / ASCII
Is there command to display the files encoding?
Thank you! (2 Replies)
Discussion started by: mrreds
2 Replies
10. UNIX for Beginners Questions & Answers
Hi all,
I'm using iconv command to change files encoding to UTF-8
If my input file has chars as those are removed creating the file without those special chars.
I tried using iconv -c, but there is still the removal.
Is there a way to keep those special chars changing just the... (6 Replies)
Discussion started by: mrreds
6 Replies
UTF(6) Games Manual UTF(6)
NAME
UTF, Unicode, ASCII, rune - character set and format
DESCRIPTION
The Plan 9 character set and representation are based on the Unicode Standard and on the ISO multibyte UTF-8 encoding (Universal Character
Set Transformation Format, 8 bits wide). The Unicode Standard represents its characters in 16 bits; UTF-8 represents such values in an
8-bit byte stream. Throughout this manual, UTF-8 is shortened to UTF.
In Plan 9, a rune is a 16-bit quantity representing a Unicode character. Internally, programs may store characters as runes. However, any
external manifestation of textual information, in files or at the interface between programs, uses a machine-independent, byte-stream
encoding called UTF.
UTF is designed so the 7-bit ASCII set (values hexadecimal 00 to 7F), appear only as themselves in the encoding. Runes with values above
7F appear as sequences of two or more bytes with values only from 80 to FF.
The UTF encoding of the Unicode Standard is backward compatible with ASCII: programs presented only with ASCII work on Plan 9 even if not
written to deal with UTF, as do programs that deal with uninterpreted byte streams. However, programs that perform semantic processing on
ASCII graphic characters must convert from UTF to runes in order to work properly with non-ASCII input. See rune(2).
Letting numbers be binary, a rune x is converted to a multibyte UTF sequence as follows:
01. x in [00000000.0bbbbbbb] -> 0bbbbbbb
10. x in [00000bbb.bbbbbbbb] -> 110bbbbb, 10bbbbbb
11. x in [bbbbbbbb.bbbbbbbb] -> 1110bbbb, 10bbbbbb, 10bbbbbb
Conversion 01 provides a one-byte sequence that spans the ASCII character set in a compatible way. Conversions 10 and 11 represent higher-
valued characters as sequences of two or three bytes with the high bit set. Plan 9 does not support the 4, 5, and 6 byte sequences pro-
posed by X-Open. When there are multiple ways to encode a value, for example rune 0, the shortest encoding is used.
In the inverse mapping, any sequence except those described above is incorrect and is converted to rune hexadecimal 0080.
FILES
/lib/unicode
table of characters and descriptions, suitable for look(1).
SEE ALSO
ascii(1), tcs(1), rune(2), keyboard(6), The Unicode Standard.
UTF(6)