[SOLVED] problem tr using pipe

Pinguino99 · 12-15-2019, 08:43 PM

i'm using tr to change letters but it has a problem when using the pipe

Code:

cat file |tr 'aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ1234567890' '7Ns3GwKfPDihv9dFq6Z8grnyLWSCp0VEQoBkAzbU5jmOJYeuXM24Ixl1aRtHT'

words in file
abc : 123foobar

Code:

output: +++ 9 r3s++++++

berndbausch · 12-15-2019, 08:50 PM

I suppose you want us to guess which problem it has. My suggestion: Describe the problem.

By the way, you need neither cat nor pipe:

Code:

tr 'aAbBcCd...' '7Ns3GwKfP...' file

Pinguino99 · 12-15-2019, 09:05 PM

tr sends me to help if I run this way
and i need cat in pipe, it's a file

rnturn · 12-15-2019, 09:49 PM

Quote:

Originally Posted by Pinguino99

i'm using tr to change letters but it has a problem when using the pipe

Code:

cat file |tr 'aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ1234567890' '7Ns3GwKfPDihv9dFq6Z8grnyLWSCp0VEQoBkAzbU5jmOJYeuXM24Ixl1aRtHT'

words in file
abc : 123foobar

Code:

output: +++ 9 r3s++++++

Try:

Code:

SET1=aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ1234567890
SET2=7Ns3GwKfPDihv9dFq6Z8grnyLWSCp0VEQoBkAzbU5jmOJYeuXM24Ixl1aRtHT
$ cat > INPUT.FILE
abc : 123foobar
^D
$ OUTPUT=$( tr "$SET1" "$SET2" < INPUT.FILE )
$ echo $OUTPUT
7sG : Ixlipps7B

or, yout could replace that variable assignment to send the results directly to a file with

Code:

$ tr "$SET1" "$SET2" < INPUT.FILE > OUTPUT.FILE
$ cat OUTPUT.FILE
7sG : Ixlipps7B

Check your translation strings. Do you see that "SET1" is one character longer than "SET2"? I'm not sure how 'tr' deals with that.

Update: According to the man page, 'tr' extends "set2" to the length of "set1" by repeating the last character. This wouldn't make unequal translation strings terribly useful for undoing the "encryption" (if that's the goal here).

berndbausch · 12-15-2019, 10:15 PM

Quote:

Originally Posted by Pinguino99

tr sends me to help if I run this way
and i need cat in pipe, it's a file

Oops sorry, I didn't know that tr reads from stdin only.

Code:

tr ..... < file

Which output do you expect?

EDIT: My output is 7sG : Ixlipps7B, same as rnturn's. Perhaps it has something to do with your language setting; in my case, LANG=en_US.UTF-8.

Pinguino99 · 12-15-2019, 10:43 PM

if I redirect the input "<" the output is +++ 9 r3s++++++

astrogeek · 12-15-2019, 10:59 PM

Quote:

Originally Posted by berndbausch

Perhaps it has something to do with your language setting; in my case, LANG=en_US.UTF-8.

I agree with berndbausch, it is not a problem with the pipe or redirection, it is non-ascii character encodings in the file.

What is your LANG setting? (echo $LANG)

WHere did the file text come from? Did you type it or copy paste from a browser?

Pinguino99 · 12-15-2019, 11:06 PM

lang is en_us.utf-8

berndbausch · 12-16-2019, 12:14 AM

Non-ASCII characters can be revealed like this:

Code:

od -x file

or this:

Code:

cat -v file

among other solutions.

pan64 · 12-16-2019, 12:51 AM

You may try to unset LANG also (to check if that solves this issue)

MadeInGermany · 12-16-2019, 01:29 AM

Set LANG or better LC_ALL for the tr command:

Code:

< file LC_ALL=C tr 'aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ1234567890' '7Ns3GwKfPDihv9dFq6Z8grnyLWSCp0VEQoBkAzbU5jmOJYeuXM24Ixl1aRtHT'

After the command the previous LC_ALL is again active.
Explanation:
The shell forks itself, and the forked instance execs (turns into) the command. An inline ENVVAR=value runs in the forked instance before the exec.
The
< file
is usually put after the command, but also works before the command (and even between command arguments).

Pinguino99 · 12-17-2019, 10:24 PM

I was able to solve, just correctly set the language
thank you all