Hi Emmanual,
Thanks for the message!
Kiwix-serve is able to serve any ZIM file: http://www.kiwix.org/wiki/Kiwix-serve
That's great!
'''Scenario 3: Use on tablets / phones.''' We would love to have a
We have Kiwix for Android which is able to open any ZIM file: https://play.google.com/store/apps/details?id=org.kiwix.kiwixmobile
Yes - I saw the post about the new version, and it's very exciting.
We want to develop a version for iOS, but for now there no concrete agenda: http://www.kiwix.org/wiki/IOS
This would of course be good to have, but for our scenarios it won't be needed, as iPhones/iPads are not very common in most places in Africa. Android devices are far more competitively priced, so if people have a smart phone or tablet, it's usually Android. (Though in some places Blackberry is still quite common.)
- '''Offline access:''' We'd love to have some advice how we can
We have a still in dev, but already working solution for ZIM incremental update. This should be available for users in a few months. But, as far as I can see, you mediawiki is not too big, so the ZIM file shouldn't be too big to.
Well, we have a lot of audio and video. Some of it (the audio/images/files) are wiki uploads, but the video is kept separately (and YouTube, and on our server, so that it can be mirrored for local use). Just the uploads, i.e. the 'w/images' directory, alone is 1.2GB at the moment, so it's pretty substantial. So we might want to 'side load' the video content, if that makes sense, and would definitely need incremental updates for 'w/images'. The wiki text is not massive: the number of articles is about 1,500.
The real problem is the ZIM file generation. The future solution based on Parsoid should allow you (and anyone if your wiki is public) to build easily a ZIM file of it. For now we need to fix things on Parsoid and Kiwix side before having a perfectly usable solution.
Ok, so the use of Parsoid also means that the html5 generated is used for the ZIM file, so any <div>s we put in (for boxes) will appear in the output?
We are using Widgets (e.g. for YouTube), so would this also work with Kiwix? (By embedding the video from YouTube, same as on our web site?)
But, if you achieve to get a dev instance of Parsoid working onr your wiki, I would be happy to try to build a ZIM file for you: https://www.mediawiki.org/wiki/Parsoid
That would be great - many thanks! I'll see what I can do in terms of getting Parsoid working. We're on a virtual server, that I don't have su rights for, but I'll see what I can do.
Many thanks, Bjoern
Hi Bjoern
Le 13/11/2013 14:03, Bjoern Hassler a écrit :
- '''Offline access:''' We'd love to have some advice how we can
We have a still in dev, but already working solution for ZIM incremental update. This should be available for users in a few months. But, as far as I can see, you mediawiki is not too big, so the ZIM file shouldn't be too big to.
Well, we have a lot of audio and video. Some of it (the audio/images/files) are wiki uploads, but the video is kept separately (and YouTube, and on our server, so that it can be mirrored for local use). Just the uploads, i.e. the 'w/images' directory, alone is 1.2GB at the moment, so it's pretty substantial. So we might want to 'side load' the video content, if that makes sense, and would definitely need incremental updates for 'w/images'. The wiki text is not massive: the number of articles is about 1,500.
Having "external" content is certainly something which makes everything more complicated. I never have worked on this "problem" before.
The real problem is the ZIM file generation. The future solution based on Parsoid should allow you (and anyone if your wiki is public) to build easily a ZIM file of it. For now we need to fix things on Parsoid and Kiwix side before having a perfectly usable solution.
Ok, so the use of Parsoid also means that the html5 generated is used for the ZIM file, so any <div>s we put in (for boxes) will appear in the output?
We are using Widgets (e.g. for YouTube), so would this also work with Kiwix? (By embedding the video from YouTube, same as on our web site?)
For now, there is no support for widgets. It's not a limitation of the format, but all what we do is duplicating a wiki, and widgets display content which are not part of it.
Emmanuel