• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript]


  • Subject: Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript]
  • From: KOENIG Yvan <email@hidden>
  • Date: Mon, 16 Mar 2009 16:10:06 +0100


Le 16 mars 2009 à 15:02:01, Jon Pugh a écrit :

At 11:24 AM +0100 3/16/09, KOENIG Yvan wrote:
You posted an exemple of what I call an English-centric code.

It may be useful for English writers but is useless for others.

English is not the unique language in the world and,
even in MacOS Roman there are some characterss which you didn't take care of:


œ,Œ,æ,Æ,
á, Á, à, À, â, Â, ä,� Ä, ã, Ã, å, Å,
é, É, è, È, ê, Ê, ë, Ë,
ó, Ó, ò, Ò, ô, Ô, ö, Ö, õ, Õ,
ú, Ú, ù, Ù, û, €, ü, Ü,
í, Í, ì, Ì, î, Î, ï, Ï,
ñ, Ñ,
ç, Ç,
ø, Ø,
ÿ, Ÿ,
π, ∏

I'm missing your point here. Are you concerned about upper and lower casing operations, as discussed in my previous post, or was there more to it? These characters all work fine in SmartString. They merely don't upper and lowercase very well at this moment.


However, this points out another advantage to using a code library which consolidates functionality like this. It can be upgraded and the improved behavior will be incorporated into your scripts when you recompile.

Jon

My point is that when we read: (The file is MacOS Roman encoding.) we logically assume that the embedded uppercase() and lowercase() handlers are able to treat the entire MacRoman set, not a small subset.


They treat only the characters used in languages without accented characters.
It's what I call an English-centric code exactly like most of the GUI scripting files which I encounter in forums triggering items by their English names.
The fact that on this forum we are urged to 'speak' English doesn't mean than scripts must speak English too.


They are AppleScript's users in Germany, Italy, Spain … and even in France.

The tools delivered with the Apple IIgs in 1989 where able to take care of these chars.
Is it logical than tools delivered twenty years later aren't ?


Souvenir, souvenir:
<http://www.apple-iigs.info/software/home.htm>

Yvan KOENIG (from FRANCE lundi 16 mars 2009 16:10:04)


_______________________________________________ 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
  • Follow-Ups:
    • Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript]
      • From: "Mark J. Reed" <email@hidden>
    • Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript]
      • From: Jon Pugh <email@hidden>
References: 
 >Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript] (From: Shane Stanley <email@hidden>)
 >Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript] (From: Jon Pugh <email@hidden>)
 >Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript] (From: KOENIG Yvan <email@hidden>)
 >Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript] (From: Jon Pugh <email@hidden>)

  • Prev by Date: Re: Can someone explain this?
  • Next by Date: Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript]
  • Previous by thread: Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript]
  • Next by thread: Re: Re. third-party dependencies [was Re: Stock Quotes using AppleScript]
  • Index(es):
    • Date
    • Thread