Re: Why do I get this error?
Re: Why do I get this error?
- Subject: Re: Why do I get this error?
- From: "Adam Bell" <email@hidden>
- Date: Mon, 24 Apr 2006 10:36:07 -0300
Works for me, even in TextWrangler or BBEdit. Thanks.
On 4/24/06, kai <email@hidden> wrote:
On 20 Apr 2006, at 14:32, Adam Bell wrote:
> While these are easy to see in a displayed dialog or event log, I
> have not been able to save theDeal as text that I could decipher
> with different encodings. What font are the card symbols in?
It's not so much the font that's critical here, but preserving the
encoding. If the latter is lost, no amount of applying the former
will have the desired effect.
However, to try and answer the question, here are some fonts that
support the card suit characters used:
Family [Typeface]
-------------------
WHITE DIAMOND SUIT:
-------------------
#GungSeo [Regular]
#PCMyungjo [Regular]
#PilGi [Regular]
Apple Symbols [Regular]
AppleGothic [Regular]
AppleMyungjo [Regular]
Hiragino Kaku Gothic Pro [W3]
Hiragino Kaku Gothic Pro [W6]
Hiragino Kaku Gothic Std [W8]
Hiragino Maru Gothic Pro [W4]
Hiragino Mincho Pro [W3]
Hiragino Mincho Pro [W6]
MS Gothic [Regular]
MS Mincho [Regular]
MS PGothic [Regular]
MS PMincho [Regular]
Osaka [Regular]
Osaka [Regular-Mono]
Seoul Regular [Regular]
-------------------
WHITE HEART SUIT:
-------------------
Fonts from above suite plus:
Batang [Regular]
Gulim [Regular]
-------------------
BLACK CLUB SUIT &
BLACK SPADE SUIT:
-------------------
Fonts from above suites plus:
Arial [Regular]
Arial [Bold]
Arial [Italic]
Arial [Bold Italic]
Century [Regular]
STFangsong [Regular]
STXihei [Regular]
STHeiti [Regular]
STKaiti [Regular]
STSong [Regular]
Symbol [Regular]
Times New Roman [Regular]
Times New Roman [Bold]
Times New Roman [Italic]
Times New Roman [Bold Italic]
Zapf Dingbats [Regular]
So only a font from the first list would support all four suits -
although, these days, applications are often smart enough to choose
an appropriate font for 'exotic' characters.
The following examples all use this handler:
------------
on newPack()
set p to {}
repeat with s in «data utxt2660266126632662» as Unicode text
repeat with c in {"A", "K", "Q", "J", "10", "9", "8", "7", "6",
"5", "4", "3", "2"}
set p's end to c & s
end repeat
end repeat
p as string
end newPack
------------
OMM, TextEdit normally defaults to Helvetica Regular. However, when
responding to the following, it uses Hiragino Kaku Gothic Pro [W3]
for each of the four card suite characters:
------------
tell application "TextEdit" to make new document with properties
{text:my newPack()}
------------
Tex-Edit Plus behaves similarly. While generally defaulting here to
Geneva [Regular], it uses Osaka [Regular] for the card suite characters:
------------
tell application "Tex-Edit Plus" to set text of (make new document)
to my newPack()
------------
When writing direct to a file, specifying the type class as «class
ut16» should (in Tiger) write the byte order mark and the data in one
go:
------------
set p to (path to desktop as Unicode text) & "
newPack.txt"
set f to open for access file p with write permission
set eof f to 0
write newPack() to f as «class ut16»
close access f
tell application "TextEdit" (* check result *)
activate
open p
end tell
------------
---
kai
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden