Re: How to use the UNIX command: tr

From: Dan Espen (daneNO_at_SPAM.mk.telcordia.com)
Date: 08/06/04 

Date: Fri, 06 Aug 2004 15:43:31 -0400

tonij67@hotmail.com (Tonij) writes:

>>
>> That was my post, I didn't misunderstand anything.
>>
>> I know very well they are POSIX compliant keywords.
>> My post should have been very clear that UCB tr ignores
>> that and instead using the 2 parameters as translate patterns.
>>
>> I guess I just have to spell things out because a few
>> posters seemed to have missed the point.
>
>
> Here is the OPs question:
>
>
> "Does anyone know how to convert a lower case string to upper case
> string on the
> Solaris 9, version April 2004 for Intel? Or, how to fix the problem
> I'm
> having. Apparently, the above UNIX command doesn't work anymore on
> this new
> Solaris version. Thanks."
>
> Regardless of ones knowledge of POSIX compliance and what not, I think
> we can all agree that this is a simple case of seeing different
> behaviour between two commands with the same name. One of them
> converts the word upper to lower, one of them converts the case
> itself.
>
> Is it too much to ask to just say it in so many words?
>
> One of the first responses:
>
> "Make sure you are not using "/usr/ucb/tr". Check your path."
>
> ( which nailed it on the head. Thread could have stopped here, OPs
> question has been answered)
>
> Then we see this response:
>
> "I think for a UCB tar, it is working fine:
>
> xxx> echo "lower" | /usr/ucb/tr '[:lower:]' '[:upper:]'
> upper"
>
> Which ignores the OPs question, even though the poster is obviously
> aware that there are two different versions of tr being discussed.

I'm sorry, that is my response, taken out of context.

Someone else proffered the theory that ucb tar wasn't working.
That was my response to the claim that it wasn't working.

> It's these kind of responses, that state *just* enough information to
> be techinically accurate but don't address the original question that
> doesnt serve any purpose other than to inflate threads like this into
> a big post-fest about the history of Unix when all the OP wanted to
> know was:
>
> "Does anyone know how to convert a lower case string to upper case
> string"
>
> Talk about going around the block to cross the street...

Guess you can't please everyone.

Last I heard, it was permissible for a thread to wander.

Relevant Pages

  • Re: How to use the UNIX command: tr
    ... > I know very well they are POSIX compliant keywords. ... "Does anyone know how to convert a lower case string to upper case ... Which ignores the OPs question, even though the poster is obviously ...
    (comp.unix.solaris)
  • RE: Add Record with combo box
    ... Private Sub JCTARSectionLayer1ID_NotInList(NewData As String, ... Response As Integer) ... Dim strMsg As String ... Dim rst As DAO.Recordset ...
    (microsoft.public.access.formscoding)
  • RE: Add Record with combo box
    ... Private Sub JCTARSectionLayer1ID_NotInList(NewData As String, ... Response As Integer) ... Dim strMsg As String ... Dim rst As DAO.Recordset ...
    (microsoft.public.access.formscoding)
  • RE: Cbo Update Problems
    ... Dim strFormName As String ... > original form, but it then asks if I want to add the part number again. ... > Private Sub PartNumber_NotInList(NewData As String, Response As Integer) ... > Dim strMessage As String ...
    (microsoft.public.access.forms)
  • RE: Combo Box and Limit To List
    ... No that is not on the list I get the message "Add a new charge No?". ... Private Sub ChargeNo_EL_NotInList(NewData As String, Response As Integer) ... Dim mbrResponse As VbMsgBoxResult ...
    (microsoft.public.access.formscoding)