osdir.com
mailing list archive F.A.Q. -since 2001!



Subject: cuecat readers and 2.6.x kernel - msg#00038

List: gnome.apps.alexandria

Mail Archive Navigation:
by Date: Prev Next Date Index by Thread: Prev Next Thread Index

Alexandria is very good. Now I want to purchase a cuecat barcode reader
just to use it with alexandria to read ISBN. I'm running alexandria on
Ubuntu, kernel il 2.6 series. I read somewhere that cuecat in alexandria
works only with kernel of 2.4 series... Is this true?


Thread at a glance:

Previous Message by Date:

Re: ISBN number - errant?

Hi, On 1/8/06, Rolf Marvin Bøe Lindgren <roffe-tNfNCQ8KSmuI6WJCb1EQGw@xxxxxxxxxxxxxxxx> wrote: > "Lissa" <qibhom-EnPF47/3+YSD9iCl+R0B7w@xxxxxxxxxxxxxxxx> writes: > > > google is not a valid search source for this kind of thing. A library > > catalog > > would be. You are getting it from the verso, not from the cover? Misprints > > are > > more common on the cover. > > I follow the very simple algorithm that I do the cover one first; if > that fails to validate, I look in the colophon, then I attemt Google. > > the ISBN in question is printed on the cover and nowhere else in the > book. Since some of Alexandria's sources allow such invalid ISBN > numbers, then the user should be able to override validation. > So just to clarify, here is the actual behavior: 1/ When adding books from the Internet (using the regular search dialog), when books providers return an invalid ISBN we ask the user to either reject the book or keep it anyway but with a blank ISBN. 2/ When editing the properties of a book (or adding a new book manually), you _must_ provide a valid ISBN, otherwise you can leave the field blank. But if you enter something on it, this must validate. I don't think this behavior is wrong. The user might be interested about invalid ISBNs, and I do not see why we would keep an invalid one in his/her database. But we can alter this behavior if it's really frustrating for users. Laurent

Next Message by Date:

Alexandria just crashed

bash-2.05b$ alexandria ----------------------- Alexandria just crashed ----------------------- Timestamp: Tue Dec 20 16:08:18 PYST 2005 Message: wrong number of arguments (1 for 2) Backtrace: /usr/lib/ruby/site_ruby/1.8/alexandria/ui/main_app.rb:528:in `move' /usr/lib/ruby/site_ruby/1.8/alexandria/ui/main_app.rb:528:in `restore_preferences' /usr/lib/ruby/site_ruby/1.8/alexandria/ui/main_app.rb:81:in `initialize' /usr/lib/ruby/site_ruby/1.8/alexandria/ui.rb:40:in `main' /usr/lib/ruby/site_ruby/1.8/alexandria.rb:60:in `main' /usr/bin/alexandria:10 Release: 0.5.1 Uname -a: Linux onizuka-sensei 2.6.8.1 #20 Fri Jun 17 12:02:05 PYT 2005 i686 Mobile Intel(R) Celeron(R) CPU 2.40GHz GenuineIntel GNU/Linux -- Please report this dump to 'alexandria-list-GrnCvJ7WPxnNLxjTenLetw@xxxxxxxxxxxxxxxx' with some additional information, such as the description of the crash and the steps to reproduce it (if it's possible).

Previous Message by Thread:

ISBN number - errant?

I have a book sporting the ISBN number 140212124. I can find the book by that ISBN number on Google. however Alexandria refuses to acknowledge it. bug? -- Rolf Lindgren http://www.roffe.com/ roffe-tNfNCQ8KSmuI6WJCb1EQGw@xxxxxxxxxxxxxxxx http://www.dignus.no/

Next Message by Thread:

Alexandria just crashed

bash-2.05b$ alexandria ----------------------- Alexandria just crashed ----------------------- Timestamp: Tue Dec 20 16:08:18 PYST 2005 Message: wrong number of arguments (1 for 2) Backtrace: /usr/lib/ruby/site_ruby/1.8/alexandria/ui/main_app.rb:528:in `move' /usr/lib/ruby/site_ruby/1.8/alexandria/ui/main_app.rb:528:in `restore_preferences' /usr/lib/ruby/site_ruby/1.8/alexandria/ui/main_app.rb:81:in `initialize' /usr/lib/ruby/site_ruby/1.8/alexandria/ui.rb:40:in `main' /usr/lib/ruby/site_ruby/1.8/alexandria.rb:60:in `main' /usr/bin/alexandria:10 Release: 0.5.1 Uname -a: Linux onizuka-sensei 2.6.8.1 #20 Fri Jun 17 12:02:05 PYT 2005 i686 Mobile Intel(R) Celeron(R) CPU 2.40GHz GenuineIntel GNU/Linux -- Please report this dump to 'alexandria-list-GrnCvJ7WPxnNLxjTenLetw@xxxxxxxxxxxxxxxx' with some additional information, such as the description of the crash and the steps to reproduce it (if it's possible).
blog comments powered by Disqus

Home | News | Sitemap | FAQ | advertise | OSDir is an Inevitable website. GBiz is too!