|
|
Install a new tcsh shell for better UTF8 support
eno wrote:
Doesn't work for me... :-( For example, when I drag folders into the Terminal with Spanish characters I get the accents stripped off them (so they don't work). I can't type them either, like I would in any other app. And I've tried changed the "Window settings" in Terminal.app too, but they have no visible effect....and then carsten wrote: I had to also add "-N --show-control-chars" to ls to get non-ascii chars to display in directory listings within the terminal (using gnu ls from fink). Also unable to drag files with odd characters in the filename into a Terminal here too, the non-ascii characters are still stripped. :(another thing to check is to make sure that in terminal, the encoding (found under the "display" entry (not "window", btw) in the "terminal inspector" (cmd-i) for a given window) is set to utf8 explicitly. also, don't forget that not only do all your changes (installing the new version, editing your .cshrc, etc.) need to be in place before you can try them, but that they will affect only new terminal windows opened after you've got everything set up. you might want to double check the version of tcsh you're getting when you spawn a new shell ... it should be 6.12.00 ... as far as accented characters, since i use a plain us/ascii keyboard, my tests mostly involved double-clicking them in the character palette, from whence they seemed to show up normally at the cursor position in the terminal window, as they should with any app. also, now i recall that at least umlaut worked as well via an option key sequence (e.g., typing opt-u then o should give you an o with an umlaut over it (so at least we can write motörhead properly!)) there may be an issue there, however, with the font you're using for your terminal window ... you can check in the character palette to see if a given font has a glyph for a given character. i did notice some anomalies with the font i like to use, "lucida sans typewriter oblique": there are certain accented characters (e.g., one that looks like a z with a dot over it, unicode 0x017C) that seem to work ok when entered, but then don't show up properly in a filename via "ls", etc. i think this is because the font i'm using does not actually contain that character. interesting how osx does a fair job of substituting the missing double-byte characters (no kanji in lucida sans typewriter oblique either!), but kind of breaks a little for something that might be considered in some cases just high ascii. also, regarding the version of ls, i can't really address that, because i'm just using the stock ls shipped with osx, which works fine for me. and i can't speak for those using the tcsh available via fink, since that's not the one referred to in the hint. it's possible that the two binaries were compiled with entirely different options, etc., which may explain the difficulty some folks seem to be having as well.
try using the -v switch with ls
To see Hebrew in file listings, I had to use "ls -v"; otherwise I see question marks.
Install a new tcsh shell for better UTF8 support
Found the problem with my setup. For Finder drag-and-drop into the Terminal to work, I had to turn on the
Install a new tcsh shell for better UTF8 support
Thanks ! It was my problem too. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|