1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

TPIPE: /FILTER and /OUTPUT unexpected incompatibility

Discussion in 'Support' started by Howard Goldstein, Aug 11, 2012.

  1. Howard Goldstein

    Joined:
    Jun 1, 2008
    Messages:
    111
    Likes Received:
    1
    I am using TCC 14.0.32 under Windows XP.

    I am trying to use TPIPE to convert an Ansi file to UTF-16 and add a BOM to the front. After some experimentation I was able to get it to work. I then decided that it would be nice to save the sequence so I could use it whenever I wanted without retyping the whole thing. So I entered:
    Code:
    tpipe /unicode=ansi,utf-16le /string=1,0,\xff\xfe /save=a2u.tpf
    and then tried using it with:
    Code:
    tpipe /input=in.txt /output=out.txt /filter=a2u.tpf
    The result was that my filter was applied but In.txt was replaced with the Unicode version. Out.txt was never created. Is /FILTER supposed to behave this way? If so, is there a way to get TPIPE to send its output to the specified output file when using /FILTER?

    --
    Howard
     
  2. Howard Goldstein

    Joined:
    Jun 1, 2008
    Messages:
    111
    Likes Received:
    1
    I'm still seeing this issue with build 33. Is this something that can be fixed in TCC or would it require a change in Textpipeengine? Or am I misunderstanding how it's supposed to work?

    --
    Howard
     
  3. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,784
    Likes Received:
    29
    I see it too.
    Code:
    v:\> tpipe /simple=34 /save=rev.tpf
     
    v:\> echo 1^r^n2^r^n3 > 123.txt
     
    v:\> tpipe /input=123.txt /filter=rev.tpf
    3
    2
    1
     
    v:\> type 123.txt
    1
    2
    3
     
    v:\> tpipe /input=123.txt /output=321.txt /filter=rev.tpf
     
    v:\> type 321.txt
    TCC: (Sys) The system cannot find the file specified.
    "V:\321.txt"
     
    v:\> type 123.txt
    3
    2
    1
     
  4. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,784
    Likes Received:
    29
    My simple example works OK when /filter-rev.tpf is *NOT* the last argument.
    Code:
    v:\> del 321.txt
    Deleting V:\321.txt
        1 file deleted
     
    v:\> type 123.txt
    1
    2
    3
     
    v:\> tpipe /input=123.txt /filter=rev.tpf /output=321.txt
     
    v:\> type 123.txt
    1
    2
    3
     
    v:\> type 321.txt
    3
    2
    1
     
  5. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,729
    Likes Received:
    80
    The textpipeengine.dll wants the /filter argument to be entered prior to /output. This isn't documented, so I don't know if it is by design; I've queried the developers about it.
     
  6. JohnQSmith

    Joined:
    Jan 19, 2011
    Messages:
    560
    Likes Received:
    8
    I haven't tried it, but possibly to allow chained outputs?
    Code:
    tpipe /input=input.txt /filter=1.tpf /output=a.txt /filter=2.tpf /output=b.txt
     
  7. Howard Goldstein

    Joined:
    Jun 1, 2008
    Messages:
    111
    Likes Received:
    1
    Thanks. I'll be interested to know what they say.

    --
    Howard
     

Share This Page