Apologies if this has already been covered in this site somewhere, I did try looking but without any success. I am new to the whole XML thing, very late starter, and have a requirement to convert an XML fiule to a CSV fomat. I am crrently working on a Solaris OS. Does anyone have any suggestions,... (2 Replies)
Iam pretty new to UNIX and would like to convert a CSV to an XML file using AWK scripts. Can anybody suggest a solution? My CSV file looks something like this :
Serial No Growth% Annual % Commission % Unemployed %
1 35% 29% 59% 42%
2 61% ... (15 Replies)
Hi,
i am really fresh with shell scripting and programming,
i have an issue i am not able to solve to populate data on my server for Cisco IP phones.
I have CSV file within the following format:
;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;... (9 Replies)
Hi,
I want to write a perl script. Which should accept the xml file, one xsl file and the loaction. The perl script should process the xml file using the xsl file and puts the out put in specified location.
For example:
My.perl is perls cript.
my.xml
is like this
<?xml version="1.0"... (2 Replies)
Hi ,
Please any one to help on ,extract this xml code into csv columns list.
<SOURCEFIELD BUSINESSNAME ="" DATATYPE ="date" DESCRIPTION ="" FIELDNUMBER ="1"
FIELDPROPERTY ="0" FIELDTYPE ="ELEMITEM" HIDDEN ="NO" KEYTYPE ="NOT A KEY" LENGTH ="19"
LEVEL ="0" NAME ="BUSINESS_DATE"... (4 Replies)
I need to convert below xml code to csv. I searched other posts as well but this post (_https://www.unix.com/shell-programming-scripting/174417-extract-parse-xml-data-statistic-value-csv.html) gives "sed command garbled" error. As of now I have written a long script to do it, but can it be done with... (7 Replies)
I am in need of converting billions of XML into csv file to load data to DB, i have found the below code in perl but not sure why it's not working properly.
CODE:
#!/usr/bin/perl
# Script to illustrate how to parse a simple XML file
# and pick out all the values for a specific element, in... (1 Reply)
Hello,
I have copied .xml code for a single item below. I am trying to extract three items (field indices*b244 (second occurrence), b203, and j151), so the desired output would be:
9780323013543 Manual of Natural Veterinary Medicine: Science and Tradition, 1e 68.95
A parallel solution,... (14 Replies)
Hello,
For i while i have been using XMLStarlet to convert several XML files to CSV files. So far this always went fine.
Today however i got a new XML format however but i cannot find out how to get the data i need.
Below is part of the code where it shows the different format. What... (10 Replies)
Discussion started by: SDohmen
10 Replies
LEARN ABOUT OPENSOLARIS
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.11 23 Mar 1999 xgettext(1)