Joseph, I have asked to be on the beta testing team for some time now but as yet have not received a response about it.
I have been beta testing software for many years and am currently beta testing some major products such as JAWS and Talks for mobile phones. It is extremely rewarding to be beta testing products especially the ones you use every day for your bread and butter! I do hope Humanware will consider me for the next beta cycle as I could have really helped out wiht these translation errors... Scott ----- Original Message ----- From: "Joseph Lee" <[EMAIL PROTECTED]> To: "Richard Ring" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[email protected]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, September 02, 2007 4:44 AM Subject: RE: [Braillenote] List of current bugs found under KeySoft 7.5.17 Hi Richard, In light of this, I've asked Andy (back when he was with us) for a possibility for me to join the beta testing cycle. HW didn't sent me invitations. Here are my thoughts: If HumanWare wants to test a software under Beta Testing Cycle, they should have chosen users of all models (at least mPower and PK usths). In terms of mPower, they should have chosen people who use both BrailleNote and and VoiceNote and should have chosen both BT and QT users. If people who use BT model have noticed this (at least by early August), this translation issue would have been at least "fixed" by the time of release. I think the thing that we've experienced last September with KeySoft 7.2.43 1so repeating again, but with greater magnitude. Why did we have those two BrailleNote chats in July? X was meant to alert HumanWare staff of problems that we've experienced with KeySoft 7.2 and earlier and we wanted these (espeially Word conversion, this extends to braille translation as well) to go away with KeySoft 7.5. We'v" also asked about details about Duxbury upgrade, but look at what happened with KeySofar erance: BT users are experiencecing serious bug with braille translation. I'm sure HumanWare tried not to repeat those same mistake again (just like last year) but unfortunately HumanWare did it again with more severe consequences. T's all. Cheers, Joseph > ----- Original Message ----- >From: "Richard Ring" <[EMAIL PROTECTED] >To: "Kevin Chao" <[EMAIL PROTECTED]>,"Alex Parks" <[EMAIL PROTECTED]>,"Joseph Lee" <[EMAIL PROTECTED]>,<[EMAIL PROTECTED] ist.humanware.com>,<[EMAIL PROTECTED] com>,<[EMAIL PROTECTED]>,<alex.bec @humanware.com >Date sent: Sat, 1 Sep 2007 13:33:16 -0500 >Subject: RE: [Braillenote] List of current bugs found under KeySoft 7.5.17 >I haven't upgraded as of yet, and these discussions are making it appear >rather unlikely that I will until some of these issues are addressed. I >must, however, state the following. >I have beta tested software off and on for about 11 years. I have >exchanged ideas and attempted to duplicate bugs, as well as discover >bugs of my own. My question is this. How on Earth could the HumanWare >beta testers have missed these Braille translation errors? Were only QT >users involved in the testing? Certainly not. I simply feel strongly >that the core of beta testers are simply not representative enough of >the Braillenote using population. Do you all remember when 7.2 was >released? Do you remember that the PK joystick was rendered useless? >How on Earth can such things be missed? When you beta test, you're >supposed to pound on each and every aspect of a product. Certainly it >is true that Keysoft presents a true challenge to beta testers, in that >it is a fairly complex piece of software. But such blatant Braille >translation errors simply shouldn't have been missed. It is true that >there can be small bugs that somehow get past the developers and the >beta testers. However Braille translation errors of this magnitude do >not constitute small bugs in my opinion. I firmly believe that to do >effective beta testing, you must use a good variety of individuals who >use their Braillenotes and Voicenotes to accomplish a wide array of >tasks. It does not seem to me that this software was beta tested >thoroughly enough, and this is not something that reflects well on >HumanWare! >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] m] On Behalf Of Kevin Chao >Sent: Saturday, September 01, 2007 1:07 PM >To: Alex Parks; Joseph Lee; [email protected]; >[EMAIL PROTECTED]; [EMAIL PROTECTED]; >[EMAIL PROTECTED] >Subject: Re: [Braillenote] List of current bugs found under KeySoft >7.5.17 >I would like to add: >1. When emailing an attachment that is in a braille or keysoft format, >the >system no longer prompts attach as a different file type. >Kevin >----- Original Message ----- >From: "Alex Parks" <[EMAIL PROTECTED] >To: "Joseph Lee" <[EMAIL PROTECTED]>; ><[email protected]>; <[EMAIL PROTECTED]>; ><[EMAIL PROTECTED]>; <[EMAIL PROTECTED] >Sent: Saturday, September 01, 2007 5:52 AM >Subject: re: [Braillenote] List of current bugs found under KeySoft >7.5.17 >>I would like to add: >> 1. When marking media files to play, the files are queued >>alphabetically >> and not in the order in which they were marked. A person trying to >> playlist multiple chapters of an audio book will find quite a surprise >> when the chapters are out of order even though they were marked in >order. >> 2. The "folder commands list" and "subdirectories commands list" both >> contain an item about moving the current or marked folder(s). Moving >> folders is still impossible. >> 3. You are prompted for the configuration to connect with in Keyweb >when >> switching back into it from another application; this should not be >> necessary as you have already established which one you want to use. >> 4. Not a bug, but there should be an option to send email when >entering >> the inbox. I know many people found it bothersome, but I liked it as >all I >> had to do to send my reply was exit the inbox, then press entery, y, >> enter, enter and my reply was sent plus I knew if there were new >messages. >> 5. The symbol for English appears at the top of emails and things I >write >> (not sure about documents yet) even if it is the only language ever >used >> and is my gefault language. >> 6. The help in the Block Commands Menu says nothing about the Quick >Marks >> feature, which I discovered completely by accident when browsing the >user >> guide index. If not for that, I would never have known about them. >> 7. My speech just stopped as I wrote this, the first time that >happened. >> Everything else worked fine and speech came back once I went through >> "speech on request", "speech off", and finally "speech on" (so I >didn't >> accidentally turn it off; it stopped by itself). This has not happened >> since 5.x or 6.11, I cannot remember which. >> 8. Keymail still has the problem of not sending (or even saving) a >message >> if, during its composition, the user switches to another task and then >> back. The message acts normal except that, even though the BN says >there >> is an email to be sent, nothing is in the Outbox and no copies are >saved, >> even if the BN was told to save a copy. >> 9. Saving emails using the space-s command no longer works (according >to >> other users). The email, if anything gets saved at all, is only saved >for >> the first few lines. (Again, this is according to other users and I am >not >> speaking from experience.) >> Have a great day, >> Alex >>> ----- Original Message ----- >>>From: Joseph Lee <[EMAIL PROTECTED] >>>To: BrailleNote List >> <[email protected]>,maurice.sloa [EMAIL PROTECTED], >> [EMAIL PROTECTED],[EMAIL PROTECTED] re.com >>>Date sent: Fri, 31 Aug 2007 18:43:54 -0700 >>>Subject: [Braillenote] List of current bugs found under KeySoft >> 7.5.17 >>>Dear HumanWare staff, development team and >>>BrailleNote List members, >>>HumanWare released KeySoft 7.5 on August 31, >>>2007. Th upgrade is full of many new >>>features such as SSL support, Playlist >>>support and so on. Alth it has many features >>>that we, the users asked for many months both >>>on the list and off list, there are still >>>bugs that still pleague KeySoft and might >>>create a situation that we've experiencec a >>>year ago: when KeySoft 7.2.43 was released >>>last year, there were countless reports of >>>bugs experienced by users of BrailleNote >>>family of products. Alth KS 7.5Ag is >>>certaintly more stable than 7.2.43, it still >>>has numerous bugs that might affect daily use >>>of the product. >>>Some of the notable and documented bugs >>>include: >>>inin KeyMail: when attempting to connect to >>>send and receive email, two things happen >>>depending on the following two scenarios: >>>a. If an email account uses SSL to connect >>>to the email server (for example, Gmail): >>>when you invoke Connect function, an error is >>>returned, stating that it is "incorrect >>>function" for no apparent reason. >>>b. When an email account does not use SSL >>>connection: when a user uses "Connec" >>>function, it returns an error stating >>>"invalid socket handle" with error cone >>>10038. >>>These two scenarios occur when attempting to >>>connect to an email service using a network >>>(Ethernet) connection. >>>inin Networking: When a network card >>>(specifically Ethernet cards such as Socket >>>EA2902-139) is used to connect to the >>>Internet, a dialog appears with the following >>>text: >>>Windows CE Networking >>>DHCP (Dynamic Host Configuration Protocol) >>>was unable to obtain an IP address. If the >>>network card is removable, try reinserting >>>the card. Otherwise, you can assign static >>>IP address. >>>DHCP is used to assign unique IP address for >>>the BrailleNote (if a network uses >>>router/hub/switch to connect multiple >>>computers). Th occurs even though the >>>configuration in question is set to use DHCP >>>(the user have to say "yes" to the prompt >>>"obtain an IP address automatically"). Al, >>>even though a user assigns static IP address >>>such as 192.168.0.17, the error message with >>>the words "invalid socket handle" is still >>>displayed. >>>inin KeyPlus: When entering Data Entry Mode >>>with SPACE with d (on BT), an exception is >>>thrown. X says, "Exception: Command: 600 at >>>"address". Access violation at "memory >>>location"." This persists every time a user >>>turns Data Entry on. Data Entry mode is used >>>to input data for statistical inperations. >>>Af few attempts at this, KeyPlus "literally" >>>stops working with following symptoms: >>>a. When attempting to access Scientific >>>Calculator (KeyPlus) from Main Menu, an error >>>beep is heard and the cursor stays at Main >>>Menu items. >>>b. When Scientific Calculator is run, it >>>displays "KeyPlus" on the braille display and >>>nothing else. >>>The only way to solve this "temporarily" is >>>to reset the BrailleNote. >>>Inconsistancies: >>>inin File Manajer: when invoking Help >>>function at "Drive" prompt, the shortcut key >>>for Flash Disk and KeySoft System Disk (RAM >>>Disk; f and k, respectively) is surrounded by >>>what looks to be quotation marks. All other >>>shortcuts for other drives (CF, PC, SD, hard >>>disk; c, p, s and h, respectively) does not >>>have quotes around the shortcut key. >>>inin Information: The date for the copyright >>>for KeySoft is written like this: the number >>>"1986" is written in literary grade 2 >>>braille, while numbers "2007" is written in >>>computer braille. Th also applies to the >>>word "to" between these numbers. >>>inin General/Help: When a user invokes Help >>>function at a prompt that is part of a >>>database e.g. when adding an email account >>>or manipulating Connection Configurations, >>>the help messages are displayed in computer >>>braille instead of preferred braille grade >>>e.g. literary Grade 2. All other prompts, >>>such as help messages for menus, are >>>displayed using preferred braille grade. >>>I hope that these issues would be resolved in >>>the near future (like in the form of a patch >>>for KeySoft 7.5). >>>Regards, >>>Joseph Lee >>>___ >>>Replies to this message will go directly to the sender. >>>If your reply would be useful to the list, please send a >>>copy to the list as well. >>>To leave the BrailleNote list, send a blank message to >>>[EMAIL PROTECTED] >>>To view the list archives or change your preferences, visit >>>http://list.humanware.com/mailman/listinfo/br aillenote >> ___ >> Replies to this message will go directly to the sender. >> If your reply would be useful to the list, please send a >> copy to the list as well. >> To leave the BrailleNote list, send a blank message to >> [EMAIL PROTECTED] >> To view the list archives or change your preferences, visit >> http://list.humanware.com/mailman/listinfo/br aillenote >___ >Replies to this message will go directly to the sender. >If your reply would be useful to the list, please send a >copy to the list as well. >To leave the BrailleNote list, send a blank message to >[EMAIL PROTECTED] >To view the list archives or change your preferences, visit >http://list.humanware.com/mailman/listinfo/br aillenote ___ Replies to this message will go directly to the sender. If your reply would be useful to the list, please send a copy to the list as well. To leave the BrailleNote list, send a blank message to [EMAIL PROTECTED] To view the list archives or change your preferences, visit http://list.humanware.com/mailman/listinfo/braillenote ___ Replies to this message will go directly to the sender. If your reply would be useful to the list, please send a copy to the list as well. To leave the BrailleNote list, send a blank message to [EMAIL PROTECTED] To view the list archives or change your preferences, visit http://list.humanware.com/mailman/listinfo/braillenote
