I installed the new Plucker (1.6.2) and it's a fine reader. I must tell you, however, that I can't find the dictionary lookup or how to get other than the pre-packaged fonts to work. (Is that in 1.7?) I tried to read a cyrillic text and could not.
Permit me, please, one comment. I think this product is distributed in an offputting way: when I install a reader with a converter, I want the two to work seamlessly. I am not a computer person and I will not start hunting for other converters, especially if there is no manual or other material to tell me what to look for and where.
You should know that I bought a T3, after using a Sony 615 for two years, mainly because of the larger screen. That I cannot use that with Plucker, whatever the reason, is a real downer.
Thanks again for your comments. Philippe Radley
Quote:
|
Originally Posted by hacker
Gestures, as in using graffiti strokes for navigation through the document itself.
Ok, so it isn't as seamless as it is in Plucker. In Plucker, you highlight the word, and tap Lookup, and it launches the dictionary and looks up the word. Exiting the dictionary returns you to Plucker. In our case, the AbsoltueWord people run their app in "registered" mode, if they find that it was launched via Plucker.
That must be new. I didn't think you could have the same exact content, multiple times, with the same names, in different categories, with iSilo.
No, actually it isn't. It isn't a "silly" correction at all. We don't ship JPluck. It is a completely separate, independant project, which just happens to include our viewer in the installer. JPluck is being moved to a proprietary model anyway, and the author is making his own viewer (proprietary also), largely because he wanted features that we didn't think were worthy of supporting in Plucker.
Yes, you absolutely must. Plucker Desktop is very different from JPluck, which is very different from pler, which is very different from FlingIt, which is very different from Sitescooper, which is very different from my own perl distiller code. They all output Plucker documents, but they all use very different languages and methods to do it.
If you have trouble doing conversions with one, don't blame Plucker, try a different tool. Knowing which tool you're using is important, because each one has its own positives and negatives.
See above. JPluck is not part of Plucker. It is not developed by anybody who develops Plucker. It is an independant, "third-party" package that produces Plucker documents as its current output format. Now that the development of JPluck is stopped, the author is moving onto his own proprietary viewer and desktop components.
As I said previously... use whatever works, just don't mislead people into believing things which can't be backed up with facts. If iSilo works for you, great, continue using it. I could care less what people use. I'm just trying to correct the misconceptions and untruths about the project I contribute a significant amount of my time supporting.
We're getting a lot of work now, custom work, from companies and businesses that used to use iSilo for their products, but are now moving to Plucker, because it is openly available, with source code, and is developed by a fast-moving team of people distributed across the globe. If one of us happens to get hit by a bus, the project still moves forward.
What happens if the iSilo author gets hit by a bus?
|