Sponsored Content
Full Discussion: Whats Behind Your Name?
The Lounge What is on Your Mind? Whats Behind Your Name? Post 55589 by Anamika on Wednesday 15th of September 2004 09:40:43 AM
Old 09-15-2004
Hammer & Screwdriver

Eventhough "Anamika" is a gender neutral name...it is mostly used as a feminine name...
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Whats does this mean

Found this piece of code written in ksh. I have no ideas what do the stuff like ${SRF##*\.} do. SUFFIX=${SRF##*\.} if ; then SUFFIX="" fi I have encountered similar expressions in other programs also. Any pointers on where to learn more about these... (1 Reply)
Discussion started by: jyotipg
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Whats the go?

woofie, Your posts are being deleted because your use of profanity. I am close to changing your status to read only. In fact, if you argue with the mods again, I will ban you from these boards. Neo (1 Reply)
Discussion started by: Neo
1 Replies

3. Shell Programming and Scripting

whats the difference between $* and $@

Hi, whats the difference between $* and $@ in command line arguments to a shell scripts (3 Replies)
Discussion started by: pbsrinivas
3 Replies

4. Shell Programming and Scripting

tell me whats wrong in this?

#! /bin/bash head -5 $1 echo "remove $1 ?" read answer if then echo invalid answer elif rm $1 echo "$1 is deleted" elif then echo file is not deleted else echo "invalid answer" fi What i really want this to do is to ask to delete the file or not..it says something wrong... (1 Reply)
Discussion started by: nadman123
1 Replies

5. Shell Programming and Scripting

tell me whats wrong with this

#! /bin/bash USAGE=" | ] if then echo "$USAGE" exit 1 fi while getopts lb: OPTION do case $(OPTION)in a) echo Hi there! exit 2;; b) echo hello o) OARG=$OPTARG;; \?)echo "$USAGE" ;; exit 2;; esac done shift `expr... (1 Reply)
Discussion started by: nadman123
1 Replies

6. Shell Programming and Scripting

whats this NAME=${0##*/}

hi all, i found NAME=${0##*/} in a script. i given this coomand in my unix box(presently in ksh). echo ${0##*/} it returned ksh. the purpose of the above is to return the shell name or more than that. do you have any more information like this, please share with me. one more query... (7 Replies)
Discussion started by: Arunprasad
7 Replies

7. Shell Programming and Scripting

##*_ - whats this?

Hi all, could you please tell me whats this stands ##*_ 0##*/ i knew this alone if some more is there please tell me that also. (3 Replies)
Discussion started by: Arunprasad
3 Replies

8. UNIX for Dummies Questions & Answers

whats wrong with this?

can anyone tell me why this code doesn't work how its supposed to, its the hangman game but it doesn't play how its supposed to #!/bin/bash NoAttempts="0" livesgiven="5" LivesRemain=$livesgiven LettersAttempted="" wordfile=words numwords=0 function menu() { clear cat << menu... (1 Reply)
Discussion started by: ferrycorsten73
1 Replies

9. Homework & Coursework Questions

Whats wrong with the following

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: ls -ld htdocs drwxr-x--- 3 root root 8192 2006-11-19 10:41 htdocs How would a host administrator... (1 Reply)
Discussion started by: Larry_1
1 Replies
unidesc(1)						      General Commands Manual							unidesc(1)

NAME
unidesc - Describe the contents of a Unicode text file SYNOPSIS
unidesc ([option flags]) (<file name>) If no input file name is supplied, unidesc reads from the standard input. DESCRIPTION
unidesc describes the content of a Unicode text file by reporting the character ranges to which different portions of the text belong. The ranges reported include both official Unicode ranges and the constructed language ranges within the Private Use Areas registered with the Conscript Unicode Registry (http://www.evertype.com/standards/csur/). For each range of characters, unidesc prints the character or byte offset of the beginning of the range, the character or byte offset of the end of the range, and the name of the range. Offsets start from 0. Since the ASCII digits, punctuation, and whitespace characters are frequently used by other writing systems, by default these characters are treated as neutral, that is, as not belonging exclusively to any particular character range. These characters are treated as belonging to the range of whatever characters precede them. If the input begins with neutral characters, they are treated as belonging to the range of whatever characters follow them. If the file consists entirely of neutral characters, the range is identified as Neutral followed by Basic Latin in square brackets. A magic number identifying the Unicode encoding is not part of the Unicode standard, so pure Unicode files do not contain a magic number. However, informal conventions have arisen for this purpose. If the command line flag -m is given, unidesc will attempt to identify the Unicode subtype by examining the first few bytes of the input. If the input is identified as one of the two acceptable types, UTF-8 or native order UTF-32, it will then proceed to describe the contents of the input. Otherwise, it will report what it has learned and exit. Note that if the file does contain a magic number, you must use the -m flag. Without this flag unidesc assumes that the input consists of pure Unicode with the character data beginning immediately. It will therefore be thrown off by the magic number. By default, input is expected to be UTF-8. Native order UTF-32 is also acceptable. UTF-32 may be specified via the command line flag -u or, if the command line flag -m is given, via the magic number. COMMAND LINE FLAGS
-b Give file offsets in bytes rather than characters. -d Treat the ASCII digits as belonging exclusively to the Basic Latin range. -h Print usage information. -L List the Unicode ranges alphabetically. -l List the Unicode ranges by codepoint. -m Check the file's magic number to determine the Unicode subtype. -p Treat ASCII punctuation as belonging exclusively to the Basic Latin range. -r Instead of listing ranges as they are encountered, just list the ranges detected after all input has been read. -u Input is native order UTF-32. -v Print version information. -w Treat ASCII whitespace as belonging exclusively to the Basic Latin range. SEE ALSO
uniname REFERENCES
Unicode Standard, version 5.0 AUTHOR
Bill Poser billposer@alum.mit.edu LICENSE
GNU General Public License June, 2007 unidesc(1)
All times are GMT -4. The time now is 08:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy