Wikifunctions:Project chat

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>Wikifunctions</sitename>
    <dbname>wikifunctionswiki</dbname>
    <base>https://www.wikifunctions.org/wiki/Wikifunctions:Main_Page</base>
    <generator>MediaWiki 1.45.0-wmf.4</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">Wikifunctions</namespace>
      <namespace key="5" case="first-letter">Wikifunctions talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="710" case="first-letter">TimedText</namespace>
      <namespace key="711" case="first-letter">TimedText talk</namespace>
      <namespace key="828" case="first-letter">Module</namespace>
      <namespace key="829" case="first-letter">Module talk</namespace>
      <namespace key="1198" case="first-letter">Translations</namespace>
      <namespace key="1199" case="first-letter">Translations talk</namespace>
    </namespaces>
  </siteinfo>
  <page>
    <title>Wikifunctions:Project chat</title>
    <ns>4</ns>
    <id>1184</id>
    <revision>
      <id>192203</id>
      <parentid>192039</parentid>
      <timestamp>2025-06-11T00:01:21Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* proposed Read and Display functions for Day of Roman Year */ new section</comment>
      <origin>192203</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="56743" sha1="pfrsqnfinj1t5t31l7edligmsxwdnkv" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>pfrsqnfinj1t5t31l7edligmsxwdnkv</sha1>
    </revision>
    <revision>
      <id>192205</id>
      <parentid>192203</parentid>
      <timestamp>2025-06-11T01:50:54Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* proposed Read and Display functions for Unicode code point */ {{Section resolved|1=~~~~}}</comment>
      <origin>192205</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="56840" sha1="byykryz8w4bmviy8mwdirldi8dkejqm" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>byykryz8w4bmviy8mwdirldi8dkejqm</sha1>
    </revision>
    <revision>
      <id>192206</id>
      <parentid>192205</parentid>
      <timestamp>2025-06-11T01:51:09Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Request for connecting implementations */ {{Section resolved|1=~~~~}}</comment>
      <origin>192206</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="56937" sha1="2rkb0souqh0yperop8pj0ti7ykk96v5" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>2rkb0souqh0yperop8pj0ti7ykk96v5</sha1>
    </revision>
    <revision>
      <id>192207</id>
      <parentid>192206</parentid>
      <timestamp>2025-06-11T01:51:46Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Just wonder, that fair use is allowed here or not? */ {{Section resolved|1=~~~~}}</comment>
      <origin>192207</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="57034" sha1="8s1o23w1chia51x47bdfc92qfo27rfq" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>8s1o23w1chia51x47bdfc92qfo27rfq</sha1>
    </revision>
    <revision>
      <id>192208</id>
      <parentid>192207</parentid>
      <timestamp>2025-06-11T01:52:21Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Taxon rank function(s) */ {{Section resolved|1=~~~~}}</comment>
      <origin>192208</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="57131" sha1="ojncrpkfpu3xmxquq3hm8hrzz3xu02l" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:52, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>ojncrpkfpu3xmxquq3hm8hrzz3xu02l</sha1>
    </revision>
    <revision>
      <id>192209</id>
      <parentid>192208</parentid>
      <timestamp>2025-06-11T01:56:04Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Smaller natural numbers */ {{Section resolved|1=~~~~}}</comment>
      <origin>192209</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="57228" sha1="e08rrjfb3hojhnuo4p1f5fod3xbccxu" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 11 June 2025 (UTC)}}

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:52, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>e08rrjfb3hojhnuo4p1f5fod3xbccxu</sha1>
    </revision>
    <revision>
      <id>192210</id>
      <parentid>192209</parentid>
      <timestamp>2025-06-11T01:57:42Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Internal server error in running a composition */ this bug is now resolved</comment>
      <origin>192210</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="57325" sha1="3cli07ckhd8h0i8jde6gy9wtuu98dpp" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:57, 11 June 2025 (UTC)}}

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 11 June 2025 (UTC)}}

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:52, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>3cli07ckhd8h0i8jde6gy9wtuu98dpp</sha1>
    </revision>
    <revision>
      <id>192211</id>
      <parentid>192210</parentid>
      <timestamp>2025-06-11T01:58:17Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Problems with a js implementation */ this bug is now resolved {{Section resolved|1=~~~~}}</comment>
      <origin>192211</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="57422" sha1="111nhz8typdvv08bh3y0j6ok06i5qmp" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:58, 11 June 2025 (UTC)}}

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:57, 11 June 2025 (UTC)}}

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 11 June 2025 (UTC)}}

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:52, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>111nhz8typdvv08bh3y0j6ok06i5qmp</sha1>
    </revision>
    <revision>
      <id>192213</id>
      <parentid>192211</parentid>
      <timestamp>2025-06-11T02:02:59Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* proposed Display function for Gregorian calendar month Type */ Reply</comment>
      <origin>192213</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="57544" sha1="6ito16ixg6gb06uemjyy1xsz3n7pxhi" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)
