[bookport] Re: BUG OR FEATURE, SOME FILES WON'T NAVIGATE BACKWARD?
- From: "ROB MEREDITH" <rmeredith@xxxxxxx>
- To: <bookport@xxxxxxxxxxxxx>
- Date: Mon, 19 Sep 2005 08:59:16 -0400
Brian:
There is not a feature which is accidentally getting turned on or off.
The problem usually lies with files which have very short, or
non-spoken, portions between two navigation marks.
Imagine that each paragraph starts with a ":" character. In this case,
you would likely find it impossible to navigate backwards, because the
colon is not spoken in the default punctuation mode. So, every time you
moved back, the unit would immediately think it was beyond the colon,
and would get stuck. Turning on Most punctuation mode may help. Sarah's
example of the double period is a perfect example.
In short, there is something about the files with which you are having
trouble. We made an exception with page navigation a while back where
you should always be able to move back a page no matter what.
Rob Meredith
>>> buhrow@xxxxxxxxxxxxxxxxxxxxx 09/16/05 04:27PM >>>
Hello. Let me appologize in advance for the length of this
message.
Background:
I'm running Bookport, Firmware V2.1, released in June of this year, I
believe.
Description of problem:
I have a number of texts on my Bookport, some gleaned from
Daisy
files from Bookshare, some gleaned from the ASCII files on the CDROM
which
came with the Bookport, and some indexed MP3 files.
When reading through some of the texts, I find that the 1 and 4
keys
go back to the beginning of the current line or sentence while reading,
but
no further, regardless of how often I press the 1 or 4 keys. On other
texts, which appear to be indexed exactly the same
way, repeated use of the 1 or 4 keys while reading causes the reading
pointer to move past the beginning of the current line or sentence, and
on to the
beginning of the previous line or sentence. In all cases, the 7 or
1-4
keys appear to work properly and move backward, from page to page, or
section to section, as advertised in the documentation.
Is there some feature whereby some sort of hierarchical
navigational
restriction can get turned on such that only commands which move you
backward
through the texts with less granularity take precedence over ones
which
move in smaller increments? It is worth noting, that there is never a
problem moving forward through texts, just backward.
At first I thought the problem was that I wasn't hitting the
navigational keys fast enough. The pointer would move back to the
beginning
of the selected index point, and them move forward as reading
continued.
Then, when I pressed the key again, the pointer would be beyond the
beginning of the selected index point, and so it would move back to
where
it was. Then, I discovered some files where the behavior was
different.
With those files, when navigating backward, Bookport would move bak to
the
beginning of the indicated index point, then, with another key press,
it
would move back to the beginning of the previous block.
Has anyone else noticed this inconsistency? Has anyone else
noticed
it and figured out what's different? Is there some feature of which
I'm
not aware?
-thanks
-Brian
Other related posts:
