Klaus Elsbernd

Remove Space after "(variant ...) "

web_archive.org missing in RecognizedDomains?

I assume, that ISFDB is running on Linux. Most all distributions I know are using Mariadb instead of MySQL (Oracle). Is there any reason, why you prefer MySQL? Nevertheless, upgrading to the current version is a good idea. Any notes about the differences between the regex?

I would easily agree with these points. Nevertheless, as far, as I know, it's svn update command, which enters the non-ASCII characters as the $Date data into the header of file. I'll change locale for the check out to en_US, if I use the command in the future. Rem.: But why should it not be allowed to use UTF-8 code into text-strings of the python code? SVN-Repository is based on UTF-8

Add Encoding of python source code files to comment lines.

I just scanned some changes in nightly and initially stumbled upon www.worldcat.org, which will be searched in notes (report 226) and in library.py. All references of HTTP-URLs of this sites will be moved to the HTTPS-port 443. Same for www.goodreads.com and others. I think I reported these. I then had a look at scripts/create_identifiers.sql, which creates a table identifiers and identifiers_sites. Within this file, references to https://www.amazon.com, https://iss.ndl.go.jp... and alike will be...

As I understand the DB (Records/Books) in ISFDB, you store data exactly,like they are used in the books (book title, author,...) This is marvelous. And I like that you're picky about those data. That means, there is no need for translation of those data in other languages. This is done by using transliterations/pseudonyms (alias...). My approach is much simpler. Translate only "Publisher", "Author", (Error-) Messages, Menus, Buttons and so on into other languages. That means, a book title like Vampires...

Yes, I meant the user-interface. But not different UIs for each language. Only a translation of the print-strings, which you have consolidated with ISFDBLink... functions. Well you know the complexity of the work to be done. I agree, that conversion to utf-8 at least would be needed. Indeed, it may be a task for itself. (Rem: I use utf-8 for the media-wiki 1.36. this has to be done too) Currently I have only three (possibly combined) ideas: Use strings entered in the ISFDBLink... as arguments (Record-id...