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

TEE Umlaut

Discussion in 'TCC/LE Support' started by Heinz, Nov 11, 2014.

  1. Heinz

    Joined:
    Jul 30, 2014
    Messages:
    2
    Likes Received:
    0
    The TEE Command cant handle Umlaut. Show in Command Line:

    echo ÄäÖöÜü
    ÄäÖöÜü

    echo ÄäÖöÜü |tee temp.dat
    ??????

    Whats Wrong ?
     
  2. Charles Dye

    Charles Dye Super Moderator
    Staff Member

    Joined:
    May 20, 2008
    Messages:
    3,374
    Likes Received:
    40
    Does it work if you do OPTION //UNICODEOUTPUT=YES first?
     
  3. Heinz

    Joined:
    Jul 30, 2014
    Messages:
    2
    Likes Received:
    0
    Wow, this is functional. Thank You for this Info !
     
  4. Charles Dye

    Charles Dye Super Moderator
    Staff Member

    Joined:
    May 20, 2008
    Messages:
    3,374
    Likes Received:
    40
    Well, I'm confused. Those characters all exist in code pages 437, 850, 852, 1250, 1252. There's no problem piping them to TYPE or LIST, but they get lost on the way to TEE if you're using CP437, 850, 852. They do seem to survive if the current code page is 1250 or 1252. I don't get it. Is is possible that TEE is using the Windows/"ANSI" code page instead of the console code page for input? Why do those characters get trashed?

    All I know for sure is that I dislike code pages more and more. I wish they would go away altogether. But as long as CMD.EXE compatibility is a selling point, I guess that isn't possible....
     

Share This Page