No subject
Thu Dec 25 21:32:58 EST 2014
ctive of the user this will be great improvements=0A=
in the access time to the information.=0A=
</pre>=0A=
<blockquote>=0A=
<pre></pre>=0A=
<blockquote>=0A=
<pre>Overall I miss the great picture on what is going on. There is no met=
a=0A=
document that discribes the difference between cursor and reading focus=
=0A=
movement and=0A=
this crucial difference is also not reflected in the terminology of the=
=0A=
config files.=0A=
</pre>=0A=
</blockquote>=0A=
<pre>But it's implicitly understood by blind users. </pre>=0A=
</blockquote>=0A=
Mh. My brother may not have this inbuild implicit insight you attest=0A=
all blind users. :-)<br>=0A=
Without my help he had never mastered the focus 14 brltty=0A=
keybindings.<br>=0A=
He is very intelligent - has an absolute memory -- he never forget=0A=
anything - and learns at a speed of light.<br>=0A=
But without knowing the names of the buttons all the documentation=0A=
of the keybindings is useless.<br>=0A=
It was not possible even for his genius to fiddle it out by try and=0A=
fail.=0A=
<blockquote>=0A=
<blockquote>=0A=
<pre>You may find a graphical documentation of the BRLTTY Key-Bindings to =
the=0A=
physical keys on the FS Focus 14 here:=0A=
=0A=
<a href=3D"https://inqbus-hosting.de/volker/focus_14_doku.odg/at_download/=
file">https://inqbus-hosting.de/volker/focus_14_doku.odg/at_download/file<=
/a>=0A=
</pre>=0A=
</blockquote>=0A=
<pre>Including this sort of thing for just one model wouldn't, in and of i=
tself, be =0A=
all that useful. It might be extremely useful, however, were we to have su=
ch a =0A=
picture for each and every model (or, for at least most of them). I'm =
=0A=
wondering, therefore, if you might have the time to put together just such=
a =0A=
collection.</pre>=0A=
</blockquote>=0A=
I would be honored to craft this graphical documentation for the=0A=
community.<br>=0A=
Since I do not have physical access to all the many braille device=0A=
brltty support, I will need some help from the community.<br>=0A=
<br>=0A=
Here is my plan:<br>=0A=
<br>=0A=
1) I will get me an overview of the different devices and their key=0A=
naming schemes.<br>=0A=
2) These I will compare with the brltty keynames in the=0A=
documentation and look for differences.<br>=0A=
3) The differences I then will publish for the community to give me=0A=
hints to correct or complete.<br>=0A=
4) I will produce documentation of the devices and name all the=0A=
buttons, levers, rockers according to the brltty notation. I will=0A=
produce these graphics <br>=0A=
in a way that visual impaired people like my mother (10=
% sight)=0A=
can read it at their reading device easily.<br>=0A=
5) A judge will review the documentation and will report to the=0A=
community.<br>=0A=
6) The reviewed documentation will then be published<br>=0A=
<br>=0A=
For all this we need <br>=0A=
* a judge<br>=0A=
* a medium for collaboration. What medium do blind use to work=0A=
effectively together on a single document?<br>=0A=
We non blind use etherpad for this task but this is usi=
ng=0A=
javascript and does not works with console browsers like links2.<br>=0A=
<br>=0A=
What do you recommend?<br>=0A=
<br>=0A=
<blockquote>=0A=
<pre>It also highlights an interesting "problem". I myself - and, in fact,=
most of =0A=
us - am unable to even check it out in order to aprove it for web site =
=0A=
inclusion. You see, most of us (myself included) are fully blind.</pre>=
=0A=
</blockquote>=0A=
Recently I have asked Klaus/Adriane Knopper for assistance. I think=0A=
they may be a good judge for the quality of my work. <br>=0A=
<blockquote>=0A=
<pre></pre>=0A=
<blockquote>=0A=
<pre>Tell me how to contribute more ..=0A=
</pre>=0A=
</blockquote>=0A=
<pre>We'd welcome whatever you may be able to contribute. As mentioned abo=
ve, =0A=
perhaps you could put together a collection of braille device pictures for=
us =0A=
that would assist sighted users.=0A=
=0A=
On the issue of key layouts: Some of our key tables already do contain ver=
bal =0A=
descriptions of them. Check out the *.ktb and *.kti files within the =
=0A=
Tables/Input/*/ subdirectories of the source tree for lines which begin wi=
th =0A=
the keyword "note". After installation, these files end up in the /etc/brl=
tty/ =0A=
directory. Since verbal descriptions are useful to both blind and sighted =
=0A=
users, completing these descriptions is something that definitely must be =
done.=0A=
=0A=
</pre>=0A=
</blockquote>=0A=
I have checked them out. One Idea my wife has was to give every key=0A=
binding some optional tags. <br>=0A=
Together with sorting and tagging the list of keybindings can be=0A=
structured easily and very personally.<br>=0A=
<br>=0A=
Best Regards<br>=0A=
<br>=0A=
Dr Volker Jaenisch<br>=0A=
<br>=0A=
<br>=0A=
<br>=0A=
<br>=0A=
<pre>-- =0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=0A=
inqbus it-consulting Dr. Volker Jaenisch=0A=
Richard-Strau=C3=9F-Str. 1 +49(08861) 690 474 0=0A=
86956 Schongau-West <a href=3D"http://www.inqbus.de">http://www=
.inqbus.de</a>=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D =0A=
=0A=
=0A=
</pre>=0A=
</div>_______________________________________________<br>This message was =
sent via the BRLTTY mailing list.<br>To post a message, send an e-mail to:=
BRLTTY at mielke.cc<br>For general information, go to: http://mielke.cc/mail=
man/listinfo/brltty</blockquote></body></html>=
--=_768c09353c1d43d4181e11ce=9d00de43-1be5-57ad-963f-8f1a1df13e36_=--
More information about the BRLTTY
mailing list