:::::It looks like this is now working again. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:02, 11 June 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:58, 11 June 2025 (UTC)}}

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:57, 11 June 2025 (UTC)}}

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 11 June 2025 (UTC)}}

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:52, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>6ito16ixg6gb06uemjyy1xsz3n7pxhi</sha1>
    </revision>
    <revision>
      <id>192214</id>
      <parentid>192213</parentid>
      <timestamp>2025-06-11T02:03:29Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* proposed Display functions for Day of the week Type */ {{Section resolved|1=~~~~}}</comment>
      <origin>192214</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="57641" sha1="ho6pb7fy7omn3y7pkevrk7v5fdpzr3l" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:03, 11 June 2025 (UTC)}}

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)
:::::It looks like this is now working again. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:02, 11 June 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:58, 11 June 2025 (UTC)}}

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:57, 11 June 2025 (UTC)}}

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 11 June 2025 (UTC)}}

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:52, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>ho6pb7fy7omn3y7pkevrk7v5fdpzr3l</sha1>
    </revision>
    <revision>
      <id>192216</id>
      <parentid>192214</parentid>
      <timestamp>2025-06-11T03:08:07Z</timestamp>
      <contributor>
        <username>SpBot</username>
        <id>978</id>
      </contributor>
      <minor />
      <comment>archive 1 section: 1 to [[Wikifunctions:Project chat/Archive/2025/05]] (after section [[Wikifunctions:Project chat/Archive/2025/05#Fold_and_reduce_swapped|Fold_and_reduce_swapped]]) - previous edit: [[:User:99of9|99of9]], 2025-06-11 02:03</comment>
      <origin>192216</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="56974" sha1="owr6eawol8jqexxghqqh6zrxd65uhmj" xml:space="preserve">{{shortcut|[[WF:CHAT]]}}
__NEWSECTIONLINK__
[[Category:Help]] &lt;!-- please do not remove this line --&gt;
Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:
* [[Wikifunctions:Administrators' noticeboard]]
* [[Wikifunctions:Report a technical problem]]
* [[Wikifunctions:FAQ]]

{{Autoarchive resolved section
 |age = 1
 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##))
 |timeout=30
}}
{{Archives|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1}}}}

== proposed Reader and Display functions for Byte Type ==

I suggest we use the following functions as a reader and display function for the Byte Type:
* {{Z|Z22866}}
* {{Z|Z22887}}
Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:40, 27 February 2025 (UTC)

:How do you feel about displaying in three or more formats: hex, binary, decimal and (maybe) octal? Something like “F1 (hex), 11110001 (binary), 241 (decimal), 361 (octal)” or “F1 [16], 11110001 [2], 241 [10], 361 [8]”? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:09, 2 March 2025 (UTC)
::They all seem too long IMO. Imagine how they would show up in rendered displays (e.g. on Tests). I agree that choosing a base has no right answer, but I think choosing any is still better than all. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 22:21, 2 March 2025 (UTC)
:::Ah, yes… you’re right, of course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:24, 2 March 2025 (UTC)
:Can we proceed with this one? In particular the reader will be useful to accept a wider range of inputs. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:31, 26 March 2025 (UTC)
::{{ping|DVrandecic (WMF)}} I know you've been busy, and am sorry to be pushy, but you asked for this [[Wikifunctions:Status_updates/2025-02-26|about 6 weeks ago]], and I tried to get it done the next day. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:32, 14 April 2025 (UTC)
:::@[[User:DVrandecic (WMF)|DVrandecic (WMF)]] @[[User:Denny|Denny]] ping again. The bot wants to archive this section. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:46, 16 May 2025 (UTC)
::::@[[User:99of9|99of9]] Thank you so much for your patience! The read and write function have been now set on [[Z80|Byte]] as per your proposal. Everyone, feel free to test it, I tried it a bit and it works like a charm! Thank you for all the work. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 09:33, 16 May 2025 (UTC)
:::::Thanks for clearing some important backlog. It's great to have you back. If you have more capacity, I sent a reminder of a few trickier backlogs for you via @[[User:Sannita (WMF)|Sannita (WMF)]] at [https://t.me/Wikifunctions/25377]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:56, 21 May 2025 (UTC)
::::::Hi @[[User:99of9|99of9]]! I checked with Sannita, and I am trying to find the other topics you listed. One is about [[Wikifunctions:Project chat/Archive/2024/06#Revisiting community %22maintainer%22 rights|connecting tests to built-ins]], and the other two seem about the converter for floating point numbers. I haven't caught up on the chat yet, is there a place I can read up on the floating point issues (besides going through the chat, which I will do some day)? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 14:46, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/24417 April 7th] “I've just been investigating Z21923 and am now confident that the float64 converters to code are not dealing with the special case of subnormal numbers. When the exponent is -1023 (just this specific value), the mantissa should not get the 1+ in line 47 of [[Z20875]]. Similar omission in the JS converter.
:::::::“Then in [[Z20885]] it looks like like 83 should not subtract the 0.5 for the specific case of the exp being -1023 (or actually -1022 at that stage, since it is decremented in the following line)” [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:30, 26 May 2025 (UTC)
::::::::Hi @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], yes, thanks @[[User:GrounderUK|GrounderUK]] that's all I wrote about #3. If you need more info let me know, but I learned most of what I know from wiki. Most relevant here is [[:w:Double-precision_floating-point_format#Exponent_encoding]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:12, 26 May 2025 (UTC)
:::::::[https://t.me/Wikifunctions/22480 February 2nd] is #4: &quot;I've realised that the question at the end of the [[Wikifunctions:Status_updates/2025-01-29|FOTW section]] I wrote is now more urgent. The question was &quot;Should special values return with their other (usually disregarded) keys matching the values of the sign, mantissa and exponent in the IEEE 754 binary representations?&quot;. It's now urgent because the type reader is now hardcoding the representation of the special values in every test that involves them (e.g. [[Z22081]]). Perhaps obviously by posing the question, I favour returning values for all keys that match how they appear in the binary representations.&quot; This received some concurrence, and I haven't seen anyone against it. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:15, 26 May 2025 (UTC)

== Numeric type : Real number ? ==

In order to allow π to be supported in my previously suggested cartesian/polar conversion function, I note that a 'real' type needed to be supported.  

A 'real'  differs from a rational in that it it can take any supportable numerical value. 

Obviously for Wikifunctions purposes a real has a floor and ceiling value for positive/negative infinity, and underflow infinity ( i.e too close to zero).  Can someone assist me on converting this into  a formal explanation?

I had this so for for real :
Constraint :  &lt;math&gt; \pm \left| (\infty &gt; x &gt; 0) \right| &lt;/math&gt;
Representation: &quot;[0-9]*\.[0-9](\E((\+|\-)|)[0-9]*|)&quot;
Pi would then be - 
Function Name: Pi
Function type: Constant value - Real.
Constraint : 3.141... Unless in abstract there's a different way to define it. 

Formal methods is not an area I thave that much experience with. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:37, 26 March 2025 (UTC)

:Defining a color for referenche elsehwere either as :
Representation:\#[0-9A-F]{6}. \* Hex String *\
Representaion: (\1\.\0|\0\.[1-9]+)\,{2}(\1\.\0|\0\.[1-9]+) \* 3 value float (0.0 &lt; n 1.0  *\
:We don’t have a [[Wikifunctions:Type proposals|Type proposal]] for Real numbers yet. We can support arbitrarily precise approximations for an irrational number as a [[Z19677]] and we already have a float64 approximation for [[Z20862]], but someone should propose a Real number type (or, perhaps, an Irrational number type) if they have a clear idea of how it might work. I’m rather drawn to the idea of a separate Irrational number type, without thinking it through… [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:28, 26 March 2025 (UTC)
::One way it could work is to reprensent (comptable) real numbers by fonctions that take a precision and returns a rational number. &lt;math&gt;\pi&lt;math&gt; would be internally implementations of algorithms / formulas that computes it up to some arbutrary precision.
::The arithmetic basic opération like addition would be higher order fonctions that takes real numbers as arguments and returns themselves a real number, so a function that takes a precision and returns a rational number that approximates the sum up to that precision. (A number of bits, or a number of decimals) [[User:TomT0m|TomT0m]] ([[User talk:TomT0m|talk]]) 12:35, 21 April 2025 (UTC)
:::I've started a little way down this track. A good example is {{Z|Z23902}}, but with a rational return. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:47, 25 April 2025 (UTC)
:::@[[User:Dv103|Dv103]] made another very nice example of this at {{Z|Z24505}}, which I hope we can use as a general model. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 15:03, 5 May 2025 (UTC)
:::If I understand the proposal right, the proposal is not to create a type for real numbers, but rather functions that return a real number with an argument for the precision in one of the existing types. Is that right? That seems to take us pretty far.
:::To the best of my knowledge -- but I am not a mathematician -- the answer to the question of how to create a type for real numbers isn't obvious yet. See also [https://chadnauseam.com/coding/random/calculator-app this thread] and [https://dl.acm.org/doi/pdf/10.1145/3385412.3386037 this paper].
:::Having said that, and re-reading the thread and skimming the paper, it would involve two new types:
:::# a number with a precision. Since we need that for the Wikidata quantity type anyway, we should probably have one such type that will also work for the Wikidata quantity type.
:::# the type as described in the paper for even more goodness.
:::Just a thought. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:39, 16 May 2025 (UTC)

== Using functions on main page ==

Now that functions can be used on wikitext pages on wikifunctions.org, I think it would be a good idea to use at least a few of these functions on the main page. Additionally, while we are at it, it would be a good idea to update the welcome section with current goings-on. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 16 April 2025 (UTC)

:Yes this is a good idea from my point of view. What functions do you want to publish there. I think for example a function to get difference between two dates would be interesting. Another thing is the information how many months Wikifunctions exists so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:07, 16 April 2025 (UTC)
:Although we can’t actually count the number of functions, I think we could replace the plaintext count with a function that formats the value of some Natural number object. Picking up on @[[User:Hogü-456|Hogü-456]]’s suggestion, we could have a Wikifunctions data object (a list destined to become a map), and select the required datum from there. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 17 April 2025 (UTC)
::Is it possible to count the number of functions with a script. At [[Special:ListObjectsByType]] I have not found the total number of functions as the count is not related to the total number of objects of the selected type and instead to the objects displayed. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 18 April 2025 (UTC)
:::Yes. I meant we can’t have a Wikifunctions function that counts them, but we could have a function that displays the count according to language and rounded appropriately. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:07, 18 April 2025 (UTC)
::@[[User:GrounderUK|GrounderUK]]: If you want us to provide a MediaWiki magic word that reports the number of Functions on the site, we can definitely build that — equivalent to &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 13:36, 24 April 2025 (UTC)
:::Yes, please! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:07, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]], @[[User:Feeglgeef|Feeglgeef]]: Patch written; will hopefully get it reviewed over the weekend and shipped next week, or maybe that thereafter. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:19, 25 April 2025 (UTC)
:::::Ah, yes… and just those counts is also not a problem. No need to reply to my previous comment. Thank you for this (and everything you do). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:45, 25 April 2025 (UTC)
::::::{{ping|99of9|Feeglgeef|GrounderUK|Hogü-456}} With apologies for the delay, this is now live – you can see entries in [[Special:Statistics]], and summon them in wikitext via:
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFOBJECTS}}&lt;/nowiki&gt;&lt;/code&gt;, the total number of Objects ({{NUMBEROFOBJECTS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Functions ({{NUMBEROFFUNCTIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFIMPLEMENTATIONS}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Implementations ({{NUMBEROFIMPLEMENTATIONS}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTESTCASES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Test cases ({{NUMBEROFTESTCASES}}),
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFTYPES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of Types ({{NUMBEROFTYPES}}), and
::::::* &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFLANGUAGES}}&lt;/nowiki&gt;&lt;/code&gt;, the number of (natural) languages ({{NUMBEROFLANGUAGES}}).
::::::Do we want to add these to [[Template:Main page]]? (Should this particular part of the conversation move to [[Wikifunctions talk:Main Page]]?) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:20, 13 May 2025 (UTC)
:::::::Number of Functions in the current manual spot please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:03, 14 May 2025 (UTC)
:::::::I have replaced our manual counter for the number of functions with &lt;nowiki&gt;{{NUMBEROFFUNCTIONS}}&lt;/nowiki&gt;. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 13:46, 14 May 2025 (UTC)
::::::::Thank you! --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 10:46, 16 May 2025 (UTC)
:::Should that be number of functions or number of functions excluding built-ins? The “…that anyone can edit” tag suggests the latter, but we could just deduct the (relatively stable) number of built-ins. Thanks for the offer… I think this is [[phab:T345477]] (or related). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:46, 24 April 2025 (UTC)
::::@[[User:GrounderUK|GrounderUK]]: Excluding pre-defined Objects is a real chore (and currently meaningless //e.g.// for Types or (natural) Languages, so for now I'm not offering it, but if really needed we can bear this in mind next time we re-build the DB table so it stores this information. Sorry to disappoint! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:20, 25 April 2025 (UTC)
:::::Not a problem. We were talking specifically about functions, though. A separate count per type is also not a problem, but a count of all objects on its own does not satisfy the specific use case. Thanks! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 25 April 2025 (UTC)
:::Yes please. Please also consider which other magic words can he used to supply us with contemporaneous data. Real data makes running functions much more interesting. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:04, 25 April 2025 (UTC)
::::@[[User:99of9|99of9]]: Perhaps something like &quot;this wiki has been running for {…} years, since opening on 2023-08-01&quot;, using [[Z20756|Z20756/age]]? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:22, 25 April 2025 (UTC)

== proposed Display functions for Day of the week Type ==

I suggest we use the following functions as a display function for the Day of the week Type:
*{{Z+|Z24041}}
Types without display functions [[Help:Using_Wikifunctions#Output_type_not_supported|aren't supported]] when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.
--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:35, 19 April 2025 (UTC)

:'''Support''' That function works pretty well, thanks for your contributions 99of9! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 12:43, 19 April 2025 (UTC)
::You're welcome. Though most of the credit for the hard work done on this one goes to {{User|GrounderUK}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:53, 19 April 2025 (UTC)
:I have no problem with the function, but I do have reservations about setting an unfortunate precedent by relying on labels. I think the “officially correct” approach would be to go from the Wikifunctions object to the corresponding Wikidata item and from there to the item’s lexeme and the appropriate form/representation. Failures are possible, of course, and we have two fallback routes to consider, according to the language. 
:First, for language varieties with a lot of overlap, like Australian English and (en) English, we should fall back to the more common variety. (Note that the function currently returns a blank for Australian English. I imagine that the general fallback for Australian English would be to British English before (en) English, with US-English as a last resort, but even this simple example leads us into treacherous waters.)
:Secondly, (also by language), whether we prefer labels to lexemes or a specific function, or (assuming defaults are excluded or handled when a specific function is the option) lexeme/label first then label/lexeme in specified language, or lexeme/label in any fallback language then label/lexeme in any fallback language… and then our default (fall-through) option.
:How might this work in practice? We could have a [[Z14294]] that would handle the second cases first. For example, English might be set to prefer labels whereas Italian might prefer lexemes (because « domenica » is feminine whereas other days are masculine, so we’d have « domenica prossima » (“next Sunday”) but « lunedì prossimo » (“next Monday”), per esempio). I guess we’d have separate functions for label then lexeme, lexeme only, lexeme then label, label only; the default function here might also be configured by language for a “native Wikifunctions” experience.
:However, configuration by language doesn’t allow the specified language to be switched (from “en-au” to “en”, for example). This suggests that language-switching should be handled separately in the configured functions. It might be a common function, but the sequence may differ according to whether you're looking for labels or lexemes. In any event, I suspect that &quot;language&quot; is better specified as a list, with an empty list defaulting to [[Z1360|&quot;mul&quot;]] (say) and falling through to the default specified in the configuration (or a &quot;mul&quot;-specific alternative). (And when I say “list”, I suppose it would have to be a string representation, for integration, so we might see something like “[Z60, &quot;dag&quot;, &quot;en&quot;, &quot;mul&quot;]”. I guess we can’t use a read or display function for a generic type, though, and perhaps that challenge is better considered under a separate heading.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:46, 20 April 2025 (UTC)
::Good thoughts. I think your proposed &quot;officially correct&quot; function would be worth writing (as would some of the variants you mention), and may indeed work even better for some languages. For language fallbacks, I think we can get separate functions to handle that without changing the input type of a display function. It will take some building, and will be more than a configuration by language, but I don't think it will be too much worse. Just as you were posting this, I was writing a crude language fallback map: {{Z|Z24097}} as a start! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:10, 20 April 2025 (UTC)
:::Update: I've now adjusted the implementations to use the general language fallback if variants (like en-au) come up empty. And the test {{Z|Z24105}} now passes (with a long runtime). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 20 April 2025 (UTC)
:::Perhaps “crude” is a little harsh… but switching between “nn” and “no” then falling back to “sv” or “en” (according to personal preference) is the sort of scenario we might contemplate. One step at at time, though… so long as we don’t trip over one another’s feet! (You have a free run today, as far as I’m concerned! When I get started, I’m more interested in pursuing the lexeme route, but I want graceful fallback from [[Z6830]] outwards, and that means the option to switch languages if no lexeme is found, and (logically) a list of properties to work through too. Although such searches may have less of a performance overhead than item labels, I guess we’d only be able to manage a couple if we want to be able to default to labels afterwards.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:16, 20 April 2025 (UTC)
::::I'm not aiming for personal preference, because in my understanding display functions will generally apply to all users of a uselang. So I'm just aiming for the best (configurable) outcome for every language. For now I'll stick within the label space rather than the lexemes, but I agree it would be good to have a robust lexeme path available too. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:27, 20 April 2025 (UTC)
:::::You’re probably right, but I’m ''speculating'' that a personal preference and a project default could/should/would look the same at the function level. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:25, 20 April 2025 (UTC)
::Althouh we obviously want as much progress on lexemes as possible, I've realised that I don't agree it is &quot;officially correct&quot; for display functions. These are rendered output of single day values in a language, not lexically correct parts of a sentence. I think the intent is almost exactly coincident with the intent of a Wikidata label. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:03, 21 April 2025 (UTC)
:::I take your point. Without [[phab:T366459]], the display function cannot display the Wikifunctions object label, and even assuming the counterfactual, I can see the sense in defaulting to the label for the corresponding Wikidata item. Presumably, this is how [[phab:T390558|“light-weight enumerations” (T390558)]] will operate, since there will be no persistent instances to which to attach labels. In any event, as I said before, “I have no problem with the function” and I am happy to withdraw my remark about the lexeme route being « “officially correct” ». (@[[User:DMartin (WMF)|DMartin (WMF)]] Any thoughts about displaying the string for a light-weight enumeration? Does the generic type get read and display functions?)
:::That having been said, the performance is a concern and I am getting a time-outs for Thursday in a language-fallback scenario like [[Z24106]]. I suggest we defer language-fallback until we can return multiple selected labels from a single visit to an item. I just used [[Z13436]] in [[Z24109]] to support [[Z24110]] but I think “label-list from item for language-list” will require a code implementation, in the absence of a [[phab: T390226|variadic filter function (T390226)]]. I’ll get started on that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:38, 21 April 2025 (UTC)
:::Update: I’ve created [[Z24118]], which seems to do the job. I’ve left it disconnected for now as I accidentally passed all the tests with my interim fallback. I think we can just plug in an additional function call for a single “general” language (like “en”) but we’d need to flatten the list if a function returns a list of languages (like my Scandinavian example). It all looks doable but it looks as though a simple variadic filter would not have done the job, downstream, because we need the results in language order (so that’s something else to think about). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:15, 21 April 2025 (UTC)
::::Nice. I've made a harder test {{Z|Z24143}}, but also squeezed {{Z|Z24097}} into your list, so now your new composition passes and is fast enough. Scandinavian hierarchies still to come. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:29, 22 April 2025 (UTC)
:::::I've added {{Z|Z24329}}, which I'm confident does everything we need, because it ultimately relies on the complete flexibility of hardcoding fallback chains for every language in {{Z|Z24310}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:06, 30 April 2025 (UTC)
:@[[User:DVrandecic (WMF)]] I think this is ready to go. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:10, 8 May 2025 (UTC)
::@[[User:99of9|99of9]] thank you for your patience and your ping, I added {{Z|Z24041}} as a display function to {{Z|Z17402}}. Thanks to @[[User:GrounderUK|GrounderUK]] for the work! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 07:37, 18 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:03, 11 June 2025 (UTC)}}

== proposed Display function for Gregorian calendar month Type ==

I suggest we use {{Z|Z24086}} as a display function for the {{Z|Z16098}} Type. Similar to [[#proposed Display functions for Day of the week Type]], this display function calls for a Wikidata label of the object, and has elaborate and flexible handling of fallback languages if the editing language variant does not have a corresponding Wikidata label.

Types without display functions aren't supported when called from Wikipedias, so IMO it is a priority that we continue to connect display functions.  --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:13, 30 April 2025 (UTC)

:@[[User:99of9|99of9]]: Thank you! Done so! Again, thank you for your patience and for shepherding this change. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 15:06, 18 May 2025 (UTC)
{{tracked|T394769}}
::For some reason now {{Z|Z24086}} doesn't work [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:45, 18 May 2025 (UTC)
:::Good pickup. I can't see anything wrong, and have tested the functions that the composition calls. Likely a bug? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:09, 19 May 2025 (UTC)
::::Weird. It worked yesterday when I was testing it out. I'll let the team know. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 11:27, 19 May 2025 (UTC)
:::::It looks like this is now working again. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:02, 11 June 2025 (UTC)

== Problems with a js implementation ==
{{tracked|T394663}}
The implementation [[Z24188]] doesn't work (it fails a testcase), and I have no idea why. Is it a Wikifunctions bug or am I doing something wrong? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 10:44, 2 May 2025 (UTC)

:I didn't see anything immediately wrong, and my attempt at [[Z24414]] also fails. There are a lot of issues with lists and timeout/errors at the moment, but it appears that my changes have triggered it to go into infinite running mode https://phabricator.wikimedia.org/T392905. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:13, 2 May 2025 (UTC)
::@[[User:Dv103|Dv103]] reported as [[:phab:T394663]] for investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:04, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:58, 11 June 2025 (UTC)}}

== Internal server error in running a composition ==

I'm getting internal server errors in all testcases for {{Z|Z24456}}. Any idea why?&lt;br&gt;
Also, is there some way to translate those oblique long Z-jsons you get as actual output into a way more human-readable form, like how normal objects are viewed on Wikifunctions? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 15:00, 3 May 2025 (UTC)

:It's a problem that arises in {{Z|Z13397}} (see testcase {{Z|Z24458}}). I don't know why. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:50, 3 May 2025 (UTC)
::I filed a bug [[:phab:T394664]] for further investigation. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:10, 19 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:57, 11 June 2025 (UTC)}}

== Smaller natural numbers ==

I want to use some number codes to represent an enum of 17 possible values. I find converting to and fro BigInt—the JS representation of the natural number type—bothersome, especially when 17 is the maximum number I need. Is there a representation of numbers that's analogous to an int8 or uint8?

Speaking of which, is there a list of types somewhere? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:06, 3 May 2025 (UTC)
: Diving into things more: Is really every single number on Wikifunctions represented by a String? Parsing everything from and to ints seems quite inefficient and precluding some optimization. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:32, 3 May 2025 (UTC)
::The simple answer is yes, since every type expands to values of other types, with only strings and references being the terminal types. The more complete answer in at [[Wikifunctions:Function model]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:34, 3 May 2025 (UTC)
::: That indeed explains how it is—that there are no canonical numbers. I've tried searching for why it is, though, and haven't found anything. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:11, 3 May 2025 (UTC)
::::It was done for simplification. If there are no built-in numbers, there are no built-in mathematics, and it can reduce the number of built-ins considerably. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:11, 19 May 2025 (UTC)
::::: You don't need to introduce built-in mathematics when introducing numbers either. There's like 2 built-in implementations for String functions. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
::::::Yes, good point. I really wanted to keep the number of built-in types low, that's the main reason. And even for numbers we had quite a few decisions to make, so I think it is good we did that in the open and together through a type proposal. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:57, 22 May 2025 (UTC)
:There is no int8 type. The complete list of types is at [https://www.wikifunctions.org/w/index.php?title=Special:ListObjectsByType/Z4]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 21:37, 3 May 2025 (UTC)
:: Ooh, lovely! Is there a way to bump the &quot;Wikifunctions pages&quot; section to the top of [[Special:SpecialPages]]? I decided to look under &quot;Lists of pages&quot; and couldn't find that. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 22:06, 3 May 2025 (UTC)
::There's {{Z|80}} for u8. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 23:19, 3 May 2025 (UTC)
::: Thanks. I've checked that before, though. It is exactly the same as natural number and using it here would be semantically confusing. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 01:32, 4 May 2025 (UTC)
:Enums should be represented as enums (e.g. such as [[Z16098]]) and not as numbers, ideally. Let me know what's blocking that. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:28, 19 May 2025 (UTC)
::I don't have the permissions to create types, so that's gonna take a long time if the (absence of) responses to [[Wikifunctions:Type proposals/Grapheme]] are anything to go by. Do you think I have a shot at getting functioneer? [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 17:03, 19 May 2025 (UTC)
:::Enums usually go pretty fast (unless we are waiting for the light-weight enumerations, some of the current proposals are blocked on that). Even as a functioneer, one doesn't have type creation rights, these are currently limited to staff (type creation is currently not a user-friendly process, we want to improve that before opening that up). Yes, I would assume you have a good chance at becoming functioneer. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 12:59, 22 May 2025 (UTC)
:::: Ah, makes sense. Thanks! [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 13:32, 22 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 11 June 2025 (UTC)}}

== Quick prototyping possible? ==

Generally, to see the output of a piece of code I'd like to write for Wikifunctions, I have to first create the function for it, then create an implementation, then connect that implementation if I want to see its output, even if it's not done. With compositions I can simply go to [[Special:RunFunction]] and test it there, but with code implementations there's not much I can do (to my knowledge, at least).

I've a relatively ambitious idea and I'd like to experiment with it before I try making a full-fledged function + implementation + tests for it. Is there any way I could do this in a way that doesn't require too much extraneous effort and ZObject creation? It's something that will require specific steps and I'd like to lay it out and test it before I fully commit to implementing it, but there doesn't seem to be an easy way for me to do that. &amp;mdash; [[User:Theki|rae&lt;sup&gt;5e&lt;/sup&gt;]] &amp;lt;[[User talk:Theki|talk]]&amp;gt; 16:59, 7 May 2025 (UTC)

:No, I think you have laid out most ways to do it for now. There is one small way that can improve it: the way I do it is that I usually create a small number of tests first, and then I can run and rerun the tests while coding the implementation before I publish the implementation. And then, only once the tests are good, I click on publish. Would that help a bit? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:15, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #201 is out: Abstract Wikipedia and the Wikimedia AI Strategy ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss how Abstract Wikipedia ties in with the newly announced WMF's strategy for AI, we talk about the Wikimedia Hackathon and our community meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:27, 10 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;
:This is an interesting update. I have thinked a bit about usage of AI for Abstract Wikipedia and I am not sure how well it will work for small language versions. As far as I unterstand it is necessary to have enough data to train a model. It is important to check a text if it makes sense and not just translate it or generating content in a language a person can not speak. Instead of having no article I also like boilerplate templates. So a text with gaps for variable content depending on the specific subject. For simple use cases it is possible to make suggestions without a huge LLM in the background and instead with simple decision trees. So I think it is necessary to improve the data in Wikidata and add more statements to items. Usually larger articles in Wikipedia have more contents at what is listed in statements in the related Wikidata item. For the definition and necessary for the translation of the boilerplate templates people who can speak the local language the an abstract text should be converted to are required. So far I miss interaction of people of small Wikipedia language versions in Wikifunctions and it seems to me like a theoretical discussion and I hope there is enough awareness about irregular cases. Languages are in parts not easy to generate automatically. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:25, 11 May 2025 (UTC)
:Why shouldn't the language model also translate (render) from the middle pane (abstract content) to readable prose?
:I uploaded a screenshot of the middle pane and fed it into Gemma 3, Google's latest open model, with the prompt:
::''Render the abstract knowledge representation displayed in the image into fluent expository Hebrew prose, suitable for an encyclopedia.''
:The result was:
::''.מרי קורי היא האדם היחיד שזכה בפרס נובל בשתי קטגוריות מדעיות שונות''
:Or, in English:
::''Marie Curie is the only person to have won the Nobel Prize in two different scientific categories.''
:This is achievable using open models ''today''. It will only get better as LLMs are trained on richer corpora, expanding their reach to a wider variety of human languages. Where will these capabilities be in a year, and where will Wikifunction's natural language generation capabilities be? [[User:ATDT|ATDT]] ([[User talk:ATDT|talk]]) 01:39, 12 May 2025 (UTC)
::Hi @[[User:ATDT|ATDT]], thanks for the question! There area a number of reasons:
::* this doesn't work well for many of our small languages, such as Dagbani. For the large languages it often works OK, but they are the ones that need it least.
::* there is no guarantee of the results being correct. This system could work with a &quot;let's generate and then have humans check the results&quot; approach, but the goal of Abstract Wikipedia is to be able to edit the abstract content and then publish immediately in all supported languages ''without'' having to check the output again.
::* if a generation is wrong, it is unclear how to fix it (unless we do it manually, but in that case we are at the same point as with just using machine translation right now).
::I would think that if we use a model for generating output, we'd always need a human in the loop who understands both the input and the output languages. And that's basically the 1:1 machine translation approach, not the Abstract Wikipedia approach, where we create with high fidelity the output in all participating languages without requiring a human in the loop in the generation step. --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:37, 19 May 2025 (UTC)

== Taxon rank function(s) ==

I understand that function suggestions usually go in [[:Wikifunctions:Suggest a function]], but I could use some feedback on this, especially since I'm unsure of what Wikifunctions is capable of currently...

I think it would be useful to have a function that, given a Wikidata item that is an instance of {{Q|Q427626}} (hereafter a taxon rank), e.g. {{Q|Q7432}}, {{Q|Q34740}}, {{Q|Q35409}}, etc., returns whether or not that taxon rank is situated at or below the rank of genus. That is, it would return true for genus, subgenus, species, subspecies, variety, and botany's series, subseries, section, and subsection, among a handful of other infraspecific ranks (or infrageneric ranks that I may be forgetting about). For efficiency, it may be worth it to hard-code a partial list of taxon ranks that are considered to be at the generic level or below, and as a fallback traverse the taxon rank hierarchy by looking at the values of {{Q|P361}}. Here's a pseudocode example.
 function genericRankOrLower(taxonRank) {
     const hardcodedGen = [
         'Qxxxxx', //species
         'Qxxxxx', //subgenus
         'Qxxxxx'  //genus
     ];
     const hardcodedNonGen = [
         'Qxxxxx', //family
         'Qxxxxx', //order
         'Qxxxxx', //class
         'Qxxxxx', //phylum
         'Qxxxxx'  //kingdom
     ];
     if (hardcodedGen.contains(taxonRank)) return true;
     if (hardcodedNonGen.contains(taxonRank)) return false; // want to avoid expensive long traversals
 
     let nextRank = WikidataLookup.GetFirst(item: taxonRank, property: P361);
     if (nextRank != null) return genericRankOrLower(nextRank);
     return false;
 }

This would be useful because the names of taxa at the genus rank and lower should be italicized, but the names of taxa above the genus rank should not; e.g. the taxon name {{Q|Q13612717}} may be written as ''Eristalis stipator'' or ''Eristalis (Eoseristalis) stipator'' (the subgenus, in parentheses, is optional), while the family name {{Q|Q217905}} is written as Syrphidae. Wikispecies and the English Wikipedia have something that can help somewhat with this, [[:species:Template:Taxon italics]]/[[:en:Template:Taxon italics]], which will correctly italicize a taxon name (including cases where there are unitalicized portions, such as &quot;var.&quot;). However, I don't believe they have a Wikidata-enabled template or module for determining if a taxon should be italicized.

In the actual use of this proposed function, there may need to be exceptions or special cases for e.g. viruses - I am unfamiliar with the italicization rules for virus names. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 20:02, 15 May 2025 (UTC)

:Sounds like a good function suggestion to me. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:34, 16 May 2025 (UTC)
::Thanks. I've added a suggestion at [[Wikifunctions:Suggest a function#Taxon functions]] - feel free to move it if necessary, as I'm not entirely sure where it fits best. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:30, 16 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:52, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #202 is out: Location of Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we invite you to our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:56, 16 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Just wonder, that fair use is allowed here or not? ==
Of course it doesn't seem allowed for files, as [[special:upload]] is disabled here, but how about functions or other text-like contents? Those may also be fair use-allowed on some certain projects (e.g. several Wikiquotes), [[m:Non-free_content#Other_projects]] only suggests &quot;A new developing project, lack of discussions on this matter yet&quot;. Any inputs? --[[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 01:12, 18 May 2025 (UTC)

:Code contributions are licensed under Apache 2.0, and any contributions must be compatible with that license. [https://lib.asu.edu/news/research/fair-use-code Fair use and code] are a complicated combination, that can be crucial in some cases (for example for header declarations), but I don't think that would cover whole function implementations copied from sources that are not Apache 2.0 compatible. I am not a lawyer, and if we want a proper answer involving lawyers, we can work towards that. Why are you asking, what's the idea you're mulling over? --[[User:Denny|Denny]] ([[User talk:Denny|talk]]) 13:44, 19 May 2025 (UTC)
:@[[User:Liuxinyu970226|Liuxinyu970226]]: I see that [https://meta.wikimedia.org/w/index.php?diff=25452852&amp;oldid=25438584&amp;title=Non-free_content you are the one who added that claim] to the page on meta, nearly two years ago. I don't think it's correct; non-free content has never been allowed. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:18, 19 May 2025 (UTC)
::Somewhat modified, but looks still vague even for me... [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 21:46, 19 May 2025 (UTC)
:::Thanks for [https://meta.wikimedia.org/w/index.php?diff=28754698&amp;oldid=28747475&amp;title=Non-free_content your edit]! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:11, 21 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== Wikitext -&gt; AST and vice versa ==

It may be useful to have functions for lexing/tokenizing and parsing Wikitext into an [[:en:Abstract syntax tree|AST]], and going from that AST back to Wikitext. It would vastly improve the power of functions in [[:Wikifunctions:Catalogue/String operations#Wikitext and Mediawiki string operations]]. I think this also meshes neatly with Abstract Wikipedia. If it's planned to have rich/styled output, dealing with an AST is much preferable to performing operations on Wikitext directly.

The downside of this is that it would be complicated and a lot of work to implement, and likely require the creation of a couple new types, at least. However, there already exist [[:mw:Alternative parsers|several Wikitext parsers]], so perhaps a parser (Parsoid?) could be provided as a built-in implementation? Though, this would still necessitate the creation of several types.

Would this be (a) feasible and (b) useful? --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 22:55, 19 May 2025 (UTC)

:Ah, I just read [[:Wikifunctions:Embedded function calls#Wikitext output]]. That would mean this wouldn't really be possible... though it may still be possible to implement an AST for HTML. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 23:23, 19 May 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #203 is out: Ongoing consultation about the Location for Abstract Content ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we invite you again to [[:m:Abstract Wikipedia/Location of Abstract Content|a consultation]] about where should the content of Abstract Wikipedia be stored, we present some updates about existing and new types, we remind you of our next online presentation, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:54, 23 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28661550 --&gt;

== Request for connecting implementations ==

Could a functioneer take a look at [[Z15362|Z15362/nth prime]] and [[Z24716|Z24716/bitwise NAND]] and consider revising the respective lists of connected implementations?

[[Z15362|Z15362/nth prime]]: I'd recommend connecting [[Z24783|Z24783/nth prime, caching primes]] and [[Z24784|Z24784/nth prime, caching primes, JS]], as these seem to be the fastest - they pass all the tests, whereas the others time out on at least one. It should also be noted that these two implementations use more memory than the other implementations, but it doesn't seem to have a particularly noticeable effect on the memory usage.

[[Z24716|Z24716/bitwise NAND]]: I'd like to see [[Z24780|Z24780/bitwise NAND, javascript]] connected. I understand that there's a potential performance benefit when multiple implementations used in a call share the same programming language (though this may not be the case at current), so it would be beneficial to have implementations in all supported programming languages, where possible.

Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 05:02, 24 May 2025 (UTC)

:All {{d}}. Thanks for the work! &lt;span style=&quot;font-family:monospace;font-weight:bold&quot;&gt;[[User:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;~/Bunny&lt;/span&gt;&lt;span style=&quot;color:#2c5282&quot;&gt;pranav&lt;/span&gt;]]:&amp;lt;[[User talk:Bunnypranav|&lt;span style=&quot;color:#63b3ed&quot;&gt;ping&lt;/span&gt;]]&amp;gt;&lt;/span&gt; 06:02, 24 May 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:51, 11 June 2025 (UTC)}}

== proposed Read and Display functions for Unicode code point ==

I suggest we use the following functions as a read and display function for the Unicode code point Type:
* {{Z|Z23041}}
* {{Z|Z24823}}
The reader is intended to be as lenient as possible. If there are other possible input formats, feel free to extend it to include them.

The display uses U+FFFF notation. We have choice here. I picked this because it seems to be common and unambiguous. I'm happy to use another convention if others want it.

Feel free to add an implementation to either with a language configuration if you would like to convert to a different numeral script. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:01, 27 May 2025 (UTC)

:Thank you! Done as per [https://www.wikifunctions.org/wiki/Z86?uselang=en&amp;diff=prev&amp;oldid=189454 this edit]. Looks great!
:I was just hoping this week for having this type with a read and display function! This is awesome! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 12:01, 27 May 2025 (UTC)
::Your work on {{Z|Z24809}} reminded me to finish this off. Last time I'd worked on it I had done almost everything but had been uncertain about which display format to use. Coming back to it the answer seemed clear. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:37, 27 May 2025 (UTC)
:::@[[User:99of9|99of9]] Ha! It was exactly writing the tests for that function which made me wish there was this display and read function! --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 10:03, 2 June 2025 (UTC)
{{Section resolved|1=[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:50, 11 June 2025 (UTC)}}

== Wikifunctions &amp; Abstract Wikipedia Newsletter #204 is out: Rolling out to five Wiktionaries; Calculating with today's date ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we talk about our latest deployment on five Wiktionaries, we showcase a couple of functions about dates, we remind you of ongoing discussions and upcoming presentations, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1748885400 June 2, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:38, 29 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28780680 --&gt;

== Solvers (and color spectrum reconstruction.) ==

I am posting here as I wasn't sure how to define it formally for requesting directly.

A specific spreadsheet used for reconstructing approximate 'reflectance'  data from RGB triplets, uses the Generalized Reduced Gradient(GRG) solver from Excel.  This doesn't exist in Libre Office.

That spreadsheet is linked from ( http://scottburns.us/reflectance-curves-from-srgb-10/.(Burns,2025)  The author also links - http://scottburns.us/matlab-octave-and-python-source-code-for-refl-recon-chrom-adapt/  (I don't see a license indication, but the authors are approachable, and have licensed some of their online contributions under Creative Commons, and I've already suggested they look into writing  a contribution for Wikiversity under Open Access.)

My understanding of what the GRG does is that for a range of input values, a function is setup for the results set, with the sum of the intermediate steps having to meet some 'goal'(in the linked use case a 'minimized' value, these intermediate calculations being used to generate a set of finalised 'results'.

In the use case for (Burns,2025), the results set obtained through the GRG approach, is further constrained. Namely that an XYZ color, obtained from applying CIE observer functions to the generated 'reflectance' data must match a pre determined input XYZ color, although obtained by applying a suitable conversion from an sRGB triplet).   

Would it be possible for some kind of 'solver' function/algorithim to be considered for Wikifunctions, to allow for the kinds of approaches taken in Burns, to be developed or expanded upon?

I appreciate the specific use case is a bit niche, and implentations are possibly beyond me, but having 'solvers' would be useful I think. 

As an aside, having Wikifunctions able to make use reconstructed 'refelctance' data for typical RGB triplets  might prove useful long term, especially if the approach can be extended to approximate for any 'color' ( such as xyz spaces recently added in CSS and recent browsers).  A different author (Ronald Van Winjen, 2025), also uses approximated reflectance curves to implement a 'pigment' style subtractive color mixing 'function' as Spectral.js (https://github.com/rvanwijnen/spectral.js). 
(That code is under MIT license, and uses a faster but possibly less specfic approximation technique.)

My apologies if I sound a bit more formalised in places, and if opthers are able to improve the referencing , feel free. 
[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 08:59, 5 June 2025 (UTC)

:Many solvers use something like [[:w:Newton's method]]. We have a few functions that attempt something like this ([[Z24539]], [[Z24553]]) which you could have a look at to incorporate into your colour analysis field. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:04, 6 June 2025 (UTC)

: Actual coding is beyond my expertise, but I figured I'd put the suggestion down for future reference.  In Excel what it's doing is 'guessing' for an entire set of vlaues and tweaking those at goes I think.  The estimation method you linked is for a single value, not a constrained set I think. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|talk]]) 11:22, 6 June 2025 (UTC)

== Wikifunctions &amp; Abstract Wikipedia Newsletter #205 is out: Where will Abstract Content go? ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we give you some updates on the discussion about where to store abstract content, we present you the recordings of our latest presentations and meetings, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:38, 9 June 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28806388 --&gt;

== A guide to easily implement a lenient Gregorian calendar date reader ==
I have created [[User:Dv103/Writing Gregorian calendar date readers|a guide]] on how to implement a specialisation of {{Z|Z20808}} for new languages (since for now it is specialised only for English, Italian and Dagbani, while all the other languages have to rely on the suboptimal [[Z23976|generic reader]]). I hope it is easy to understand (otherwise let me know). At the end I also added the instructions on how to implement a localised version of the function {{Z|Z24990}}, even if is not yet the {{Z|Z20342}} reading function. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:09, 9 June 2025 (UTC)

:This is fantastic - those implementations can be a bit intimidating!  I hope we can set the read/display for Z20342 soon. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:59, 9 June 2025 (UTC)

== proposed Read and Display functions for Day of Roman Year ==

I suggest we use the following functions as a read and display function for the {{Z|Z20342}} Type:
* {{Z|Z24990}}
* {{Z|Z22941}}

The reader is intended to be as lenient as possible, but splits by language for specific month names and ambiguity. If there are other possible input formats, feel free to extend it to include them.

The display is configured by language. Choose the function appropriate to your language! 

Thanks [[User:Dv103]] for all the work on the read functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:01, 11 June 2025 (UTC)</text>
      <sha1>owr6eawol8jqexxghqqh6zrxd65uhmj</sha1>
    </revision>
  </page>
  <page>
    <title>Z11151</title>
    <ns>0</ns>
    <id>15277</id>
    <revision>
      <id>192184</id>
      <parentid>117661</parentid>
      <timestamp>2025-06-10T16:28:22Z</timestamp>
      <contributor>
        <username>WikiLambda system</username>
        <id>3</id>
      </contributor>
      <comment>Updated the implementation list</comment>
      <origin>192184</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="7121" sha1="eqn6qfdohux9zlk4by1hkepz9ilf98h" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z11151&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z8&quot;,
        &quot;Z8K1&quot;: [
            &quot;Z17&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z6&quot;,
                &quot;Z17K2&quot;: &quot;Z11151K1&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;Text&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1186&quot;,
                            &quot;Z11K2&quot;: &quot;טקסט&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1011&quot;,
                            &quot;Z11K2&quot;: &quot;যে অক্ষরের উভপাশ থেকে কোনো বর্ণকে সরাতে হবে&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1004&quot;,
                            &quot;Z11K2&quot;: &quot;Texte&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1014&quot;,
                            &quot;Z11K2&quot;: &quot;Ederede&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1013&quot;,
                            &quot;Z11K2&quot;: &quot;Zaren&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1430&quot;,
                            &quot;Z11K2&quot;: &quot;Text&quot;
                        }
                    ]
                }
            },
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z6&quot;,
                &quot;Z17K2&quot;: &quot;Z11151K2&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;Wrapper&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1186&quot;,
                            &quot;Z11K2&quot;: &quot;עוטף&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1011&quot;,
                            &quot;Z11K2&quot;: &quot;যে বর্ণটিকে সরাতে হবে&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1004&quot;,
                            &quot;Z11K2&quot;: &quot;Enveloppe&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1014&quot;,
                            &quot;Z11K2&quot;: &quot;ihe mkpuchi&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1013&quot;,
                            &quot;Z11K2&quot;: &quot;Zaren&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1430&quot;,
                            &quot;Z11K2&quot;: &quot;Umhüllung&quot;
                        }
                    ]
                }
            }
        ],
        &quot;Z8K2&quot;: &quot;Z6&quot;,
        &quot;Z8K3&quot;: [
            &quot;Z20&quot;,
            &quot;Z11153&quot;,
            &quot;Z11154&quot;,
            &quot;Z11155&quot;
        ],
        &quot;Z8K4&quot;: [
            &quot;Z14&quot;,
            &quot;Z12311&quot;,
            &quot;Z11152&quot;
        ],
        &quot;Z8K5&quot;: &quot;Z11151&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;unwrap string&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1186&quot;,
                &quot;Z11K2&quot;: &quot;הסרת עוטף מחרוזת&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1616&quot;,
                &quot;Z11K2&quot;: &quot;odstrani obod niza&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1011&quot;,
                &quot;Z11K2&quot;: &quot;অক্ষরসারিকে মোড়ক মুক্ত&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;désenvelopper une chaîne de caractère&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;Wopute strinji&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1013&quot;,
                &quot;Z11K2&quot;: &quot;kwance igiya&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;Umhüllung der Zeichenkette entfernen&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;removes text from start and end of string once only if both are present&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1616&quot;,
                &quot;Z11K2&quot;: &quot;odstrani besedilo iz začetka in konca niza&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1186&quot;,
                &quot;Z11K2&quot;: &quot;הסרת העוטף מעל הטקסט פעם בודדת, אם הוא מופיע הן בתחילתו והן בסופו&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1011&quot;,
                &quot;Z11K2&quot;: &quot;কোনো অক্ষরের প্রথম ও শেষ থেকে একই সমান বর্ণকে সরানো, যদি প্রথমে ও শেষে সেই বর্ণটি উপস্থিত থাকে&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;Supprime le texte du début et de la fin de la chaîne une seule fois si les deux sont présents&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;Na-ewepụ ederede site na mmalite na njedebe eriri otu ugboro naanị ma ọ bụrụ na ha abụọ nọ&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1013&quot;,
                &quot;Z11K2&quot;: &quot;Yana cire rubutu daga farko da ƙarshen kirtani sau ɗaya kawai idan duka suna nan&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;entfernt Text am Anfang und Ende einer Zeichenkette, wenn er an beiden Stellen vorhanden ist&quot;
            }
        ]
    }
}</text>
      <sha1>eqn6qfdohux9zlk4by1hkepz9ilf98h</sha1>
    </revision>
  </page>
  <page>
    <title>Z12864</title>
    <ns>0</ns>
    <id>22361</id>
    <revision>
      <id>192238</id>
      <parentid>191029</parentid>
      <timestamp>2025-06-11T06:16:42Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>nudge</comment>
      <origin>192238</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="6052" sha1="r3xlyee7jgkfhg7619g0gjx9mncfn1m" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z12864&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z8&quot;,
        &quot;Z8K1&quot;: [
            &quot;Z17&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: {
                    &quot;Z1K1&quot;: &quot;Z7&quot;,
                    &quot;Z7K1&quot;: &quot;Z881&quot;,
                    &quot;Z881K1&quot;: &quot;Z1&quot;
                },
                &quot;Z17K2&quot;: &quot;Z12864K1&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;first list&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1430&quot;,
                            &quot;Z11K2&quot;: &quot;erste Liste&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1025&quot;,
                            &quot;Z11K2&quot;: &quot;pierwsza lista&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1014&quot;,
                            &quot;Z11K2&quot;: &quot;ndepụta mbụ: Edepụtara ndepụta ( Ihe )&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1004&quot;,
                            &quot;Z11K2&quot;: &quot;première liste&quot;
                        }
                    ]
                }
            },
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: {
                    &quot;Z1K1&quot;: &quot;Z7&quot;,
                    &quot;Z7K1&quot;: &quot;Z881&quot;,
                    &quot;Z881K1&quot;: &quot;Z1&quot;
                },
                &quot;Z17K2&quot;: &quot;Z12864K2&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;second list&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1430&quot;,
                            &quot;Z11K2&quot;: &quot;zweite Liste&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1025&quot;,
                            &quot;Z11K2&quot;: &quot;druga lista&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1014&quot;,
                            &quot;Z11K2&quot;: &quot;ndepụta nke abụọ: Edepụtara ndepụta ( Ihe )&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1004&quot;,
                            &quot;Z11K2&quot;: &quot;seconde liste&quot;
                        }
                    ]
                }
            }
        ],
        &quot;Z8K2&quot;: &quot;Z40&quot;,
        &quot;Z8K3&quot;: [
            &quot;Z20&quot;,
            &quot;Z12866&quot;,
            &quot;Z13395&quot;,
            &quot;Z18127&quot;,
            &quot;Z24730&quot;,
            &quot;Z24731&quot;
        ],
        &quot;Z8K4&quot;: [
            &quot;Z14&quot;,
            &quot;Z13394&quot;,
            &quot;Z12865&quot;,
            &quot;Z13890&quot;
        ],
        &quot;Z8K5&quot;: &quot;Z12864&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;lists have equal length&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;Listen sind gleich lang&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1025&quot;,
                &quot;Z11K2&quot;: &quot;czy listy mają tę samą długość&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;ndepụta nwere nha nha ogologo&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;ces listes sont-elles de longueur égale ?&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1002&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;length equal&quot;,
                    &quot;equal length lists&quot;,
                    &quot;are equal length&quot;,
                    &quot;lists equal length&quot;,
                    &quot;is equal length&quot;,
                    &quot;equality (list length)&quot;,
                    &quot;equal list lengths&quot;,
                    &quot;is list equal length to another&quot;,
                    &quot;are lists equal length&quot;,
                    &quot;same length&quot;,
                    &quot;lengths equal&quot;,
                    &quot;= length lists&quot;,
                    &quot;== (length)&quot;
                ]
            }
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;true if the lists have an equal number of elements, false otherwise&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;gibt wahr zurück, wenn die verglichenen Listen gleich viele Elemente enthalten&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1025&quot;,
                &quot;Z11K2&quot;: &quot;Zwraca prawdę, jeśli listy mają tę samą długość&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;eziokwu ma ọ bụrụ na ndepụta ahụ nwere nha nha nke mmewere, ụgha ma ọ bụghị&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;renvoie \&quot;vrai\&quot; si les listes ont un nombre égal d'éléments, sinon \&quot;faux\&quot;&quot;
            }
        ]
    }
}</text>
      <sha1>r3xlyee7jgkfhg7619g0gjx9mncfn1m</sha1>
    </revision>
  </page>
  <page>
    <title>Z15651</title>
    <ns>0</ns>
    <id>28914</id>
    <revision>
      <id>192186</id>
      <parentid>164543</parentid>
      <timestamp>2025-06-10T17:43:23Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192186</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="2478" sha1="1zvb5urhnjhj9bj850qt59hycxzis0u" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15651&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z8&quot;,
        &quot;Z8K1&quot;: [
            &quot;Z17&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z13518&quot;,
                &quot;Z17K2&quot;: &quot;Z15651K1&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;n&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1014&quot;,
                            &quot;Z11K2&quot;: &quot;n: Nọmba eke&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1004&quot;,
                            &quot;Z11K2&quot;: &quot;nombre&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1430&quot;,
                            &quot;Z11K2&quot;: &quot;n&quot;
                        }
                    ]
                }
            }
        ],
        &quot;Z8K2&quot;: &quot;Z13518&quot;,
        &quot;Z8K3&quot;: [
            &quot;Z20&quot;,
            &quot;Z15653&quot;,
            &quot;Z15655&quot;
        ],
        &quot;Z8K4&quot;: [
            &quot;Z14&quot;,
            &quot;Z15652&quot;
        ],
        &quot;Z8K5&quot;: &quot;Z15651&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;nth Belphegor number&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;nth Belphegor nọmba&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;énième nombre de Belphégor&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;nte Belphegor-Zahl&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1002&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;A232449&quot;
                ]
            }
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>1zvb5urhnjhj9bj850qt59hycxzis0u</sha1>
    </revision>
  </page>
  <page>
    <title>Z15652</title>
    <ns>0</ns>
    <id>28915</id>
    <revision>
      <id>192187</id>
      <parentid>164545</parentid>
      <timestamp>2025-06-10T17:43:52Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192187</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="1076" sha1="lvsuy9gfc59jhhwt1b8n8hv0xm9zi1k" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15652&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z14&quot;,
        &quot;Z14K1&quot;: &quot;Z15651&quot;,
        &quot;Z14K3&quot;: {
            &quot;Z1K1&quot;: &quot;Z16&quot;,
            &quot;Z16K1&quot;: &quot;Z610&quot;,
            &quot;Z16K2&quot;: &quot;def Z15651(Z15651K1):\n\treturn 10**(2*Z15651K1+4)+666*10**(Z15651K1+1)+1&quot;
        }
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;nth Belphegor number, python&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;énième nombre de Belphégor, en Python&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;nte Belphegor-Zahl in Python&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>lvsuy9gfc59jhhwt1b8n8hv0xm9zi1k</sha1>
    </revision>
  </page>
  <page>
    <title>Z15653</title>
    <ns>0</ns>
    <id>28916</id>
    <revision>
      <id>192188</id>
      <parentid>164547</parentid>
      <timestamp>2025-06-10T17:44:22Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192188</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="1281" sha1="qfeiqm1ulb6hiaetetn661ejp24p915" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15653&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z20&quot;,
        &quot;Z20K1&quot;: &quot;Z15651&quot;,
        &quot;Z20K2&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z15651&quot;,
            &quot;Z15651K1&quot;: {
                &quot;Z1K1&quot;: &quot;Z13518&quot;,
                &quot;Z13518K1&quot;: &quot;0&quot;
            }
        },
        &quot;Z20K3&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z13522&quot;,
            &quot;Z13522K2&quot;: {
                &quot;Z1K1&quot;: &quot;Z13518&quot;,
                &quot;Z13518K1&quot;: &quot;16661&quot;
            }
        }
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;0th Belphegor number is 16661&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;le 0e nombre de Belphégor est 16661&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;nullte Belphegor-Zahl ist 16661&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>qfeiqm1ulb6hiaetetn661ejp24p915</sha1>
    </revision>
  </page>
  <page>
    <title>Z15654</title>
    <ns>0</ns>
    <id>28917</id>
    <revision>
      <id>192189</id>
      <parentid>164549</parentid>
      <timestamp>2025-06-10T17:48:09Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192189</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="892" sha1="13w14lzumbp1nj5mraygwdm9jeod2cg" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15654&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z13518&quot;,
        &quot;Z13518K1&quot;: &quot;1000000000000066600000000000001&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;Belphegor's prime&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;nombre premier de Belphégor&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;Belphegors Primzahl&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>13w14lzumbp1nj5mraygwdm9jeod2cg</sha1>
    </revision>
  </page>
  <page>
    <title>Z15655</title>
    <ns>0</ns>
    <id>28918</id>
    <revision>
      <id>192190</id>
      <parentid>164548</parentid>
      <timestamp>2025-06-10T17:48:40Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192190</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="1433" sha1="qxe4lgfsgi3zxi2ivphnrzp2ohs6r1x" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15655&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z20&quot;,
        &quot;Z20K1&quot;: &quot;Z15651&quot;,
        &quot;Z20K2&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z15651&quot;,
            &quot;Z15651K1&quot;: {
                &quot;Z1K1&quot;: &quot;Z13518&quot;,
                &quot;Z13518K1&quot;: &quot;13&quot;
            }
        },
        &quot;Z20K3&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z13522&quot;,
            &quot;Z13522K2&quot;: &quot;Z15654&quot;
        }
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;13th Belphegor number is the Belphegor's prime&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;le 13e nombre de Belphégor est son nombre premier&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;13. Belphegor-Zahl ist Belphegors Primzahl&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;le 13e nombre de Belphégor est le nombre premier de Belphégor &quot;
            }
        ]
    }
}</text>
      <sha1>qxe4lgfsgi3zxi2ivphnrzp2ohs6r1x</sha1>
    </revision>
  </page>
  <page>
    <title>Z15656</title>
    <ns>0</ns>
    <id>28919</id>
    <revision>
      <id>192191</id>
      <parentid>164556</parentid>
      <timestamp>2025-06-10T17:49:09Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192191</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="1415" sha1="af5q82lta80zpb13ldw0hqcsyhgrzaz" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15656&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z20&quot;,
        &quot;Z20K1&quot;: &quot;Z15055&quot;,
        &quot;Z20K2&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z15055&quot;,
            &quot;Z15055K1&quot;: &quot;Z15654&quot;
        },
        &quot;Z20K3&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z844&quot;,
            &quot;Z844K2&quot;: {
                &quot;Z1K1&quot;: &quot;Z40&quot;,
                &quot;Z40K1&quot;: &quot;Z41&quot;
            }
        }
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;Belphegor's prime is palindromic prime&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;premier de Belph. est un nombre premier palindrome&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;Belphegors Primzahl ist Primzahlpalindrom&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;le nombre premier de Belphégor est un nombre premier palindrome&quot;
            }
        ]
    }
}</text>
      <sha1>af5q82lta80zpb13ldw0hqcsyhgrzaz</sha1>
    </revision>
  </page>
  <page>
    <title>Z15657</title>
    <ns>0</ns>
    <id>28920</id>
    <revision>
      <id>192192</id>
      <parentid>164542</parentid>
      <timestamp>2025-06-10T17:49:32Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192192</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="1226" sha1="jf7x2rk09ynj8baz5s0q1rve5f0gnob" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15657&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z20&quot;,
        &quot;Z20K1&quot;: &quot;Z15050&quot;,
        &quot;Z20K2&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z15050&quot;,
            &quot;Z15050K1&quot;: &quot;Z15654&quot;
        },
        &quot;Z20K3&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z844&quot;,
            &quot;Z844K2&quot;: {
                &quot;Z1K1&quot;: &quot;Z40&quot;,
                &quot;Z40K1&quot;: &quot;Z41&quot;
            }
        }
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;Belphegor's prime is palindromic number&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;le nombre de Belphégor est un nombre palindrome&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;Belphegors Primzahl ist Zahlenpalindrom&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>jf7x2rk09ynj8baz5s0q1rve5f0gnob</sha1>
    </revision>
  </page>
  <page>
    <title>Z15658</title>
    <ns>0</ns>
    <id>28921</id>
    <revision>
      <id>192193</id>
      <parentid>98710</parentid>
      <timestamp>2025-06-10T17:50:07Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192193</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="1527" sha1="gtnzncgedu0cn1r74yg383jrm8w3i3t" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15658&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z14&quot;,
        &quot;Z14K1&quot;: &quot;Z15626&quot;,
        &quot;Z14K2&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z11693&quot;,
            &quot;Z11693K1&quot;: {
                &quot;Z1K1&quot;: &quot;Z18&quot;,
                &quot;Z18K1&quot;: &quot;Z15626K1&quot;
            },
            &quot;Z11693K2&quot;: {
                &quot;Z1K1&quot;: &quot;Z7&quot;,
                &quot;Z7K1&quot;: &quot;Z10000&quot;,
                &quot;Z10000K1&quot;: &quot;぀ぁあぃいぅうぇえぉおかがきぎくぐけげこごさざしじすずせぜそぞただちぢっつづてでとどなにぬねのはばぱひびぴふぶぷへべぺほぼぽまみむめもゃやゅゆょよらりるれろゎわゐゑをんゔゕゖ゗゘゙゚゛゜ゝゞゟ&quot;,
                &quot;Z10000K2&quot;: &quot;。、？「」『』〜 ・！（）【】｛｝…‥っー々ゝゞヶ￥〒〶&quot;
            }
        }
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;is string in hiragana, composition of only has characters from alphabet&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;ist Zeichenkette in Hiragana, Komposition Alphabet&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>gtnzncgedu0cn1r74yg383jrm8w3i3t</sha1>
    </revision>
  </page>
  <page>
    <title>Z15659</title>
    <ns>0</ns>
    <id>28922</id>
    <revision>
      <id>192194</id>
      <parentid>119642</parentid>
      <timestamp>2025-06-10T17:51:23Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192194</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="2266" sha1="4bylffolj4fpxb3dt0qdjgsmqitcpgs" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15659&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z8&quot;,
        &quot;Z8K1&quot;: [
            &quot;Z17&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z13518&quot;,
                &quot;Z17K2&quot;: &quot;Z15659K1&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;n&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1014&quot;,
                            &quot;Z11K2&quot;: &quot;n&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1430&quot;,
                            &quot;Z11K2&quot;: &quot;n&quot;
                        }
                    ]
                }
            }
        ],
        &quot;Z8K2&quot;: &quot;Z13518&quot;,
        &quot;Z8K3&quot;: [
            &quot;Z20&quot;,
            &quot;Z15661&quot;,
            &quot;Z15662&quot;,
            &quot;Z15663&quot;
        ],
        &quot;Z8K4&quot;: [
            &quot;Z14&quot;,
            &quot;Z15660&quot;,
            &quot;Z15665&quot;
        ],
        &quot;Z8K5&quot;: &quot;Z15659&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;subfactorial&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;subfactorial&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;Subfakultät&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1002&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;nth derangement number&quot;,
                    &quot;!n&quot;,
                    &quot;A000166&quot;,
                    &quot;nth subfactorial number&quot;
                ]
            }
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>4bylffolj4fpxb3dt0qdjgsmqitcpgs</sha1>
    </revision>
  </page>
  <page>
    <title>Z15660</title>
    <ns>0</ns>
    <id>28923</id>
    <revision>
      <id>192195</id>
      <parentid>98172</parentid>
      <timestamp>2025-06-10T17:51:45Z</timestamp>
      <contributor>
        <username>Ameisenigel</username>
        <id>44</id>
      </contributor>
      <comment>de</comment>
      <origin>192195</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="963" sha1="14nc4dnp4374qq58he9kslwsmfdvpva" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15660&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z14&quot;,
        &quot;Z14K1&quot;: &quot;Z15659&quot;,
        &quot;Z14K3&quot;: {
            &quot;Z1K1&quot;: &quot;Z16&quot;,
            &quot;Z16K1&quot;: &quot;Z610&quot;,
            &quot;Z16K2&quot;: &quot;def Z15659(Z15659K1):\n\timport math\n\tn = Z15659K1\n\treturn sum(math.factorial(k)*(-1)**(n-k)*math.comb(n,k) for k in range(n+1))&quot;
        }
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;nth subfactorial, python&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;Subfakultät in Python&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>14nc4dnp4374qq58he9kslwsmfdvpva</sha1>
    </revision>
  </page>
  <page>
    <title>Z15684</title>
    <ns>0</ns>
    <id>28956</id>
    <revision>
      <id>192185</id>
      <parentid>192072</parentid>
      <timestamp>2025-06-10T17:31:18Z</timestamp>
      <contributor>
        <username>WikiLambda system</username>
        <id>3</id>
      </contributor>
      <comment>Updated the implementation list</comment>
      <origin>192185</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="4406" sha1="ibyugjlgs4x2iwyq37nom6ptfh1sxyb" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z15684&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z8&quot;,
        &quot;Z8K1&quot;: [
            &quot;Z17&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z1&quot;,
                &quot;Z17K2&quot;: &quot;Z15684K1&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;argument&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1014&quot;,
                            &quot;Z11K2&quot;: &quot;arụmụka:   Ihe&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1011&quot;,
                            &quot;Z11K2&quot;: &quot;আর্গুমেন্ট&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1004&quot;,
                            &quot;Z11K2&quot;: &quot;argument&quot;
                        }
                    ]
                }
            }
        ],
        &quot;Z8K2&quot;: &quot;Z40&quot;,
        &quot;Z8K3&quot;: [
            &quot;Z20&quot;,
            &quot;Z15685&quot;,
            &quot;Z15687&quot;,
            &quot;Z15688&quot;,
            &quot;Z15689&quot;,
            &quot;Z15690&quot;,
            &quot;Z15691&quot;,
            &quot;Z15692&quot;,
            &quot;Z15693&quot;
        ],
        &quot;Z8K4&quot;: [
            &quot;Z14&quot;,
            &quot;Z15694&quot;,
            &quot;Z15686&quot;,
            &quot;Z15701&quot;
        ],
        &quot;Z8K5&quot;: &quot;Z15684&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;is truthy&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;ọ bụ eziokwu&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;ist truthy&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1011&quot;,
                &quot;Z11K2&quot;: &quot;শূন্য কিংবা খালি নয়&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;est-ce vrai ?&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1002&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;truthy&quot;,
                    &quot;not falsy&quot;,
                    &quot;not zero or empty&quot;
                ]
            },
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1430&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;truthy&quot;,
                    &quot;nicht falsy&quot;,
                    &quot;nicht Null oder leer&quot;
                ]
            },
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1004&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;vrai&quot;,
                    &quot;pas faux&quot;,
                    &quot;pas zéro ou vide&quot;
                ]
            }
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;returns True if the argument is truthy&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;na-alaghachi na-ezi ma ọ bụrụ na arụmụka bụ eziokwu&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1430&quot;,
                &quot;Z11K2&quot;: &quot;gibt Wahr zurück, wenn die Eingabe truthy ist&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1011&quot;,
                &quot;Z11K2&quot;: &quot;যদি ইনপুট শূন্য বা খালিস্থান না হয় তাহলে সত্য প্রদান করবে। &quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;renvoie \&quot;vrai\&quot; si l'argument est vrai, sinon \&quot;faux\&quot;&quot;
            }
        ]
    }
}</text>
      <sha1>ibyugjlgs4x2iwyq37nom6ptfh1sxyb</sha1>
    </revision>
  </page>
  <page>
    <title>Z16136</title>
    <ns>0</ns>
    <id>30149</id>
    <revision>
      <id>192240</id>
      <parentid>185861</parentid>
      <timestamp>2025-06-11T07:22:27Z</timestamp>
      <contributor>
        <username>Dv103</username>
        <id>11127</id>
      </contributor>
      <comment>+it</comment>
      <origin>192240</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="5800" sha1="f2x81ou8iwvlpxgwnr5fjo2s5vhgltb" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z16136&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z8&quot;,
        &quot;Z8K1&quot;: [
            &quot;Z17&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z16098&quot;,
                &quot;Z17K2&quot;: &quot;Z16136K1&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;month&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1827&quot;,
                            &quot;Z11K2&quot;: &quot;μήνας&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1592&quot;,
                            &quot;Z11K2&quot;: &quot;månad&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1011&quot;,
                            &quot;Z11K2&quot;: &quot;মাসের নাম&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1014&quot;,
                            &quot;Z11K2&quot;: &quot;ọnwa: Ọnwa kalenda Gregorian&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1004&quot;,
                            &quot;Z11K2&quot;: &quot;mois&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1787&quot;,
                            &quot;Z11K2&quot;: &quot;mese&quot;
                        }
                    ]
                }
            }
        ],
        &quot;Z8K2&quot;: &quot;Z16098&quot;,
        &quot;Z8K3&quot;: [
            &quot;Z20&quot;,
            &quot;Z16144&quot;,
            &quot;Z16145&quot;,
            &quot;Z16218&quot;,
            &quot;Z16219&quot;,
            &quot;Z16292&quot;
        ],
        &quot;Z8K4&quot;: [
            &quot;Z14&quot;,
            &quot;Z16146&quot;,
            &quot;Z16370&quot;,
            &quot;Z16147&quot;,
            &quot;Z16298&quot;,
            &quot;Z16271&quot;,
            &quot;Z16148&quot;
        ],
        &quot;Z8K5&quot;: &quot;Z16136&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;following month&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1827&quot;,
                &quot;Z11K2&quot;: &quot;επόμενος μήνας&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1592&quot;,
                &quot;Z11K2&quot;: &quot;nästa månad&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1011&quot;,
                &quot;Z11K2&quot;: &quot;পরবর্তী মাস&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;Ọnwa na- abia&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1005&quot;,
                &quot;Z11K2&quot;: &quot;следующий месяц&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;mois suivant&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1787&quot;,
                &quot;Z11K2&quot;: &quot;mese successivo&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1002&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;next month&quot;,
                    &quot;increment month&quot;,
                    &quot;month after&quot;,
                    &quot;following Gregorian month&quot;,
                    &quot;next Gregorian month&quot;,
                    &quot;increment Gregorian month&quot;
                ]
            },
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1592&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;följande månad&quot;
                ]
            },
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1011&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;মাসের বৃদ্ধি&quot;,
                    &quot;পরের মাস&quot;
                ]
            },
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1787&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;mese dopo&quot;,
                    &quot;incrementa mese&quot;
                ]
            }
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;Returns the month that follows a given month&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1827&quot;,
                &quot;Z11K2&quot;: &quot;λαμβάνει ως είσοδο έναν μήνα και επιστρέφει τον επόμενο μήνα στη σειρά&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1011&quot;,
                &quot;Z11K2&quot;: &quot;ইনপুটে প্রদান করা মাসের ঠিক পরবর্তী মাসটিকে ফলাফল হিসেবে প্রদান করবে। &quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1014&quot;,
                &quot;Z11K2&quot;: &quot;Na-eweghachi ọnwa na-esote ọnwa enyere&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1004&quot;,
                &quot;Z11K2&quot;: &quot;renvoie le mois qui suit un mois donné&quot;
            }
        ]
    }
}</text>
      <sha1>f2x81ou8iwvlpxgwnr5fjo2s5vhgltb</sha1>
    </revision>
  </page>
  <page>
    <title>Wikifunctions:NLG SIG</title>
    <ns>4</ns>
    <id>49539</id>
    <revision>
      <id>192217</id>
      <parentid>187147</parentid>
      <timestamp>2025-06-11T03:49:42Z</timestamp>
      <contributor>
        <username>Mahir256</username>
        <id>38</id>
      </contributor>
      <comment>/* Upcoming meeting */</comment>
      <origin>192217</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2039" sha1="3yte8y1u1pa54xjoazs5abwqqyrblto" xml:space="preserve">This page is for coordinating the work of the NLG SIG - the '''natural language generation special interest group''' on Wikifunctions.

