06-06-2013
I tired but it doesn't work
Any other options?
9 More Discussions You Might Find Interesting
1. Solaris
Hi there,
I need to get a Chinese disclaimer attached to an email on a Solaris 2.7 box. The disclaimer we use is in English and stored as a text file although I've been asked to see if we can add the Chinsese one?
Is it simply just a matter of adding the Chinese locale to the OS or is there... (1 Reply)
Discussion started by: Hayez
1 Replies
2. Filesystems, Disks and Memory
Dear All,
I have excel files containing Chinese characters. I have a requirement to display the contents of both the English and the Chinese files in the Unix box using the vi editor. But I when I try to open the Chinese files, the characters are junk. Can one of you help me in getting rid of... (4 Replies)
Discussion started by: chrisanto_2000
4 Replies
3. Shell Programming and Scripting
Hi,
I'm trying to email from UNIX, a file which has Japanese characters in it (i,e. in the contents -- not the filename).
The file gets emailed, but the Japanese characters do not show up properly when I open the file on Windows in my Outlook mailbox.
I searched a lot of forums but still... (4 Replies)
Discussion started by: jainkirti
4 Replies
4. Programming
When i write the source code in netbeans environment,if the source code,there are chinese characters,chinese characters will be displayed as box,how to solve this problem?please (2 Replies)
Discussion started by: fang_xiaoan
2 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,
I have large xml files with chinese characters on a windows box and they need to be FTP'd to UNIX box. When I ftp the file, the chinese text converts to junk characters.
I tried changing my setting on putty to UTF-8, but still cannot view the correct text. Is there something I need to... (4 Replies)
Discussion started by: tokool420
4 Replies
7. Shell Programming and Scripting
Hi there, I'm looking for a way to remove all lines that don't contain chinese characters from an xml file.
Example: http://pastebin.com/8KzSbCKe
The result should be like this: http://pastebin.com/ZywXsNhx
Only lines that don't contain chinese characters should be deleted. If theres a mix of... (3 Replies)
Discussion started by: g4rb4g3
3 Replies
8. Red Hat
Hi, One simple question: Does RHEL4 support CJK (Chinese, Japanese and Korean)? If the answer is yes, then how to implement it? Thank you in advance! (0 Replies)
Discussion started by: aixlover
0 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
XZDEC(1) XZ Utils XZDEC(1)
NAME
xzdec, lzmadec - Small .xz and .lzma decompressors
SYNOPSIS
xzdec [option]... [file]...
lzmadec [option]... [file]...
DESCRIPTION
xzdec is a liblzma-based decompression-only tool for .xz (and only .xz) files. xzdec is intended to work as a drop-in replacement for
xz(1) in the most common situations where a script has been written to use xz --decompress --stdout (and possibly a few other commonly used
options) to decompress .xz files. lzmadec is identical to xzdec except that lzmadec supports .lzma files instead of .xz files.
To reduce the size of the executable, xzdec doesn't support multithreading or localization, and doesn't read options from XZ_DEFAULTS and
XZ_OPT environment variables. xzdec doesn't support displaying intermediate progress information: sending SIGINFO to xzdec does nothing,
but sending SIGUSR1 terminates the process instead of displaying progress information.
OPTIONS
-d, --decompress, --uncompress
Ignored for xz(1) compatibility. xzdec supports only decompression.
-k, --keep
Ignored for xz(1) compatibility. xzdec never creates or removes any files.
-c, --stdout, --to-stdout
Ignored for xz(1) compatibility. xzdec always writes the decompressed data to standard output.
-q, --quiet
Specifying this once does nothing since xzdec never displays any warnings or notices. Specify this twice to suppress errors.
-Q, --no-warn
Ignored for xz(1) compatibility. xzdec never uses the exit status 2.
-h, --help
Display a help message and exit successfully.
-V, --version
Display the version number of xzdec and liblzma.
EXIT STATUS
0 All was good.
1 An error occurred.
xzdec doesn't have any warning messages like xz(1) has, thus the exit status 2 is not used by xzdec.
NOTES
Use xz(1) instead of xzdec or lzmadec for normal everyday use. xzdec or lzmadec are meant only for situations where it is important to
have a smaller decompressor than the full-featured xz(1).
xzdec and lzmadec are not really that small. The size can be reduced further by dropping features from liblzma at compile time, but that
shouldn't usually be done for executables distributed in typical non-embedded operating system distributions. If you need a truly small
.xz decompressor, consider using XZ Embedded.
SEE ALSO
xz(1)
XZ Embedded: <http://tukaani.org/xz/embedded.html>
Tukaani 2010-09-27 XZDEC(1)