Hi.
I've seriously started to use Orca with a Modular Evolution 88.
Currently, the "status cells" (the display is contiguous, i.e. there
is no break between the 80 cells and the remaining 8 cells) can not
be used by Orca. This is
1. slightly confusing since the BRLTTY status cell info is still s
Hi.
Our current implementation of -b auto on the USB bus
does work, but it is pretty inefficient. This gets extremely
obvious if one tries to run brltty in auto-detection mode
on a small embeeded-type device, like ARM based machines
running Linux. While BRLTTY is idling and trying to
find a brai
Hi.
Currently, GCC emits a warning regarding a statment without effect
in the python bindings that comes from the definition of returnerror.
returnerror is currently defined as a cdef. cdef does not really support
docstrings in pyrex (why should it). On second glance however, returnerror is
onl
Hi.
The following python session is reproducible for me with latest svn:
Python 2.4.4 (#2, Apr 25 2007, 22:41:41)
[GCC 4.1.3 20070423 (prerelease) (Debian 4.1.2-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import brlapi
>>> c = brlapi.Connection()
>>> c
Hi.
I can not build BRLTTY outside its source directory. To reproduce,
do the following:
$ mkdir build && cd build && ../configure && make
The patch below fixes the problems with the drivers, but the python
bindings still fail. The problem is inclusion paths:
brlapi_keycodes.h and brlapi_constan
<[EMAIL PROTECTED]>, Dave Mielke <[EMAIL PROTECTED]>, Mario Lang <[EMAIL PROTECTED]>
HELP_DEPS = $(HELP_TEXT)
Index: BrailleDrivers/HandyTech/help4.txt
===
--- BrailleDrivers/HandyTech/help4.txt (revision 0)
+++ Braill
Hi.
Just to let you know, I am running Linux 2.6.21 on
Debian unstable (sid) on a x86_64 machine. I am currently
using a serial display on that machine, but the Easy Braille for
which I just implemented support is a USB display and
that worked completely flawlessly here. In other words,
I can no
Lars Bjørndal <[EMAIL PROTECTED]> writes:
> On Tue, Jul 03, 2007 at 09:55:14PM +0200, Samuel Thibault wrote:
>> Note: it only works with serial devices with speed <= 9600bps.
>
> So it won't work with one of Handy Tech's braille displays? (I think
> they're using 19200, right?)
Yes. In fact, man
Hi.
I am seeing three (minor) warnings from the Debian lintian
package checking system for brltty 3.8 that are all related
to BRLTTY manual pages:
W: libbrlapi-dev: manpage-has-errors-from-man
usr/share/man/man3/brlapi_keys.3.gz 315: warning [p 5, 2.5i]: can't break line
W: brltty-x11: binary-wi
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sun 22 Jul 2007 15:27:25 +0200, a écrit :
>> W: libbrlapi-dev: manpage-has-errors-from-man
>> usr/share/man/man3/brlapi_keys.3.gz 315: warning [p 5, 2.5i]: can't break
>> line
>
> Here is a patc
Hi.
I remember we've discussed this several months ago already,
but now that I am trying brltty 3.8 on one maschine of mine
that uses a TSI PowerBraille 80, I have seen this bug again.
When I disconnect my TSI and reconnect it later on, it can happen
that the Baum driver claims the display in Pow
Jason White <[EMAIL PROTECTED]> writes:
>> Does the Baum driver really have to claim a 80 cell PowerBraille?
>
> I think this is a bug that should be fixed. Perhaps the Baum driver should
> skip checking for TSI and Handytech protocols if the display is connected via
> a serial interface and the m
Dave Mielke <[EMAIL PROTECTED]> writes:
> [quoted lines by Jason White on 2007/08/27 at 10:15 +1000]
>
>>Am I correct, however, in assuming that the problem only arises with a serial
>>interface?
>
> And, I suspect, with Bluetooth.
No, the powerbraille has no bluetooth interface.
>>Under USB, t
Dave Mielke <[EMAIL PROTECTED]> writes:
>>> the Baum driver would continue to check for emulation modes
>>> if USB is bieng used but would only check for the native Baum protocol if
>>> serial or Bluetooth is being used.
>>
>>The Bluetooth part in the above sentence looks like an error.
>
> So you
Hi.
I have a really strange problem with the Debian package of BRLTTY 3.8
that I fail to understand, maybe someone can shed a little more
light on the issue. Its related to the configure stage
for the Java bindings. When I build the package on
amd64 (64-bit arch) I get working Java bindings.
If
Samuel Thibault <[EMAIL PROTECTED]> writes:
>> Does anyone have the slightest idea why our configure script
>> does not find jni.h on an i386 host?
>
> Possibly a difference in update-alternatives --display javac ?
No, both report Current `best' version is /usr/lib/jvm/java-gcj/bin/javac.
Besides
Jason White <[EMAIL PROTECTED]> writes:
> I just discovered today, while installing Debian on a new machine and
> upgrading it to the Unstable distribution, that the version of BRLTTY 3.8 in
> the Debian Unstable repository has the Autosuspend bug which affects Baum
> Supervario (aka Brailliant) a
Christopher Gray <[EMAIL PROTECTED]> writes:
> I have 3.8 working now in a terminal window. However, when I go to a
> full-screen session, alt+ctrl+f7 in Ubuntu, I get the message "not in text
> mode". Is their a cure for this?
That depends if you are already logged in to GNOME or not.
I have
Christopher Gray <[EMAIL PROTECTED]> writes:
> On Fri, 7 Sep 2007, Dave Mielke wrote:
>
>> Is this perhaps a symptom of starting brltty after the X screen reader? Maybe
>> it doesn't try to reconnect.
>
> I don't think so, but wouldn't say for certain. The reason I am doubting
> this
> is that
Dave Mielke <[EMAIL PROTECTED]> writes:
> I'm just about ready to release 3.9 now, like in a week or so. Although
> things may (probably will) change a bit still, revision 3262 should
> be good. Would those who'd like to ensure that their packaging
> issues are fixed by the time 3.9 is released, t
Mario Lang <[EMAIL PROTECTED]> writes:
> I am right now testin r3290 with the packaging for Debian.
> For some reason, the installation of the BrlAPI manpages (section 3) fails.
> Did something change regarding the generation of the BrlAPI man pages
> in the 3.8->3.9 cycle?
Hi.
I've just had a pretty strange error on my TSI PowerBraille 80 that
I've never seen before (with brltty 3.8):
Sep 9 13:12:52 x2 brltty[28789]: Unexpected Response: 40 C0 20 A0 62 E0 00 05
51 08 56 31
Sep 9 13:12:52 x2 brltty[28789]: Input byte missing at offset 6.
Sep 9 13:12:52 x2 brltty
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sun 09 Sep 2007 13:30:34 +0200, a écrit :
>> Follow up to myself: It looks like the man pages do not get installed
>> anymore by default when running make install. Is this intentional?
>> Should I now c
Samuel Thibault <[EMAIL PROTECTED]> writes:
> /usr/bin/install -c -d /tmp/brltty/debian/brltty/share/man/man3
>
> dh_installman -plibbrlapi-dev debian/brltty/usr/share/man/man3/*.3
>
> Here is the problem: Dave, it looks like
> BRLTTY_PORTABLE_DIRECTORY([mandir], [/usr/share])
> doesn't work as ex
Hi.
It seems our use of gettimeofday to calculate elapsed time is potentially
buggy. When I run "rdate" to resync my computers clock with some internet
time server, it can happen that brltty stops to interact with my display for
a certain period of time.
This only happens when the time gets adjus
Samuel Thibault <[EMAIL PROTECTED]> writes:
> It looks like you only have libgcj8-dev, provided by gcj-4.2. Are you
> maybe compiling with gcc 4.1? In that case I guess gcc 4.1 can't find
> gcj-4.2's jni.h. It's possible that you have to explicitely choose
> between gcc 4.1 & gcj 4.1 or gcc 4.2
Dave Mielke <[EMAIL PROTECTED]> writes:
> [quoted lines by Samuel Thibault on 2007/09/09 at 21:13 +0200]
>
>>Mario Lang, le Sun 09 Sep 2007 20:51:54 +0200, a écrit :
>>> When I run "rdate" to resync my computers clock with some internet
>>> time serve
Dave Mielke <[EMAIL PROTECTED]> writes:
>>Voyager 44
>>I don't like status cels
>
> The Voyager driver is one which does support what you'd like to do. You need
> to
> pass in the driver parameter "statuscells=0" (without the quotes). You can do
> this via the -B (uppercase) command line option
[EMAIL PROTECTED] (Lars Bjørndal) writes:
> I'm working at Handy Tech Norway, which is an undependent company, not
> tied to Handy Tech in Germany, execpt for selling their products. I'm
> using Linux to do all my tasks in office, and I also use an Mod.
> Evolution 88.
>
> I too look forward to se
J.Schöber <[EMAIL PROTECTED]> writes:
> I used Debian 4.1 Lenny and found it recognised my Papenmeier els out of the
> box with no parameters at all! Great!
Yes, USB displays should all just work out of the box without any
boot parameters.
--
CYa,
Mario | Debian Developer http://debian.org/>
Hi.
I am getting the message from the subject if
I launch brltty from the initramfs (very early, before init is launched)
when I switch away from console 1 to something else (like 2, or 7).
If I restart brltty after runlevel 2 started up completely,
I can again switch to consoles other than 1. A
Dave Mielke <[EMAIL PROTECTED]> writes:
>>I guess this is because some device did not exist in my /dev hierarchy
>>while brltty was started first. Is this right?
>
> Yes, it would be.
>
>>Can we perhaps fix this such that brltty does not need to be restarted?
>
> That depends on why brltty needs
Dave Mielke <[EMAIL PROTECTED]> writes:
>>Actually, initramfs moves the /dev hierarchy over to the
>>new root directory, so the /dev directory is actually not different,
>>but I guess it could happen that brltty still lives in the old root.
>
> Yes, the current root directory is part of a process'
Samuel Thibault <[EMAIL PROTECTED]> writes:
>> > Note that brltty does try to create them within the writable directory but
>> > it
>> > won't be able to if that directory either doesn't exist or isn't writable.
>>
>> So I could rpbobably also just set -W /dev ?
>
> That should probably work fo
Dave Mielke <[EMAIL PROTECTED]> writes:
>>"Shows up" is going to be complicated, because it might as well take some
>>time until the chroot actually happens and the root fs is fully populated
>>(e.g.,
>>I use a custom setup at work where the root fs is actually retrieved
>>with rsync, that can ta
Hi.
Virtual console screen readers that wanted to use the
normal keyboard for review functionality always had the
problem on linux that some sort of a non-standardized kernel
patch was needed to get keysniffing to work.
I've been thinking about a method that allows to do this completely
from with
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Andor Demarteau, le Sat 15 Dec 2007 17:28:30 +0100, a écrit :
>> nice concept however for yoru special gkeys you could have used
>> setkeycoeds and loadkey, at elast for the console.
>> on my dell inspiron system some keypresses give off unknown keyco
Dave Mielke <[EMAIL PROTECTED]> writes:
>>some starting help for getting this into brltty core would
>>be very appreciated? Dave?
>
> Sure. What are the recommendations regarding how it should be activated? A
> command line option? If so, what should happen on non-Linux platforms?
I would recom
Dave Mielke <[EMAIL PROTECTED]> writes:
>>I think a command line option does not makes sense.
>
> What about a command line option to specify the configuration file?
A command line option + config variable to specify the mapping along
the lines of text-table and such would indeed be useful.
--
Dave Mielke <[EMAIL PROTECTED]> writes:
> If we want most of the code to be common within the core then we probably
> need
> a scheme for portabilizing key representations. Does one already exist or do
> we
> need to invent it?
AIUI, what linux currently uses is derived from the HID
standard
Dave Mielke <[EMAIL PROTECTED]> writes:
> Can anyone tell me how Speakup intercepts key events?
Speakup intercepts all sorts of things by directly patching
the kernel.
> If we use this scheme how will we be interacting with it?
I guess its a bit unpredictable if we are dealing with something
th
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Dave Mielke, le Sat 15 Dec 2007 14:56:32 -0500, a écrit :
>> Can anyone tell me how Speakup intercepts key events? If we use this scheme
>> how
>> will we be interacting with it? Does it intercept them first, do we, does
>> one
>> scheme disable or
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sat 15 Dec 2007 22:29:27 +0100, a écrit :
>> Dave Mielke <[EMAIL PROTECTED]> writes:
>>
>> > If we want most of the code to be common within the core then we probably
>> > need
>&g
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sat 15 Dec 2007 22:29:27 +0100, a écrit :
>> Dave Mielke <[EMAIL PROTECTED]> writes:
>>
>> > If we want most of the code to be common within the core then we probably
>> > need
>&g
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Hi,
>
> Jason White, le Sun 16 Dec 2007 20:22:55 +1100, a écrit :
>> Has anybody managed to create a Debian from Scratch image that loads BRLTTY
>> automatically when booted?
>
> Mmmm, this should already be the case with images starting from Etch.
>
>
Luke Yelavich <[EMAIL PROTECTED]> writes:
> On Sun, Jan 13, 2008 at 10:42:13AM EST, Luke Yelavich wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Sun, Jan 13, 2008 at 10:30:22AM EST, Dave Mielke wrote:
>> > Have you tried with the latest brltty source?
>>
>> I intend to do ju
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sun 13 Jan 2008 22:09:52 +0100, a écrit :
>> Luke Yelavich <[EMAIL PROTECTED]> writes:
>>
>> > On Sun, Jan 13, 2008 at 10:42:13AM EST, Luke Yelavich wrote:
>> >> On Sun, Jan 13, 2008 at
Dave Mielke <[EMAIL PROTECTED]> writes:
> How should we decide which event device is the keyboard? The simplest might
> be
> someting like selecting the first device which can deliver some well-known
> key
> event, e.g. space or enter. Any better ideas?
Yes, select the keyboard based on the b
Hi.
I recently had a chance to play with Optical Music Recognition
software under Windows. There are various products that can scan a page
of music and export in MusicXML format. So the hard part (the actual
OMR) can be done by the application of choice of the user (there
is even a free software
Hi.
Does anyone here know if it is at all possible to display
braille characters (0X2800-0X28ff) in console mode and
have brltty map them correctly to the associated dot combination?
I would be sort of happy if it just worked for brltty, if it
also worked to have the correct fonts displayed on th
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Samuel Thibault, le Sat 19 Jan 2008 21:13:46 +, a écrit :
>> > have brltty map them correctly to the associated dot combination?
>>
>> Unfortunately the screen driver model still does't take unicode into
>> account and thus brltty will still show
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Samuel Thibault, le Mon 21 Jan 2008 00:20:47 +, a écrit :
>> Samuel Thibault, le Sat 19 Jan 2008 23:23:22 +, a écrit :
>> > Samuel Thibault, le Sat 19 Jan 2008 21:13:46 +, a écrit :
>> > > > have brltty map them correctly to the associated
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Mon 21 Jan 2008 17:49:45 +0100, a écrit :
>> Reversed (or previously applied) patch detected! Assume -R? [n]
>
> Grmbl, it looks like I somehow sent the same patch. Here is hopefully
> the correct one.
Wow! Th
Hi.
I have a Optilec BC640 sitting on my desk for
potential driver development. I find the HID interface
pretty interesting to play with, so I requested specs from Optilec.
They told me Dave is already working on a driver for BRLTTY.
Is this true? Any early preview patches to play with and maybe
Dave Mielke <[EMAIL PROTECTED]> writes:
>>I have a Optilec BC640 sitting on my desk for
>>potential driver development. I find the HID interface
>>pretty interesting to play with, so I requested specs from Optilec.
>>They told me Dave is already working on a driver for BRLTTY.
>>Is this true? An
Hi.
This is as far as I could get without any specs.
Below is a C file that dumps the keypresses to stdout.
Keypresses are delivers pretty strangely, first the "keycode"
arrives, and then the key type. A key type indicator has
the left nibble set to 1110 or to indicate press and release,
an
Andor Demarteau <[EMAIL PROTECTED]> writes:
> you will probably not get any specs, I've been bugging optelec here in .nl
> for them for some time.
Well, Dave already has the specs, so thats not the problem...
--
CYa,
⡍⠁⠗⠊⠕ | Debian Developer http://debian.org/>
.''`. | Get my public key vi
Dave Mielke <[EMAIL PROTECTED]> writes:
>>Below is a C file that dumps the keypresses to stdout.
>
> So all you do is open a hiddev and read from it?
Yes, for now, thats all that is necessary. The Linux hiddev
interface has a bunch of ioctls as well (all defined in linux/hiddev.h).
They can be u
Dave Mielke <[EMAIL PROTECTED]> writes:
>>Yes, for now, thats all that is necessary. The Linux hiddev
>>interface has a bunch of ioctls as well (all defined in linux/hiddev.h).
>>They can be used to get "reports" and do other things, but
>>reading incoming events is as simple as reading from the
Nath <[EMAIL PROTECTED]> writes:
> I have installed debian testing on my new Asus Eee pc and I encounter a
> problem I never have had before : the braille display turns on sleep
> mode every 4 or 5 seconds. when I press a key on the braille display or
> on the laptop keyboard the braille display i
Samuel Thibault <[EMAIL PROTECTED]> writes:
>> Just checking again to see whether or not the version of brltty that fixes
>> the
>> problem with powerpc architecture has yet been implemented in any debian
>> installers?
>
> Not yet :/
I apparently cant find the mail anymore where you told
me the
Hi.
Orca uses glib to add a callback for when some data arrives
at the BrlAPI file descriptor. This is very useful to implement
a callback driven system for receiving brlapi keypresses.
Does anyone have code for doing this in pure python, without a dependency
on glib?
--
Thanks,
⡍⠁⠗⠊⠕ | Debian
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
[...]
> ../autogen && ./configure --disable-relocatable-install \
> --disable-table-selection --disable-contracted-braille \
> --enable-beeper-support --disable-midi-support --disable-fm-support \
> --disable-pm-configfile --disable-api --enable-st
Samuel Thibault <[EMAIL PROTECTED]> writes:
> BTW, Dave, I can see -licuuc -lsupc++ in API_LIBRARIES. These shouldn't
> be set, because that makes libbrlapi.so depend on libicuuc.so and
> libsupc++.so (and then a packaging dependency) for no reason.
BTW, now that I think of it, do we still really
Hi.
We do have the PASSDOTS command so that drivers can send along
braille keyboard keypresses to the core. Some displays
do have a braille-keyboard layout by default, and most of
our drivers for them do implement something like "input mode" so that
the keys can be switched between commands and b
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Dave Mielke, le Sat 08 Mar 2008 10:39:10 -0500, a écrit :
>> A related issue is that there really should be a way for a braille reader to
>> know if a given cell contains a dot pattern or a character. What if, for
>> example, the toggle is in the oth
Dave Mielke <[EMAIL PROTECTED]> writes:
>>But what if I want to use the input mode for typing Unicode braille?
>>
>>Can we add a toggle setting so that I can decide if I want PASSDOTS to
>>go through the translation table, or straight to unicode braille?
>
> Yes, we could certainly add that. The p
Dave Mielke <[EMAIL PROTECTED]> writes:
>>We have DESCCHAR for finding out details about a cells content.
>
> Yes, for when the user knows he may need to care. What, though, about
> accidents
> like when he thinks he's in character mode but is actually entering braille
> patterns? How will he c
Dave Mielke <[EMAIL PROTECTED]> writes:
> [quoted lines by Mario Lang on 2008/03/08 at 18:24 +0100]
>
>>What if we add a very short blip like sound that gets played if braille input
>>does not go through the translation table and is not sent to an API client?
>
&
Jason White <[EMAIL PROTECTED]> writes:
> In general, I think BRLTTY should eventually move to a model where all of the
> bindings of keys/buttons/switches/sensors etc., on the display to BRLTTY
> commands are specifiable and configurable outside the drivers, ultimately in a
> configuration file.
Daniel Dalton <[EMAIL PROTECTED]> writes:
> On Thu, 21 Feb 2008, Dave Mielke wrote:
>
>> [quoted lines by Daniel Dalton on 2008/02/21 at 22:19 +1100]
>>
>>> How do I get brltty talking with speech-dispatcher?
>>>
>>> And then will it read as I use the arrows? (Like other screenreaders?)
>>>
>>> Wh
Jason White <[EMAIL PROTECTED]> writes:
> On Mon, Mar 17, 2008 at 08:25:16AM +1100, Daniel Dalton wrote:
>>
>> When I choose speech-dispatcher in brltty.conf and boot it says:
>> speech-dispatcher: open failure.
>>
>> I have no speech.
>>
>> Anyone know why?
I am guessing this is because you a
"Lee Maschmeyer" <[EMAIL PROTECTED]> writes:
> The fact that it says "rev unknown" means brltty has not been updated; that
> was a bug fixed right after that version was released.
No, "rev UNKNOWN" was only fixed in the development branch, there
was no new stable release. Because of the lack of
Dave Mielke <[EMAIL PROTECTED]> writes:
> The only significant component of brltty which isn't yet Unicode-based is
> the text tables support. What do you people think of getting rid of
> them and just using contraction tables (whetther or not we
> eventually rename them is another topic)?
FWIW,
Daniel Dalton <[EMAIL PROTECTED]> writes:
> When pluging my braille note into my box with a usb to serial (and an
> adapter) (So it will connect since the port on the end of the cable is not
> different so won't connect to the BN) I then plug the usb end into my usb
> port.
> $ sudo dmesg | les
Jason White <[EMAIL PROTECTED]> writes:
> If, as I suspect, it is writing to the correct device, there may be a kernel
> issue.
I've also seen usb-to-serial adaptors that did not fully support
the serial port standard -- which do not work with certain serial braille
displays (I think it was somet
Dave Mielke <[EMAIL PROTECTED]> writes:
> If we use contraction tables in place of the strictly one-to-one text tables,
> what are your collective thoughts on the one major difference that
> contraction
> table support splits braille windows on word boundaries whereas text table
> support does
Hi.
I am seeing the following warnings from doxygen:
/usr/bin/doxygen BrlAPIref.doxy
Warning: Tag `USE_WINDOWS_ENCODING' at line 64 of file BrlAPIref.doxy has
become obsolete.
To avoid this warning please update your configuration file using "doxygen -u"
Warning: Tag `MAX_DOT_GRAPH_WIDTH' at lin
Hi.
If I svn export my checkout of brltty, run autogen.sh on my exported
version and build brltty and its documentation as usual, I do get
a very strange manpage that has the full path of my build directory in it,
something like
_home_user_some_dir_to_exported-brltty_Programs_.3
which appears to b
Hi.
Doxygen confuses me, so I am forwarding this bugreport I just
got regarding brlapi manpages: Basically, we generate (and install)
a manpage named error.3. This conflicts with an already existing
manpage on Linux with the same name.
Does anyone know how to fix this? The page should
probably
Sébastien Hinderer <[EMAIL PROTECTED]> writes:
> It is also impossible for me to continue order on Amazon. The site tells
> me I should enable cookies in my browser, but they are supposed to be
> enabled.
I see the same thing here for amazon.de with botz, lynx and lynx-cur.
My suspicion is that t
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Wed 07 May 2008 13:20:55 +0200, a écrit :
>> Doxygen confuses me, so I am forwarding this bugreport I just
>> got regarding brlapi manpages: Basically, we generate (and install)
>> a manpage named error.3.
&
Sébastien Hinderer <[EMAIL PROTECTED]> writes:
>> I have to use firefox
>> for amazon ordering since about 3 months now, which really sucks
>> since it takes me about 3 times as much time to acomplish the same
>> thing I previously did with lynx.
>
> Hmm! That's an interesting news for me because
Dave Mielke <[EMAIL PROTECTED]> writes:
> [quoted lines by Mario Lang on 2008/05/07 at 15:29 +0200]
>
>>Excuse me, but where are these install rules to be found?
>>Documents/Makefile doesn't have a install rule, and in the main
>>makefile, I couldnt find any
Dave Mielke <[EMAIL PROTECTED]> writes:
>>1. Note that vtsp and xbrlapi were installed, but their respective
>> manpages were not.
>
> Because they haven't been written yet.
Thats not quite true:
x2:~/src/a11y/brltty% find . -name vstp.1 -o -name xbrlapi.1
./Documents/xbrlapi.1
./BrailleDrivers
Dave Mielke <[EMAIL PROTECTED]> writes:
>>2. The man3 directory is completely empty, why? Should I have
>> run make in the Documents directory manually? If so, why?
>
> Yes, because not all users have doxygen, sgmltools, etc. This was a conscious
> decision. Perhaps it's no longer a valid r
Sébastien Hinderer <[EMAIL PROTECTED]> writes:
> Mario Lang (2008/05/07 15:33 +0200):
>> I initially used FF with braille and speech, but after I
>> did my first youtube.com experiments, I realized speech doesn't
>> work together with flash movies, so I had to
Hi.
* Install xbrlapi.1 and man3/*.3 files if BLD_TOP != SRC_TOP:
Index: Programs/Makefile.in
===
--- Programs/Makefile.in(revision 3714)
+++ Programs/Makefile.in(working copy)
@@ -518,7 +518,7 @@
$(INSTALL_PRO
Sébastien Hinderer <[EMAIL PROTECTED]> writes:
> Hi,
>
> Stéphane Doyon (2008/05/07 08:43 -0400):
>> It still likes to pause and show it to you, along with
>> lots of other useless status messages, makes it a lot slower than it
>> could be.
>
> The -nopause command-line option solves this proble
Samuel Thibault <[EMAIL PROTECTED]> writes:
> There is quite often some confusion between -d usb: and
> -d serial:ttyUSB0, and it is not necessarily obvious for the beginners
> to understand the difference between both.
This is the same on other operating systems. In fact, to configure
a USB dev
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Fri 27 Jun 2008 13:55:24 +0200, a écrit :
>> I have to say, my gut reaction is that I am against such a change.
>
> I have to say that mine was the same.
>
> The problem is that a few weeks ago I'v
Hi.
While skimming over the new converted de.ttb file in
the dev repo, I noticed the following:
char \xA7 (12345678) # ⣿ § [SECTION SIGN]
char \xB6 (12345678) # ⣿ ¶ [PILCROW SIGN]
On first sight, this looks wrong. Given that we have 2^8 possible
chars and 2^8 possible dot-patterns, we shouldn'
Dave Mielke <[EMAIL PROTECTED]> writes:
>>> On first sight, this looks wrong. Given that we have 2^8 possible
>>> chars and 2^8 possible dot-patterns, we shouldn't reuse the
>>> same dot pattern for two different characters.
>
> We actually now have way more than that since the tables have become
Jason White <[EMAIL PROTECTED]> writes:
> On Sat, Aug 09, 2008 at 01:30:12AM -0400, Dave Mielke wrote:
>
>> >There are other things like certain symbols are kind of duplicated in
>> >Unicode.
>> >But I cant think of any right now, I'd need to check.
>
> As I remember, accented letters are among
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sat 09 Aug 2008 07:03:32 +0200, a écrit :
>> There are other things like certain
>> symbols are kind of duplicated in Unicode. But I cant think
>> of any right now, I'd need to check.
>
> Well, th
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Hello,
>
> Mario Lang, le Sat 09 Aug 2008 07:03:32 +0200, a écrit :
>> One example that kind of interests me is the international phonetic
>> alphabet, which is used on Wikipedia sometimes. A mapping
>> for that
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sat 09 Aug 2008 10:55:00 +0200, a écrit :
>> Jason White <[EMAIL PROTECTED]> writes:
>> > On Sat, Aug 09, 2008 at 01:30:12AM -0400, Dave Mielke wrote:
>> >
>> >> >There are other
"Marc Mulcahy" <[EMAIL PROTECTED]> writes:
> Sory if this has been discussed here before-- but it appears as though the
> BrailleNote is supported, but only over a serial connection, and not via
> Bluetooth. Has anyone attempted this? I'm game to try to get it working
> with some initial guidanc
Luke Yelavich <[EMAIL PROTECTED]> writes:
> On Thu, Sep 04, 2008 at 01:48:26AM EST, Labrador wrote:
>> A) it doesn't autodetects my Alva Satellite 544, that's a big problem
>> and IMHO an important *regression*, sorry :
>> it "auto" was causing some problems, the "serial-usb" now causes 100% of
>
Scott Berry <[EMAIL PROTECTED]> writes:
> I have a Power Braille 80 braille display. I am trying to configure in
> the "/etc/brltty.conf" file that I want it too load the braille display
> on "/dev/ttyUSB)" because I have a usb to serial converter. But I am
> having trouble getting the syntax co
1 - 100 of 450 matches
Mail list logo
