Closed GoogleCodeExporter closed 9 years ago
See also discussion on MR post #3901 ff
http://www.mobileread.com/forums/showpost.php?p=2281399&postcount=3901
Copy of post #3909 by Analogus
I think it's an issue of PRS 2.1 Alpha. So far as I can remember I have had no
problem until I merged my Zork with alpha.
The glitch is quite strange. It's not possible to highlight or use a dic
SOMETIMES. It depends on the page of a book you are using. Say, the first page
might be ok, on the second page you only coul use the last 3 lines, on the next
page line 9-13 is unusable...
After playing quite a while I may clearly say, this behaviour is connected to
SINGLE PARAGRAPHS (Absätze)!
Roughly each second paragraph is not working. If one word is not working, the
whole paragraph is not working. Most of the time, the next paragraph is ok, the
following refuses to work, ...
A.
Original comment by Mark.N...@gentlemansclub.de
on 28 Oct 2012 at 8:32
I made some further tests with my PRS350:
PRS+ 2.0 "LeChuck" for 350:
EPUB: Highlighting & using dics not possible roughly every other/second
paragraph
RTF: no problems
PDF: no problems
PRS+ 2.1 alpha for 350:
EPUB: Highlighting & using dics not possible roughly every other/second
paragraph
RTF: no problems
PDF: no problems
ZORK for 350 using repository from 08-october-2012:
RTF: no problems
PDF: no problems
BBeB: no problems
EPUB: Highlighting & using dics not possible roughly every other/second
paragraph.
But:
This error is not present in each EPUB. I tried to find out what could be
responsible.
I started with EPUB (over 200 pages) having this glitch:
Calibre: converting epub --> epub: glitch further present
Calibre: exploding epub and brute removing picture & CSS: glitch present
Calibre: converting epub --> rtf: glitch removed in rtf
Calibre: rtf --> epub: glitch gone!
Original comment by josef.mi...@gmail.com
on 1 Nov 2012 at 1:27
same thing for PRS-650
Original comment by kristof....@gmail.com
on 4 Nov 2012 at 7:18
I got a test-file form Analogus.
Indeed there are paragraphs, where after a double tap the "don't enter lane"
sign blinks up, instead of calling the dic.
This is independend of the orientation.
If a word in a paragraph isn't recognised in portrait, then it is the same in
landscape, same goes for true-landscape.
BUT, I ran a quick test in safe-mode, and there is the same behaviour!
So this looks like a bug in the SONY-firmware / or the epub-encoding.
Though the testfile is calibre-formated, it doesn't look suspicious at a first
glance, but should be check against a validator.
Original comment by Mark.N...@gentlemansclub.de
on 5 Nov 2012 at 8:49
Hi Mark,
I want to point out that as stated in the report, "When I remove PRS+ and use
original firmware, everything is working fine. "
So, if it is still not working in safe mode there is something about that safe
mode.
Also dictionary issue and highlight text issue could be different issues, I
reported about highlighting text, didn't check the dictionary functionality.
Original comment by hes...@gmail.com
on 5 Nov 2012 at 9:32
hesse,
thanks for your headsup, but I just unistalled PRS+ on my reader, and it
behaves the same!
After further testing it is clearly that annotations and calling the dictionary
are interlinked. If a double-tap didn't bring up the dictionary, you coudn't
highlight in this paragraph. Though you can highlight, if you start in a
"tap-aware" paragraph, mark over a "bad" one, and end in a "tap-aware" one.
With the testfile provided by Analogus this is the same in native firmware
(after PRS+ uninstall and rebooting twice - just to be sure) and in any PRS+
version.
Also it isn't just linked to certain paragraphs, the "tap-aware" paragraphs
might change upon your font-size-setting.
I'm able to highligt a paragraph in XS, which couldn't be marked in "S"
I'm glade that reverting to stock-firmware solved it for you, but for my 650,
the problem remains in the stock-fw too.
Will try to investigate further, but as I can't reproduce this on a regular
base, and - at least for my 650 - this isn't related to PRS+ it is hard to
track this down.
Original comment by Mark.N...@gentlemansclub.de
on 6 Nov 2012 at 7:54
Original comment by msukhias...@gmail.com
on 17 Dec 2012 at 1:39
Original issue reported on code.google.com by
hes...@gmail.com
on 22 Jul 2012 at 6:48