Uppercase a Bash input variable

James Sissel James.Sissel at labone.com
Wed Apr 2 21:56:47 CST 2003


Standard Oracle dates here are (example today) 02-APR-2003.  I needed the
month to always be uppercase.  Otherwise there are 96 different ways to
"spell" the months.  Coding a case statement for that, although not
impossible, wouldn't be fun.  :)

-----Original Message-----
From: Jeremy Fowler [mailto:jfowler at westrope.com]
Sent: Wednesday, April 02, 2003 3:36 PM
To: Gene Dascher; Kclug at Kclug. Org
Subject: RE: Uppercase a Bash input variable

Those aren't numbers. They're numerals.

> -----Original Message-----
> From: owner-kclug at marauder.illiana.net
> [mailto:owner-kclug at marauder.illiana.net]On Behalf Of Gene Dascher
> Sent: Wednesday, April 02, 2003 2:38 PM
> To: kclug at kclug.org
> Subject: RE: Uppercase a Bash input variable
> 
> 
> Au contraire:
> i ii iii iv v vi vii viii ix x
> ;)
> 
> Gene
> 
> > -----Original Message-----
> > From: owner-kclug at marauder.illiana.net
> > [mailto:owner-kclug at marauder.illiana.net]On Behalf Of Jeremy Fowler
> > Sent: Wednesday, April 02, 2003 1:38 PM
> > To: James Sissel; kclug at kclug.org
> > Subject: RE: Uppercase a Bash input variable
> > 
> > 
> > um... There is no such thing as lower case numbers. 
> > 
> > > -----Original Message-----
> > > From: owner-kclug at marauder.illiana.net
> > > [mailto:owner-kclug at marauder.illiana.net]On Behalf Of James Sissel
> > > Sent: Wednesday, April 02, 2003 12:19 PM
> > > To: kclug at kclug.org
> > > Subject: Uppercase a Bash input variable
> > > 
> > > 
> > > Using RedHat 7.3 and Bash 2.05a I can write the following script.
> > > 
> > > 
> > > 
> > > echo -n "Please enter a date (DD-MON-YYYY): "
> > > read indate
> > > 
> > > 
> > > 
> > > How can I make sure indate is in uppercase?
> > > 
> > > Thanks.
> > > 
> > > This transmission (and any information attached to it) may be 
> > > confidential and is intended solely for the use of the individual or 
> > > entity to which it is addressed. If you are not the intended 
> > > recipient or the person responsible for delivering the transmission 
> > > to the intended recipient, be advised that you have received this 
> > > transmission in error and that any use, dissemination, forwarding, 
> > > printing, or copying of this information is strictly prohibited. If 
> > > you have received this transmission in error, please immediately 
> > > notify LabOne at the following email address: 
> > > securityincidentreporting at labone.com
> > > 
> > > 
> > > 
> > > 
majordomo at kclug.org
> > 
> > 
> 
> 


This transmission (and any information attached to it) may be confidential and is intended solely 
for the use of the individual or entity to which it is addressed. If you are not the intended 
recipient or the person responsible for delivering the transmission to the intended recipient, be 
advised that you have received this transmission in error and that any use, dissemination, 
forwarding, printing, or copying of this information is strictly prohibited. If you have received 
this transmission in error, please immediately notify LabOne at the following email address: 
securityincidentreporting at labone.com




More information about the Kclug mailing list