This page is just a starter page. It aims to collect links to documents by the group, plan upcoming meetings of the group, and help the members coordinate.

You want to join? Anyone can become a member. Enter your wiki user name below to become a publicly listed member. Work happens on-wiki, off-wiki and through meetings.

== Upcoming meeting ==
The next meeting of the NLG SIG is scheduled for Tuesday, June 17, 2025 on [https://meet.google.com/xzn-kqer-mah Google Meet]. The meeting will be recorded. If you want to add something to the agenda, please feel free to do so below:
* [[User:Mahir256|Mahir256]]: exploring sources for constructs used in abstract content

== Past meetings ==

=== 2025-03-18 ===

The second meeting of the NLG SIG was held on [https://zonestamp.toolforge.org/1742313600 Tuesday, March 18, 2025, at 16:00-17:00 UTC] on [https://meet.google.com/xzn-kqer-mah Google Meet]. The meeting was recorded.
* [[User:Mahir256|Mahir256]]: Finding lexemes for concepts, and actual and potential fallback mechanisms for this task ([https://elemwala.toolforge.org/static/nlgsig-18march.html slides])

=== 2025-02-18 ===
The first meeting of the NLG SIG was held on [https://zonestamp.toolforge.org/1739894400 Tuesday, February 18, 2025, at 16:00-17:00 UTC] using [https://meet.google.com/xzn-kqer-mah Google Meet]. The meeting was recorded.
* [[User:Denny|Denny]]: [[Wikifunctions:Type proposals/Syntactic type|Representing lexemes on Wikifunctions]]

== Documents ==
Collect lists of interesting documents by and for the group. Can be on-wiki or external references.

== Publicly listed members ==
# [[user:Denny|Denny]]
# [[user:Arlo Barnes|Arlo Barnes]]
# [[User:Jérémy-Günther-Heinz Jähnick|Jérémy-Günther-Heinz Jähnick]]
# [[User:Mahir256|Mahir256]]
# [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]])
# [[User:Fexpr|Fexpr]]
# [[User:King ChristLike|King ChristLike]]</text>
      <sha1>3yte8y1u1pa54xjoazs5abwqqyrblto</sha1>
    </revision>
  </page>
  <page>
    <title>User:Dv103/Sandbox</title>
    <ns>2</ns>
    <id>54610</id>
    <revision>
      <id>192241</id>
      <parentid>190928</parentid>
      <timestamp>2025-06-11T07:25:32Z</timestamp>
      <contributor>
        <username>Dv103</username>
        <id>11127</id>
      </contributor>
      <origin>192241</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="564" sha1="2jfmmtsd12x2ad4wkqbko41vcac915f" xml:space="preserve">* Today is {{#function:Z24884|}}.
* Oggi è il {{#function:Z24884||renderlang=it}}.
* Hoy es {{#function:Z24884||renerlang=es}}.
* Hodiaŭ ĝi estas {{#function:Z24884||renerlang=eo}}.

{{#function:Z20440|1 may 5|renderlang=it}} .

{{#time:Y-m-d}}

{{#function:Z24007|{{#time:Y-m-d}}}} .

Dates in Dagbani:
{{#function:Z24880|31-05-2025}}

Senza parametro: {{#function:Z24880|}}

Mese dopo giugno: {{#function:Z16136|Z16106}}
 

[//www.wikifunctions.org/w/index.php?title=User:Dv103/Sandbox&amp;action=purge refresh cache]

[[Category:Pages with Wikifunctions calls]]</text>
      <sha1>2jfmmtsd12x2ad4wkqbko41vcac915f</sha1>
    </revision>
  </page>
  <page>
    <title>Z24086</title>
    <ns>0</ns>
    <id>54740</id>
    <revision>
      <id>192212</id>
      <parentid>189561</parentid>
      <timestamp>2025-06-11T01:59:36Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>nudge</comment>
      <origin>192212</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="3561" sha1="9ynmbvisrh9latwvtd6dk4vb5ubfgv2" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z24086&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z8&quot;,
        &quot;Z8K1&quot;: [
            &quot;Z17&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z16098&quot;,
                &quot;Z17K2&quot;: &quot;Z24086K1&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;month&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1787&quot;,
                            &quot;Z11K2&quot;: &quot;mese&quot;
                        }
                    ]
                }
            },
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z60&quot;,
                &quot;Z17K2&quot;: &quot;Z24086K2&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;language to display in&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1787&quot;,
                            &quot;Z11K2&quot;: &quot;lingua&quot;
                        }
                    ]
                }
            }
        ],
        &quot;Z8K2&quot;: &quot;Z6&quot;,
        &quot;Z8K3&quot;: [
            &quot;Z20&quot;,
            &quot;Z24088&quot;,
            &quot;Z24335&quot;,
            &quot;Z24336&quot;,
            &quot;Z24337&quot;,
            &quot;Z24704&quot;
        ],
        &quot;Z8K4&quot;: [
            &quot;Z14&quot;,
            &quot;Z24330&quot;
        ],
        &quot;Z8K5&quot;: &quot;Z24086&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;display Gregorian calendar month&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1787&quot;,
                &quot;Z11K2&quot;: &quot;formatta Mese di calendario gregoriano&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1002&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;render month&quot;,
                    &quot;show month&quot;,
                    &quot;display month&quot;,
                    &quot;display calendar month&quot;,
                    &quot;render Gregorian calendar month&quot;,
                    &quot;string of month&quot;,
                    &quot;show Gregorian calendar month&quot;
                ]
            },
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1787&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;mostra mese&quot;,
                    &quot;stampa mese&quot;
                ]
            }
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;returns a string representing the Gregorian calendar month in the selected language (a Wikidata label) or fallback&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1787&quot;,
                &quot;Z11K2&quot;: &quot;Restituisce una stringa rappresentante il Mese di calendario gregoriano nella lingua selezionata o in una surrogata&quot;
            }
        ]
    }
}</text>
      <sha1>9ynmbvisrh9latwvtd6dk4vb5ubfgv2</sha1>
    </revision>
  </page>
  <page>
    <title>Wikifunctions:Type proposals/Wikidata time</title>
    <ns>4</ns>
    <id>56521</id>
    <revision>
      <id>192197</id>
      <parentid>191820</parentid>
      <timestamp>2025-06-10T19:36:18Z</timestamp>
      <contributor>
        <username>DMartin (WMF)</username>
        <id>24</id>
      </contributor>
      <comment>/* Structure */</comment>
      <origin>192197</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="11969" sha1="416umvqp4t49ditu76biwlyvdyuoymt" xml:space="preserve">== Summary ==

This type is modeled after Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Dates_and_times time] datatype, and will support the import of all values of that type from Wikidata into Wikifunctions. The content here also builds on [[Wikifunctions:Time_in_Wikidata|Time in Wikidata]], which provides additional background information for this proposal. We also acknowledge and draw upon an earlier type proposal, [[Wikifunctions:Type_proposals/Wikidata_value#Point_in_time|Point in time]], with similar objectives.

In addition to ''Wikidata time'' , we also propose here 4 other simple types used for keys inside ''Wikidata time'': ''Wikidata time precision, Datetime, Time of day,'' and ''Calendar model.''

== Uses ==
* ''Why should this exist?''
Wikidata contains many statements with values of the [https://www.mediawiki.org/wiki/Wikibase/DataModel#Dates_and_times time] datatype. A wide variety of Wikifunctions will be able to make use of these values, and this type will enable Wikifunctions to import these values from Wikidata.

* ''What kinds of functions would be created using this?''
Many kinds, including in particular functions that are called from Wikipedias and other MediaWiki projects to provide [https://www.mediawiki.org/wiki/Wikibase/DataModel#Dates_and_times time] values (or content computed from them), and Abstract Wikipedia functions that generate statements, paragraphs, and articles containing these values.

* ''What standard concepts, if any, does this align with?''
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Dates_and_times time] datatype.

== Structure ==
'''''Wikidata time''''' has these 6 keys, shown with proposed English labels:

* &lt;code&gt;K1/datetime&lt;/code&gt;, of a new type ''Datetime'' to be defined as shown below.  This represents the point in time which serves as the base value for ''Wikidata time''.
* &lt;code&gt;K2/precision&lt;/code&gt;, of an enum type ''Wikidata time precision,'' to be defined as shown below.
* &lt;code&gt;K3/after&lt;/code&gt;, of type [[Z13518|Natural number]]. If the date is uncertain, how many units (given by the precision) after the given time could it be?
* &lt;code&gt;K4/before&lt;/code&gt;, of type [[Z13518|Natural number]]. If the date is uncertain, how many units (given by the precision) before the given time could it be?
* &lt;code&gt;K5/timezone&lt;/code&gt;, of type [[Z16683|Integer]], for the ''timezone'' offset from UTC in minutes (by which to display the value).
* &lt;code&gt;K6/calendar model&lt;/code&gt;, of an enum type ''Calendar model (''see below), telling which calendar to use for displaying the value.


'''''Datetime''''' has these 2 keys:

* &lt;code&gt;K1/date&lt;/code&gt;, of type [[Z20420|Gregorian calendar date]] or ''Julian calendar date'' (when it's available).
* &lt;code&gt;K2/time&lt;/code&gt;, of type ''Time of day'' described below.

'''Notes for ''Datetime'''''

* Until the ''Julian calendar date'' type is available, statements from Wikidata indicating ''Julian calendar'' as their calendar model will not be imported into Wikifunctions (by the  Wikidata fetch functions).  Instead, the fetch function will raise an error indicating that the calendar type is not yet supported.
* When the Wikidata timestamp string has zero as the value of the day (i.e., unknown), zero will also be recorded inside the instance of [[Z20342|Day of Roman year]], which is inside [[Z20420|Gregorian calendar date]].  
* When the Wikidata timestamp string has zero as the value of the month (i.e., unknown), [https://www.wikifunctions.org/view/en/Z24 Z24/void] will be recorded inside the instance of [[Z20342|Day of Roman year]], which is inside [[Z20420|Gregorian calendar date]]. 

'''''Time of day''''' has these 3 keys:

* &lt;code&gt;K1/hour&lt;/code&gt;, of type [[Z13518|Natural number]].
* &lt;code&gt;K2/minute&lt;/code&gt;, of type [[Z13518|Natural number]].
* &lt;code&gt;K3/second&lt;/code&gt;, of type [[Z13518|Natural number]].


'''''Wikidata time precision''','' an enum type, has these 15 allowed elements (as specified for the [[mediawikiwiki:Wikibase/DataModel#Dates_and_times|time]] datatype), one of which appears as the value of &lt;code&gt;K1&lt;/code&gt; in an instance of the type. Each of these concepts has a Wikidata item; we hope to implement this as a Wikidata item reference-based &quot;lightweight enum type&quot; (If that capability is available in time):

* billion years
* hundred million years
* ten million years
* million years
* hundred thousand years
* ten thousand years
* millennium
* century
* decade
* year
* month
* day
* hour
* minute
* second


'''Calendar model,''' a lightweight enum type of Wikidata item reference, will include (at least) these possible values:

* { Z1K1: 'Z6091', Z6091K1: 'Q1985727' } / Gregorian calendar
* { Z1K1: 'Z6091', Z6091K1: 'Q11184' } / Julian calendar

=== Example values ===
''TBD''

{|class=&quot;wikitable&quot; style=&quot;margin:.6em 1.6em&quot;
|-
| &lt;syntaxhighlight lang=&quot;json&quot; line=&quot;line&quot;&gt;{
  &quot;type&quot;: &quot;…&quot;,
  &quot;value&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
| &lt;syntaxhighlight lang=&quot;json&quot;&gt;{
  &quot;Z1K1&quot;: &quot;Zxyz&quot;,
  &quot;ZxyzK1&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
|}

== Validator ==
The validator for '''Wikidata time''' checks that:
* The value of each key is a valid instance of the key's defined type. 
* The value of &lt;code&gt;K5/offset&lt;/code&gt; is between -719 and +720, inclusive.

The validator for '''Datetime''' checks that:
* The value of each key is a valid instance of the key's defined type.

The '''Time of day''' validator checks that:

* The value of &lt;code&gt;K1/hour&lt;/code&gt; is a valid ''Natural number'' between 0 and 23, inclusive.  
* The value of &lt;code&gt;K2/minute&lt;/code&gt;  is a valid ''Natural number'' between 0 and 59, inclusive.  
* The value of &lt;code&gt;K3/second&lt;/code&gt;  is a valid ''Natural number'' between 0 and 60, inclusive.  (60 is allowed to accommodate leap-seconds.)

The validators for '''Wikidata time precision''' and '''Calendar model''' check that:
* The value of their &lt;code&gt;K1&lt;/code&gt;  key is one of the allowed elements for the type.

== Identity ==
For each of the above types''':'''  

* Two instances are the same if they have equal values for each of their keys. Equality of those values, in turn, is specified by the definitions &amp; documentation of their respective types.

== Converting to code ==
=== Python ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

=== JavaScript ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

== Display function ==
'''''Wikidata time''''' ...TBD

'''''Datetime''''' should display as a string that joins the output of the {{Z|Z20420}} display function and the ''Time of day'' display function with a suitable, language-dependent separator. For example, in English a possible output could be &quot;7 June 2025, 10:05:42&quot;. The default, language-independent display function should instead use ISO 8601 format (e.g.: &quot;2025-06-07T10:05:42&quot;).

'''''Time of day''''' should display as the time as the language-default time representation (e.g.: &quot;22:10:56&quot; or &quot;10:10:56 p.m.&quot;). The language-independent display function should use the 24h hh:mm:ss format, as per ISO 8601.

== Read function ==
'''''Wikidata time''''' …TBD

'''''Datetime''''' should be read from any string that contains a {{Z|Z20420}} and a ''Time of day'' input separated by a reasonable separator (in both orders). Every language should support the ISO 8601 formats.

'''''Time of day''''' reader should be mostly language-independent, supporting both 24h and 12h formats (and supporting other representations of the arab digits). If the input doesn't contain the seconds' value, it should be assumed to have value 00. The hour &quot;24&quot; should be interpreted as equivalent to &quot;00&quot;. Language-specific readers should be implemented for languages that have other commonly used formats to represent the time of day. Every language should support the ISO 8601 formats.

== Open questions ==
* In Wikidata practice for ''Wikidata time'', is the time part of &lt;code&gt;K1/datetime&lt;/code&gt; always in UTC, or is it in the offset time (given by the timezone property)?
* In Wikidata practice for ''Wikidata time'', is the date part of &lt;code&gt;K1/datetime&lt;/code&gt; always in the ''Gregorian calendar date'', even if the displayed calendar model is Julian?
** According to both of these documentation pages, this is '''not''' the case:
*** [https://www.wikidata.org/wiki/Special:ListDatatypes Special:ListDatatypes]
*** [https://doc.wikimedia.org/Wikibase/master/php/docs_topics_json.html Wikibase JSON]
** So we have an '''unresolved issue''': do we convert a Julian calendar timestamp to Gregorian and save it that way, or do we allow for Wikidata datetime to contain an instance of ''Julian calendar date'' (which would have to be created first)?
*** If we  decide for the latter, we still need to figure out if it is the ''Datetime'' type whose first element can be both of ''Gregorian calendar date'' or ''Julian calendar date'', or if we should separate the ''Datetime with Gregorian calendar'' and the ''Datetime with Julian calendar''. Personally I would prefer this second option, since the Datetime type would be very useful in Wikifunctions even outside of Wikidata dealing functions, so it would be better to make the standard ''Datetime'' type as easy to use as possible. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:56, 7 June 2025 (UTC)
*:Hi @[[User:Dv103|Dv103]], thanks for commenting.  I'm currently leaning the other direction (the first option), because (a) it seems unfortunate to have to create multiple Datetime types (''Datetime'', ''Datetime with Gregorian calendar'', ''Datetime with Julian calendar'', probably more in future) and (b) I believe we could address your concern by having just two Datetime types: one called ''Wikidata datetime'' that allows for ''Gregorian calendar date'' and ''Julian calendar date'' (and possibly other calendars used on Wikidata in future) in its first element, and another called just ''Datetime'', used for non-Wikidata purposes, which could be structured however we like so it could be maximally easy to use.  Does that make sense? [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 05:01, 9 June 2025 (UTC)
*::This actually makes more sense. I didn't think about this. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 9 June 2025 (UTC)
* Revisit: is the use of lightweight enum type of Wikidata item reference our best option for ''Calendar model''?
** For one thing, how many different calendar models are currently used, and how many should we anticipate might be used in future?
** Also, when we have ZObject-based lightweight enum types, are we going to want to switch to those?
*** Probably not, because Wikidata may have more calendar models, at any given time, than what is present on Wikifunctions.

== Alternatives ==
''In order to capture the idea presented in the summary, what alternative structures, display functions, read functions, etc. could have made sense too?''

* In ''Datetime,'' [[Wikifunctions:Type_proposals/Moment_in_time|Moment in time]] could have been used as the type of &lt;code&gt;K2&lt;/code&gt;.
* For &lt;code&gt;K6&lt;/code&gt;, instead of creating an enum type for ''Calendar model,'' its allowed values could have been references to [[Z20420|Gregorian calendar date]]  or ''Julian calendar date'' (which doesn't exist yet).

== Comments ==
''For general comments, please reply to the proposer, or use the ''Discussion'' section below.''
* {{s}} as proposer. --[[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 06:10, 23 May 2025 (UTC)
* {{s}} strong support obviously (functions can be connected to Wikidata so we should support Wikidata types) with two comments: Wikidata support hour, minute, second in theory but not in practice ; and I'm wondering about the display/read functionality. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 16:07, 1 June 2025 (UTC)
*
…

== Discussion ==</text>
      <sha1>416umvqp4t49ditu76biwlyvdyuoymt</sha1>
    </revision>
  </page>
  <page>
    <title>Wikifunctions:Type proposals/Wikidata geocoordinates</title>
    <ns>4</ns>
    <id>56628</id>
    <revision>
      <id>192196</id>
      <parentid>191226</parentid>
      <timestamp>2025-06-10T19:19:49Z</timestamp>
      <contributor>
        <username>DMartin (WMF)</username>
        <id>24</id>
      </contributor>
      <comment>/* Structure */</comment>
      <origin>192196</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7160" sha1="4547h2u4utr3818hybhjydw1x1ozlhq" xml:space="preserve">== Summary ==
This type is modeled after Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype, and will support the import of all values of that type from Wikidata into Wikifunctions. We acknowledge and draw upon an earlier type proposal, [[Wikifunctions:Type_proposals/Wikidata_value#Geographic_coordinate|Geographic coordinate]], with similar objectives.

== Uses ==
* ''Why should this exist?''
Wikidata contains many statements with values of the [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype. A wide variety of Wikifunctions will be able to make use of these values, and this type will enable Wikifunctions to import these values from Wikidata.

* ''What kinds of functions would be created using this?''
Many kinds, including in particular functions that are called from Wikipedias and other MediaWiki projects to provide [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] values (or content computed from them), and Abstract Wikipedia functions that generate statements, paragraphs, and articles containing these values.

* ''What standard concepts, if any, does this align with?''
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype.

== Structure ==
'''''Wikidata geocoordinates''''' has these 4 keys, shown with proposed English labels:

* &lt;code&gt;K1/latitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K2/longitude&lt;/code&gt;, of an enum type [[Z19677|Rational number]].
* &lt;code&gt;K3/precision&lt;/code&gt;, of type [[Z19677|Rational number]], representing degrees of distance.
* &lt;code&gt;K4/globe&lt;/code&gt;, of type [[Z6091|Wikidata item reference]].  

=== Optionality ===
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations DataModel] documentation ''seems'' to imply, by the use of the word &quot;default&quot;, that &lt;code&gt;K3/precision&lt;/code&gt; and &lt;code&gt;K4/globe&lt;/code&gt; properties ''might'' be missing sometimes.  Wikifunctions does not currently have an ability to declare keys as optional.  When importing a [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] value, if either of those properties is missing, Wikifunctions will assign the value of [https://www.wikifunctions.org/view/en/Z24 Z24/void] to these keys.

=== Example values ===
TBD

{|class=&quot;wikitable&quot; style=&quot;margin:.6em 1.6em&quot;
|-
| &lt;syntaxhighlight lang=&quot;json&quot; line=&quot;line&quot;&gt;{
  &quot;type&quot;: &quot;…&quot;,
  &quot;value&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
| &lt;syntaxhighlight lang=&quot;json&quot;&gt;{
  &quot;Z1K1&quot;: &quot;Zxyz&quot;,
  &quot;ZxyzK1&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
|}

== Validator ==
The '''Wikidata geocoordinates''' validator checks that:

* The value of &lt;code&gt;K1/latitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K2/longitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K3/precision&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.
* The value of &lt;code&gt;K4/globe&lt;/code&gt; is a valid instance of [[Z6091|Wikidata item reference]]. (In most cases, per Wikidata practice, its value will be the Wikidata item reference for Q2, the Earth, which means WGS84.)

== Identity ==
For each of the above types''':'''  

* Two instances are the same if they have equal values for each of their keys. Equality of those values, in turn, is specified by the definitions &amp; documentation of their respective types.

== Converting to code ==
=== Python ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

=== JavaScript ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

== Display function ==
''How would a value of this type be displayed on Wikifunctions''

…TBD

== Read function ==
''When entering a value for this type as a string, what format should that string have?''

…TBD

== Questions ==

* The JSON encoding of a geocoordinates value includes a property &quot;altitude&quot;, but so far I've only seen null values for that property.  It doesn't seem to be documented anywhere.  I've found an old discussion indicating that there were no plans to make use of it (at least, not at that time).  Does anyone know if it has any values in Wikidata, or if it might still be used?
* Some values for &lt;code&gt;precision&lt;/code&gt;, coming back from Wikidata, end with an exponent part, like this: &lt;code&gt;&quot;precision&quot;: 2.777777777777778e-5&lt;/code&gt;.  The exponent part isn't mentioned in [https://www.mediawiki.org/wiki/Wikibase/DataModel#decimal Wikibase/DataModel], and doesn't conform to the Wikidata Object Notation given for &lt;code&gt;decimal&lt;/code&gt; there.  It would be good to know if all properties with &lt;code&gt;decimal&lt;/code&gt; values are allowed to include the exponent part, or just &lt;code&gt;precision&lt;/code&gt;.

== Alternatives ==
''In order to capture the idea presented in the summary, what alternative structures, display functions, read functions, etc. could have made sense too?''
* Regarding &lt;code&gt;K4/globe&lt;/code&gt;, it would be possible to create a &quot;lightweight enum type&quot;, but we have an estimate (from Denny) of about 20 different globes currently in use in Wikidata, and we believe that many elements would make the enum type a bit unwieldy.  Also, would like to avoid the maintenance overhead  as additional globes get used over time.

== Comments ==
''For general comments, please reply to the proposer, or use the ''Discussion'' section below.''
* {{s}} as proposer. --[[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 06:11, 23 May 2025 (UTC)
* {{s}} strong support obviously (functions can be connected to Wikidata so we should support Wikidata types) with a warning to be careful about precision and it's representation (it has been and still is a source of many problem on the Wikidata side). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 16:11, 1 June 2025 (UTC)
*
…

== Discussion ==

* A couple months ago, I drafted [[WF:Type proposals/Position on Earth]] with some idea of potential geospatial use-cases but a limited understanding of the Wikidata type. The main differences from this proposal are the lack of a &lt;code&gt;globe&lt;/code&gt; key (Earth assumed, per my suggested name), and the addition of an &lt;code&gt;altitude&lt;/code&gt; key. I think it could easily be adapted to use this type as a component, if there's a need for a position type that includes altitude. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 22:36, 23 May 2025 (UTC)
*:Thanks for mentioning!  Such an adaptation sounds reasonable to me. Let's keep this in mind.  Feel free to adapt the proposal, but it would make sense to wait until this type is published; that's expected by the end of the month. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 00:00, 4 June 2025 (UTC)
*::See also the bullet about altitude in the ''Questions ''section above. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 02:46, 5 June 2025 (UTC)</text>
      <sha1>4547h2u4utr3818hybhjydw1x1ozlhq</sha1>
    </revision>
    <revision>
      <id>192198</id>
      <parentid>192196</parentid>
      <timestamp>2025-06-10T23:27:14Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Structure */ surely the enum is not on the longitude! I assume it was meant for the globe?</comment>
      <origin>192198</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7160" sha1="ch6ucbtdmcpqpafjegafum6mdtrkx27" xml:space="preserve">== Summary ==
This type is modeled after Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype, and will support the import of all values of that type from Wikidata into Wikifunctions. We acknowledge and draw upon an earlier type proposal, [[Wikifunctions:Type_proposals/Wikidata_value#Geographic_coordinate|Geographic coordinate]], with similar objectives.

== Uses ==
* ''Why should this exist?''
Wikidata contains many statements with values of the [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype. A wide variety of Wikifunctions will be able to make use of these values, and this type will enable Wikifunctions to import these values from Wikidata.

* ''What kinds of functions would be created using this?''
Many kinds, including in particular functions that are called from Wikipedias and other MediaWiki projects to provide [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] values (or content computed from them), and Abstract Wikipedia functions that generate statements, paragraphs, and articles containing these values.

* ''What standard concepts, if any, does this align with?''
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype.

== Structure ==
'''''Wikidata geocoordinates''''' has these 4 keys, shown with proposed English labels:

* &lt;code&gt;K1/latitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K2/longitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K3/precision&lt;/code&gt;, of type [[Z19677|Rational number]], representing degrees of distance.
* &lt;code&gt;K4/globe&lt;/code&gt;, of an enum type [[Z6091|Wikidata item reference]].  

=== Optionality ===
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations DataModel] documentation ''seems'' to imply, by the use of the word &quot;default&quot;, that &lt;code&gt;K3/precision&lt;/code&gt; and &lt;code&gt;K4/globe&lt;/code&gt; properties ''might'' be missing sometimes.  Wikifunctions does not currently have an ability to declare keys as optional.  When importing a [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] value, if either of those properties is missing, Wikifunctions will assign the value of [https://www.wikifunctions.org/view/en/Z24 Z24/void] to these keys.

=== Example values ===
TBD

{|class=&quot;wikitable&quot; style=&quot;margin:.6em 1.6em&quot;
|-
| &lt;syntaxhighlight lang=&quot;json&quot; line=&quot;line&quot;&gt;{
  &quot;type&quot;: &quot;…&quot;,
  &quot;value&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
| &lt;syntaxhighlight lang=&quot;json&quot;&gt;{
  &quot;Z1K1&quot;: &quot;Zxyz&quot;,
  &quot;ZxyzK1&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
|}

== Validator ==
The '''Wikidata geocoordinates''' validator checks that:

* The value of &lt;code&gt;K1/latitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K2/longitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K3/precision&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.
* The value of &lt;code&gt;K4/globe&lt;/code&gt; is a valid instance of [[Z6091|Wikidata item reference]]. (In most cases, per Wikidata practice, its value will be the Wikidata item reference for Q2, the Earth, which means WGS84.)

== Identity ==
For each of the above types''':'''  

* Two instances are the same if they have equal values for each of their keys. Equality of those values, in turn, is specified by the definitions &amp; documentation of their respective types.

== Converting to code ==
=== Python ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

=== JavaScript ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

== Display function ==
''How would a value of this type be displayed on Wikifunctions''

…TBD

== Read function ==
''When entering a value for this type as a string, what format should that string have?''

…TBD

== Questions ==

* The JSON encoding of a geocoordinates value includes a property &quot;altitude&quot;, but so far I've only seen null values for that property.  It doesn't seem to be documented anywhere.  I've found an old discussion indicating that there were no plans to make use of it (at least, not at that time).  Does anyone know if it has any values in Wikidata, or if it might still be used?
* Some values for &lt;code&gt;precision&lt;/code&gt;, coming back from Wikidata, end with an exponent part, like this: &lt;code&gt;&quot;precision&quot;: 2.777777777777778e-5&lt;/code&gt;.  The exponent part isn't mentioned in [https://www.mediawiki.org/wiki/Wikibase/DataModel#decimal Wikibase/DataModel], and doesn't conform to the Wikidata Object Notation given for &lt;code&gt;decimal&lt;/code&gt; there.  It would be good to know if all properties with &lt;code&gt;decimal&lt;/code&gt; values are allowed to include the exponent part, or just &lt;code&gt;precision&lt;/code&gt;.

== Alternatives ==
''In order to capture the idea presented in the summary, what alternative structures, display functions, read functions, etc. could have made sense too?''
* Regarding &lt;code&gt;K4/globe&lt;/code&gt;, it would be possible to create a &quot;lightweight enum type&quot;, but we have an estimate (from Denny) of about 20 different globes currently in use in Wikidata, and we believe that many elements would make the enum type a bit unwieldy.  Also, would like to avoid the maintenance overhead  as additional globes get used over time.

== Comments ==
''For general comments, please reply to the proposer, or use the ''Discussion'' section below.''
* {{s}} as proposer. --[[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 06:11, 23 May 2025 (UTC)
* {{s}} strong support obviously (functions can be connected to Wikidata so we should support Wikidata types) with a warning to be careful about precision and it's representation (it has been and still is a source of many problem on the Wikidata side). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 16:11, 1 June 2025 (UTC)
*
…

== Discussion ==

* A couple months ago, I drafted [[WF:Type proposals/Position on Earth]] with some idea of potential geospatial use-cases but a limited understanding of the Wikidata type. The main differences from this proposal are the lack of a &lt;code&gt;globe&lt;/code&gt; key (Earth assumed, per my suggested name), and the addition of an &lt;code&gt;altitude&lt;/code&gt; key. I think it could easily be adapted to use this type as a component, if there's a need for a position type that includes altitude. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 22:36, 23 May 2025 (UTC)
*:Thanks for mentioning!  Such an adaptation sounds reasonable to me. Let's keep this in mind.  Feel free to adapt the proposal, but it would make sense to wait until this type is published; that's expected by the end of the month. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 00:00, 4 June 2025 (UTC)
*::See also the bullet about altitude in the ''Questions ''section above. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 02:46, 5 June 2025 (UTC)</text>
      <sha1>ch6ucbtdmcpqpafjegafum6mdtrkx27</sha1>
    </revision>
    <revision>
      <id>192199</id>
      <parentid>192198</parentid>
      <timestamp>2025-06-10T23:29:23Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Discussion */ Reply</comment>
      <origin>192199</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7307" sha1="af7vnyi5wfigiu1t5v6eqknrzi0wffp" xml:space="preserve">== Summary ==
This type is modeled after Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype, and will support the import of all values of that type from Wikidata into Wikifunctions. We acknowledge and draw upon an earlier type proposal, [[Wikifunctions:Type_proposals/Wikidata_value#Geographic_coordinate|Geographic coordinate]], with similar objectives.

== Uses ==
* ''Why should this exist?''
Wikidata contains many statements with values of the [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype. A wide variety of Wikifunctions will be able to make use of these values, and this type will enable Wikifunctions to import these values from Wikidata.

* ''What kinds of functions would be created using this?''
Many kinds, including in particular functions that are called from Wikipedias and other MediaWiki projects to provide [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] values (or content computed from them), and Abstract Wikipedia functions that generate statements, paragraphs, and articles containing these values.

* ''What standard concepts, if any, does this align with?''
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype.

== Structure ==
'''''Wikidata geocoordinates''''' has these 4 keys, shown with proposed English labels:

* &lt;code&gt;K1/latitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K2/longitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K3/precision&lt;/code&gt;, of type [[Z19677|Rational number]], representing degrees of distance.
* &lt;code&gt;K4/globe&lt;/code&gt;, of an enum type [[Z6091|Wikidata item reference]].  

=== Optionality ===
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations DataModel] documentation ''seems'' to imply, by the use of the word &quot;default&quot;, that &lt;code&gt;K3/precision&lt;/code&gt; and &lt;code&gt;K4/globe&lt;/code&gt; properties ''might'' be missing sometimes.  Wikifunctions does not currently have an ability to declare keys as optional.  When importing a [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] value, if either of those properties is missing, Wikifunctions will assign the value of [https://www.wikifunctions.org/view/en/Z24 Z24/void] to these keys.

=== Example values ===
TBD

{|class=&quot;wikitable&quot; style=&quot;margin:.6em 1.6em&quot;
|-
| &lt;syntaxhighlight lang=&quot;json&quot; line=&quot;line&quot;&gt;{
  &quot;type&quot;: &quot;…&quot;,
  &quot;value&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
| &lt;syntaxhighlight lang=&quot;json&quot;&gt;{
  &quot;Z1K1&quot;: &quot;Zxyz&quot;,
  &quot;ZxyzK1&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
|}

== Validator ==
The '''Wikidata geocoordinates''' validator checks that:

* The value of &lt;code&gt;K1/latitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K2/longitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K3/precision&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.
* The value of &lt;code&gt;K4/globe&lt;/code&gt; is a valid instance of [[Z6091|Wikidata item reference]]. (In most cases, per Wikidata practice, its value will be the Wikidata item reference for Q2, the Earth, which means WGS84.)

== Identity ==
For each of the above types''':'''  

* Two instances are the same if they have equal values for each of their keys. Equality of those values, in turn, is specified by the definitions &amp; documentation of their respective types.

== Converting to code ==
=== Python ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

=== JavaScript ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

== Display function ==
''How would a value of this type be displayed on Wikifunctions''

…TBD

== Read function ==
''When entering a value for this type as a string, what format should that string have?''

…TBD

== Questions ==

* The JSON encoding of a geocoordinates value includes a property &quot;altitude&quot;, but so far I've only seen null values for that property.  It doesn't seem to be documented anywhere.  I've found an old discussion indicating that there were no plans to make use of it (at least, not at that time).  Does anyone know if it has any values in Wikidata, or if it might still be used?
* Some values for &lt;code&gt;precision&lt;/code&gt;, coming back from Wikidata, end with an exponent part, like this: &lt;code&gt;&quot;precision&quot;: 2.777777777777778e-5&lt;/code&gt;.  The exponent part isn't mentioned in [https://www.mediawiki.org/wiki/Wikibase/DataModel#decimal Wikibase/DataModel], and doesn't conform to the Wikidata Object Notation given for &lt;code&gt;decimal&lt;/code&gt; there.  It would be good to know if all properties with &lt;code&gt;decimal&lt;/code&gt; values are allowed to include the exponent part, or just &lt;code&gt;precision&lt;/code&gt;.

== Alternatives ==
''In order to capture the idea presented in the summary, what alternative structures, display functions, read functions, etc. could have made sense too?''
* Regarding &lt;code&gt;K4/globe&lt;/code&gt;, it would be possible to create a &quot;lightweight enum type&quot;, but we have an estimate (from Denny) of about 20 different globes currently in use in Wikidata, and we believe that many elements would make the enum type a bit unwieldy.  Also, would like to avoid the maintenance overhead  as additional globes get used over time.

== Comments ==
''For general comments, please reply to the proposer, or use the ''Discussion'' section below.''
* {{s}} as proposer. --[[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 06:11, 23 May 2025 (UTC)
* {{s}} strong support obviously (functions can be connected to Wikidata so we should support Wikidata types) with a warning to be careful about precision and it's representation (it has been and still is a source of many problem on the Wikidata side). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 16:11, 1 June 2025 (UTC)
*
…

== Discussion ==

* A couple months ago, I drafted [[WF:Type proposals/Position on Earth]] with some idea of potential geospatial use-cases but a limited understanding of the Wikidata type. The main differences from this proposal are the lack of a &lt;code&gt;globe&lt;/code&gt; key (Earth assumed, per my suggested name), and the addition of an &lt;code&gt;altitude&lt;/code&gt; key. I think it could easily be adapted to use this type as a component, if there's a need for a position type that includes altitude. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 22:36, 23 May 2025 (UTC)
*:Thanks for mentioning!  Such an adaptation sounds reasonable to me. Let's keep this in mind.  Feel free to adapt the proposal, but it would make sense to wait until this type is published; that's expected by the end of the month. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 00:00, 4 June 2025 (UTC)
*::See also the bullet about altitude in the ''Questions ''section above. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 02:46, 5 June 2025 (UTC)
*:I would probably support altitude, but it would need to be optional. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:29, 10 June 2025 (UTC)</text>
      <sha1>af7vnyi5wfigiu1t5v6eqknrzi0wffp</sha1>
    </revision>
    <revision>
      <id>192200</id>
      <parentid>192199</parentid>
      <timestamp>2025-06-10T23:29:53Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Structure */ per alternatives below, it looks like the intent is not to have enum</comment>
      <origin>192200</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7299" sha1="thxp1y2b5d36vhcdj2ktpif29fjmi4z" xml:space="preserve">== Summary ==
This type is modeled after Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype, and will support the import of all values of that type from Wikidata into Wikifunctions. We acknowledge and draw upon an earlier type proposal, [[Wikifunctions:Type_proposals/Wikidata_value#Geographic_coordinate|Geographic coordinate]], with similar objectives.

== Uses ==
* ''Why should this exist?''
Wikidata contains many statements with values of the [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype. A wide variety of Wikifunctions will be able to make use of these values, and this type will enable Wikifunctions to import these values from Wikidata.

* ''What kinds of functions would be created using this?''
Many kinds, including in particular functions that are called from Wikipedias and other MediaWiki projects to provide [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] values (or content computed from them), and Abstract Wikipedia functions that generate statements, paragraphs, and articles containing these values.

* ''What standard concepts, if any, does this align with?''
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype.

== Structure ==
'''''Wikidata geocoordinates''''' has these 4 keys, shown with proposed English labels:

* &lt;code&gt;K1/latitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K2/longitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K3/precision&lt;/code&gt;, of type [[Z19677|Rational number]], representing degrees of distance.
* &lt;code&gt;K4/globe&lt;/code&gt;, of type [[Z6091|Wikidata item reference]].  

=== Optionality ===
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations DataModel] documentation ''seems'' to imply, by the use of the word &quot;default&quot;, that &lt;code&gt;K3/precision&lt;/code&gt; and &lt;code&gt;K4/globe&lt;/code&gt; properties ''might'' be missing sometimes.  Wikifunctions does not currently have an ability to declare keys as optional.  When importing a [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] value, if either of those properties is missing, Wikifunctions will assign the value of [https://www.wikifunctions.org/view/en/Z24 Z24/void] to these keys.

=== Example values ===
TBD

{|class=&quot;wikitable&quot; style=&quot;margin:.6em 1.6em&quot;
|-
| &lt;syntaxhighlight lang=&quot;json&quot; line=&quot;line&quot;&gt;{
  &quot;type&quot;: &quot;…&quot;,
  &quot;value&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
| &lt;syntaxhighlight lang=&quot;json&quot;&gt;{
  &quot;Z1K1&quot;: &quot;Zxyz&quot;,
  &quot;ZxyzK1&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
|}

== Validator ==
The '''Wikidata geocoordinates''' validator checks that:

* The value of &lt;code&gt;K1/latitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K2/longitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K3/precision&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.
* The value of &lt;code&gt;K4/globe&lt;/code&gt; is a valid instance of [[Z6091|Wikidata item reference]]. (In most cases, per Wikidata practice, its value will be the Wikidata item reference for Q2, the Earth, which means WGS84.)

== Identity ==
For each of the above types''':'''  

* Two instances are the same if they have equal values for each of their keys. Equality of those values, in turn, is specified by the definitions &amp; documentation of their respective types.

== Converting to code ==
=== Python ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

=== JavaScript ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

== Display function ==
''How would a value of this type be displayed on Wikifunctions''

…TBD

== Read function ==
''When entering a value for this type as a string, what format should that string have?''

…TBD

== Questions ==

* The JSON encoding of a geocoordinates value includes a property &quot;altitude&quot;, but so far I've only seen null values for that property.  It doesn't seem to be documented anywhere.  I've found an old discussion indicating that there were no plans to make use of it (at least, not at that time).  Does anyone know if it has any values in Wikidata, or if it might still be used?
* Some values for &lt;code&gt;precision&lt;/code&gt;, coming back from Wikidata, end with an exponent part, like this: &lt;code&gt;&quot;precision&quot;: 2.777777777777778e-5&lt;/code&gt;.  The exponent part isn't mentioned in [https://www.mediawiki.org/wiki/Wikibase/DataModel#decimal Wikibase/DataModel], and doesn't conform to the Wikidata Object Notation given for &lt;code&gt;decimal&lt;/code&gt; there.  It would be good to know if all properties with &lt;code&gt;decimal&lt;/code&gt; values are allowed to include the exponent part, or just &lt;code&gt;precision&lt;/code&gt;.

== Alternatives ==
''In order to capture the idea presented in the summary, what alternative structures, display functions, read functions, etc. could have made sense too?''
* Regarding &lt;code&gt;K4/globe&lt;/code&gt;, it would be possible to create a &quot;lightweight enum type&quot;, but we have an estimate (from Denny) of about 20 different globes currently in use in Wikidata, and we believe that many elements would make the enum type a bit unwieldy.  Also, would like to avoid the maintenance overhead  as additional globes get used over time.

== Comments ==
''For general comments, please reply to the proposer, or use the ''Discussion'' section below.''
* {{s}} as proposer. --[[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 06:11, 23 May 2025 (UTC)
* {{s}} strong support obviously (functions can be connected to Wikidata so we should support Wikidata types) with a warning to be careful about precision and it's representation (it has been and still is a source of many problem on the Wikidata side). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 16:11, 1 June 2025 (UTC)
*
…

== Discussion ==

* A couple months ago, I drafted [[WF:Type proposals/Position on Earth]] with some idea of potential geospatial use-cases but a limited understanding of the Wikidata type. The main differences from this proposal are the lack of a &lt;code&gt;globe&lt;/code&gt; key (Earth assumed, per my suggested name), and the addition of an &lt;code&gt;altitude&lt;/code&gt; key. I think it could easily be adapted to use this type as a component, if there's a need for a position type that includes altitude. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 22:36, 23 May 2025 (UTC)
*:Thanks for mentioning!  Such an adaptation sounds reasonable to me. Let's keep this in mind.  Feel free to adapt the proposal, but it would make sense to wait until this type is published; that's expected by the end of the month. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 00:00, 4 June 2025 (UTC)
*::See also the bullet about altitude in the ''Questions ''section above. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 02:46, 5 June 2025 (UTC)
*:I would probably support altitude, but it would need to be optional. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:29, 10 June 2025 (UTC)</text>
      <sha1>thxp1y2b5d36vhcdj2ktpif29fjmi4z</sha1>
    </revision>
    <revision>
      <id>192201</id>
      <parentid>192200</parentid>
      <timestamp>2025-06-10T23:32:32Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>/* Discussion */</comment>
      <origin>192201</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7647" sha1="4id2w77cmwuqwiiun1vpqxijev4wu12" xml:space="preserve">== Summary ==
This type is modeled after Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype, and will support the import of all values of that type from Wikidata into Wikifunctions. We acknowledge and draw upon an earlier type proposal, [[Wikifunctions:Type_proposals/Wikidata_value#Geographic_coordinate|Geographic coordinate]], with similar objectives.

== Uses ==
* ''Why should this exist?''
Wikidata contains many statements with values of the [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype. A wide variety of Wikifunctions will be able to make use of these values, and this type will enable Wikifunctions to import these values from Wikidata.

* ''What kinds of functions would be created using this?''
Many kinds, including in particular functions that are called from Wikipedias and other MediaWiki projects to provide [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] values (or content computed from them), and Abstract Wikipedia functions that generate statements, paragraphs, and articles containing these values.

* ''What standard concepts, if any, does this align with?''
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] datatype.

== Structure ==
'''''Wikidata geocoordinates''''' has these 4 keys, shown with proposed English labels:

* &lt;code&gt;K1/latitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K2/longitude&lt;/code&gt;, of type [[Z19677|Rational number]].
* &lt;code&gt;K3/precision&lt;/code&gt;, of type [[Z19677|Rational number]], representing degrees of distance.
* &lt;code&gt;K4/globe&lt;/code&gt;, of type [[Z6091|Wikidata item reference]].  

=== Optionality ===
Wikidata's [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations DataModel] documentation ''seems'' to imply, by the use of the word &quot;default&quot;, that &lt;code&gt;K3/precision&lt;/code&gt; and &lt;code&gt;K4/globe&lt;/code&gt; properties ''might'' be missing sometimes.  Wikifunctions does not currently have an ability to declare keys as optional.  When importing a [https://www.mediawiki.org/wiki/Wikibase/DataModel#Geographic_locations geocoordinates] value, if either of those properties is missing, Wikifunctions will assign the value of [https://www.wikifunctions.org/view/en/Z24 Z24/void] to these keys.

=== Example values ===
TBD

{|class=&quot;wikitable&quot; style=&quot;margin:.6em 1.6em&quot;
|-
| &lt;syntaxhighlight lang=&quot;json&quot; line=&quot;line&quot;&gt;{
  &quot;type&quot;: &quot;…&quot;,
  &quot;value&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
| &lt;syntaxhighlight lang=&quot;json&quot;&gt;{
  &quot;Z1K1&quot;: &quot;Zxyz&quot;,
  &quot;ZxyzK1&quot;: &quot;…&quot;
}&lt;/syntaxhighlight&gt;
|}

== Validator ==
The '''Wikidata geocoordinates''' validator checks that:

* The value of &lt;code&gt;K1/latitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K2/longitude&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.  
* The value of &lt;code&gt;K3/precision&lt;/code&gt; is a valid ''Rational number'' in an appropriate range of values.
* The value of &lt;code&gt;K4/globe&lt;/code&gt; is a valid instance of [[Z6091|Wikidata item reference]]. (In most cases, per Wikidata practice, its value will be the Wikidata item reference for Q2, the Earth, which means WGS84.)

== Identity ==
For each of the above types''':'''  

* Two instances are the same if they have equal values for each of their keys. Equality of those values, in turn, is specified by the definitions &amp; documentation of their respective types.

== Converting to code ==
=== Python ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

=== JavaScript ===
We expect to get started by relying on the existing default conversion strategy; something more sophisticated could come later if needed.

== Display function ==
''How would a value of this type be displayed on Wikifunctions''

…TBD

== Read function ==
''When entering a value for this type as a string, what format should that string have?''

…TBD

== Questions ==

* The JSON encoding of a geocoordinates value includes a property &quot;altitude&quot;, but so far I've only seen null values for that property.  It doesn't seem to be documented anywhere.  I've found an old discussion indicating that there were no plans to make use of it (at least, not at that time).  Does anyone know if it has any values in Wikidata, or if it might still be used?
* Some values for &lt;code&gt;precision&lt;/code&gt;, coming back from Wikidata, end with an exponent part, like this: &lt;code&gt;&quot;precision&quot;: 2.777777777777778e-5&lt;/code&gt;.  The exponent part isn't mentioned in [https://www.mediawiki.org/wiki/Wikibase/DataModel#decimal Wikibase/DataModel], and doesn't conform to the Wikidata Object Notation given for &lt;code&gt;decimal&lt;/code&gt; there.  It would be good to know if all properties with &lt;code&gt;decimal&lt;/code&gt; values are allowed to include the exponent part, or just &lt;code&gt;precision&lt;/code&gt;.

== Alternatives ==
''In order to capture the idea presented in the summary, what alternative structures, display functions, read functions, etc. could have made sense too?''
* Regarding &lt;code&gt;K4/globe&lt;/code&gt;, it would be possible to create a &quot;lightweight enum type&quot;, but we have an estimate (from Denny) of about 20 different globes currently in use in Wikidata, and we believe that many elements would make the enum type a bit unwieldy.  Also, would like to avoid the maintenance overhead  as additional globes get used over time.

== Comments ==
''For general comments, please reply to the proposer, or use the ''Discussion'' section below.''
* {{s}} as proposer. --[[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 06:11, 23 May 2025 (UTC)
* {{s}} strong support obviously (functions can be connected to Wikidata so we should support Wikidata types) with a warning to be careful about precision and it's representation (it has been and still is a source of many problem on the Wikidata side). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 16:11, 1 June 2025 (UTC)
*
…

== Discussion ==

* A couple months ago, I drafted [[WF:Type proposals/Position on Earth]] with some idea of potential geospatial use-cases but a limited understanding of the Wikidata type. The main differences from this proposal are the lack of a &lt;code&gt;globe&lt;/code&gt; key (Earth assumed, per my suggested name), and the addition of an &lt;code&gt;altitude&lt;/code&gt; key. I think it could easily be adapted to use this type as a component, if there's a need for a position type that includes altitude. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 22:36, 23 May 2025 (UTC)
*:Thanks for mentioning!  Such an adaptation sounds reasonable to me. Let's keep this in mind.  Feel free to adapt the proposal, but it would make sense to wait until this type is published; that's expected by the end of the month. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 00:00, 4 June 2025 (UTC)
*::See also the bullet about altitude in the ''Questions ''section above. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 02:46, 5 June 2025 (UTC)
*:I would probably support altitude, but it would need to be optional. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:29, 10 June 2025 (UTC)

*IMO a lightweight enum is right for globe, even if it needs occasional maintenance to add globes over time. The community will have rights to do this maintenance eventually. Enum will help enforce constraints on the values, and will help guide editors dropdown choices. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:32, 10 June 2025 (UTC)</text>
      <sha1>4id2w77cmwuqwiiun1vpqxijev4wu12</sha1>
    </revision>
  </page>
  <page>
    <title>Wikifunctions:Project chat/Archive/2025/05</title>
    <ns>4</ns>
    <id>56771</id>
    <revision>
      <id>192215</id>
      <parentid>191341</parentid>
      <timestamp>2025-06-11T03:08:07Z</timestamp>
      <contributor>
        <username>SpBot</username>
        <id>978</id>
      </contributor>
      <minor />
      <comment>archiving 1 section from [[Wikifunctions:Project chat]] (after section [[Wikifunctions:Project chat/Archive/2025/05#Fold_and_reduce_swapped|Fold_and_reduce_swapped]])</comment>
      <origin>192215</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="11693" sha1="7429unn159tm1kfv0stpn9xaa66j1rz" xml:space="preserve">{{Talkarchive}}

== Update language tag of &quot;Simple English&quot; (Z1124) ==

Please update the language tag of [[Z1124]] to &quot;&lt;code&gt;en-simple&lt;/code&gt;&quot; as the variant subtag &quot;&lt;code&gt;simple&lt;/code&gt;&quot; is already registered in the Language Subtag Registry: https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry . -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 07:03, 13 May 2025 (UTC)

: @[[User:Winston Sung|Winston Sung]]: This can't be done until MediaWiki drops use of the tag, sorry. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 18:42, 14 May 2025 (UTC)

: @[[User:Jdforrester (WMF)|Jdforrester (WMF)]]:
: MediaWiki [https://codesearch.wmcloud.org/search/?q=en-x-simple no longer use &lt;code&gt;en-x-simple&lt;/code&gt;] but [https://codesearch.wmcloud.org/search/?q=en-simple already use &lt;code&gt;en-simple&lt;/code&gt; instead]. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 01:16, 15 May 2025 (UTC)

:: @[[User:Winston Sung|Winston Sung]]: Ah, interesting, whoever did those changes didn't file a task with us. Will file one. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 11:36, 15 May 2025 (UTC)

: Just note it here: the Phabricator task filed by @[[User:Jdforrester (WMF)|Jdforrester (WMF)]] is [[phab:T394401]]. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 11:44, 15 May 2025 (UTC)

: :&lt;small&gt;This section was archived on a request by: -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 11:55, 16 May 2025 (UTC)&lt;/small&gt;

== Edit request - broken implementation ==

Please see [[:Talk:Z19164#Edit request: implementation broken]]. I found a bug and wish to make a change, but I do not have permissions to do so. Thanks. --[[User:WrenFalcon|WrenFalcon]] ([[User talk:WrenFalcon|talk]]) 06:23, 15 May 2025 (UTC)

:Thanks. It looks like this is now resolved. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:32, 16 May 2025 (UTC)
::&lt;small&gt;This section was archived on a request by: [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:32, 16 May 2025 (UTC)&lt;/small&gt;

== Wikifunctions &amp; Abstract Wikipedia Newsletter #200 is out: Abstract Wikipedia is a MacArthur 100&amp;Change finalist ==

There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we announce that we reached the final stage of a grant competition, we introduce our next big conversation about where the content of Abstract Wikipedia will be located, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]!

Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1746466200 May 5, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]).

Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:57, 1 May 2025 (UTC)
&lt;!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&amp;oldid=28628447 --&gt;
:&lt;small&gt;This section was archived on a request by: [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:57, 23 May 2025 (UTC)&lt;/small&gt;

== Change to translatewiki.net-like/Miraheze-Meta-like page translation target languages ==

Currently, the page translation target language configuration on Wikifunctions were [[gerrit:plugins/gitiles/operations/mediawiki-config/+/a4d0b2f22e0270ddd12d5a07ae78efde47a3566e/wmf-config/InitialiseSettings.php#7422|inherited from the &quot;language converter page translation model&quot;]].

However, this actually created several problems including the broken main page with malfunctioned language converter tags ( [https://www.wikifunctions.org/wiki/Wikifunctions:Main_Page?uselang=zh-hans zh-Hans] , [https://www.wikifunctions.org/wiki/Wikifunctions:Main_Page?uselang=zh-hant zh-Hant] , [https://www.wikifunctions.org/wiki/Wikifunctions:Main_Page?uselang=zh-hk zh-Hant-HK] ). More breakages could be found on [[phab:T328838]].

As Wikifunctions haven't build up the large &quot;tech debt&quot;, I would like to propose to use the [[gerrit:plugins/gitiles/translatewiki/+/e61ec8f4d0d342d793cbb415ca50536901ed2393/mw-config/TranslateSettings.php#172|&quot;translatewiki page translation model&quot;]]/[https://github.com/miraheze/mw-config/blob/2f622587bbb5b78933ef3e940d3141edb4928df5/LocalSettings.php#L5911 &quot;Miraheze Meta page translation model&quot;] instead [[gerrit:1143697|on Wikifunctions]].

This would also make the page translation target languages align with the ZObjects translation target languages. 

-- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 06:58, 13 May 2025 (UTC)

: @[[User:Winston Sung|Winston Sung]]: This sounds reasonable as an approach, thank you for flagging. Are there any community members here doing wikitext translation into multi-script languages who might have a view? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 18:46, 14 May 2025 (UTC)

: Pinging @[[User:0xDeadbeef|0xDeadbeef]], @[[User:LowensteinYang|LowensteinYang]], @[[User:MilkyDefer|MilkyDefer]], @[[User:S8321414|S8321414]], @[[User:Stevenliuyi|Stevenliuyi]], @[[User:Supaplex|Supaplex]], @[[User:星海子|星海子]], @[[User:魔琴|魔琴]]. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 02:58, 15 May 2025 (UTC)

: Cannot understand the technical configs and details. Just to say fixing it would be nice. [[User:魔琴|魔琴]] ([[User talk:魔琴|talk]]) 03:08, 15 May 2025 (UTC)

: Please explain in detail about these translation models and their differences. I only see some configurations in your links and cannot grasp their differences. [[User:MilkyDefer|&lt;span style=&quot;color:#09C&quot;&gt;Milky&lt;/span&gt;]][[User talk:MilkyDefer|'''&lt;span style=&quot;color:#F09&quot;&gt;Defer&lt;/span&gt;''']] 03:39, 15 May 2025 (UTC)

: @[[User:MilkyDefer|MilkyDefer]]:
: Below are examples of the proposed translation model.
:* https://translatewiki.net/wiki/Special:Translate?group=page-Project%3AAbout&amp;action=page&amp;language=zh-hans&amp;filter=
:* https://translatewiki.net/wiki/Special:Translate?group=page-Project%3AAbout&amp;action=page&amp;language=zh-hant&amp;filter=
:* https://meta.miraheze.org/wiki/Special:Translate?group=page-Miraheze+Meta&amp;action=page&amp;language=zh-hans&amp;filter=
:* https://meta.miraheze.org/wiki/Special:Translate?group=page-Miraheze+Meta&amp;action=page&amp;language=zh-hant&amp;filter=
: Note: &quot;translatewiki page translation model&quot;/&quot;Miraheze Meta page translation model&quot; refer to the same translation model.
: -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 03:44, 15 May 2025 (UTC)
::Correct me if I am misunderstanding sth. The old configuration only has a blanket zh. The new configuration has zh-hans (for cn, my, sg), zh-hant (for tw) and zh-hk (for mo, hk). Is that right? [[User:MilkyDefer|&lt;span style=&quot;color:#09C&quot;&gt;Milky&lt;/span&gt;]][[User talk:MilkyDefer|'''&lt;span style=&quot;color:#F09&quot;&gt;Defer&lt;/span&gt;''']] 11:49, 16 May 2025 (UTC)
::That's correct for the zh/zh-* part. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 11:54, 16 May 2025 (UTC)
:If this issue can be fixed by changing translation model, I will {{Support}}--[[User:S8321414|S8321414]] ([[User talk:S8321414|talk]]) 03:53, 15 May 2025 (UTC)

: {{Done}} in [https://schedule-deployment.toolforge.org/window/1748502000 Thursday, May 29, 2025 UTC morning backport window].

: :&lt;small&gt;This section was archived on a request by: -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 08:16, 29 May 2025 (UTC)&lt;/small&gt;

== Error in &quot;is Jalali leap year&quot; ==

Hi!

The correct implementation for this function should consider 4 as a leap year not 5. Otherwise the algorithm is correct. So it should be:
&lt;syntaxhighlight lang=&quot;python&quot;&gt;
def Z11011(Z11011K1):
	year = int(Z11011K1)
	if(year &lt;= 5):
		  mod = year % 4;
		  return (mod == 0);
	is_leap_year = (year % 33) in [1, 5, 9, 13, 17, 22, 26, 30]
	return is_leap_year
&lt;/syntaxhighlight&gt;I didn't have permission to edit. How can I edit functions? Do I also need permission for function creation? [[User:Niyumard|Niyumard]] ([[User talk:Niyumard|talk]]) 12:02, 3 May 2025 (UTC)

:I've just disconnected the Python implementation, so that you van edit it. An advice: create a testcase that the current implementation fails, so it's evident that there is a bug that should be corrected. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:05, 3 May 2025 (UTC)
::I fixed the python code and added the test case that fails the JavaScript code. Can I disconnect the javascript code myself, or connect my own test cases or not, is there any guide for newbies? [[User:Niyumard|Niyumard]] ([[User talk:Niyumard|talk]]) 12:20, 3 May 2025 (UTC)
:::I've disconnected the js implementation.
:::Only Functioneers can connect and disconnect implementations and testcases, but everyone can create functions, testcases and implementations. This is described in the page [[Wikifunctions:Functioneers]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:26, 3 May 2025 (UTC)
::::I find it odd given the open nature of other wikis.
::::Done! And thanks a lot for your prompt reaction. Is this the correct place for asking Functioneers to connect and disconnect, or should I take my requests to some other place next time? [[User:Niyumard|Niyumard]] ([[User talk:Niyumard|talk]]) 12:32, 3 May 2025 (UTC)
:::::It's mainly for security concerns (it's not wise to freely execute code uploaded by anyone). For now there is not a place specifically for requesting connections or disconnections (at least not that I am aware of), the closest page is [[Wikifunctions:Community portal]]. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:41, 3 May 2025 (UTC)
::::::Makes sense. Thanks! [[User:Niyumard|Niyumard]] ([[User talk:Niyumard|talk]]) 12:49, 3 May 2025 (UTC)

== Problems with evaluations: fixes are coming ==

Hi all, a quick update on the situation about evaluations not properly working in all cases, raised in the Telegram group. We identified the problem, and have been working in the last couple of weeks to solve it.

More specifically, you can find more info at [[phab:T393130]] (some fixes already merged that should come up today, others will come in the next weeks), at [[phab:T392905]] (fix already merged, should be up today), and at [[phab:T393152]] (fix already merged, should be already up). We're also following [[phab:T391435]] and [[phab:T392905]].

If you have more malfunctions to report, please let me know here. Also, you can freely comment the Phab tickets to discuss directly with the engineers. Thanks for your attention! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:18, 7 May 2025 (UTC)

== Fold and reduce swapped ==

Per my comments on [[Talk:Z876#Naming]] and [[WF:Catalogue/List operations#In-built functions with list outputs]],
I believe these functions' names are reversed from the conventional ones. Are there any FP greybeards who can confirm? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:22, 11 May 2025 (UTC)

:I was involved in the construction of some of these, following suggestions from others. I have no particular expertise in the nomenclature, so may well have transmitted naming errors. Feel free to rename if others confirm your suggestion. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:44, 11 May 2025 (UTC)</text>
      <sha1>7429unn159tm1kfv0stpn9xaa66j1rz</sha1>
    </revision>
  </page>
  <page>
    <title>Z24731</title>
    <ns>0</ns>
    <id>57143</id>
    <revision>
      <id>192239</id>
      <parentid>188293</parentid>
      <timestamp>2025-06-11T06:18:27Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>switching to valid rational in case that is tripping python</comment>
      <origin>192239</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="2199" sha1="aj5c5zss2rl8burwof253jz55y3osb7" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z24731&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z20&quot;,
        &quot;Z20K1&quot;: &quot;Z12864&quot;,
        &quot;Z20K2&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z12864&quot;,
            &quot;Z12864K1&quot;: [
                &quot;Z40&quot;,
                {
                    &quot;Z1K1&quot;: &quot;Z40&quot;,
                    &quot;Z40K1&quot;: &quot;Z41&quot;
                },
                {
                    &quot;Z1K1&quot;: &quot;Z40&quot;,
                    &quot;Z40K1&quot;: &quot;Z42&quot;
                }
            ],
            &quot;Z12864K2&quot;: [
                &quot;Z19677&quot;,
                {
                    &quot;Z1K1&quot;: &quot;Z19677&quot;,
                    &quot;Z19677K1&quot;: {
                        &quot;Z1K1&quot;: &quot;Z16659&quot;,
                        &quot;Z16659K1&quot;: &quot;Z16660&quot;
                    },
                    &quot;Z19677K2&quot;: {
                        &quot;Z1K1&quot;: &quot;Z13518&quot;,
                        &quot;Z13518K1&quot;: &quot;1&quot;
                    },
                    &quot;Z19677K3&quot;: {
                        &quot;Z1K1&quot;: &quot;Z13518&quot;,
                        &quot;Z13518K1&quot;: &quot;1&quot;
                    }
                },
                {
                    &quot;Z1K1&quot;: &quot;Z19677&quot;,
                    &quot;Z19677K1&quot;: {
                        &quot;Z1K1&quot;: &quot;Z16659&quot;,
                        &quot;Z16659K1&quot;: &quot;Z16660&quot;
                    },
                    &quot;Z19677K2&quot;: {
                        &quot;Z1K1&quot;: &quot;Z13518&quot;,
                        &quot;Z13518K1&quot;: &quot;1&quot;
                    },
                    &quot;Z19677K3&quot;: {
                        &quot;Z1K1&quot;: &quot;Z13518&quot;,
                        &quot;Z13518K1&quot;: &quot;2&quot;
                    }
                }
            ]
        },
        &quot;Z20K3&quot;: {
            &quot;Z1K1&quot;: &quot;Z7&quot;,
            &quot;Z7K1&quot;: &quot;Z844&quot;,
            &quot;Z844K2&quot;: {
                &quot;Z1K1&quot;: &quot;Z40&quot;,
                &quot;Z40K1&quot;: &quot;Z41&quot;
            }
        }
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;equal length lists of Boolean and Rational&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;
        ]
    }
}</text>
      <sha1>aj5c5zss2rl8burwof253jz55y3osb7</sha1>
    </revision>
  </page>
  <page>
    <title>Wikifunctions:Status updates/pt-br</title>
    <ns>4</ns>
    <id>57415</id>
    <revision>
      <id>192219</id>
      <parentid>192172</parentid>
      <timestamp>2025-06-11T06:09:01Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Bem-vinda, Sharvani!&quot;</comment>
      <origin>192219</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13763" sha1="sqc3s0fgluon8mueneotaad8q90xc01" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: New Type: Integers&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: New Type: Igbo calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: New Type: Sign&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: A single singular or a plurality of plurals?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: New Type: Gregorian calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Call for Functions: Spell out the number!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Flagship type for enumerations: Months of the Gregorian calendar&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Team meeting and Quarterly plan&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>sqc3s0fgluon8mueneotaad8q90xc01</sha1>
    </revision>
    <revision>
      <id>192221</id>
      <parentid>192219</parentid>
      <timestamp>2025-06-11T06:09:28Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Reunião da equipe e plano trimestral&quot;</comment>
      <origin>192221</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13713" sha1="j18i2802hapjey0hp4ch64rjf0es2y5" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: New Type: Integers&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: New Type: Igbo calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: New Type: Sign&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: A single singular or a plurality of plurals?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: New Type: Gregorian calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Call for Functions: Spell out the number!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Flagship type for enumerations: Months of the Gregorian calendar&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>j18i2802hapjey0hp4ch64rjf0es2y5</sha1>
    </revision>
    <revision>
      <id>192223</id>
      <parentid>192221</parentid>
      <timestamp>2025-06-11T06:10:26Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Tipo principal para enumerações: Meses do calendário gregoriano&quot;</comment>
      <origin>192223</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13659" sha1="rmfii43twpseki555t19i6w9lnso7oh" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: New Type: Integers&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: New Type: Igbo calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: New Type: Sign&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: A single singular or a plurality of plurals?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: New Type: Gregorian calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Call for Functions: Spell out the number!&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Tipo principal para enumerações: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>rmfii43twpseki555t19i6w9lnso7oh</sha1>
    </revision>
    <revision>
      <id>192225</id>
      <parentid>192223</parentid>
      <timestamp>2025-06-11T06:11:12Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Chamada para Funções: Soletre o número!&quot;</comment>
      <origin>192225</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13604" sha1="cmqp8kyhbez8k2a5hrs5zx596hsseh2" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: New Type: Integers&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: New Type: Igbo calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: New Type: Sign&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: A single singular or a plurality of plurals?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: New Type: Gregorian calendar months&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Chamada para Funções: Soletre o número!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Tipo principal para enumerações: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>cmqp8kyhbez8k2a5hrs5zx596hsseh2</sha1>
    </revision>
    <revision>
      <id>192227</id>
      <parentid>192225</parentid>
      <timestamp>2025-06-11T06:12:12Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Novo Tipo: Meses do calendário gregoriano&quot;</comment>
      <origin>192227</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13555" sha1="dhdksjk7r7lt7jdni6lvwi1hhdt8dj3" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: New Type: Integers&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: New Type: Igbo calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: New Type: Sign&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: A single singular or a plurality of plurals?&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Chamada para Funções: Soletre o número!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Tipo principal para enumerações: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>dhdksjk7r7lt7jdni6lvwi1hhdt8dj3</sha1>
    </revision>
    <revision>
      <id>192229</id>
      <parentid>192227</parentid>
      <timestamp>2025-06-11T06:12:51Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Um singular na singularidade ou uma pluralidade de plurais?&quot;</comment>
      <origin>192229</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13514" sha1="brj6dhezn0141vw6p6bso0bzpituevs" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: New Type: Integers&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: New Type: Igbo calendar months&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: New Type: Sign&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: Um singular na singularidade ou uma pluralidade de plurais?
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Chamada para Funções: Soletre o número!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Tipo principal para enumerações: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>brj6dhezn0141vw6p6bso0bzpituevs</sha1>
    </revision>
    <revision>
      <id>192231</id>
      <parentid>192229</parentid>
      <timestamp>2025-06-11T06:13:25Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Novo Tipo: Sinal&quot;</comment>
      <origin>192231</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13460" sha1="2bp43k6d9rdvzkw36wyr5nsyqmotn01" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: New Type: Integers&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: New Type: Igbo calendar months&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: Novo Tipo: Sinal
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: Um singular na singularidade ou uma pluralidade de plurais?
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Chamada para Funções: Soletre o número!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Tipo principal para enumerações: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>2bp43k6d9rdvzkw36wyr5nsyqmotn01</sha1>
    </revision>
    <revision>
      <id>192233</id>
      <parentid>192231</parentid>
      <timestamp>2025-06-11T06:13:45Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Novo Tipo: Meses do calendário igbo&quot;</comment>
      <origin>192233</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13410" sha1="gfochqddqauppzzx3k2gvc71qkp8lm3" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: New Type: Integers&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário igbo
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: Novo Tipo: Sinal
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: Um singular na singularidade ou uma pluralidade de plurais?
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Chamada para Funções: Soletre o número!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Tipo principal para enumerações: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>gfochqddqauppzzx3k2gvc71qkp8lm3</sha1>
    </revision>
    <revision>
      <id>192235</id>
      <parentid>192233</parentid>
      <timestamp>2025-06-11T06:13:57Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Novo Tipo: Inteiros&quot;</comment>
      <origin>192235</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13355" sha1="n444a28ewu5hh0xpnp1pvqipjh1zmtl" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
== Newsletters ==
&lt;/div&gt;
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: Novo Tipo: Inteiros
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário igbo
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: Novo Tipo: Sinal
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: Um singular na singularidade ou uma pluralidade de plurais?
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Chamada para Funções: Soletre o número!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Tipo principal para enumerações: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>n444a28ewu5hh0xpnp1pvqipjh1zmtl</sha1>
    </revision>
    <revision>
      <id>192237</id>
      <parentid>192235</parentid>
      <timestamp>2025-06-11T06:14:22Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;== Boletins informativos ==&quot;</comment>
      <origin>192237</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13340" sha1="dhkw74j21y8vg75sjwbvgxm6sxutyn8" xml:space="preserve">&lt;languages/&gt;
{{shortcut|WF:SU}}{{notice|1='''[[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|Inscreva-se]]''' para receber notificações curtas via MassMessage na sua wiki preferida para cada nova edição}}
{{Wikifunctions updates
| prevlabel = Atualização anterior
| prev = 2024-02-01
| nextlabel = Última atualização
| next = 2025-06-06
}}
Muita coisa está acontecendo em torno do Wikifunctions e da Wikipédia Abstrata. Esta é a página onde nossas atualizações são postadas, incluindo a “[[Special:MyLanguage/WF:function of the Week|Função da Semana]]”.

Também é possível assinar o [[:m:Global message delivery/Targets/Wikifunctions &amp; Abstract Wikipedia|boletim informativo na wiki]] para que toda edição dele seja enviada para a sua página de discussão ou para a esplanada do seu projeto.

&lt;span id=&quot;Newsletters&quot;&gt;&lt;/span&gt;
== Boletins informativos ==
&lt;!--&lt;nowiki&gt; Newsletter entry template:
* &lt;translate&gt;&lt;tvar name=&quot;1&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-??-??|2025-??-??]]&lt;/bdi&gt;&lt;/tvar&gt;: Title&lt;/translate&gt;

NOTE: Remember to also update the &quot;next =&quot; date at the top of this page.
&lt;/nowiki&gt;--&gt;
=== 2025 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-06-06|2025-06-06]]&lt;/bdi&gt;: Where will Abstract Content go?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-29|2025-05-29]]&lt;/bdi&gt;: Rolling out to five Wiktionaries; Calculating with today's date&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-23|2025-05-23]]&lt;/bdi&gt;: Ongoing consultation about the Location for Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-15|2025-05-15]]&lt;/bdi&gt;: Location of Abstract Content&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-05-09|2025-05-09]]&lt;/bdi&gt;: Abstract Wikipedia and the Wikimedia AI Strategy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-30|2025-04-30]]&lt;/bdi&gt;: Abstract Wikipedia is a MacArthur 100&amp;Change finalist&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-25|2025-04-25]]&lt;/bdi&gt;: Welcome, Gregory!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-16|2025-04-16]]&lt;/bdi&gt;: Wikifunctions integrated in Dagbani - and Wikifunctions; and the date of Easter&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-11|2025-04-11]]&lt;/bdi&gt;: Quarter in review&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-04-05|2025-04-05]]&lt;/bdi&gt;: Quarterly Planning for April–June 2025; We are looking for a Senior Product Manager&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-28|2025-03-28]]&lt;/bdi&gt;: It's about time&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-20|2025-03-20]]&lt;/bdi&gt;: Wikidata-based simple enumerations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-15|2025-03-15]]&lt;/bdi&gt;: Upcoming NLG meeting, Recent Changes in the software&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-03-07|2025-03-07]]&lt;/bdi&gt;: Recent Changes in the software, Recording of Volunteer’s Corner, and talks in London&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-26|2025-02-26]]&lt;/bdi&gt;: From things to words&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-19|2025-02-19]]&lt;/bdi&gt;: A proposal for types per language and part of speech&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-13|2025-02-13]]&lt;/bdi&gt;: Restricting the World, redux&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-02-06|2025-02-06]]&lt;/bdi&gt;: Invitation to the Natural Language Generation Special Interest Group&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-29|2025-01-29]]&lt;/bdi&gt;: With 2000 Functions into the new year: time for stats&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-22|2025-01-22]]&lt;/bdi&gt;: Welcome, David! Naming conventions recommendations&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2025-01-15|2025-01-15]]&lt;/bdi&gt;: Happy Wikipedia day! Quarterly planning&lt;/span&gt;

=== 2024 ===
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-19|2024-12-19]]&lt;/bdi&gt;: Function of the Week: age; Intros for year articles; New Type: Floating-point number&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-12-12|2024-12-12]]&lt;/bdi&gt;: Sketching a path to Abstract Wikipedia; Team offsite in Lisbon; and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-27|2024-11-27]]&lt;/bdi&gt;: WordGraph release; New Special page: list functions by tests; new type for day of the year, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-21|2024-11-21]]&lt;/bdi&gt;: New special page for missing labels, new type for Gregorian years, and much more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-13|2024-11-13]]&lt;/bdi&gt;: New Type: Rational number; Documentation on Wikidata-based types; and more&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-07|2024-11-07]]&lt;/bdi&gt;: The Dream of a Universal Language&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-11-01|2024-11-01]]&lt;/bdi&gt;: Rewriting the backend&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-25|2024-10-25]]&lt;/bdi&gt;: Our goal for this Quarter: Agreement&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-17|2024-10-17]]&lt;/bdi&gt;: What could abstract content look like?&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-11|2024-10-11]]&lt;/bdi&gt;: Wikidata Lexemes in Wikifunctions are coming soon&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-10-02|2024-10-02]]&lt;/bdi&gt;: Focus topic: Food&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-26|2024-09-26]]&lt;/bdi&gt;: Quarterly planning for October–December 2024; Presentation at Celtic Knot tomorrow&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-20|2024-09-20]]&lt;/bdi&gt;: Introducing focus topic areas&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-13|2024-09-13]]&lt;/bdi&gt;: Dagbani Wikipedia will be our first wiki for Wikifunctions integration&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-09-06|2024-09-06]]&lt;/bdi&gt;: Volunteer's corner and other updates&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-29|2024-08-29]]&lt;/bdi&gt;:  Limits on Name and Description Lengths&lt;/span&gt; 
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-23|2024-08-23]]&lt;/bdi&gt;: WasmEdge, Now 300ms Less Edgy&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-16|2024-08-16]]&lt;/bdi&gt;: Wikimania 2024 edition&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-08-02|2024-08-02]]&lt;/bdi&gt;: Revamping our 'About' widget&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-26|2024-07-26]]&lt;/bdi&gt;: Wikimania 2024 coming soon!&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-18|2024-07-18]]&lt;/bdi&gt;: Research report on integrating Wikifunctions from Wikipedia&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-10|2024-07-10]]&lt;/bdi&gt;: Type proposals for accessing Lexemes&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-07-03|2024-07-03]]&lt;/bdi&gt;: Quarterly planning&lt;/span&gt;
* &lt;span lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;&lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-26|2024-06-26]]&lt;/bdi&gt;: Welcome, Daphne!&lt;/span&gt;
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-20|2024-06-20]]&lt;/bdi&gt;: Novo Tipo: Inteiros
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-13|2024-06-13]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário igbo
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-06-06|2024-06-06]]&lt;/bdi&gt;: Novo Tipo: Sinal
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-30|2024-05-30]]&lt;/bdi&gt;: Um singular na singularidade ou uma pluralidade de plurais?
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-22|2024-05-22]]&lt;/bdi&gt;: Novo Tipo: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-15|2024-05-15]]&lt;/bdi&gt;: Chamada para Funções: Soletre o número!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-10|2024-05-10]]&lt;/bdi&gt;: Tipo principal para enumerações: Meses do calendário gregoriano
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-05-03|2024-05-03]]&lt;/bdi&gt;: Reunião da equipe e plano trimestral
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-19|2024-04-19]]&lt;/bdi&gt;: Bem-vinda, Sharvani!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-11|2024-04-11]]&lt;/bdi&gt;: Nova API para realizar chamadas à Wikifunctions, e celebração das mil funções
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-04-03|2024-04-03]]&lt;/bdi&gt;: Atualização de Produto sobre o Dif e Futuras Melhorias na API
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-28|2024-03-28]]&lt;/bdi&gt;: A criação de testes está muito mais fácil!
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-21|2024-03-21]]&lt;/bdi&gt;: A caminho da internacionalização dos números
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-13|2024-03-13]]&lt;/bdi&gt;: Sobre identidade
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-03-07|2024-03-07]]&lt;/bdi&gt;: Apresentando nosso segundo novo tipo: Números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-28|2024-02-28]]&lt;/bdi&gt;: Proposta de tipo para números naturais
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-22|2024-02-22]]&lt;/bdi&gt;: Atualizando o modelo de função
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-14|2024-02-14]]&lt;/bdi&gt;: Semana de consertos
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-07|2024-02-07]]&lt;/bdi&gt;: Planejamento trimestral. Obrigado, Nick! Função da semana: é permutação
* &lt;bdi dir=&quot;ltr&quot;&gt;[[Special:MyLanguage/Wikifunctions:Status updates/2024-02-01|2024-02-01]]&lt;/bdi&gt;: O modo imperativo em igbo!

