![]() In the end, if you have a routine set up for kiwix, you're probably best sticking with it. If you unzip it in the /xowa/ dir, it will automatically put all files into relevant folders For example, the XOWA wikiquote package is one zip file. You could always zip the files with relative paths, and instruct the users to unzip the zip. I had a reason for this layout, but it's causing confusion among a few users. Regarding your other point: I will probably centralize all the directories, instead of spreading them out between /wiki/, /file/, /user/. You would probably need imageMagick and inkscape installed though. In this scenario, you'd have all your files in some root directory (C:\images) and XOWA would index the directory and look-up the file by filename. Another user asked for this for his own private wiki. The other alternative is that XOWA should have the ability to read from a non-Wikimedia directory. If you have questions, feel free to ask / post. You can look at this thread for another user's attempts. XOWA allows the user to work directly with the WMF tarballs, so this should work for you as well. ![]() You can change the XOWA config file to explicitly specify this WMF layout. ![]() If you're using a MediaWiki installation, your files should be laid out similarly. These wikis have a standard file layout of wikipedia/wikidomain/thumb/hash0/hash01/name_of_file/thumbnail_file/ EX: wikipedia/commons/thumb/9/97/The_Earth_seen_from_Apollo_17.jpg/270px-The_Earth_seen_from_Apollo_17.jpg. To answer your question, yes: the image databases were prepared with expectations of a standard Wikimedia wiki. I just happened to check this thread and saw your response. The actual deployment is "copy zim files to this dir, then double-click on this script" There is one small deficiency in the kiwix deployment in that the automatic index files are user specific unless prepared in advance and recorded in the libary.xml file, so in practice I had to prepare a script to make sure the index and library were right. I just need to instruct the unskilled user to replace the ZIM file. Right now, kiwix deployment it is close to ideal. Overall, setting up one of the well known wikis is probably pretty smooth, but the private wiki requires a lot of technical knowledge about implementation details that make this tool impractical for unskilled users. The deployment needs to be completely offline becuase there is no Internet at the prison. Also, it would be impractical for me to manually crawl my whole site triggering downloads of images, and even if I did that, it is unclear how to package and deploy it. How would one prepare a similar image database for an unsupported wiki? I expect this is a custom thing you prepared as opposed to the xml text dump which is a standard mediawiki dump format.Īs to the imagemagik part, it doesn't work for an unsupported wiki. The filesystem layout was kinda confusing with the "user" and "wiki" separation. I tried tar'ing up my images directory from the server, and unpacking them in a few locations on the filesystem that looked like likely places, but that didn't work. I did see the things you mention regarding images, but the gap is that I'm exporting a private mediawiki, not one of the well known wikis that you have added explicit support for. I'm going off to work now, but I'll check again later.ĮDIT: I forgot to add that if you set up ImageMagick and Inkscape (installation instructions are on XOWA's Main_Page), you can download images dynamically for each article (i.e.: you don't need to download the entire image dump first) Let me know if you run into other issues. If you're on Windows and have C:\xowa as your folder, you should get a file called C:\xowa\file\\fsdb.main\3 as well as many othersĮnwiki is a little more difficult, but only in that it requires downloading more files. If you look at, then there should be two steps: There is some assembly acquired, but I tried to make the instructions as simple as possible. I'd like to think that though XOWA isn't as friendly UI wise, it offers a lot more power / options. Kiwix is definitely more polished in UI, especially as it has been around for 5 years. ![]()
0 Comments
Leave a Reply. |