09-11-2010
Quote:
Originally Posted by
cjcox
LANG=C TERM=lpr man ln >ln.txt
.
The code presented by cjcox does not work at all. Setting the environment variable TERM to lpr does not seem to change the behavior of man. The man command still outputs non-ASCII characters. Furthermore, because he omitted col, the resultant ln.txt is illegible when opened with KWrite. I wonder if cjcox was just kidding.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am writing the script to encrypt and decrypt content of the text file.
How can I convert ASCII to characters and backward? I need it for Bourne shell script.
Thanks::confused: (3 Replies)
Discussion started by: woody
3 Replies
2. Shell Programming and Scripting
after converting my ebcidic file to ascii i get the following output
2097152+0 records in
1797345+1 records out
Why is there a difference in number of records.
Is the converson chopping off any records.
All i am doing is just a conversion using the following script
dd if=xaa cbs=152 ... (0 Replies)
Discussion started by: rintingtong
0 Replies
3. Shell Programming and Scripting
I have a file say "codefile" here ,contains data like this
Hi! How are you?
I need to covert this data into stram of equivalant ASCII values
I wrote follwoing script.
#!/bin/bash
while read -n1 char
do
printf "%d" \'$char
done < codefile
this gives me output
... (4 Replies)
Discussion started by: sunilmenhdiratt
4 Replies
4. Shell Programming and Scripting
Hi,
Can anyone please help me ascci to decimal conversion in bash
I have a file which contains stream of numbers like this,these are ascci values
729711810132973278105991013268971213233
I want to covert it to its actual value like upper code's decimal is
"Have a Nice Day!"
... (15 Replies)
Discussion started by: sunilmenhdiratt
15 Replies
5. UNIX for Dummies Questions & Answers
when i try to convert a mainframe EBCDIC file to ASCII ,i dont see correct file this is the source file
... (3 Replies)
Discussion started by: venkatvelpula
3 Replies
6. Programming
Compiling xpp (The X Printing Panel) on SL6 (RHEL6 essentially):
xpp.cxx: In constructor ‘printFiles::printFiles(int, char**, int&)’:
xpp.cxx:200: error: invalid conversion from ‘const char*’ to ‘char*’
The same error with all c++ constructors - gcc 4.4.4.
If anyone can throw any light on... (8 Replies)
Discussion started by: GSO
8 Replies
7. Shell Programming and Scripting
I Am trying to change the file encoding from ASCII to UTF-8 using below command
iconv -f ASCII -t UTF-8 <input_file> > <output_file>
But the output_file is not actually in UTF-8 format. If I use the file command to check the file encoding it still says ASCII.
While converting am not... (5 Replies)
Discussion started by: Sriranga
5 Replies
8. Programming
Pointers are seeming to get the best of me and I get that error in my program.
Here is the code
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#define REPORTHEADING1 " Employee Pay Hours Gross Tax Net\n"
#define REPORTHEADING2 " Name ... (1 Reply)
Discussion started by: Plum
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have a input file which is EBCIDIC and it has packed decimals.
Can anyone help me to convert EBCIDIC file to ASCII(Need to convert even Packed decimal values also to normal format).
Thanks
swapna (12 Replies)
Discussion started by: swapna_1990
12 Replies
10. UNIX for Advanced & Expert Users
Hi,
We have a mainframe file which is in EBCDIC format.We dont have direct access to mainframe ,client has provided us the mainframe file.The mainframe file is containing pact data(COMP1 ,COMP2 etc) which are unreadble.Can anyone suggest me how to convert this kind of ebcdic file to ascii... (11 Replies)
Discussion started by: swapna_1990
11 Replies
LEARN ABOUT OSX
osascript
OSASCRIPT(1) BSD General Commands Manual OSASCRIPT(1)
NAME
osascript -- execute AppleScripts and other OSA language scripts
SYNOPSIS
osascript [-l language] [-s flags] [-e statement | programfile] [argument ...]
DESCRIPTION
osascript executes the given script. It was designed for use with AppleScript, but will work with any Open Scripting Architecture (OSA) lan-
guage. To get a list of the OSA languages installed on your system, use osalang(1). For documentation on AppleScript itself, see
<http://www.apple.com/applescript>.
osascript will look for the script in one of the following three places:
1. Specified line by line using -e switches on the command line.
2. Contained in the file specified by the first filename on the command line. This file may be plain text or a compiled script.
3. Passed in using standard input. This works only if there are no filename arguments; to pass arguments to a STDIN-read script, you must
explicitly specify ``-'' for the script name.
Any arguments following the script will be passed as a list of strings to the direct parameter of the ``run'' handler. For example:
a.scpt:
on run argv
return "hello, " & item 1 of argv & "."
end run
% osascript a.scpt world
hello, world.
The options are as follows:
-e statement
Enter one line of a script. If -e is given, osascript will not look for a filename in the argument list. Multiple -e options may be
given to build up a multi-line script. Because most scripts use characters that are special to many shell programs (e.g., AppleScript
uses single and double quote marks, ``('', ``)'', and ``*''), the statement will have to be correctly quoted and escaped to get it past
the shell intact.
-l language
Override the language for any plain text files. Normally, plain text files are compiled as AppleScript.
-s flags
Modify the output style. The flags argument is a string consisting of any of the modifier characters e, h, o, and s. Multiple modi-
fiers can be concatenated in the same string, and multiple -s options can be specified. The modifiers come in exclusive pairs; if con-
flicting modifiers are specified, the last one takes precedence. The meanings of the modifier characters are as follows:
h Print values in human-readable form (default).
s Print values in recompilable source form.
osascript normally prints its results in human-readable form: strings do not have quotes around them, characters are not escaped,
braces for lists and records are omitted, etc. This is generally more useful, but can introduce ambiguities. For example, the
lists '{"foo", "bar"}' and '{{"foo", {"bar"}}}' would both be displayed as 'foo, bar'. To see the results in an unambiguous form
that could be recompiled into the same value, use the s modifier.
e Print script errors to stderr (default).
o Print script errors to stdout.
osascript normally prints script errors to stderr, so downstream clients only see valid results. When running automated tests, how-
ever, using the o modifier lets you distinguish script errors, which you care about matching, from other diagnostic output, which
you don't.
SEE ALSO
osacompile(1), osalang(1)
HISTORY
osascript in Mac OS X 10.0 would translate '
' characters in the output to '
' and provided c and r modifiers for the -s option to change
this. osascript now always leaves the output alone; pipe through tr(1) if necessary.
Prior to Mac OS X 10.4, osascript did not allow passing arguments to the script.
Mac OS X June 10, 2003 Mac OS X