Sponsored Content
Top Forums Shell Programming and Scripting Need help in getting count from xml file Post 303005478 by RudiC on Wednesday 18th of October 2017 09:49:48 AM
Old 10-18-2017
You have a list of integer numbers in successive lines; tr converts <NL> (\n, 0x0A) characters to plus signs so you have 31220+56492+...+34722+. The trailing + is considered offensive by the now to be applied "arithmetic evaluation" $(( ... )), so a solitary zero is appended.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to remove xml namespace from xml file using shell script?

I have an xml file: <AutoData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Table1> <Data1 10 </Data1> <Data2 20 </Data2> <Data3 40 </Data3> <Table1> </AutoData> and I have to remove the portion xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" only. I tried using sed... (10 Replies)
Discussion started by: Gary1978
10 Replies

2. Shell Programming and Scripting

How to add the multiple lines of xml tags before a particular xml tag in a file

Hi All, I'm stuck with adding multiple lines(irrespective of line number) to a file before a particular xml tag. Please help me. <A>testing_Location</A> <value>LA</value> <zone>US</zone> <B>Region</B> <value>Russia</value> <zone>Washington</zone> <C>Country</C>... (0 Replies)
Discussion started by: mjavalkar
0 Replies

3. Shell Programming and Scripting

Help required in Splitting a xml file into multiple and appending it in another .xml file

HI All, I have to split a xml file into multiple xml files and append it in another .xml file. for example below is a sample xml and using shell script i have to split it into three xml files and append all the three xmls in a .xml file. Can some one help plz. eg: <?xml version="1.0"?>... (4 Replies)
Discussion started by: ganesan kulasek
4 Replies

4. Shell Programming and Scripting

XML: parsing of the Google contacts XML file

I am trying to parse the XML Google contact file using tools like xmllint and I even dived into the XSL Style Sheets using xsltproc but I get nowhere. I can not supply any sample file as it contains private data but you can download your own contacts using this script: #!/bin/sh # imports... (9 Replies)
Discussion started by: ripat
9 Replies

5. Shell Programming and Scripting

Comparing delta values of one xml file in other xml file

Hi All, I have two xml files. One is having below input <NameValuePair> <name>Daemon</name> <value>tcp:7474</value> </NameValuePair> <NameValuePair> <name>Network</name> <value></value> </NameValuePair> ... (2 Replies)
Discussion started by: sharsour
2 Replies

6. Shell Programming and Scripting

Splitting xml file into several xml files using perl

Hi Everyone, I'm new here and I was checking this old post: /shell-programming-and-scripting/180669-splitting-file-into-several-smaller-files-using-perl.html (cannot paste link because of lack of points) I need to do something like this but understand very little of perl. I also check... (4 Replies)
Discussion started by: mcosta
4 Replies

7. Shell Programming and Scripting

Split xml file into multiple xml based on letterID

Hi All, We need to split a large xml into multiple valid xml with same header(2lines) and footer(last line) for N number of letterId. In the example below we have first 2 lines as header and last line as footer.(They need to be in each split xml file) Header: <?xml version="1.0"... (5 Replies)
Discussion started by: vx04
5 Replies

8. Shell Programming and Scripting

Splitting a single xml file into multiple xml files

Hi, I'm having a xml file with multiple xml header. so i want to split the file into multiple files. Sample.xml consists multiple headers so how can we split these multiple headers into multiple files in unix. eg : <?xml version="1.0" encoding="UTF-8"?> <ml:individual... (3 Replies)
Discussion started by: Narendra921631
3 Replies

9. UNIX for Beginners Questions & Answers

Grepping multiple XML tag results from XML file.

I want to write a one line script that outputs the result of multiple xml tags from a XML file. For example I have a XML file which has below XML tags in the file: <EMAIL>***</EMAIL> <CUSTOMER_ID>****</CUSTOMER_ID> <BRANDID>***</BRANDID> Now I want to grep the values of all these specified... (1 Reply)
Discussion started by: shubh752
1 Replies

10. UNIX for Beginners Questions & Answers

How to pull multiple XML tags from the same XML file in Shell.?

I'm searching for the names of a TV show in the XML file I've attached at the end of this post. What I'm trying to do now is pull out/list the data from each of the <SeriesName> tags throughout the document. Currently, I'm only able to get data the first instance of that XML field using the... (9 Replies)
Discussion started by: hungryd
9 Replies
format(n)						       Tcl Built-In Commands							 format(n)

__________________________________________________________________________________________________________________________________________________