&lt;span id=&quot;Before_February_2024&quot;&gt;&lt;/span&gt;
=== Anteriores a fevereiro de 2024 ===

Todas as atualizações deste período estão [[:m:Special:MyLanguage/Abstract Wikipedia/Updates|disponíveis no Meta-Wiki]].

[[Category:Status updates{{#translation:}}| ]]</text>
      <sha1>dhkw74j21y8vg75sjwbvgxm6sxutyn8</sha1>
    </revision>
  </page>
  <page>
    <title>Z25065</title>
    <ns>0</ns>
    <id>58367</id>
    <revision>
      <id>192202</id>
      <parentid>192173</parentid>
      <timestamp>2025-06-10T23:51:18Z</timestamp>
      <contributor>
        <username>99of9</username>
        <id>1622</id>
      </contributor>
      <comment>restore overwrite</comment>
      <origin>192202</origin>
      <model>zobject</model>
      <format>text/plain</format>
      <text bytes="3145" sha1="b54010z83tkbaz022va9hphe1nt9kcw" xml:space="preserve">{
    &quot;Z1K1&quot;: &quot;Z2&quot;,
    &quot;Z2K1&quot;: {
        &quot;Z1K1&quot;: &quot;Z6&quot;,
        &quot;Z6K1&quot;: &quot;Z25065&quot;
    },
    &quot;Z2K2&quot;: {
        &quot;Z1K1&quot;: &quot;Z8&quot;,
        &quot;Z8K1&quot;: [
            &quot;Z17&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z14294&quot;,
                &quot;Z17K2&quot;: &quot;Z25065K1&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;functions to choose from&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1787&quot;,
                            &quot;Z11K2&quot;: &quot;funzioni tra cui scegliere&quot;
                        }
                    ]
                }
            },
            {
                &quot;Z1K1&quot;: &quot;Z17&quot;,
                &quot;Z17K1&quot;: &quot;Z60&quot;,
                &quot;Z17K2&quot;: &quot;Z25065K2&quot;,
                &quot;Z17K3&quot;: {
                    &quot;Z1K1&quot;: &quot;Z12&quot;,
                    &quot;Z12K1&quot;: [
                        &quot;Z11&quot;,
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1002&quot;,
                            &quot;Z11K2&quot;: &quot;language to choose best function for&quot;
                        },
                        {
                            &quot;Z1K1&quot;: &quot;Z11&quot;,
                            &quot;Z11K1&quot;: &quot;Z1787&quot;,
                            &quot;Z11K2&quot;: &quot;lingua&quot;
                        }
                    ]
                }
            }
        ],
        &quot;Z8K2&quot;: &quot;Z8&quot;,
        &quot;Z8K3&quot;: [
            &quot;Z20&quot;,
            &quot;Z25067&quot;
        ],
        &quot;Z8K4&quot;: [
            &quot;Z14&quot;
        ],
        &quot;Z8K5&quot;: &quot;Z25065&quot;
    },
    &quot;Z2K3&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;select a function based on language with fallbacks&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1787&quot;,
                &quot;Z11K2&quot;: &quot;seleziona una funz. in base alla lingua, fallback&quot;
            }
        ]
    },
    &quot;Z2K4&quot;: {
        &quot;Z1K1&quot;: &quot;Z32&quot;,
        &quot;Z32K1&quot;: [
            &quot;Z31&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z31&quot;,
                &quot;Z31K1&quot;: &quot;Z1787&quot;,
                &quot;Z31K2&quot;: [
                    &quot;Z6&quot;,
                    &quot;seleziona una funzione in base alla lingua con fallback&quot;
                ]
            }
        ]
    },
    &quot;Z2K5&quot;: {
        &quot;Z1K1&quot;: &quot;Z12&quot;,
        &quot;Z12K1&quot;: [
            &quot;Z11&quot;,
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1002&quot;,
                &quot;Z11K2&quot;: &quot;Returns a function associated with the requested language on a configuration list, or similar languages from Z24144. This is a more robust version of Z14310.&quot;
            },
            {
                &quot;Z1K1&quot;: &quot;Z11&quot;,
                &quot;Z11K1&quot;: &quot;Z1787&quot;,
                &quot;Z11K2&quot;: &quot;Restituisce una funzione associata alla lingua richiesta o simile in una lista di configurazione. È una versione più robusta di Z14310.&quot;
            }
        ]
    }
}</text>
      <sha1>b54010z83tkbaz022va9hphe1nt9kcw</sha1>
    </revision>
  </page>
  <page>
    <title>User:MagicDippyEgg</title>
    <ns>2</ns>
    <id>58384</id>
    <revision>
      <id>192204</id>
      <timestamp>2025-06-11T00:35:05Z</timestamp>
      <contributor>
        <username>MagicDippyEgg</username>
        <id>13442</id>
      </contributor>
      <comment>just creating my page</comment>
      <origin>192204</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="11" sha1="17blrxomrhaob95awbn7iuqcxatt8sw" xml:space="preserve">Hello World</text>
      <sha1>17blrxomrhaob95awbn7iuqcxatt8sw</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/21/pt-br</title>
    <ns>1198</ns>
    <id>58385</id>
    <revision>
      <id>192218</id>
      <timestamp>2025-06-11T06:08:59Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Bem-vinda, Sharvani!&quot;</comment>
      <origin>192218</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="24" sha1="nbs46fzleyqe2u78vlq9x78fieouq73" xml:space="preserve">$1: Bem-vinda, Sharvani!</text>
      <sha1>nbs46fzleyqe2u78vlq9x78fieouq73</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/22/pt-br</title>
    <ns>1198</ns>
    <id>58386</id>
    <revision>
      <id>192220</id>
      <timestamp>2025-06-11T06:09:27Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Reunião da equipe e plano trimestral&quot;</comment>
      <origin>192220</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="41" sha1="7q5d9uj2tfwfzmb742gjq15u1tt659z" xml:space="preserve">$1: Reunião da equipe e plano trimestral</text>
      <sha1>7q5d9uj2tfwfzmb742gjq15u1tt659z</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/23/pt-br</title>
    <ns>1198</ns>
    <id>58387</id>
    <revision>
      <id>192222</id>
      <timestamp>2025-06-11T06:10:25Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Tipo principal para enumerações: Meses do calendário gregoriano&quot;</comment>
      <origin>192222</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="70" sha1="3v44itrwmqqqh55y2g1k65dd4wpyer5" xml:space="preserve">$1: Tipo principal para enumerações: Meses do calendário gregoriano</text>
      <sha1>3v44itrwmqqqh55y2g1k65dd4wpyer5</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/24/pt-br</title>
    <ns>1198</ns>
    <id>58388</id>
    <revision>
      <id>192224</id>
      <timestamp>2025-06-11T06:11:11Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Chamada para Funções: Soletre o número!&quot;</comment>
      <origin>192224</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="46" sha1="dyovnj6qvdriw3gn40w0bpd9iaslloz" xml:space="preserve">$1: Chamada para Funções: Soletre o número!</text>
      <sha1>dyovnj6qvdriw3gn40w0bpd9iaslloz</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/25/pt-br</title>
    <ns>1198</ns>
    <id>58389</id>
    <revision>
      <id>192226</id>
      <timestamp>2025-06-11T06:12:11Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Novo Tipo: Meses do calendário gregoriano&quot;</comment>
      <origin>192226</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="46" sha1="1m3obe1wd03jly2ved1nh60wunz68jj" xml:space="preserve">$1: Novo Tipo: Meses do calendário gregoriano</text>
      <sha1>1m3obe1wd03jly2ved1nh60wunz68jj</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/26/pt-br</title>
    <ns>1198</ns>
    <id>58390</id>
    <revision>
      <id>192228</id>
      <timestamp>2025-06-11T06:12:50Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Um singular na singularidade ou uma pluralidade de plurais?&quot;</comment>
      <origin>192228</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="63" sha1="knomjahxvcowz1405hdewjzcmxw1n88" xml:space="preserve">$1: Um singular na singularidade ou uma pluralidade de plurais?</text>
      <sha1>knomjahxvcowz1405hdewjzcmxw1n88</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/27/pt-br</title>
    <ns>1198</ns>
    <id>58391</id>
    <revision>
      <id>192230</id>
      <timestamp>2025-06-11T06:13:24Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Novo Tipo: Sinal&quot;</comment>
      <origin>192230</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20" sha1="f0i9air5awy1y1ykx02tvzbbjpomn0s" xml:space="preserve">$1: Novo Tipo: Sinal</text>
      <sha1>f0i9air5awy1y1ykx02tvzbbjpomn0s</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/29/pt-br</title>
    <ns>1198</ns>
    <id>58392</id>
    <revision>
      <id>192232</id>
      <timestamp>2025-06-11T06:13:44Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Novo Tipo: Meses do calendário igbo&quot;</comment>
      <origin>192232</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40" sha1="5hdowxxsj2h4lyp20fjwxk3ehx6msut" xml:space="preserve">$1: Novo Tipo: Meses do calendário igbo</text>
      <sha1>5hdowxxsj2h4lyp20fjwxk3ehx6msut</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/30/pt-br</title>
    <ns>1198</ns>
    <id>58393</id>
    <revision>
      <id>192234</id>
      <timestamp>2025-06-11T06:13:55Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;$1: Novo Tipo: Inteiros&quot;</comment>
      <origin>192234</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="23" sha1="hlhn2117899qqz1usbgmsxkcgj6ccso" xml:space="preserve">$1: Novo Tipo: Inteiros</text>
      <sha1>hlhn2117899qqz1usbgmsxkcgj6ccso</sha1>
    </revision>
  </page>
  <page>
    <title>Translations:Wikifunctions:Status updates/28/pt-br</title>
    <ns>1198</ns>
    <id>58394</id>
    <revision>
      <id>192236</id>
      <timestamp>2025-06-11T06:14:21Z</timestamp>
      <contributor>
        <username>Eduardogobi</username>
        <id>2982</id>
      </contributor>
      <comment>Created page with &quot;== Boletins informativos ==&quot;</comment>
      <origin>192236</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="27" sha1="ei6o6u1ra6oprg3phcl70ztvcqwn1r5" xml:space="preserve">== Boletins informativos ==</text>
      <sha1>ei6o6u1ra6oprg3phcl70ztvcqwn1r5</sha1>
    </revision>
  </page>
</mediawiki>