Guys,

I swear to God I'm about ready to pull my f***ing hair out over here!  So is my 
friend.

I never ever have ever used a braille display before.  My friend who flew down 
to visit with me for a few weeks brought along with him a Packmate QX 40 
original USB braille display.  This is not the up to date display.  It's only 
the classic model.  He got it in 2004 if that helps.

I have plugged it into my I5 Mac Mini Late 2012 system, running Yosemite 
10.10.4.  This is not a public beta or the like.  This is the official 
available up to date release.  I have also pulled the EFI firmware update that 
just came down on July the 15th, if that makes any difference, although, even 
before doing so, I still saw this issue.

I have disabled all the status cells, and am using contracted braille, 
therefore causing dot 7 8 braille to be disabled.

In my Voiceover Utility, (VO+F8,) I have disabled the showing of the Voiceover 
Cursor, although even when turned on, I'm still noticing this issue.

I've reset Voiceover to all default settings, and even have imported my 
friend's Voiceover settings from his macbook which did absolutely no good.

The issue is that when I go into Text Edit, and create either a rich text, or a 
plain txt document, either/or, which has carriage returns throughout the file, 
I'm literally seeing the physical carriage return code on the display.

So, for instance, say I open up Text Edit, and type the following:

Hello, then after the letter o in hello is typed, I immediately hit return to 
make a new line.

Then on the next line of text, I write:  
My name is Chris.

OK, if you're reading this with a braille display currently, and you are in 
uncontracted braille, let me type out literally what you'll see.  Note to 
nonbraille display users, the following line of text is going to look very 
strange:

,hello1 my "n is ,*ris4

However, after the low d, (dots 2, 5, and 6,) for the period sign, I see the 
letter j, (dots 2, 4, and 5,) plus in that same cell, dots 7 and 8.  Just to 
further! wackid things up, as if that isn't odd enough, if I move the literal 
text edit insertion point to the end of the first line of text with command+up 
arrow, followed by command+right arrow, that j+dots 7 and 8 now turns into two 
cells.  Both have dots 7 8 under them.  Basically, now, instead of just a 
letter j, I now see m, (dots 1, 3, and 4,) followed by the letter j, (dots 2, 
4, and 5.)  

So in other words, instead of seeing:

Hello
My name is Chris.

I see:

cap sign, (dot 6,) helloj+dots 7 and 8my name is cap sign chris.

All of that on one line of text.  Move to the end of the line with the word 
hello, and then it goes to:

Hellomj+dots 7 and 8my name is Chris.

Again, all on one line.  No, I am not mistaking the j or mj with dots 7 and 8 
as the blinking cursor.  That's just showing as a blinking dot 7, which is to 
the right of the mj, or if at the start of the line, is under the dot 6 capital 
sign.

I've tried turning off contracted braille, and also have tried enabling and 
disabling dot 7 8 braille.  NO good.

I've tried English US, and also have tried English Unified in Braille on 
Voiceover Utility in the language popup button.  They both are producing this 
issue.

I've rebooted the mac.  NO good.  I've unplugged and replugged the USB cord 
both from the mac side, and from the display side.  I've swapped out the USB 
cable, and that didn't work either.

I've thrown the thing across the room and then paid him back ten grand.  LOL!  
Only kidding on that one!  I feel like I could! though?

I called Apple Accessibility, 1-877-204-3930, Option 2 from IVR, and they were 
stumped beyond belief!  My friend using a white Polycarbon macbook mid 2010, 13 
inch also on Yosemite 10.10.4 official release is not having this issue.

We've looked in Text Edit's preferences, and compared our settings.  All are 
100% identical.  I've reset my settings.  NO good.  I'm totally out of 
possibilities.  I think Pages calls these things the display is showing, 
"Invisibles."  Pages isn't having this issue though.  It is *only!* doing it in 
Text Edit.  My friend isn't having this issue at all.  Not even! in Text Edit.  
This isn't an assumption either.  We very concreetly tried it, and sure enough. 
 It's not occurring on his system.

The only thing I've not done is to delete the .plist file associated with Text 
Edit.  I'm not sure though where that file would be exactly, nor what it would 
be called.  I'm sure I could find it easily enough, but I've not gone that far 
just quite yet.

Aside that though, I am totally out of options!

I've even looked under Accessibility within System Prefs, but see absolutely 
nothing rellavent.

Please please! can someone help before I go insane over here trying to figure 
this out, or put my friend in a mental institution?  LOL!

Chris.

-- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

Reply via email to