Hi
I remark that it seems it makes a year a half that we don't have post
posted here news about Kiwix JS. It is a pity, because this is one of
our most active code repository!
On the top of this, we just have released version 3.3.1 of all Web
Browser extensions (Firefox, Chrome & Edge) and Kiwix JS for Windows.
You can find the latest version of Kiwix JS Browser extensions:
* Chrome:
https://chrome.google.com/webstore/detail/kiwix/donaljnlmapmngakoipdmehbfci…
* Firefox: https://addons.mozilla.org/en-US/firefox/addon/kiwix-offline/
* Edge:
https://microsoftedge.microsoft.com/addons/detail/kiwix/jlepddlenlljlnnhjin…
Here are the recent changelogs:
Kiwix-JS v3.3.0
* FIX: Improve packaging for the Ubuntu Touch app
* FEATURE: Provided a workaround to enable Service Worker mode in
Firefox extensions (via a PWA)
* NEW: App now defaults to Service Worker mode if accessed directly as a
PWA (does not apply to browser extensions)
* NEW: Support for non-http URLs in img and link tags (e.g. data:
javascript:) in JQuery mode
* NEW: Added helpful tooltips to icons and settings in the app
* FIX: Scrolling to anchor targets in JQuery mode
* FIX: Caching of ZIM assets now includes any required query string in
SW mode
* FIX: Any favicon declared by the ZIM is now extracted and attached in
JQuery mode
* BUGFIX: Incorrect processing of titles with question marks or hashes
prevented display of some articles
Kiwix-JS v3.2.0
* NEW: Support latest format of ZIM archives (with no namespace)
* NEW: Optimization of title search by eliminating redundancies
* NEW: Support new format of title listings (v1) in no-namespace ZIM
archives
* NEW: Use fast binary WASM decoders with fallback to ASM if necessary
* UPDATE: Clearer and more extensive documentation for end users in About
* BUGFIX: Issue with calculation for selection of random articles
Kiwix-JS v3.1.0
* NEW: Low-level block cache significantly improves binary search speed,
and can speed up resource loading in most browsers
* NEW: Archives with WebP-encoded images are now decoded in legacy
browsers via a polyfill
* UPDATE: Images are now extracted sequentially in jQuery mode from the
top of the DOM
* BUGFIX: Running binary searches are now cancelled completely if user
enters new search term or navigates away
The full Changelog can be found here:
https://github.com/kiwix/kiwix-js/blob/master/CHANGELOG.md
We have already started to release ZIM files "without namesapces" and
this version 3.2.0+ is mandatory if you want to enjoy them with Kiwix JS.
All our Windows apps based on Kiwix JS have been updated in Microsoft
App Store too. You can enjoy our apps on all Windows
based devices (mobiles, tablets, PC, Xbox, ...):
* Wikivoyage:
https://www.microsoft.com/fr-ch/p/wikivoyage-by-kiwix/9n5sb90q4jbj
* Wikimed: https://www.microsoft.com/fr-ch/p/wikimed/9phjsnp1cz8j
* Kiwix: https://www.microsoft.com/fr-ch/p/kiwix-js/9p8slz4j979j
Please report any problem. Work continues on our forge at
https://github.com/kiwix/kiwix-js and
https://github.com/kiwix/kiwix-js-windows.
Regards
Emmanuel
--
Kiwix - Wikipedia Offline & more
* Web: http://www.kiwix.org
* Twitter: https://twitter.com/KiwixOffline
* more: http://www.kiwix.org/wiki/Communication
Dear WOW, there is an ongoing discussion on Meta about how affiliates
should participate in board elections.
---------- Forwarded message ---------
Please follow this link to make proposals and discuss these questions
<https://meta.m.wikimedia.org/wiki/Wikimedia_Foundation_Board_of_Trustees/Ca…>
:
1. How can we ensure diverse representation among elected candidates?
The Board of Trustees noted the importance of selecting candidates who
represent the full diversity of the Wikimedia movement.
2. What are the expectations for the candidates during the elections?
Board candidates have traditionally completed applications and answered
community questions. How else might we get insight into candidates?
3. How should affiliates participate in the elections?
Two seats of the Board of Trustees due to be filled this year were last
filled in 2019 through the Affiliate-selected Board seats process. A change
in the Bylaws removed the distinction between community and affiliate seats
<https://foundation.wikimedia.org/w/index.php?title=Bylaws&type=revision&dif…>.
How should affiliates be involved in the selection of new seats?
The Board is seeking feedback about this last question especially from the
affiliate community. Everyone is invited to share proposals and join the
conversation.
Hi,
We have released the first minor release of libzim7 branch: libzim 7.1.0.
Nothing really big, here is the changelog:
* Fix dirent test on 32 bits architectures (@mgautierfr #632)
* Fix compilation on Alpine - with musl (@amirouche #649)
* Don't crash if ZIM without illustration nor X/W namespace
(@mgautierfr #641)
* Switch default suggestion operator to AND (@maneeshpm #644)
* Add a new method Archive::getMetadataItem (@mgautierfr #639)
* Better indexion criterias (@mgautierfr #642)
* Avoid duplicated archives in the searcher (@veloman-yunkan #648)
* Fix random entry (@veloman-yunkan #650)
* Various improvements.
- CI @mgautierfr #640, @kelson42 #638, @legoktm #654
- Doc @rgaudin #646
A new Python-libzim using it will be released soon and we are still
working on the libzim7 Node.js binding.
A small minor release 7.2.0 is already in the pipe and should be
released next week.
More info at: https://github.com/openzim/libzim
For the Kiwix team
Kelson
--
Kiwix - Wikipedia Offline & more
* Web: https://kiwix.org/
* Twitter: https://twitter.com/KiwixOffline
* Wiki: https://wiki.kiwix.org/
Hi,
After announcing the libzim7 release a month ago, we are proud to
release the version 3.0.0 of the Zim-tools. The Zim-tools is the
swiss-knife for manipulating ZIM files.
Actually this release has been made available already a few weeks ago
and here again this is major release. It makes almost a year we have
been working on this new release which mainly brings support of libzim7
and major improvements to the zimcheck tool.
Here is the complete changelog:
* zimwriterfs: Do not allow zimwriterfs to overwrite a existing zim
file (@asashnov #193)
* zimcheck: Make zimcheck print json output with option `--json`
(@veloman-yunkan #206)
* zimcheck: Make zimcheck multithreaded (@veloman-yunkan #194)
* zimcheck: Add an option to check for redirection loops (@shashwat1002
#218)
* zimrecreate: Add an option `-j` to not create fulltext index
(@data-man #234)
* zimrecreate: Add option `-J` (--threads) to set the number of threads
to use (@data-man #235)
* remove zstd compression options. We are now always creating zim file
with zstd (@kelson42 #261, 264)
* zimwriterfs: Do not use the extension of file as mimetype (@mgautier
#265)
* zimcheck: Improve performance of detection of the kind of url
(@veloman-yunkan #179)
* Support new protocols xmpp, news and urn (@kelson42 #205)
* zimdump: zimdump now print the favicon and mainentry path instead of
the index (@kelson42 #220)
* zimdump: Add a option to create html redirect insteal of symlink
* zimdump: Fix issue where zimdump crash depending of the stored path
of redirection (@maneesh #211)
* zimdump: Fix argument --ns not working (@maneesh #216)
* Add zimcheck unit tests (@veloman-yunkan #215)
* zimdump: Fix http redirect (@veloman-yunkan #225)
* Adapt zim tools to new libzim api (@mgautier @veloman-yunkan @maneesh)
* Compile zimsearch binary only if libzim is compiled with xapian
(@mgautier, #201)
* Docker : Better open zimtools image (@rgaudin #209)
This new release is an important milestone in our global QA effort
around ZIM files. Latest Zimcheck has been already integrated in our
Zimfarm and its new machine readable output can now be checked in our
(currently being build) CMS.
From a more general point of view, improving the Zim-tools is essential
to allow hackers to easily deal with the ZIM files and maybe even
produce their own. More infos at https://github.com/openzim/zim-tools.
Happy coding!
Kelson
--
Kiwix - Wikipedia Offline & more
* Web: https://kiwix.org/
* Twitter: https://twitter.com/KiwixOffline
* Wiki: https://wiki.kiwix.org/
Dear offline community,
We've been remiss in keeping the Wikipedia 1.0 Editorial Team page (WP1) up to date on the English Wikipedia:
https://en.wikipedia.org/wiki/Wikipedia:Version_1.0_Editorial_Team
This is not too surprising, because most of the work nowadays is done in Github or at Kiwix, and WP1 is much more automated. But this rather small group is still the one that coordinates all the collation of assessment data on the English Wikipedia, and writing the new bot over the last couple of years has involved writing 15,000 lines of new code (by people much smarter than me).
There is now a vote to delete or make the main WP1 page "historical":
https://en.wikipedia.org/wiki/Wikipedia:Miscellany_for_deletion/Wikipedia_1…
Please feel free to share your opinions there.
Thanks,
[[User:Walkerma]]
Prof. Martin A. Walker
Chair, Dept. of Chemistry
SUNY Potsdam
Potsdam, NY 13676 USA
+1 315 2672271
walkerma(a)potsdam.edu
ORCID: 0000-0001-9202-0356
Hi,
After announcing the libzim7 release a few days ago, we are proud to
release the version 1.0.0 of Python-libzim. Python-libzim is our Python
binding for the libzim and the version 1.0.0 supports fully the libzim7.
Here is the complete changelog:
* [breaking] Uses new libzim 7-based API for both reader and writer
* No more namespaces
* Defaulting to zstd compression
* Python 3.9 support
* Uses libzim's own test ZIM files to test reader
* Code-coverage now includes Cython code as well
* macOS releases are signed and notarized
* Early-failure on invalid destination ZIM path
The Python-libzim is a pretty recent software library which has been
launched in 2020 and allows easily any (Linux/macOS) Python developer to
read and write ZIM files. You can easily install it with "pip", more
details at: https://pypi.org/project/libzim/
Almost all our openZIM scrapers (but not the Mediawiki one) are written
in Python and many of them rely already on the Python-libzim. If you are
a Python expert or beginner, your help is welcome to improve it... or
relying scrapers. Here is where to start:
https://github.com/openzim/python-libzim.
Happy coding!
Kelson
--
Kiwix - Wikipedia Offline & more
* Web: https://kiwix.org/
* Twitter: https://twitter.com/KiwixOffline
* Wiki: https://wiki.kiwix.org/
Hmmmm
Dear friends
Sj and I have received this information from Mervat, related to the
voting of selectors for the Movement Charter Drafting Committee
affiliate selectors group. This is an important step in the selection of
Drafting Charter Committee Members. As a result of the elections, 15
committee members will be elected and tasked with writing the Mouvement
Charter, which will in particular establish the roles and
responsibilites of the future Global Council for mouvement governance.
At this stage, I must say that despite the title of this email, it looks
generally as a rather complicated process to me
We were also offered that visual to better understand what's going on
here...
https://upload.wikimedia.org/wikipedia/commons/a/ac/Wikimedia_Movement_Char…
Step 1 is "ok". We were listed in the "Thematic Group" of voters. Which
seems perfectly suitable. There are 8 geographical regions and 1
thematic group. The next step is currently being discussed amongst
Affiliates representants. The formely approved process is that all
Affiliates should meet according to their "region/thematic" and agree to
vote on a Selector. The Selector will in turn cast the vote. The current
proposition is to "shunt" the Selector here, and have Affiliates vote
within their group, and let the vote decide of the people selected by
the group. I will follow up on that ... ermmm... very administrative
issue... and will have a talk with Sj to make sure we cast the Affiliate
vote (be it directly, or through a Selector).
This being said, I wanted to share with you the complete list of
candidates and invite you to have a look. If you have private comments
about the candidates (big opposition or big support), please write to Sj
and I privately about it
https://meta.wikimedia.org/wiki/Movement_Charter/Drafting_Committee/Candida…
Florence
-------- Message transféré --------
Sujet : Clear steps for setting up Movement Charter Drafting Committee
selection group
Date : Fri, 24 Sep 2021 13:52:11 +0300
De : Mervat Salman <msalman-ctr(a)wikimedia.org>
Pour : meta.sj(a)gmail.com, Florence Devouard <anthere(a)anthere.org>
Dear Wikimedians for Offline Wikis representatives,
I am following up on the long email we sent to you last week regarding
the setup process of the Movement Charter Drafting Committee affiliate
selectors group. We are following up with a quick step-by-step summary
to make the request more clear:
*
Step 1 - We are using a regional approach. Verify that your
affiliate appears in the right region in the list
<https://meta.wikimedia.org/wiki/Movement_Charter/Affiliates_by_Region>.
If yes, no action needed. If not, please correct it.
*
Step 2 - All affiliates in the region will nominate 1 selector for
the whole region. Arrange an online meeting, social media
conversation or wiki page to decide the process for your region.
*
Step 3 - Run the process of selecting the selector.
*
Step 4 - Notify the Movement Strategy and Governance team of the
outcome, so we can set up and convene the group of selectors.
*
These steps should be completed by October 10, 2021.
*
Movement Strategy and Governance team is readily available to
support or facilitate any regional discussions at any of the
described steps.
The Movement Strategy and Governance team will be available to answer
any questions or specifications you may have regarding this.
Looking forward to hearing from you!
*
*
*Mervat Salman (She/Her)*
Movement Strategy and Governance Facilitator
wikimediafoundation.org <https://wikimediafoundation.org/>
