Indeed I am not extracting solely what I need. the thing is I cannot use line numbers in my extraction script, since those might change, so I need to find patterns to look for.
so from this string :
I need an output like this :
thanks!
Moderator's Comments:
Use code tags to wrap code fragments or data samples
Hi all,
I have a text file of 143 lines. The I don't want all lines but want to retain line format.
How can I extract lines 34, 65, 68, 70 (plus 7 others) easliy?
I have found some example head/tail n lines and some sed -n examples that have been shown for single line or mass consecutive... (2 Replies)
Hi,
I have a text file with 15 columns and i want to extract those lines of which 7th column is ABCD.
I think we can do this using awk but could not frame the command. Please help.
TIA
Prvn (2 Replies)
Hello Friends,
I have got, this output below and i want to extract the name of symlink which is highlighted in red and the path above it highlighted in blue. At the end i want to append path and symlink.
/var/tmp/asirohi/jdk/jre
/var/tmp/asirohi/jdk/jre/.systemPrefs... (3 Replies)
Hello UNIX experts,
I have 124 text files in a directory. I want to extract the 45678th line of all the files sequentialy by file names. The extracted lines should be printed in the output file on seperate lines.
e.g. The input Files are one.txt, two.txt, three.txt, four.txt
The cat of four... (1 Reply)
hi,
i have two files.
file1.sh
echo "unix"
echo "linux"
file2.sh
echo "unix linux forums"
now the output i need is
$./file2.sh
unix linux forums (3 Replies)
Dear all,
Greetings.
I would like to ask for your help to extract lines with specific words in addition 2 lines before and after these lines by using awk or sed.
For example, the input file is:
1 ak1 abc1.0
1 ak2 abc1.0
1 ak3 abc1.0
1 ak4 abc1.0
1 ak5 abc1.1
1 ak6 abc1.1
1 ak7... (7 Replies)
I have hundreds of files to process. In each file
I need to look for a pattern then
extract value(s) from next line and then
search for value(s) selected from point (2) in the same file at a specific position.
HEADER ELECTRON TRANSPORT 18-MAR-98 1A7V
TITLE CYTOCHROME... (7 Replies)
Data file example
I look for primary and * to isolate the interesting slot number.
slot=`sed '/^primary$/,/\*/!d' filename | tail -1 | sed s'/*//' | awk '{print $1" "$2}'`
Now I want to get the Touch line for only the associate slot number, in this case, because the asterisk... (2 Replies)
I have a text file that looks like this :
root/user/usr1/0001/abab1*
root/user/usr1/0001/abab2*
root/user/usr1/0002/acac1*
root/user/usr1/0002/acac2*
root/user/usr1/0003/adad1*
root/user/usr1/0004/aeae1*
root/user/usr1/0004/aeae2*
How could I code this to extract just the subjects... (9 Replies)
Discussion started by: LeftoverStew
9 Replies
LEARN ABOUT SUNOS
xgettext
xgettext(1) User Commands xgettext(1)NAME
xgettext - extract gettext call strings from C programs
SYNOPSIS
xgettext [-ns] [ -a [-x exclude-file]] [-c comment-tag] [-d default-domain] [-j] [-m prefix] [-M suffix] [-p pathname] -| filename...
xgettext -h
DESCRIPTION
The xgettext utility is used to automate the creation of portable message files (.po). A .po file contains copies of "C" strings that are
found in ANSI C source code in filename or the standard input if `-' is specified on the command line. The .po file can be used as input
to the msgfmt(1) utility, which produces a binary form of the message file that can be used by application during run-time.
xgettext writes msgid strings from gettext(3C) calls in filename to the default output file messages.po. The default output file name can
be changed by -d option. msgid strings in dgettext() calls are written to the output file domainname.po where domainname is the first
parameter to the dgettext() call.
By default, xgettext creates a .po file in the current working directory, and each entry is in the same order that the strings are
extracted from filenames. When the -p option is specified, the .po file is created in the pathname directory. An existing .po file is
overwritten.
Duplicate msgids are written to the .po file as comment lines. When the -s option is specified, the .po is sorted by the msgid string,
and all duplicated msgids are removed. All msgstr directives in the .po file are empty unless the -m option is used.
OPTIONS
The following options are supported:
-n Add comment lines to the output file indicating file name and line number in the source file where each extracted
string is encountered. These lines appear before each msgid in the following format:
# # File: filename, line: line-number
-s Generate output sorted by msgids with all duplicate msgids removed.
-a Extract all strings, not just those found in gettext(3C), and dgettext() () calls. Only one .po file is created.
-c comment-tag The comment block beginning with comment-tag as the first token of the comment block is added to the output .po
file as # delimited comments. For multiple domains, xgettext directs comments and messages to the prevailing text
domain.
-d default-domain Rename default output file from messages.po to default-domain .po.
-j Join messages with existing message files. If a .po file does not exist, it is created. If a .po file does exist,
new messages are appended. Any duplicate msgids are commented out in the resulting .po file. Domain directives in
the existing .po file are ignored. Results not guaranteed if the existing message file has been edited.
-m prefix Fill in the msgstr with prefix. This is useful for debugging purposes. To make msgstr identical to msgid, use an
empty string ("") for prefix.
-M suffix Fill in the msgstr with suffix. This is useful for debugging purposes.
-p pathname Specify the directory where the output files will be placed. This option overrides the current working directory.
-x exclude-file Specify a .po file that contains a list of msgids that are not to be extracted from the input files. The format of
exclude-file is identical to the .po file. However, only the msgid directive line in exclude-file is used. All
other lines are simply ignored. The -x option can only be used with the -a option.
-h Print a help message on the standard output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWloc |
+-----------------------------+-----------------------------+
SEE ALSO msgfmt(1), gettext(3C), attributes(5)NOTES
xgettext is not able to extract cast strings, for example ANSI C casts of literal strings to (const char *). This is unnecessary anyway,
since the prototypes in <libintl.h> already specify this type.
In messages and translation notes, lines greater than 2048 characters are truncated to 2048 characters and a warning message is printed to
stderr.
SunOS 5.10 23 Mar 1999 xgettext(1)