NAME
format - Format a string in the style of sprintf SYNOPSIS
format formatString ?arg arg ...? _________________________________________________________________ INTRODUCTION
This command generates a formatted string in the same way as the ANSI C sprintf procedure (it uses sprintf in its implementation). Format- String indicates how to format the result, using % conversion specifiers as in sprintf, and the additional arguments, if any, provide val- ues to be substituted into the result. The return value from format is the formatted string. DETAILS ON FORMATTING
The command operates by scanning formatString from left to right. Each character from the format string is appended to the result string unless it is a percent sign. If the character is a % then it is not copied to the result string. Instead, the characters following the % character are treated as a conversion specifier. The conversion specifier controls the conversion of the next successive arg to a particu- lar format and the result is appended to the result string in place of the conversion specifier. If there are multiple conversion speci- fiers in the format string, then each one controls the conversion of one additional arg. The format command must be given enough args to meet the needs of all of the conversion specifiers in formatString. Each conversion specifier may contain up to six different parts: an XPG3 position specifier, a set of flags, a minimum field width, a pre- cision, a length modifier, and a conversion character. Any of these fields may be omitted except for the conversion character. The fields that are present must appear in the order given above. The paragraphs below discuss each of these fields in turn. If the % is followed by a decimal number and a $, as in ``%2$d'', then the value to convert is not taken from the next sequential argument. Instead, it is taken from the argument indicated by the number, where 1 corresponds to the first arg. If the conversion specifier requires multiple arguments because of * characters in the specifier then successive arguments are used, starting with the argument given by the number. This follows the XPG3 conventions for positional specifiers. If there are any positional specifiers in formatString then all of the specifiers must be positional. The second portion of a conversion specifier may contain any of the following flag characters, in any order: - Specifies that the converted argument should be left-justified in its field (numbers are normally right-justified with leading spaces if needed). + Specifies that a number should always be printed with a sign, even if positive. space Specifies that a space should be added to the beginning of the number if the first character isn't a sign. 0 Specifies that the number should be padded on the left with zeroes instead of spaces. # Requests an alternate output form. For o and O conversions it guarantees that the first digit is always 0. For x or X conver- sions, 0x or 0X (respectively) will be added to the beginning of the result unless it is zero. For all floating-point conver- sions (e, E, f, g, and G) it guarantees that the result always has a decimal point. For g and G conversions it specifies that trailing zeroes should not be removed. The third portion of a conversion specifier is a number giving a minimum field width for this conversion. It is typically used to make columns line up in tabular printouts. If the converted argument contains fewer characters than the minimum field width then it will be padded so that it is as wide as the minimum field width. Padding normally occurs by adding extra spaces on the left of the converted argu- ment, but the 0 and - flags may be used to specify padding with zeroes on the left or with spaces on the right, respectively. If the mini- mum field width is specified as * rather than a number, then the next argument to the format command determines the minimum field width; it must be a numeric string. The fourth portion of a conversion specifier is a precision, which consists of a period followed by a number. The number is used in dif- ferent ways for different conversions. For e, E, and f conversions it specifies the number of digits to appear to the right of the decimal point. For g and G conversions it specifies the total number of digits to appear, including those on both sides of the decimal point (how- ever, trailing zeroes after the decimal point will still be omitted unless the # flag has been specified). For integer conversions, it specifies a minimum number of digits to print (leading zeroes will be added if necessary). For s conversions it specifies the maximum num- ber of characters to be printed; if the string is longer than this then the trailing characters will be dropped. If the precision is spec- ified with * rather than a number then the next argument to the format command determines the precision; it must be a numeric string. The fifth part of a conversion specifier is a length modifier, which must be h or l. If it is h it specifies that the numeric value should be truncated to a 16-bit value before converting. This option is rarely useful. The l modifier is ignored. The last thing in a conversion specifier is an alphabetic character that determines what kind of conversion to perform. The following con- version characters are currently supported: d Convert integer to signed decimal string. u Convert integer to unsigned decimal string. i Convert integer to signed decimal string; the integer may either be in decimal, in octal (with a leading 0) or in hexadecimal (with a leading 0x). o Convert integer to unsigned octal string. x or X Convert integer to unsigned hexadecimal string, using digits ``0123456789abcdef'' for x and ``0123456789ABCDEF'' for X). | c | Convert integer to the Unicode character it represents. s No conversion; just insert string. f Convert floating-point number to signed decimal string of the form xx.yyy, where the number of y's is determined by the precision (default: 6). If the precision is 0 then no decimal point is output. e or e Convert floating-point number to scientific notation in the form x.yyye+-zz, where the number of y's is determined by the preci- sion (default: 6). If the precision is 0 then no decimal point is output. If the E form is used then E is printed instead of e. g or G If the exponent is less than -4 or greater than or equal to the precision, then convert floating-point number as for %e or %E. Otherwise convert as for %f. Trailing zeroes and a trailing decimal point are omitted. % No conversion: just insert %. For the numerical conversions the argument being converted must be an integer or floating-point string; format converts the argument to binary and then converts it back to a string according to the conversion specifier. DIFFERENCES FROM ANSI SPRINTF
The behavior of the format command is the same as the ANSI C sprintf procedure except for the following differences: [1] %p and %n specifiers are not currently supported. [2] For %c conversions the argument must be a decimal string, which will then be converted to the corresponding character value. [3] The l modifier is ignored; integer values are always converted as if there were no modifier present and real values are always con- verted as if the l modifier were present (i.e. type double is used for the internal representation). If the h modifier is specified then integer values are truncated to short before conversion. SEE ALSO
sprintf(3), string(n) KEYWORDS
conversion specifier, format, sprintf, string, substitution Tcl 8.1 format(n)
All times are GMT -4. The time now is 09:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy