[mac4theblind] Re: Apple quietly improving its iOS maps data

  • From: John Panarese <john@xxxxxxxxxxxxxxxxxx>
  • To: mac4theblind@xxxxxxxxxxxxx
  • Date: Fri, 5 Oct 2012 21:20:31 -0400

   What I also find interesting is now I am reading in several places, as I 
initially expected because the media loves beating on Apple, that the problems 
with Maps is not as horrible and widespread as was reported.  The old telephone 
line principle at work.


Take Care

John D. Panarese
Director
Mac for the Blind
Tel, (631) 724-4479
Email, john@xxxxxxxxxxxxxxxxxx
Website, http://www.macfortheblind.com
Twitter, @macfortheblind

APPLE CERTIFIED SUPPORT PROFESSIONAL FOR MAC OSX LION

AUTHORIZED APPLE STORE BUSINESS AFFILIATE

MAC and iOS VOICEOVER TRAINING AND SUPPORT




On Oct 5, 2012, at 8:54 PM, David Hilbert Poehlman <poehlman1@xxxxxxxxxxx> 
wrote:

> == Apple quietly improving its iOS maps data ==
>  http://feedproxy.google.com/~r/cnet/tcoc/~3/MdQ63SMe1p8/
>  (from CNET News)
> 
> New photos show Apple has pushed out a number of changes to the location data 
> in its controversial maps application. [Read more]
> 
> 
> 
> -- 
> Jonnie Appleseed
> With His
> Hands-On Technolog(eye)s
> touching the internet
> Reducing Technology's disabilities
> One Byte At a time
> 
> 
> 
> ************
> 
> 
> You are subscribed to the mac4theblind mailing list.
> 
> 
>     The url for this list, where one can unsubscribe or make any changes to 
> their list subscription is:
> 
> //www.freelists.org/list/mac4theblind
> 
> The list archive is located at
> 
> //www.freelists.org/archive/mac4theblind/
> 
>     All emails intended for the list owner can be sent to:
> 
> john@xxxxxxxxxxxxxxxxxx
> 

************


You are subscribed to the mac4theblind mailing list.


     The url for this list, where one can unsubscribe or make any changes to 
their list subscription is:

//www.freelists.org/list/mac4theblind

The list archive is located at

//www.freelists.org/archive/mac4theblind/

     All emails intended for the list owner can be sent to:

john@xxxxxxxxxxxxxxxxxx

Other related posts: