The on-wiki version of this newsletter can be found here:
https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2025-07-26
--
"Wikipedia is an encyclopedia"
This Quarter, we are working on demonstrating functions that generate
sentences and fragments
<https://www.wikifunctions.org/wiki/Wikifunctions:Abstract_Wikipedia/2025_fr…>
in
several languages. This moves us up from noun phrases
<https://www.wikifunctions.org/wiki/Z22664> and other phrases that we had
before, to whole sentences. This is a considerable step towards creating
text for Abstract Wikipedia!
Today, we discuss here a first such example, a function that can generate
the following sentences:
- Bangla: উইকিপিডিয়া হলো বিশ্বকোষ
- English: Wikipedia is an encyclopedia.
- Spanish: Wikipedia es una enciclopedia.
- Turkish: Vikipedi bir ansiklopedi
You can just go to the Function article-less instantiating fragment
<https://www.wikifunctions.org/wiki/Z26039>, select Wikipedia
<https://www.wikidata.org/wiki/Q52> as the entity and encyclopaedia
<https://www.wikidata.org/wiki/Q5292> as the class, and select one of the
four languages above and see the result. You can also try other entities
and classes, and hope that it works, and plenty do, here are the results
for Nairobi <https://www.wikidata.org/wiki/Q3870> and city
<https://www.wikidata.org/wiki/Q515>:
- Bangla: নাইরোবি হলো নগর
- English: Nairobi is a city.
- Spanish: Nairobi es una ciudad.
- Turkish: Nairobi bir şehir
Play around, it is fun!
As of time of writing, only those four languages work. That’s because the
configuration <https://www.wikifunctions.org/wiki/Z26043> used here
currently only has Functions for those four languages. The actual functions
that are being called for the individual languages are here:
- Bangla <https://www.wikifunctions.org/wiki/Z26572>
- English <https://www.wikifunctions.org/wiki/Z26088>
- Spanish <https://www.wikifunctions.org/wiki/Z26337>
- Turkish <https://www.wikifunctions.org/wiki/Z26340>
All of these have Implementations which are compositions, and thus are
hopefully easy enough to understand and take as a blueprint on how to
implement it for more languages.
We are calling for the community to add Functions that create such
sentences in more languages! And then they can be added to the
configuration.
Here’s a suggestion on how to proceed – and you won’t need any programming
skills to do so:
1. Check if such a function in your language already exists. Here is a list
of per-language catalogues
<https://www.wikifunctions.org/wiki/Wikifunctions:Catalogue/Natural_language…>
.
2. If it doesn’t exist yet, create a new Function
<https://www.wikifunctions.org/w/index.php?title=Special:CreateObject&zid=Z8>
for
making a sentence for article-less instantiation in your language. It
should have two inputs of Type Wikidata item reference
<https://www.wikifunctions.org/wiki/Z6091>, one for the entity and one
for the class.
3. On the new Function, create tests. Choose an entity and a class, and
put in the expected sentence into the result validation.
4. Connect the newly created Test case with the Function you created.
5. Try to create an Implementation. Take those in the existing
languages as an example. It might well be that you will find that helper
tools would be useful at this point. That’s OK. Note these down, and either
try to create them yourself, or let other people know on
Wikifunctions:Suggest
a function
<https://www.wikifunctions.org/wiki/Wikifunctions:Suggest_a_function>.
We understand that these steps are fiddly and not very obvious, and we
would really like to get feedback on how far you got, and where you got
stuck. If you have any questions on how to use Wikifunctions to do so,
reach out and ask questions. We will take the feedback and try to improve
the system or even just the documentation, or offer more examples, to help
you proceed.
We are also aware that currently, if something goes wrong, it is a bit
difficult to figure out what exactly went wrong. Was a label missing on
Wikidata? Is there no function to generate that sentence in the given
language? Is there no lexeme given for the given class? We are also working
on how to improve our error system, so that we can give better feedback.
We are very excited to work together with you on this!
Two years of Wikifunctions
Today is the second anniversary of Wikifunctions!
We want to thank the community for joining us on this incredible journey!
Better than any birthday gift are the continuous contributions to
Wikifunctions, as the project grows and becomes increasingly more useful.
Wikifunctions offers more than 2700 Functions for numerous domains, and as
we are widening access to Wikidata data and introducing more types, we see
novel and interesting functions being created. We are excited to see what
the next year will bring in terms of expanding the catalog of functions!
We are looking forward to a truly transformative third year, full of
opportunities. Just to mention one thing: we plan to continue to roll out
to many more Wikimedia projects, bringing the capabilities of functions to
so many more places throughout the Wikimedia ecosystem. We are curious to
see how the Wiktionary communities and later the Wikipedias will pick up
the new possibilities Wikifunctions will bring to their projects.
In short, thank you! Thank you for two amazing years, and we are looking
forward to the future!
Recent Changes in the software
This week, we added a pair of wikitext parser functions: for showing the
label, and showing the label and description, of an Object on
Wikifunctions. The first parser function, #wikifunctionlabel, shows the
label of any known Object in any known language, falling back along the
language chain to English: {{#wikifunctionlabel:Z1004|en}} -> "French (Z1004
) <https://www.wikifunctions.org/wiki/Z1004>". The second,
#wikifunctionlabeldesc, also shows the description:
{{#wikifunctionlabeldesc:Z2|en}} -> "Persistent object (Z2): A Z1/Object
which is stored persistently on the Wikifunctions wiki.
<https://www.wikifunctions.org/wiki/Z2>". These were provided after the
community-maintained Lua script stopped working, and we rushed it out early
to fix the wiki as swiftly as possible, and the {{Z}}
<https://www.wikifunctions.org/wiki/Template:Z> and {{Z+}}
<https://www.wikifunctions.org/wiki/Template:Z+> templates were switched
over to using them. In our focus on fixing the wiki, we had no time to ask
the Wikifunctions community about what was wanted; if you think there are
missing features or other similar needed tools for the community, please
discuss them with the community and (once consensus is achieved) file a
Phabricator ticket.
In Quarterly work, we're working to make it possible to include references
to Wikidata entities like items and lexemes in embedded Wikifunctions calls
(T397403 <https://phabricator.wikimedia.org/T397403>). As part of this
work, this week we made it possible for the search API to offer Functions
using these as inputs (T398728 <https://phabricator.wikimedia.org/T398728>),
and adjusted the VisualEditor integration to give a search-and-select
interface when creating or editing embedded Function calls (T398730
<https://phabricator.wikimedia.org/T398730>).
The other, very minor, user-facing feature shipping this week is that we
tweaked the configuration for the CodeEditor to wrap long lines in the Ace
editor, to make them more readable.
In terms of fixes for the code, we landed a few. We landed a large re-work
of the way the front-end Vue code talks to Wikifunctions.org through the
Action API, adding an AbortController so that we can cleanly cancel calls
that are no longer needed (T391327
<https://phabricator.wikimedia.org/T391327>). We added an extra safety
check on user input around language, to avoid logging noise (T399755
<https://phabricator.wikimedia.org/T399755>). Finally, we adjusted the
expected whitespace output for the browser tests, fixing an error spotted
in the integration of the testing platform into GitLab development of the
back-end services, which is now complete (T394558
<https://phabricator.wikimedia.org/T394558>).
News in Types: Hijiri calendar month
Last week we invited you to suggest candidates for Wikidata-based
enumeration types, and you did, thanks!
Based on the proposal
<https://www.wikifunctions.org/wiki/Wikifunctions:Type_proposals/Hijri_calen…>
for
Hijiri calendar months, we create a type for it: Hijiri calendar month
<https://www.wikifunctions.org/wiki/Z26582>.
More proposals have been incoming, such as for Grammatical number (singular
/ plural)
<https://www.wikifunctions.org/wiki/Wikifunctions:Type_proposals/Grammatical…>,
and Chemical elements
<https://www.wikifunctions.org/wiki/Wikifunctions:Type_proposals/Chemical_el…>.
Looking forward to more proposals and discussion!
Fresh Functions weekly: 52 new Functions
This week we had 52 new functions. Here is a list of functions with
implementations and passing tests to get a taste of what functions have
been created. Thanks everybody for contributing!
- kleenean compare days of Roman year (Z26271)
<https://www.wikifunctions.org/wiki/Z26271>
- kleenean compare months (Z26280)
<https://www.wikifunctions.org/wiki/Z26280>
- kleenean compare days of month (Z26286)
<https://www.wikifunctions.org/wiki/Z26286>
- round float64 (ties to even) (Z26304)
<https://www.wikifunctions.org/wiki/Z26304>
- stress placement in Spanish (Z26328)
<https://www.wikifunctions.org/wiki/Z26328>
- Spanish article-less instantiating sentence (Z26337)
<https://www.wikifunctions.org/wiki/Z26337>
- Turkish instantiating sentence (Z26340)
<https://www.wikifunctions.org/wiki/Z26340>
- read Wikidata geo-coordinate (Z26344)
<https://www.wikifunctions.org/wiki/Z26344>
- Convert month number to Malayalam month name (Z26354)
<https://www.wikifunctions.org/wiki/Z26354>
- convert (m/f) grammatical genders to (m/f/n) (Z26364)
<https://www.wikifunctions.org/wiki/Z26364>
- is valid python datetime date? (Z26369)
<https://www.wikifunctions.org/wiki/Z26369>
- genitive case of wikidata lexeme (Z26379)
<https://www.wikifunctions.org/wiki/Z26379>
- time in 24-hour format with period as delimiter (Z26385)
<https://www.wikifunctions.org/wiki/Z26385>
- converge iteratively to fixed point (Z26394)
<https://www.wikifunctions.org/wiki/Z26394>
- accusative case of wikidata lexeme (Z26399)
<https://www.wikifunctions.org/wiki/Z26399>
- replace globe in Wikidata geo-coordinate (Z26410)
<https://www.wikifunctions.org/wiki/Z26410>
- remove first and last character (Z26414)
<https://www.wikifunctions.org/wiki/Z26414>
- calculate inflation (Z26424)
<https://www.wikifunctions.org/wiki/Z26424>
- UK CPI per year (Z26428) <https://www.wikifunctions.org/wiki/Z26428>
- read Gregorian date, Bangla (Z26432)
<https://www.wikifunctions.org/wiki/Z26432>
- get Function for country's CPI by year (Z26437)
<https://www.wikifunctions.org/wiki/Z26437>
- EU CPI per year (Z26444) <https://www.wikifunctions.org/wiki/Z26444>
- geohash string (Z26448) <https://www.wikifunctions.org/wiki/Z26448>
- hexadecimal number to rational number (Z26452)
<https://www.wikifunctions.org/wiki/Z26452>
- convert string according to type and language (Z26457)
<https://www.wikifunctions.org/wiki/Z26457>
- Wikidata geocoordinates compatible within error (Z26458)
<https://www.wikifunctions.org/wiki/Z26458>
- absolute value of difference of rationals (Z26463)
<https://www.wikifunctions.org/wiki/Z26463>
- is typed pair (Z26474) <https://www.wikifunctions.org/wiki/Z26474>
A complete list of all functions sorted by when they were created
<https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderb…>
is
available.
[Apologies for cross-posting]
Hello everyone,
The Fall 2025 MediaWiki Users & Developers Conference will be held on October 28-30th, and hosted by the TIB Leibniz Centre in Hanover, Germany. The conference location will be the Leibnizhaus Guest house<https://www.uni-hannover.de/en/universitaet/organisation/dezernate/technik/…>.
https://www.semantic-mediawiki.org/wiki/MediaWiki_Users_and_Developers_Conf…
Everyone is encouraged to attend, to meet and discuss MediaWiki-related topics relating to both the Wikimedia world and uses within companies, organizations, etc.
As the Program Chair, I would like to specifically encourage you all to consider giving a talk, on any topic related to MediaWiki usage, deployment or development, including the MediaWiki extension ecosystem (Wikibase, Semantic MediaWiki, etc). Talks can be given remotely, although priority will be given to in-person attendees if there's an overflow. To propose a talk for this conference, just fill out this form<https://www.semantic-mediawiki.org/wiki/Special:FormEdit/Talk?Talk%5BConfer…>.
Please submit your contributions until September 5, so we can start to announce an interesting program early!
Thank you, and I hope to see many of you in Hanover!
Lozana Rossenova,
on behalf of the whole conference organization team
--
Dr. Lozana Rossenova
Postdoc Researcher
Open Science Lab
TIB - Leibniz Information Centre for Science and Technology and University Library
Welfengarten 1 B // 30167 Hannover
lozana.rossenova(a)tib.eu<mailto:xxx.xxx@tib.eu>
www.tib.eu<http://www.tib.eu/>
ORCID: 0000-0002-5190-1867
TIB is a public-law foundation of the Federal State of Lower Saxony. In accordance with Section 1(1) of the "Gesetz über die Stiftung Technische Informationsbibliothek (TIB)" (TIBstiftG ND), its name is "Technische Informationsbibliothek (TIB)". TIB uses the terms "Leibniz Information Centre for Science and Technology" and "University Library" as additional designations.
The on-wiki version of this newsletter can be found here:
https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2025-07-04
--
Coverage of 1298
<https://www.wikifunctions.org/wiki/File:Tiles._Field_cross_and_star_pattern…>Iranian
tiles, created 1298
Many language editions of Wikipedia have articles about individual years –
usually a few thousand of them, covering the time from 500 BC to about 2030
AD. Many Wikipedias start earlier, and some Wikipedias go further into the
future.
We took a random year, 1298 AD, and took a look at how well covered that
year is in different language editions of Wikipedia. The idea here is to
assess not simply the number of articles in a language edition, but to go
beyond that and see how much knowledge the given article provides.
When I worked on the Croatian Wikipedia, one of the early things I did was
to write a Python bot that created the year articles for the Croatian
Wikipedia. This reduced the number of red links (*i.e.*, links that go to
an article that does not exist yet) considerably, and made it easy to start
collecting knowledge on those articles, and use the link structure for
building and maintaining the encyclopedia. I wouldn’t be surprised if, in
many languages, the year articles were also started by a single author,
creating 2500+ articles with a bot.
Any bot doing this would be able to provide some structural information
about the year – Was it a leap year? What century was it in? – but usually
not more than that. Back then, I would have had neither the idea nor the
means to use a bot to write more information about the year, such as
births, deaths, events, *etc.* Today, thanks to Wikidata, that would be far
more conceivable: today we can quite easily get a list of all people in
Wikidata who died in 1298 <https://w.wiki/EcWy>, sorted by the number of
sitelinks they have, and use that to create parts of the article.
These bot-created articles often remained untouched for a long time
afterwards.
<https://www.wikifunctions.org/wiki/File:Monast%C3%A8re_Royal_de_Santa_Mar%C…>Monastery
in Spain, built in 1298
The analysis here was manual. I aimed to be rather strict with regards to
the capabilities of Abstract Wikipedia, and generous regarding the
complexity of the content of the language editions. A full list of my
assessments can be found here
<https://www.wikifunctions.org/wiki/User:Denny/1298_assessments>. The
analysis was conducted on 8 April 2025.
At that point in time, there were 341 language editions of Wikipedia. An
article for the year 1298 was available in 131 languages, and was entirely
missing from 208 languages. 2 language editions had redirects to the
relevant century instead of an article for the given year. This means that
those communities can potentially fill gaps by using Abstract Wikipedia in
61% of languages, and more than double the number of languages in which the
article for the year 1298 is available, with the simple creation of a
single function (the introduction to year function for the respective
language, as discussed in a previous newsletter
<https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2024-12-19>
).
In 65 languages, the article consisted of a simple skeleton for that year,
with no further information, likely created by a bot and not touched by a
human hand since. Many of these skeleton year articles were even more bare
than the basic introduction to year function would provide. Once Abstract
Wikipedia is launched in these languages, these articles would be possible
candidates for deletion, as it is likely that Abstract Wikipedia will very
quickly improve those articles compared to the current situation.
Now it starts to get interesting: in 28 languages, we don’t only have the
skeleton, but also a list of some births, deaths, and very simple events
(as far as I was able to tell). These all looked like they could very
easily be covered in Abstract Wikipedia, and most of these would also
benefit from being sourced from Abstract Wikipedia. This means that we
expect that 89% of Wikipedias would immediately benefit from Abstract
Wikipedia.
By the way, one of the interesting things to find was that the Thai
Wikipedia covers the concept of the Western year 1298 with the mostly
overlapping year พ.ศ. 1841
<https://th.wikipedia.org/wiki/%E0%B8%9E.%E0%B8%A8._1841> in the Thai solar
calendar <https://en.wikipedia.org/wiki/Thai_solar_calendar> – a great
example of cultural differences influencing the structure of a
multi-lingual encyclopedia. In Abstract Wikipedia, we are going to great
lengths to ensure that this remains possible in the future.
<https://www.wikifunctions.org/wiki/File:Jianzhen.jpg>Drawing from a
Japanese scroll, created 1298
Which leaves us with 38 languages, where the articles describe complex
events, or may even offer a worthwhile article, covering the trends and
changes in that year. The content of these articles will take quite a bit
more work than anything mentioned above to really be captured in Abstract
Wikipedia. I want to positively call out the articles in Slovenian and
Ukrainian for their narrative content. Yet, it is likely that some of these
articles will still benefit from being replaced or augmented by the
Abstract Wikipedia version.
Here is one big advantage of the Abstract Wikipedia model compared to the
current situation, based on my experience with the Croatian Wikipedia: if
the articles are created in a one-off by bots, written by a contributor and
run on their machine, it becomes quite difficult for the community to
maintain proper ownership of the outcome, especially later on. In small
communities, the expertise to write, adapt, and run such bots might not be
readily available. So if someone runs a bot for thousands of articles they
take over an outsized responsibility for large swaths of content on the
given Wikipedia.
That will change with Abstract Wikipedia, because the mechanisms creating
the content are on wikis themselves, they can be collaboratively
maintained, and improvements will roll out to the respective Wikipedias –
and owned by the community together. Also, some simple mistakes will
hopefully be less likely, such as copy and paste errors leading to wrong
Roman numerals, the wrong instantiation of a template, or errors in the
template.
Recent Changes in the software
We landed the last expected part of the proof-of-concept work on rich text
(HTML) output support from embedded Function calls, handling the output by
passing it through MediaWiki's HTML sanitisation code to ensure it is safe
to insert into the content page (T391983
<https://phabricator.wikimedia.org/T391983> and T391984
<https://phabricator.wikimedia.org/T391984>). We will demonstrate it
working shortly.
We adjusted our code that runs when an Object is deleted, which ensures the
Object is dropped from any caches, to also disconnect on-wiki the deleted
Object from any other Objects when it was an approved Implementation or
Test case (T392160 <https://phabricator.wikimedia.org/T392160> and T383502
<https://phabricator.wikimedia.org/T383502>).
We have fixed the Function Evaluator component to properly re-initialise
its status when switching what Function is being used (T395119
<https://phabricator.wikimedia.org/T395119>). We also fixed a recent bug in
that component that meant that Functions which have a Typed list as an
input parameter would crash the UX (T397682
<https://phabricator.wikimedia.org/T397682>). We fixed the code that shows
an Object as a simple string to not show 'undefined' as a tooltip in some
circumstances.
As part of our work to better monitor how well the system is behaving and
performing, we've switched the middleware code around to pass on non-HTTP
200 responses from the back-end services, rather than immediately error.
This will allow us to more correctly return HTTP 400s when user input is at
fault, and more importantly HTTP 500s when the service is breaking in some
way, so we can spot and fix it faster (T393522
<https://phabricator.wikimedia.org/T393522>). We also adjusted the logging
to a lower alert level when we get an HTTP 400 from the back-end.
We extended our LoadJsonDump maintenance script to let us import a range of
Objects rather than the whole database, for faster local debugging based on
production data. Now that all MediaWiki code requires PHP 8.1 or later, we
started gently switching our code to not declare catch variable names that
we don't use. We also stopped catching Throwable instead of Exception for
user-response-level issues where that's not appropriate.
We, along with all Wikimedia-deployed code, are now using the latest
version of the Codex UX library, v2.2.0, as of this week. We believe that
there should be no user-visible changes on Wikifunctions, so please comment
on the Project chat or file a Phabricator task if you spot an issue.
Volunteer’s Corner on Monday
On Monday, 7 July 2025, at 17:30 UTC
<https://zonestamp.toolforge.org/1751909400>, we will have our monthly
Volunteers’ Corner. Unless you have many questions, we will follow our
usual agenda, of giving updates on the upcoming plans and recent
activities, having plenty of time and space for your questions, and
building a Function together. Looking forward to seeing you online
<https://meet.google.com/xuy-njxh-rkw> on Monday!
Fresh Functions weekly: 47 new Functions
This week we had 47 new functions. Here is a list of functions with
implementations and passing tests to get a taste of what functions have
been created. Thanks everybody for contributing!
- Default display of Wikidata geo-coordinate (Z25629)
<https://www.wikifunctions.org/view/en/Z25629>
- rational as formatted decimal (comma separators) (Z25636)
<https://www.wikifunctions.org/view/en/Z25636>
- rational as formatted decimal (nbsp separators) (Z25639)
<https://www.wikifunctions.org/view/en/Z25639>
- digits in denominator of rational (Z25642)
<https://www.wikifunctions.org/view/en/Z25642>
- decimal places from digits in decimal denominator (Z25647)
<https://www.wikifunctions.org/view/en/Z25647>
- display rational as formatted decimal inferring dp (Z25656)
<https://www.wikifunctions.org/view/en/Z25656>
- read Time of day, English (Z25683)
<https://www.wikifunctions.org/view/en/Z25683>
- time of day as HH:MM:SS string (Z25701)
<https://www.wikifunctions.org/view/en/Z25701>
- time as 12-hour clock with am/pm (Z25705)
<https://www.wikifunctions.org/view/en/Z25705>
- time of day from Wikidata datetime (Z25711)
<https://www.wikifunctions.org/view/en/Z25711>
- if function in list apply 2 arguments, else 1 (Z25714)
<https://www.wikifunctions.org/view/en/Z25714>
- display Wikidata datetime (Z25721)
<https://www.wikifunctions.org/view/en/Z25721>
- print Wikidata datetime, mul (Z25724)
<https://www.wikifunctions.org/view/en/Z25724>
- print Wikidata datetime, language independente (Z25730)
<https://www.wikifunctions.org/view/en/Z25730>
- invert grammatical gender (m/f) (Z25754)
<https://www.wikifunctions.org/view/en/Z25754>
- same Wikidata datetime (Z25758)
<https://www.wikifunctions.org/view/en/Z25758>
- Spanish personal pronoun (Z25763)
<https://www.wikifunctions.org/view/en/Z25763>
- day of the year (Z25768) <https://www.wikifunctions.org/view/en/Z25768>
- days until the end of the year (Z25775)
<https://www.wikifunctions.org/view/en/Z25775>
- read Wikidata quantity (Z25785)
<https://www.wikifunctions.org/view/en/Z25785>
- QID from unit symbol (Z25792)
<https://www.wikifunctions.org/view/en/Z25792>
- unit string from quantity string (Z25800)
<https://www.wikifunctions.org/view/en/Z25800>
- QID of unit from quantity string (Z25806)
<https://www.wikifunctions.org/view/en/Z25806>
- amount from string representing quantity (Z25812)
<https://www.wikifunctions.org/view/en/Z25812>
- same calendar year (Z25820)
<https://www.wikifunctions.org/view/en/Z25820>
- regular expression match with flags (Z25829)
<https://www.wikifunctions.org/view/en/Z25829>
- first regular expression match with flags (Z25833)
<https://www.wikifunctions.org/view/en/Z25833>
- lower bound from quantity string (Z25840)
<https://www.wikifunctions.org/view/en/Z25840>
- number of regular expression matches with flags (Z25847)
<https://www.wikifunctions.org/view/en/Z25847>
- nth regular expression match with flags (Z25853)
<https://www.wikifunctions.org/view/en/Z25853>
- upper bound from quantity string (Z25860)
<https://www.wikifunctions.org/view/en/Z25860>
- set denominator (Z25867) <https://www.wikifunctions.org/view/en/Z25867>
- latitude from Wikidata geo-coordinate (Z25880)
<https://www.wikifunctions.org/view/en/Z25880>
- longitude from Wikidata geo-coordinate (Z25883)
<https://www.wikifunctions.org/view/en/Z25883>
- precision from Wikidata geo-coordinate (Z25886)
<https://www.wikifunctions.org/view/en/Z25886>
- globe from Wikidata geo-coordinate (Z25889)
<https://www.wikifunctions.org/view/en/Z25889>
- first weekday of the month (Z25897)
<https://www.wikifunctions.org/view/en/Z25897>
- last weekday of the month (Z25901)
<https://www.wikifunctions.org/view/en/Z25901>
- n weeks later (Z25907) <https://www.wikifunctions.org/view/en/Z25907>
A complete list of all functions sorted by when they were created
<https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderb…>
is
available.
._Quartz_ceramic,_underglaze_and_luster_painting._Islamic_Art_Museum_(Museum_f%C3%BCr_Islamische_Kunst),_Berlin,_Germany.jpg){kind=link}
