Re: Transliteration, TextCommands osax
Re: Transliteration, TextCommands osax
- Subject: Re: Transliteration, TextCommands osax
- From: Sander Tekelenburg <email@hidden>
- Date: Sat, 22 Nov 2008 14:58:40 +0100
At 00:19 +0000 UTC, on 2008-11-22, has wrote:
> Sander Tekelenburg wrote:
[...]
>> tell application "TextCommands"
>> set throughput to convert to unicode input from "mac_roman"
>> set output to convert from unicode throughput to "WINDOWS-1252"
>> [...]
>>
>> Opening the resulting file in TextWrangler, it claims it is Mac
>> Roman. [...]
>
> I'm guessing you're on 10.5, yes?
No. This is under 10.4.11.
But, when I set TextWrangler's "If file encoding can't be guessed, use " to
"Chinese (GB 18030)", then it reports the file to be Chinese (GB 18030). So
apparently TextWrangler's claim that the result is MacRoman merely means that
it cannot figure out what the file's encoding is. So it seems quite possible
that TextCommands (and iconv) work fine after all.
Any suggestions as to what other tool can guess a file's encoding more
reliably than TextWrangler?
[...]
> FWIW, if I were you I'd probably just write a one-line shell script to
> chuck your files through textutil
Ah, right. I'd forgotten about that one.
$ textutil -encoding WINDOWS-1252 -convert txt input.txt -output output.txt
But here too there's the problem of how to verify the result.
--
Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden