09-07-2009
Quote:
Originally Posted by
jainkirti
Yes, my windows machine does have Japanese fonts and they are enabled.
I even switched the Langauage to Japanese.
My guess is it's an encoding issue with eucjis/sjis charset not being set for the attachment when i'm using uuencode.
from man uuencode
Quote:
The encoding uses only print-
ing ASCII characters and includes the mode of the file and the operand
name
I guess there is a problem with this.
Try, the -base64 option and before try printing it in stdout with term set to utf8 to see its encoding/transferring what we are really interested.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a file, which when you look at it, appears as if it has spaces....
But sometimes, it is has tab or Nulls or some other character which we are not able to see.....
How to find what character exactly it is in the file, where ever we are seeing a space... (Iam in solaris)... (1 Reply)
Discussion started by: thanuman
1 Replies
2. UNIX for Dummies Questions & Answers
We have a unix file that contains special characters (ie. Ñ, °, É, ¿ , £ , ø ). When I try to read this file I get a codepage error and the characters are replaced by the # symbol. How do I keep the special characters from being read?
Thanks.
Ryan (3 Replies)
Discussion started by: Ryan2786
3 Replies
3. AIX
Hi,
I have a PPD(Postscript printer description) file which is in Japanese.
I want to use the PPD file in AIX.
Is it possible
where should i set the Lang.
and is it possible to type in Japanese language.
Please help. (3 Replies)
Discussion started by: meeraramanathan
3 Replies
4. Shell Programming and Scripting
Hi,
I have a syntax for mail attachment as
$EMAIL "Wrapper $wrapper_script_name has failed" " $wrapper_script_name has Failed " $failed_email_address
and $EMAIL is as below
MSGSub=${1}
MSGText=${2}
RMAIL=${3}
#set LANG=''
export LANG=''
echo "${MSGSub}" | mailx -s "${MSGText}" ... (1 Reply)
Discussion started by: satgur
1 Replies
5. Shell Programming and Scripting
Greetings,
I want to use a script (preferably awk) which determines if the first character in a line is double-byte (as in Japanese or Chinese) and deletes it.
For example:
(in the above quote, I see Japanese on my screen for two lines - with 2 characters in the first and 3 characters in the... (8 Replies)
Discussion started by: ubbeauty
8 Replies
6. Solaris
Hello All,
I have a solaris 10 sparc machine . I have installed all the locale .
hi_IN.UTF-8. and similarly for japanese. But when i am trying to insert Hindi test in a file using vi . Every thing is getting turned in dots .
Can any one help in this .I have configured the LANG and... (14 Replies)
Discussion started by: Arif29march
14 Replies
7. Shell Programming and Scripting
Hi Experts,
I am working on HP-UX. I am new to shell scripting. I would like to have a shell script which will prefix:
1. "H|" before first row of my file and,
2. "T" for all other rows of the file.
For Example - File before running the script 20100430|4123451810|218.50|TC
20100430 ... (4 Replies)
Discussion started by: phani333
4 Replies
8. Shell Programming and Scripting
Hi,
We have a non printable character "®" in our file , we want to remove this character, we tried tr -dc '' < oldfile> newfile but this command is removing all new line entries along with the non printable character and all the records are coming in one line(it is changing the format of the... (2 Replies)
Discussion started by: pyaranoid
2 Replies
9. Red Hat
Hello,
I'm trying to figure out how to display Chinese and Japanese Characters on my RHEL 6 Console. There is no more "bogl-bterm" for RHEL6, that is not supported anymore. Is there any way that I could display them?
Thank you. (2 Replies)
Discussion started by: pjeedu2247
2 Replies
10. SuSE
Hello,
I'm trying to figure out how to display Chinese and Japanese Characters on my SLES 11 Console. Is there any way that I could display those characters on my console?
Thank you. (3 Replies)
Discussion started by: pjeedu2247
3 Replies
LEARN ABOUT SUSE
uudecode
uuencode(1) General Commands Manual uuencode(1)
NAME
uuencode, uudecode - encode a binary file, or decode its representation
SYNOPSIS
uuencode [-m] [ file ] name
uudecode [-o outfile] [ file ]...
DESCRIPTION
Uuencode and uudecode are used to transmit binary files over transmission mediums that do not support other than simple ASCII data.
Uuencode reads file (or by default the standard input) and writes an encoded version to the standard output. The encoding uses only print-
ing ASCII characters and includes the mode of the file and the operand name for use by uudecode. If name is /dev/stdout the result will be
written to standard output. By default the standard UU encoding format will be used. If the option -m is given on the command line base64
encoding is used instead.
Note: uuencode uses buffered input and assumes that it is not hand typed from a tty. The consequence is that at a tty, you may need to hit
Ctl-D several times to terminate input.
Uudecode transforms uuencoded files (or by default, the standard input) into the original form. The resulting file is named name (or out-
file if the -o option is given) and will have the mode of the original file except that setuid and execute bits are not retained. If out-
file or name is /dev/stdout the result will be written to standard output. Uudecode ignores any leading and trailing lines. The program
can automatically decide which of the both supported encoding schemes are used.
EXAMPLES
The following example packages up a source tree, compresses it, uuencodes it and mails it to a user on another system. When uudecode is
run on the target system, the file ``src_tree.tar.Z'' will be created which may then be uncompressed and extracted into the original tree.
tar cf - src_tree | compress | uuencode src_tree.tar.Z | mail sys1!sys2!user
SEE ALSO
compress(1), mail(1), uucp(1), uuencode(5)
STANDARDS
This implementation is compliant with P1003.2b/D11.
BUGS
If more than one file is given to uudecode and the -o option is given or more than one name in the encoded files are the same the result is
probably not what is expected.
The encoded form of the file is expanded by 37% for UU encoding and by 35% for base64 encoding (3 bytes become 4 plus control information).
REPORTING BUGS
Report bugs to <bug-gnu-utils@gnu.org>. Please put sharutils or uuencode in the subject line. It helps to spot the message.
HISTORY
The uuencode command appeared in BSD 4.0.
uuencode(1)