Abstract Wikipedia abstractwiki https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page MediaWiki 1.47.0-wmf.14 first-letter Media Special Talk User User talk Abstract Wikipedia Abstract Wikipedia talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk TimedText TimedText talk Module Module talk Translations Translations talk 4 6 14257 14225 2026-08-09T18:50:46Z GrounderUK 54 /* Suggestions wanted for early pilot articles to make available cross-wiki */ Reply 14257 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) : : 65zpnmkcdkdtlj656vipxhgux1p85zv 14295 14257 2026-08-10T07:41:32Z VIGNERON 163 /* Suggestions wanted for early pilot articles to make available cross-wiki */ + 14295 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) sakzmf350s2w6o9uij5zo6yz7prz6du 14296 14295 2026-08-10T07:48:54Z VIGNERON 163 /* Suggestions wanted for early pilot articles to make available cross-wiki */ + 14296 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us now but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) ov667w96ne4w70hd4rk1xe52rycbzs5 14298 14296 2026-08-10T08:01:57Z VIGNERON 163 /* Suggestions wanted for early pilot articles to make available cross-wiki */ hopala 14298 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) 5gs3s82wlluvxt9wr6ec36t07pqojve 14332 14298 2026-08-10T09:44:39Z Choucas 4768 /* Suggestions wanted for early pilot articles to make available cross-wiki */ reply to VIGNERON ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 14332 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page clearly implies it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but currently the page is just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) ongtxcb04qx8ik872yv8h4s7t7d8ixe 14333 14332 2026-08-10T09:50:00Z Choucas 4768 /* Suggestions wanted for early pilot articles to make available cross-wiki */ edit reply to VIGNERON ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 14333 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having on only in first person plural the page is just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) n7uktq6953j2cvnanymwk8cilzpl8i1 14334 14333 2026-08-10T09:51:59Z Choucas 4768 /* Suggestions wanted for early pilot articles to make available cross-wiki */ edit reply to VIGNERON ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 14334 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) 8ycqil2j4kzp4896cd1qulno9wgu3ma 14335 14334 2026-08-10T10:16:43Z GrounderUK 54 /* Suggestions wanted for early pilot articles to make available cross-wiki */ Reply 14335 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) n7cnzifyfbt6soq5x8j9wvg51g6h72e 14336 14335 2026-08-10T10:17:15Z Jsamwrites 874 /* Suggestions wanted for early pilot articles to make available cross-wiki */ Reply 14336 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) bhmqfetn9jw3hd8m4sa68qm0hvl0r8u 14337 14336 2026-08-10T10:18:47Z Jsamwrites 874 /* Suggestions wanted for early pilot articles to make available cross-wiki */ Reply 14337 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, 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]]) 09:48, 25 May 2026 (UTC) <!-- 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&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, 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:04, 1 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, 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/1780939800 June 8, 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:14, 5 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, 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 Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- 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&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, 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]]) 12:34, 19 June 2026 (UTC) <!-- 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&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, 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/1783359000 July 6, 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]]) 09:58, 27 June 2026 (UTC) <!-- 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&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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/1783359000 July 6, 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]]) 08:22, 2 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]) 09:43, 9 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, 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]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- 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&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) pdd9zid6nxue3p96veyod6eylvdxv42 0 747 14283 12788 2026-08-10T03:32:43Z Sohom Datta 1397 add image 14283 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 4wytyz2ut5bllh2p0nmjfrp8wkc7czx 14284 14283 2026-08-10T03:44:37Z Sohom Datta 1397 14284 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } b2xefc0w5psyasifmz9hkzhgmnmqou9 14285 14284 2026-08-10T03:53:55Z Sohom Datta 1397 14285 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } nlj41rdp37j61ohimxfggabokjp9x08 14286 14285 2026-08-10T04:00:30Z Sohom Datta 1397 14286 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 5fb25dwg6ljzgar5awyi43e0k6xum5u 14288 14286 2026-08-10T04:24:50Z Sohom Datta 1397 14288 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z34637", "Z34637K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34637K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 21e7vfudl59d857sm45tuzhd2maajt8 14289 14288 2026-08-10T05:40:13Z Sohom Datta 1397 14289 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z6091", "Z6091K1": "Q129286" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P1376" }, "Z38181K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q5283295" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P797" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q48730651" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1308" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } p1kcg8mvwgbj5tpfk0zus7g0acm7jv0 14291 14289 2026-08-10T06:56:24Z Sohom Datta 1397 14291 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q6352686" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P138" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z6091", "Z6091K1": "Q129286" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P1376" }, "Z38181K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q5283295" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P797" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q48730651" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1308" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } kltp5xg007nea81y5qq68w9ip6tae6m 14292 14291 2026-08-10T07:01:43Z Sohom Datta 1397 14292 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z6091", "Z6091K1": "Q6352686" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q129286" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q5283295" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P797" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q48730651" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1308" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } sj3p4ztv8l88yqd48cyjw1vi7u8pov1 14293 14292 2026-08-10T07:05:26Z Sohom Datta 1397 14293 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z6091", "Z6091K1": "Q6352686" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q129286" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q5283295" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P797" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q48730651" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1308" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 7gebnwcijgs2jc08jsfspqjotakf9u4 14294 14293 2026-08-10T07:09:06Z Sohom Datta 1397 14294 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z6091", "Z6091K1": "Q6352686" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q129286" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q5283295" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P797" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q48730651" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1308" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q6427307" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1001" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 9sjec3nwyrcnxrkzwxkagadik8vjwez 14297 14294 2026-08-10T07:57:45Z Sohom Datta 1397 14297 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z6091", "Z6091K1": "Q6352686" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q129286" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q5283295" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P797" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q48730651" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1308" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q6427307" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1001" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q570116" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z6091", "Z6091K1": "Q1356352" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P276" }, "Z38181K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } kdg32p1340rtwhrf39amz0v4bfaglpb 0 778 14258 3452 2026-08-09T21:44:20Z 99of9 614 -spo 14258 abstractwiki text/plain { "qid": "Q1867", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q865" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q271151" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q18113714" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q2285706" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q262828" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q23492" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } hm0h8m91p69pfpj9i22drkmywb5sp37 12 2505 14300 11915 2026-08-10T08:25:54Z Ameisenigel 31 Created page with "Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels" 14300 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # <span lang="en" dir="ltr" class="mw-content-ltr">Create an article by copy and paste</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Create an article from scratch</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Steps to create an article by copy and paste == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, find an existing Abstract Wikipedia article similar to the one you wish to create. You can use this by using the search tool and clicking on an item with "- AW" next to it. Once found, click on "Edit source". </div> [[File:AW Help Copy Paste step 01.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Start</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon, then select "Copy to clipboard".</span> [[File:AW Help Copy Paste step 02.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Copy to clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == <div class="mw-translate-fuzzy"> Um einen Artikel zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. </div> [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] qyzbw4thllevu3v9ujppkygx21l9xg5 14302 14300 2026-08-10T08:26:23Z Ameisenigel 31 Created page with "Einen Artikel durch Kopieren und Einfügen erstellen" 14302 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # <span lang="en" dir="ltr" class="mw-content-ltr">Create an article from scratch</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Steps to create an article by copy and paste == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, find an existing Abstract Wikipedia article similar to the one you wish to create. You can use this by using the search tool and clicking on an item with "- AW" next to it. Once found, click on "Edit source". </div> [[File:AW Help Copy Paste step 01.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Start</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon, then select "Copy to clipboard".</span> [[File:AW Help Copy Paste step 02.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Copy to clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == <div class="mw-translate-fuzzy"> Um einen Artikel zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. </div> [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 017lbj8w651y7wqpgk35q4ot7mhlt0l 14304 14302 2026-08-10T08:26:44Z Ameisenigel 31 Created page with "Einen Artikel von Grund auf erstellen" 14304 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <div lang="en" dir="ltr" class="mw-content-ltr"> == Steps to create an article by copy and paste == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, find an existing Abstract Wikipedia article similar to the one you wish to create. You can use this by using the search tool and clicking on an item with "- AW" next to it. Once found, click on "Edit source". </div> [[File:AW Help Copy Paste step 01.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Start</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon, then select "Copy to clipboard".</span> [[File:AW Help Copy Paste step 02.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Copy to clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == <div class="mw-translate-fuzzy"> Um einen Artikel zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. </div> [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] i47rlnkm07nu6t7bncrgrw9m3257c96 14306 14304 2026-08-10T08:27:10Z Ameisenigel 31 Created page with "== Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen ==" 14306 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == <div lang="en" dir="ltr" class="mw-content-ltr"> First, find an existing Abstract Wikipedia article similar to the one you wish to create. You can use this by using the search tool and clicking on an item with "- AW" next to it. Once found, click on "Edit source". </div> [[File:AW Help Copy Paste step 01.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Start</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon, then select "Copy to clipboard".</span> [[File:AW Help Copy Paste step 02.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Copy to clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == <div class="mw-translate-fuzzy"> Um einen Artikel zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. </div> [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] pzjejox58k91ajxj9uldhoenbc9oykv 14308 14306 2026-08-10T08:27:38Z Ameisenigel 31 14308 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == <div lang="en" dir="ltr" class="mw-content-ltr"> First, find an existing Abstract Wikipedia article similar to the one you wish to create. You can use this by using the search tool and clicking on an item with "- AW" next to it. Once found, click on "Edit source". </div> [[File:AW Help Copy Paste step 01.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Start</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon, then select "Copy to clipboard".</span> [[File:AW Help Copy Paste step 02.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Copy to clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == Um einen Artikel von Grund auf zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] ki4kegs7s6gy0r8oru4bd4sbg4lfxb4 14320 14308 2026-08-10T08:39:14Z Ameisenigel 31 Created page with "Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten"." 14320 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Start</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon, then select "Copy to clipboard".</span> [[File:AW Help Copy Paste step 02.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Copy to clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == Um einen Artikel von Grund auf zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 6j77mntybv63swc9112hh5qojw72jb3 14322 14320 2026-08-10T08:39:23Z Ameisenigel 31 Created page with "Start" 14322 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|Start]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon, then select "Copy to clipboard".</span> [[File:AW Help Copy Paste step 02.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Copy to clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == Um einen Artikel von Grund auf zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] iy95gjfxrft9nb5n7z10odxohi6u951 14324 14322 2026-08-10T08:40:46Z Ameisenigel 31 Created page with "Klicke auf das Symbol mit den drei Punkten und wähle dann "In die Zwischenablage kopieren"." 14324 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|Start]] Klicke auf das Symbol mit den drei Punkten und wähle dann "In die Zwischenablage kopieren". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Copy to clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == Um einen Artikel von Grund auf zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] jbkh8of5xjaubwg2qtwueywfbqffsb7 14326 14324 2026-08-10T08:40:56Z Ameisenigel 31 Created page with "In die Zwischenablage kopieren" 14326 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|Start]] Klicke auf das Symbol mit den drei Punkten und wähle dann "In die Zwischenablage kopieren". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|In die Zwischenablage kopieren]] <span lang="en" dir="ltr" class="mw-content-ltr">Search for the topic that you wish to create an article on.</span> [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == Um einen Artikel von Grund auf zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 90jq9marpbl8zkoiapotzi7cnu1s06a 1198 2508 14307 6517 2026-08-10T08:27:38Z Ameisenigel 31 14307 wikitext text/x-wiki Um einen Artikel von Grund auf zu erstellen, kannst du auf [[$1|Einen neuen Abstrakten Artikel erstellen]] gehen. tuypfec5xdtm40zxetuz8q7hyrez32f 10 3361 14270 9026 2026-08-10T02:09:38Z Koavf 723 14270 wikitext text/x-wiki {{Documentation subpage}} {{UsesLangSwitch}} <templatedata> { "params": { "link": { "label": "Parent page link", "type": "wiki-page-name" } }, "description": "For use in talk page archives.", "format": "inline" } </templatedata> <includeonly>[[Category:Templates]]</includeonly> ha6g2ja2lxkwlmvvq5akmmwnj00ku0d 14271 14270 2026-08-10T02:09:57Z Koavf 723 14271 wikitext text/x-wiki {{Documentation subpage}} {{UsesLangSwitch}} <templatedata> { "params": { "link": { "label": "Parent page link", "type": "wiki-page-name" } }, "description": "For use in talk page archives.", "format": "inline" } </templatedata> [[Category:Templates]] g8u4i4sng7x3bpd9p78kqumpi8ypjk8 828 4487 14281 12069 2026-08-10T02:16:38Z Koavf 723 does not exist 14281 sanitized-css text/css .hatnote { font-style: italic; } /* Limit structure CSS to divs because of [[Module:Hatnote inline]] */ div.hatnote { /* @noflip */ padding-left: 1.6em; margin-bottom: 0.5em; } .hatnote i { font-style: normal; } /* The templatestyles causes an 'empty' span between hatnotes */ .hatnote + span.mw-empty-elt + .hatnote, /* remove this selector when Parsoid is the only parser, see also [[phab:T200206]] */ .hatnote + link + .hatnote { margin-top: -0.5em; } @media print { body.ns-0 .hatnote { display: none !important; } } ecpw25l80bwdzlmqsmtana0pw47g4uw 2 4581 14267 14148 2026-08-10T01:57:50Z Koavf 723 lint errors 14267 wikitext text/x-wiki ===Overview of Infobox functions I work(ed) upon=== << WORK IN PROGRESS >> {| class="wikitable" ! !! infobox for city !! infobox for person !! infobox for a taxon !! Etcetera |- | '''ZID''' || [[f:Z36678|Z36678]] || [[f:Z35370|Z35370]] || [[f:Z37827|Z37827]] || |- | '''Article as example''' || [[Q90]] || [[Q181]] || [[Q140]] || |- valign="top" | | '''Example''' | <table style="color:black; background-color:var(--background-color-interactive-subtle,#F8F9FA);border:1px solid var(--border-color-base,#A2A9B1);border-spacing:3px;clear:inline-end;float: inline-end;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Paris</td></tr><tr><td>Country</td><td>France</td></tr><tr><td>Time zone</td><td>UTC+01:00</td></tr><tr><td>Geographic coordinate</td><td>48°51′24″N 2°21′8″E</td></tr></table> | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Jimmy Wales</td></tr><tr><td>Date of birth</td><td>7 August 1966</td></tr><tr><td>Place of birth</td><td>Huntsville</td></tr></table> | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Lion</td></tr><tr><td>Scientific name</td><td>Panthera leo</td></tr><tr><td>Taxonomic rank</td><td>Species</td></tr><tr><td>Parent taxon</td><td>Panthera</td></tr></table> | |- | '''Remark''' || Rows to be added later || Rows to be added later || Rows to be added later || |} {| class="wikitable" ! ZID !! Functions used: !! Exemple of the result !! Comment |- | [[f:Z33328|Z33328]] || create HTML table fragment || <nowiki><table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"></table></nowiki> || |- | [[f:Z37644|Z37644]] || infobox section || <nowiki><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">City</td></tr></nowiki> || |- | [[f:Z37647|Z37647]] || infobox color scheme | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:90deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">test</td></tr></table> <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">default</td></tr></table> | colorscheme test and default color scheme |- | [[f:Z37623|Z37623]] || infobox row || <nowiki><tr><td>Country</td><td>France</td></tr> (if function for value is not defined: <tr><td>Xxxx</td><td>Type Zxxxx not yet defined in Z37865"</td></tr></nowiki> || |- | [[f:Z33319|Z33319]] || create HTML tr fragment || <nowiki><tr valign="top"></tr></nowiki> || |- | [[f:Z33315|Z33315]] || create HTML td fragment || <nowiki><td>xx</td></nowiki> || |- | [[f:Z37866|Z37866]] || infobox row property type || Returns Z6 String (also for images) Z6010 Wikidata quantity Z6011 Wikidata geo-coordinate Z6064 Wikidata time<br>Z6091 Wikidata item reference etc || |- | [[f:Z37880|Z37880]] || infobox value QID || France || |- | [[f:Z37883|Z37883]] || infobox value string<br>Idem for quantity etc || Panthera leo<br>2,103,778 or 105.4 km² || |- | || infobox value date || 7 August 1966 || |- | || etc || || |- | [[f:Z37655|Z37655]] || infobox 1 image || Not yet || |- | || infobox 2 images || Idem || |} izcy6m9m8imcuzdbx001jfv4ql0c3jf 14268 14267 2026-08-10T01:58:37Z Koavf 723 lint error 14268 wikitext text/x-wiki ===Overview of Infobox functions I work(ed) upon=== << WORK IN PROGRESS >> {| class="wikitable" ! !! infobox for city !! infobox for person !! infobox for a taxon !! Etcetera |- | '''ZID''' || [[f:Z36678|Z36678]] || [[f:Z35370|Z35370]] || [[f:Z37827|Z37827]] || |- | '''Article as example''' || [[Q90]] || [[Q181]] || [[Q140]] || |- valign="top" | | '''Example''' | <table style="color:black; background-color:var(--background-color-interactive-subtle,#F8F9FA);border:1px solid var(--border-color-base,#A2A9B1);border-spacing:3px;clear:inline-end;float: inline-end;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;color:black;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Paris</td></tr><tr><td>Country</td><td>France</td></tr><tr><td>Time zone</td><td>UTC+01:00</td></tr><tr><td>Geographic coordinate</td><td>48°51′24″N 2°21′8″E</td></tr></table> | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;color:black; background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Jimmy Wales</td></tr><tr><td>Date of birth</td><td>7 August 1966</td></tr><tr><td>Place of birth</td><td>Huntsville</td></tr></table> | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;color:black; background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Lion</td></tr><tr><td>Scientific name</td><td>Panthera leo</td></tr><tr><td>Taxonomic rank</td><td>Species</td></tr><tr><td>Parent taxon</td><td>Panthera</td></tr></table> | |- | '''Remark''' || Rows to be added later || Rows to be added later || Rows to be added later || |} {| class="wikitable" ! ZID !! Functions used: !! Exemple of the result !! Comment |- | [[f:Z33328|Z33328]] || create HTML table fragment || <nowiki><table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"></table></nowiki> || |- | [[f:Z37644|Z37644]] || infobox section || <nowiki><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">City</td></tr></nowiki> || |- | [[f:Z37647|Z37647]] || infobox color scheme | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:90deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">test</td></tr></table> <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">default</td></tr></table> | colorscheme test and default color scheme |- | [[f:Z37623|Z37623]] || infobox row || <nowiki><tr><td>Country</td><td>France</td></tr> (if function for value is not defined: <tr><td>Xxxx</td><td>Type Zxxxx not yet defined in Z37865"</td></tr></nowiki> || |- | [[f:Z33319|Z33319]] || create HTML tr fragment || <nowiki><tr valign="top"></tr></nowiki> || |- | [[f:Z33315|Z33315]] || create HTML td fragment || <nowiki><td>xx</td></nowiki> || |- | [[f:Z37866|Z37866]] || infobox row property type || Returns Z6 String (also for images) Z6010 Wikidata quantity Z6011 Wikidata geo-coordinate Z6064 Wikidata time<br>Z6091 Wikidata item reference etc || |- | [[f:Z37880|Z37880]] || infobox value QID || France || |- | [[f:Z37883|Z37883]] || infobox value string<br>Idem for quantity etc || Panthera leo<br>2,103,778 or 105.4 km² || |- | || infobox value date || 7 August 1966 || |- | || etc || || |- | [[f:Z37655|Z37655]] || infobox 1 image || Not yet || |- | || infobox 2 images || Idem || |} mmexqq8xawmnr742pf2njvpfny69udc 14269 14268 2026-08-10T01:59:08Z Koavf 723 lint error 14269 wikitext text/x-wiki ===Overview of Infobox functions I work(ed) upon=== << WORK IN PROGRESS >> {| class="wikitable" ! !! infobox for city !! infobox for person !! infobox for a taxon !! Etcetera |- | '''ZID''' || [[f:Z36678|Z36678]] || [[f:Z35370|Z35370]] || [[f:Z37827|Z37827]] || |- | '''Article as example''' || [[Q90]] || [[Q181]] || [[Q140]] || |- valign="top" | | '''Example''' | <table style="color:black; background-color:var(--background-color-interactive-subtle,#F8F9FA);border:1px solid var(--border-color-base,#A2A9B1);border-spacing:3px;clear:inline-end;float: inline-end;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;color:black;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Paris</td></tr><tr><td>Country</td><td>France</td></tr><tr><td>Time zone</td><td>UTC+01:00</td></tr><tr><td>Geographic coordinate</td><td>48°51′24″N 2°21′8″E</td></tr></table> | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;color:black; background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Jimmy Wales</td></tr><tr><td>Date of birth</td><td>7 August 1966</td></tr><tr><td>Place of birth</td><td>Huntsville</td></tr></table> | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;color:black; background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">Lion</td></tr><tr><td>Scientific name</td><td>Panthera leo</td></tr><tr><td>Taxonomic rank</td><td>Species</td></tr><tr><td>Parent taxon</td><td>Panthera</td></tr></table> | |- | '''Remark''' || Rows to be added later || Rows to be added later || Rows to be added later || |} {| class="wikitable" ! ZID !! Functions used: !! Exemple of the result !! Comment |- | [[f:Z33328|Z33328]] || create HTML table fragment || <nowiki><table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"></table></nowiki> || |- | [[f:Z37644|Z37644]] || infobox section || <nowiki><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">City</td></tr></nowiki> || |- | [[f:Z37647|Z37647]] || infobox color scheme | <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:90deg;color:black;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">test</td></tr></table> <table style="color:black; background-color:#F8F9FA;border:1px solid #A2A9B1;border-spacing:3px;clear:right;float:right;margin:0.5em 0 0.5em 1em;padding:0.2em;width:250px;"><tr><td colspan="2" align="center" style="--infobox-accent-hue:264deg;color:black;background-color:oklch(from var(--background-color-success-subtle,#DFF2EB) calc(0.8*l + 0.15) calc(c + 0.05) var(--infobox-accent-hue,264deg));">default</td></tr></table> | colorscheme test and default color scheme |- | [[f:Z37623|Z37623]] || infobox row || <nowiki><tr><td>Country</td><td>France</td></tr> (if function for value is not defined: <tr><td>Xxxx</td><td>Type Zxxxx not yet defined in Z37865"</td></tr></nowiki> || |- | [[f:Z33319|Z33319]] || create HTML tr fragment || <nowiki><tr valign="top"></tr></nowiki> || |- | [[f:Z33315|Z33315]] || create HTML td fragment || <nowiki><td>xx</td></nowiki> || |- | [[f:Z37866|Z37866]] || infobox row property type || Returns Z6 String (also for images) Z6010 Wikidata quantity Z6011 Wikidata geo-coordinate Z6064 Wikidata time<br>Z6091 Wikidata item reference etc || |- | [[f:Z37880|Z37880]] || infobox value QID || France || |- | [[f:Z37883|Z37883]] || infobox value string<br>Idem for quantity etc || Panthera leo<br>2,103,778 or 105.4 km² || |- | || infobox value date || 7 August 1966 || |- | || etc || || |- | [[f:Z37655|Z37655]] || infobox 1 image || Not yet || |- | || infobox 2 images || Idem || |} rlv1qa8x4ir6ydtz2862eb9fr08005u 10 5065 14277 13946 2026-08-10T02:11:59Z Koavf 723 14277 wikitext text/x-wiki <onlyinclude>[[File:Symbol keep vote.svg|15px|link=]]&nbsp;'''{{{1|{{LangSwitch | lang = {{#if:{{{lang|}}}|{{{lang}}}|{{int:Lang}}}} |ar = إبقاء |be |be-tarask = Пакінуць |bn = রাখুন |bs = Zadrži |cs = Ponechat |da = Behold |de = Behalten |el = Διατήρηση |en = Keep |eo = Konservi |es = Manténgase |et = Säilitada |fa = بماند |fi = Ei pois |fr = Conserver |gl = Manter |he = להשאיר |hu = Maradjon |hy = Թողնել |it = Mantenere |ja = 現状維持 |ka = შენარჩუნება |ko = 유지 |mk = Задржи |ml = നിലനിർത്തുക |no|nb = Behold |nds= Behollen |nl = Behouden |nn = Tak vare på |pl = Zostawić |pt = Manter |ro = Păstrare |ru = Оставить |sl = Ohranimo. |sq = Mbaje |sv = Behåll |tg|tg-cyrl=Мондан |tg-latn=Mondan |th = เก็บ |tr = Kalsın |uk = Залишити |uz|uz-latn = Qoldirilsin |uz-cyrl = Қолдирилсин |zh = 保留 |#default = Keep }}}}}'''</onlyinclude><noinclude>{{Documentation}}</noinclude> 7venpuisksz4227p0pk4d1ukotbvvn8 10 5066 14276 13947 2026-08-10T02:11:56Z Koavf 723 14276 wikitext text/x-wiki <onlyinclude>[[File:Symbol delete vote.svg|15px|link=]]&nbsp;'''{{{1|{{LangSwitch | lang = {{#if:{{{lang|}}}|{{{lang}}}|{{int:Lang}}}} |ar = حذف |be-tarask = Выдаліць |bn = অপসারণ |br = Nullañ |cs = Smazat |da = Slet |de = Löschen |el = Διαγραφή |en = Delete |eo = Forigi |es = Bórrese |et = Kustutada |fa = حذف شود |fi = Pois |fr = Supprimer |he = למחוק |hu = Törlendő |is = Eyða |it = Cancellare |ja = 削除 |ko = 삭제 |mk = Бриши |ml = നീക്കം ചെയ്യുക |no = Slett |nb = Slett |nn = Slett |nds= Wegdoon |nl = Verwijderen |pl = Usunąć |pt = Eliminar |ru = Удалить |sv = Radera |th = ลบ |tr = Silinsin |uk = Вилучити |zh-hans = 删除 |zh-hant = 刪除 |#default = {{#if:{{{lang|}}}|{{int:Delete/{{{lang}}}}}|{{int:Delete}}}} }}}}}'''</onlyinclude><noinclude>{{Documentation}}</noinclude> a0gozp21jabhxyaxaacs0fyy3lx9yxu 0 5121 14255 14226 2026-08-09T16:32:36Z Mastrocom 6231 History 14255 abstractwiki text/plain { "qid": "Q5753", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M131050271" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q265" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2044" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P206" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "History" }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q484195" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "Monuments" }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q1373583" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q174782" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q492144" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q2278212" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1713936" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33691", "Z33691K1": "Mosques" }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q679218" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4292376" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4292369" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 8witgrrnxpp7unbsbo51bojeg79lfxb 14256 14255 2026-08-09T16:56:23Z Mastrocom 6231 +places and images 14256 abstractwiki text/plain { "qid": "Q5753", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M131050271" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q265" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2044" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P206" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "History" }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q484195" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "Monuments" }, { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M30581520" }, "Z36038K2": "Registan square after sunrise in Samarkand" }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q1373583" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q174782" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q492144" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q2278212" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1713936" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33691", "Z33691K1": "Mosques" }, { "Z1K1": "Z7", "Z7K1": "Z36049", "Z36049K1": { "Z1K1": "Z310", "Z310K1": "M154628800" }, "Z36049K2": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Bibi-Khanym mosque complex" } ] }, "Z36049K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q679218" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4292376" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4292369" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33691", "Z33691K1": "Mausoleums" }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q671935" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1661582" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q20007114" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4273747" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1256223" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4273779" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4205684" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1622717" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q16533989" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33691", "Z33691K1": "Other important places" }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q13534449" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4306302" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q608580" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } armx84mmom6dd8zxn12fre1ap6w3haz 14259 14256 2026-08-09T21:51:52Z 99of9 614 fix sections (they can't be only in English) 14259 abstractwiki text/plain { "qid": "Q5753", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M131050271" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q265" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2044" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P206" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q484195" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32839", "Z32839K1": { "Z1K1": "Z6091", "Z6091K1": "Q4989906" }, "Z32839K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M30581520" }, "Z36038K2": "Registan square after sunrise in Samarkand" }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q1373583" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q174782" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q492144" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q2278212" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1713936" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z34250", "Z34250K1": { "Z1K1": "Z6091", "Z6091K1": "Q32815" }, "Z34250K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36049", "Z36049K1": { "Z1K1": "Z310", "Z310K1": "M154628800" }, "Z36049K2": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Bibi-Khanym mosque complex" } ] }, "Z36049K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q679218" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4292376" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4292369" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z34250", "Z34250K1": { "Z1K1": "Z6091", "Z6091K1": "Q162875" }, "Z34250K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q671935" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1661582" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q20007114" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4273747" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1256223" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4273779" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4205684" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q1622717" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q16533989" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q55107540" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q13534449" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q4306302" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33190", "Z33190K1": { "Z1K1": "Z6091", "Z6091K1": "Q608580" }, "Z33190K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } fxq4z1sj65h8eu13wdwtkxf4eac70ar 1198 5124 14227 2026-08-09T12:21:47Z HackerPunki 5745 Created page with "Wikipedia Abstracta: Preguntas frecuentes" 14227 wikitext text/x-wiki Wikipedia Abstracta: Preguntas frecuentes fyezd324uz38cl2omkns55au8nozl4h 4 5125 14228 2026-08-09T12:21:48Z HackerPunki 5745 Created page with "Wikipedia Abstracta: Preguntas frecuentes" 14228 wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> == What is Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is a new Wikimedia project that allows communities to collaboratively create language-independent articles in their native language, which others can then access in their own languages. This transformation is done by using functions from Wikifunctions that access structured content from Wikidata. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == What is an abstract article? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An abstract article represents information about a topic in a structured, language-independent form. Contributors combine structured data from Wikidata with language functions from Wikifunctions to produce natural-language sentences that describe the topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How is Abstract Wikipedia different from Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] mbrkhwejdk39lxywk1yq4bvxawv0p93 14230 14228 2026-08-09T12:21:51Z HackerPunki 5745 Created page with "== ¿Qué es Wikipedia Abstracta? ==" 14230 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is a new Wikimedia project that allows communities to collaboratively create language-independent articles in their native language, which others can then access in their own languages. This transformation is done by using functions from Wikifunctions that access structured content from Wikidata. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == What is an abstract article? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An abstract article represents information about a topic in a structured, language-independent form. Contributors combine structured data from Wikidata with language functions from Wikifunctions to produce natural-language sentences that describe the topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How is Abstract Wikipedia different from Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] g11tmu9xbualvbsogxk1yhzfzkw11wn 14232 14230 2026-08-09T12:27:43Z HackerPunki 5745 Created page with "La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes del lenguaje humano, lo que permite que personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata." 14232 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes del lenguaje humano, lo que permite que personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <div lang="en" dir="ltr" class="mw-content-ltr"> == What is an abstract article? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An abstract article represents information about a topic in a structured, language-independent form. Contributors combine structured data from Wikidata with language functions from Wikifunctions to produce natural-language sentences that describe the topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How is Abstract Wikipedia different from Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] 5gaik4ohpudb0c30lu8yghwqayx6a4t 14234 14232 2026-08-09T12:28:04Z HackerPunki 5745 Created page with "== ¿Qué es un artículo abstracto? ==" 14234 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes del lenguaje humano, lo que permite que personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == <div lang="en" dir="ltr" class="mw-content-ltr"> An abstract article represents information about a topic in a structured, language-independent form. Contributors combine structured data from Wikidata with language functions from Wikifunctions to produce natural-language sentences that describe the topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How is Abstract Wikipedia different from Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] r6f6ucvndq5wzeczq0uzbjo63ax9jwi 14236 14234 2026-08-09T12:30:22Z HackerPunki 5745 14236 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, lo que permite que personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == <div lang="en" dir="ltr" class="mw-content-ltr"> An abstract article represents information about a topic in a structured, language-independent form. Contributors combine structured data from Wikidata with language functions from Wikifunctions to produce natural-language sentences that describe the topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How is Abstract Wikipedia different from Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] iwrw34dp18y9qzk4qo5a3qw8ctehoow 14238 14236 2026-08-09T12:32:31Z HackerPunki 5745 Created page with "Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema." 14238 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, lo que permite que personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <div lang="en" dir="ltr" class="mw-content-ltr"> == How is Abstract Wikipedia different from Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] 6xte4mahkgvv2zag7r11prjxvejqrq8 14240 14238 2026-08-09T12:32:57Z HackerPunki 5745 14240 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, lo que permite que otras personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <div lang="en" dir="ltr" class="mw-content-ltr"> == How is Abstract Wikipedia different from Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] 1inbuuk224w5o212y76ybirh8axrjir 14242 14240 2026-08-09T12:33:34Z HackerPunki 5745 14242 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, que luego pueden ser leídas por personas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <div lang="en" dir="ltr" class="mw-content-ltr"> == How is Abstract Wikipedia different from Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] ely0xq0ivru8e9d9zram5hnk9jlecdw 14244 14242 2026-08-09T12:34:13Z HackerPunki 5745 Created page with "== ¿En qué se difenecia la Wikipedia abstracta de la Wikipedia? ==" 14244 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, que luego pueden ser leídas por personas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <span id="How_is_Abstract_Wikipedia_different_from_Wikipedia?"></span> == ¿En qué se difenecia la Wikipedia abstracta de la Wikipedia? == <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia articles are written directly in a specific language. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] 6ua3qbefew0a9rgfpqrs6mjmowkd48z 14246 14244 2026-08-09T12:34:53Z HackerPunki 5745 Created page with "Los artículos de Wikipedia se escriben directamente en un idioma determinado. (Por ejemplo, españo, francés, inglés, etc.)" 14246 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, que luego pueden ser leídas por personas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <span id="How_is_Abstract_Wikipedia_different_from_Wikipedia?"></span> == ¿En qué se difenecia la Wikipedia abstracta de la Wikipedia? == Los artículos de Wikipedia se escriben directamente en un idioma determinado. (Por ejemplo, españo, francés, inglés, etc.) <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] bl27gnjl6gfibdz8yr9149hsu8inwyh 14248 14246 2026-08-09T12:35:52Z HackerPunki 5745 Created page with "La Wikipedia Abstracta guarda información en un formato estructurado, que permite generar textos en varios idiomas con la ayuda de Wikifunciones." 14248 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, que luego pueden ser leídas por personas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <span id="How_is_Abstract_Wikipedia_different_from_Wikipedia?"></span> == ¿En qué se difenecia la Wikipedia abstracta de la Wikipedia? == Los artículos de Wikipedia se escriben directamente en un idioma determinado. (Por ejemplo, españo, francés, inglés, etc.) La Wikipedia Abstracta guarda información en un formato estructurado, que permite generar textos en varios idiomas con la ayuda de Wikifunciones. <div lang="en" dir="ltr" class="mw-content-ltr"> == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] avuiut4gxxeib3ihxa36izsh8u29uth 14250 14248 2026-08-09T12:36:30Z HackerPunki 5745 Created page with "== ¿Cómo se relaciona la Wikipedia Abstracta con Wikidata y Wikifunciones? ==" 14250 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, que luego pueden ser leídas por personas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <span id="How_is_Abstract_Wikipedia_different_from_Wikipedia?"></span> == ¿En qué se difenecia la Wikipedia abstracta de la Wikipedia? == Los artículos de Wikipedia se escriben directamente en un idioma determinado. (Por ejemplo, españo, francés, inglés, etc.) La Wikipedia Abstracta guarda información en un formato estructurado, que permite generar textos en varios idiomas con la ayuda de Wikifunciones. <span id="How_does_Abstract_Wikipedia_relate_to_Wikidata_and_Wikifunctions?"></span> == ¿Cómo se relaciona la Wikipedia Abstracta con Wikidata y Wikifunciones? == <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia builds on these Wikimedia projects: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] kfgvdsl8gar93j8mtniql30n3hz1clu 14252 14250 2026-08-09T12:37:11Z HackerPunki 5745 Created page with "La Wikipedia Abstracta se construye en base a los siguientes proyectos de Wikimedia:" 14252 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, que luego pueden ser leídas por personas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <span id="How_is_Abstract_Wikipedia_different_from_Wikipedia?"></span> == ¿En qué se difenecia la Wikipedia abstracta de la Wikipedia? == Los artículos de Wikipedia se escriben directamente en un idioma determinado. (Por ejemplo, españo, francés, inglés, etc.) La Wikipedia Abstracta guarda información en un formato estructurado, que permite generar textos en varios idiomas con la ayuda de Wikifunciones. <span id="How_does_Abstract_Wikipedia_relate_to_Wikidata_and_Wikifunctions?"></span> == ¿Cómo se relaciona la Wikipedia Abstracta con Wikidata y Wikifunciones? == La Wikipedia Abstracta se construye en base a los siguientes proyectos de Wikimedia: * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] ke4cgy39h2clelzud9y8d7i85qbbwt7 14254 14252 2026-08-09T12:38:05Z HackerPunki 5745 14254 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ¿Qué es Wikipedia Abstracta? == La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, que luego pueden ser leídas por personas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. <span id="What_is_an_abstract_article?"></span> == ¿Qué es un artículo abstracto? == Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. <span id="How_is_Abstract_Wikipedia_different_from_Wikipedia?"></span> == ¿En qué se diferencia la Wikipedia abstracta de la Wikipedia? == Los artículos de Wikipedia se escriben directamente en un idioma determinado. (Por ejemplo, españo, francés, inglés, etc.) La Wikipedia Abstracta guarda información en un formato estructurado, que permite generar textos en varios idiomas con la ayuda de Wikifunciones. <span id="How_does_Abstract_Wikipedia_relate_to_Wikidata_and_Wikifunctions?"></span> == ¿Cómo se relaciona la Wikipedia Abstracta con Wikidata y Wikifunciones? == La Wikipedia Abstracta se construye en base a los siguientes proyectos de Wikimedia: * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Is Abstract Wikipedia using AI? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically generate articles using AI. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Does Abstract Wikipedia automatically appear on other Wikipedias? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Who can contribute to Abstract Wikipedia? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Can I use Abstract Wikipedia today? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[Abstract Wikipedia:Project chat|let us know]] if that happens or if you have ideas for improvements! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </div> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] 6qsxrk7bwnvrj963u86qeads0qfcjcl 1198 5126 14229 2026-08-09T12:21:51Z HackerPunki 5745 Created page with "== ¿Qué es Wikipedia Abstracta? ==" 14229 wikitext text/x-wiki == ¿Qué es Wikipedia Abstracta? == fkaeevfo7syljxl7n1kssbrgw0wclfj 1198 5127 14231 2026-08-09T12:27:42Z HackerPunki 5745 Created page with "La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes del lenguaje humano, lo que permite que personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata." 14231 wikitext text/x-wiki La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes del lenguaje humano, lo que permite que personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. 6b3lh50tm820r0c6gkzsm7loyp8m3sr 14235 14231 2026-08-09T12:30:22Z HackerPunki 5745 14235 wikitext text/x-wiki La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, lo que permite que personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. kv7ujp5qqbqe8fyegq5jzvovzi478ad 14239 14235 2026-08-09T12:32:56Z HackerPunki 5745 14239 wikitext text/x-wiki La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, lo que permite que otras personas puedan leerlas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. cr02dwn6rm0k690jrhxxlf6lrz74ff4 14241 14239 2026-08-09T12:33:34Z HackerPunki 5745 14241 wikitext text/x-wiki La Wikipedia Abstracta es un nuevo proyecto de la Fundación Wikimedia que permite colaborar a sus diferentes comunidades en la creación de artículos independientes de idiomas humanos, que luego pueden ser leídas por personas en su idioma nativo. Esta transformación se realiza a través de funciones de Wikifunciones, que permite estructurar su contenido de Wikidata. sxhmeohuniixlfwiw3wokd1ukilvywn 1198 5128 14233 2026-08-09T12:28:04Z HackerPunki 5745 Created page with "== ¿Qué es un artículo abstracto? ==" 14233 wikitext text/x-wiki == ¿Qué es un artículo abstracto? == bad6b0qclgesvz1gvlh7gtspd8h7m6p 1198 5129 14237 2026-08-09T12:32:30Z HackerPunki 5745 Created page with "Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema." 14237 wikitext text/x-wiki Un artículo abstracto representa información sobre un determinado tema de forma estructurado e independiente de idiomas humanos. Los contribuyentes combinan datos estructurados de Wikidata con el lenguaje de funciones de Wikifunciones, para producir frases en lenguas naturales que permiten describir un tema. idh9wg3njkdnexiv58a1b6i8ow3c0bb 1198 5130 14243 2026-08-09T12:34:13Z HackerPunki 5745 Created page with "== ¿En qué se difenecia la Wikipedia abstracta de la Wikipedia? ==" 14243 wikitext text/x-wiki == ¿En qué se difenecia la Wikipedia abstracta de la Wikipedia? == 3idego9z5ucgrf7g2md8ql0ghlr1qm4 14253 14243 2026-08-09T12:38:05Z HackerPunki 5745 14253 wikitext text/x-wiki == ¿En qué se diferencia la Wikipedia abstracta de la Wikipedia? == fclw0pvehu5e5e7g1xwgeef6xoaubdl 1198 5131 14245 2026-08-09T12:34:52Z HackerPunki 5745 Created page with "Los artículos de Wikipedia se escriben directamente en un idioma determinado. (Por ejemplo, españo, francés, inglés, etc.)" 14245 wikitext text/x-wiki Los artículos de Wikipedia se escriben directamente en un idioma determinado. (Por ejemplo, españo, francés, inglés, etc.) f1s2r94j1x7wtyqco1zj4il8tb61gmv 1198 5132 14247 2026-08-09T12:35:51Z HackerPunki 5745 Created page with "La Wikipedia Abstracta guarda información en un formato estructurado, que permite generar textos en varios idiomas con la ayuda de Wikifunciones." 14247 wikitext text/x-wiki La Wikipedia Abstracta guarda información en un formato estructurado, que permite generar textos en varios idiomas con la ayuda de Wikifunciones. g7urxd21vg9wdvcjrpabuz2ge1mmzds 1198 5133 14249 2026-08-09T12:36:29Z HackerPunki 5745 Created page with "== ¿Cómo se relaciona la Wikipedia Abstracta con Wikidata y Wikifunciones? ==" 14249 wikitext text/x-wiki == ¿Cómo se relaciona la Wikipedia Abstracta con Wikidata y Wikifunciones? == eqftwk3u5wx3rzwl1qafx95mppfweq7 1198 5134 14251 2026-08-09T12:37:11Z HackerPunki 5745 Created page with "La Wikipedia Abstracta se construye en base a los siguientes proyectos de Wikimedia:" 14251 wikitext text/x-wiki La Wikipedia Abstracta se construye en base a los siguientes proyectos de Wikimedia: nph5arjqr5cptbz7mxaat2yv41dtk0s 10 5141 14272 2026-08-10T02:10:37Z Koavf 723 [[Category:Templates]] 14272 wikitext text/x-wiki [[Category:Templates]] 0t5jiibdq6k1tam9oy4zt1yld5iz80u 10 5142 14273 2026-08-10T02:10:51Z Koavf 723 Created page with "[[Category:Templates]]" 14273 wikitext text/x-wiki [[Category:Templates]] 0t5jiibdq6k1tam9oy4zt1yld5iz80u 10 5143 14274 2026-08-10T02:11:14Z Koavf 723 Created page with "{{Documentation subpage}} [[Category:Image with comment templates]]" 14274 wikitext text/x-wiki {{Documentation subpage}} [[Category:Image with comment templates]] 25uxej3avaq71r0qitr53tt2txdquc0 10 5144 14275 2026-08-10T02:11:15Z Koavf 723 Created page with "{{Documentation subpage}} [[Category:Image with comment templates]]" 14275 wikitext text/x-wiki {{Documentation subpage}} [[Category:Image with comment templates]] 25uxej3avaq71r0qitr53tt2txdquc0 14 5145 14278 2026-08-10T02:13:20Z Koavf 723 Created page with "[[Category:Abstract Wikipedia administration]]" 14278 wikitext text/x-wiki [[Category:Abstract Wikipedia administration]] 2xbhdj7u4v36yxhfrc2htwqqe9mx878 14 5146 14279 2026-08-10T02:14:03Z Koavf 723 Created page with "[[Category:Abstract Wikipedia|Az]]" 14279 wikitext text/x-wiki [[Category:Abstract Wikipedia|Az]] kh5f12p1fxghtpq4ayt4vx2gntoik5d 14 5147 14280 2026-08-10T02:14:11Z Koavf 723 Created page with "[[Category:Help|Ko]]" 14280 wikitext text/x-wiki [[Category:Help|Ko]] ss1s9iao8oxjxr9uv98atlyswm31ses 10 5148 14282 2026-08-10T02:17:38Z Koavf 723 [[User:99of9]] this did not exist 14282 wikitext text/x-wiki #redirect[[Template:Vote delete]] jgxekx43ohudn0rfmnj5qwepz34046l 0 5149 14287 2026-08-10T04:04:34Z SuperHamster 1364 Ohio is born 14287 abstractwiki text/plain { "qid": "Q1397", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q35657" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q16567" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } afokmjmt2qg2rhmuwfi1dcthy2vez3d 0 5150 14290 2026-08-10T06:01:30Z Tymewalk 2112 create new page for Kyoto 14290 abstractwiki text/plain { "qid": "Q34600", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36049", "Z36049K1": { "Z1K1": "Z310", "Z310K1": "M80131333" }, "Z36049K2": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "" } ] }, "Z36049K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q120730" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q917498" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q30185" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 9ikt6bt2lx0nw08ey7l18qzdpzklpwd 14331 14290 2026-08-10T09:03:57Z SuperHamster 1364 adding sentence separators 14331 abstractwiki text/plain { "qid": "Q34600", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36049", "Z36049K1": { "Z1K1": "Z310", "Z310K1": "M80131333" }, "Z36049K2": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "" } ] }, "Z36049K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q120730" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q917498" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q30185" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } i1nye6vk83ie7pd7pt7pyqklmwqr0lb 1198 5151 14299 2026-08-10T08:25:53Z Ameisenigel 31 Created page with "Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels" 14299 wikitext text/x-wiki Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels 4b1hvebz0335d5frafzzmyxwim71p93 1198 5152 14301 2026-08-10T08:26:21Z Ameisenigel 31 Created page with "Einen Artikel durch Kopieren und Einfügen erstellen" 14301 wikitext text/x-wiki Einen Artikel durch Kopieren und Einfügen erstellen t5k1iur12bva7gafubvhry9mhkp7iid 1198 5153 14303 2026-08-10T08:26:41Z Ameisenigel 31 Created page with "Einen Artikel von Grund auf erstellen" 14303 wikitext text/x-wiki Einen Artikel von Grund auf erstellen 00feoqi6q1c41fl33t782sugkl7y0f1 1198 5154 14305 2026-08-10T08:27:08Z Ameisenigel 31 Created page with "== Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen ==" 14305 wikitext text/x-wiki == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == 40tz6rzcdi7kz3akbs4pwcgjvetxp0e 1198 5155 14309 2026-08-10T08:27:55Z Martinligabue 7079 Created page with "== Cos'è Abstract Wikipedia? ==" 14309 wikitext text/x-wiki == Cos'è Abstract Wikipedia? == bvvfeozpwf49i6xvfjr1fsruif1bvlr 4 5156 14310 2026-08-10T08:27:56Z Martinligabue 7079 Created page with "== Cos'è Abstract Wikipedia? ==" 14310 wikitext text/x-wiki <languages /> [[Category:Abstract Wikipedia{{#translation:}}]] <span id="What_is_Abstract_Wikipedia?"></span> == Cos'è Abstract Wikipedia? == <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia is a new sister project of Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia's vision is a world in which everyone has access to the sum of all knowledge. Abstract Wikipedia will help the communities of volunteers contributing to Wikipedia and its related projects to more effectively close knowledge gaps. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia has articles about more than 20 million topics in more than 300 languages. But none of these languages alone allow access to the knowledge about these 20 million topics: English has more than seven million articles, Croatian 230,000, and Swahili 100,000. Unless you speak those languages, that knowledge is not easily available to you. And as much as machine translation has improved thanks to recent improvements in AI, it is still not at the point where it can produce translations you can trust for many language pairs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia does that without relying on AI. Each step of the way remains under human control, and is accessible and editable by the volunteers. There are no hallucinations, no inexplicable and unfixable mistakes: If anything is wrong, fixing it is just one step away, and there is full transparency about how the text has been created. It is not just a probabilistic model choosing the capital of Kenya per chance every time. It is human-curated and owned knowledge. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==How does Abstract Wikipedia work?== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles in Abstract Wikipedia are stored in a notation independent of human languages. The interface of Abstract Wikipedia allows volunteer contributors to create and maintain that language-independent notation. In a second step, this notation is being turned into text in human language. The steps required to make this happen are also created and maintained by a community of volunteers, on Wikifunctions. These steps can use the data on [[D:|Wikidata]], looking up population numbers, dates of birth, or irregular grammatical forms, which have been added to and are maintained on Wikidata by communities of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Special:MyLanguage/Help:How to create an article|Help:How to create an article]] for a step-by-step guide. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Let's follow one example: [[Q1033|Nigeria is the most populous country in Africa.]] In Abstract Wikipedia, this might be stored as: </div> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], Z27243K5)}} <span lang="en" dir="ltr" class="mw-content-ltr">Or, if we use English labels for these identifiers:</span> {{block indent|1=superlative(Nigeria, populous, country, Africa, language)}} <span lang="en" dir="ltr" class="mw-content-ltr">This is a call to a function on Wikifunctions. Based on the language, another function is being called. For English, we get the following function call:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1002|Z1002]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that results in the English text</span> {{block indent|1=''"Nigeria is the most populous country in Africa."''}} <span lang="en" dir="ltr" class="mw-content-ltr">If we had chosen German, another function would be called:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1430|Z1430]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that in turn would result in the following German text:</span> {{block indent|1=''"Nigeria ist das bevölkerungsreichste Land Afrikas."''}} <div lang="en" dir="ltr" class="mw-content-ltr"> An example with more languages can be found here.<!-- where?? --> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia brings together numerous communities from the Wikimedia Movement and allows them to work together. Basic lexical data and structured data about many topics from Wikidata, functions that capture the necessary computations from Wikifunctions, and images and maps from Wikimedia Commons are all tied together in Abstract Wikipedia and made available for the more than 300 language editions of Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The goal of Abstract Wikipedia is to make more knowledge available to more people in more languages, and to allow volunteer editors to be more effective and work across languages, no matter what language they speak. Improvements to the knowledge will automatically propagate to the Wikipedias, errors will be spotted faster and fixed more effectively, and collaborations across languages become possible. We are tearing down the language barriers which are keeping knowledge apart. </div> 4qcz3nppha4brdcpkjv4aqhajv4c637 14312 14310 2026-08-10T08:28:26Z Martinligabue 7079 Created page with "Abstract Wikipedia è un nuovo progetto fratello di Wikipedia." 14312 wikitext text/x-wiki <languages /> [[Category:Abstract Wikipedia{{#translation:}}]] <span id="What_is_Abstract_Wikipedia?"></span> == Cos'è Abstract Wikipedia? == Abstract Wikipedia è un nuovo progetto fratello di Wikipedia. <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia's vision is a world in which everyone has access to the sum of all knowledge. Abstract Wikipedia will help the communities of volunteers contributing to Wikipedia and its related projects to more effectively close knowledge gaps. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia has articles about more than 20 million topics in more than 300 languages. But none of these languages alone allow access to the knowledge about these 20 million topics: English has more than seven million articles, Croatian 230,000, and Swahili 100,000. Unless you speak those languages, that knowledge is not easily available to you. And as much as machine translation has improved thanks to recent improvements in AI, it is still not at the point where it can produce translations you can trust for many language pairs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia does that without relying on AI. Each step of the way remains under human control, and is accessible and editable by the volunteers. There are no hallucinations, no inexplicable and unfixable mistakes: If anything is wrong, fixing it is just one step away, and there is full transparency about how the text has been created. It is not just a probabilistic model choosing the capital of Kenya per chance every time. It is human-curated and owned knowledge. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==How does Abstract Wikipedia work?== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles in Abstract Wikipedia are stored in a notation independent of human languages. The interface of Abstract Wikipedia allows volunteer contributors to create and maintain that language-independent notation. In a second step, this notation is being turned into text in human language. The steps required to make this happen are also created and maintained by a community of volunteers, on Wikifunctions. These steps can use the data on [[D:|Wikidata]], looking up population numbers, dates of birth, or irregular grammatical forms, which have been added to and are maintained on Wikidata by communities of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Special:MyLanguage/Help:How to create an article|Help:How to create an article]] for a step-by-step guide. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Let's follow one example: [[Q1033|Nigeria is the most populous country in Africa.]] In Abstract Wikipedia, this might be stored as: </div> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], Z27243K5)}} <span lang="en" dir="ltr" class="mw-content-ltr">Or, if we use English labels for these identifiers:</span> {{block indent|1=superlative(Nigeria, populous, country, Africa, language)}} <span lang="en" dir="ltr" class="mw-content-ltr">This is a call to a function on Wikifunctions. Based on the language, another function is being called. For English, we get the following function call:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1002|Z1002]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that results in the English text</span> {{block indent|1=''"Nigeria is the most populous country in Africa."''}} <span lang="en" dir="ltr" class="mw-content-ltr">If we had chosen German, another function would be called:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1430|Z1430]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that in turn would result in the following German text:</span> {{block indent|1=''"Nigeria ist das bevölkerungsreichste Land Afrikas."''}} <div lang="en" dir="ltr" class="mw-content-ltr"> An example with more languages can be found here.<!-- where?? --> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia brings together numerous communities from the Wikimedia Movement and allows them to work together. Basic lexical data and structured data about many topics from Wikidata, functions that capture the necessary computations from Wikifunctions, and images and maps from Wikimedia Commons are all tied together in Abstract Wikipedia and made available for the more than 300 language editions of Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The goal of Abstract Wikipedia is to make more knowledge available to more people in more languages, and to allow volunteer editors to be more effective and work across languages, no matter what language they speak. Improvements to the knowledge will automatically propagate to the Wikipedias, errors will be spotted faster and fixed more effectively, and collaborations across languages become possible. We are tearing down the language barriers which are keeping knowledge apart. </div> tcrt9dtjzikfjiplh3c49dwmtxe2kyw 14314 14312 2026-08-10T08:32:57Z Martinligabue 7079 Created page with "Wikipedia contiene articoli su oltre 20 milioni di argomenti in più di 300 lingue. Tuttavia, nessuna di queste lingue, da sola, consente di accedere alle conoscenze relative a questi 20 milioni di argomenti: l’inglese conta oltre sette milioni di articoli, il croato 230.000 e lo swahili 100.000. A meno che non si parlino quelle lingue, tali conoscenze non sono facilmente accessibili. E per quanto la traduzione automatica sia migliorata grazie ai recenti progressi nell..." 14314 wikitext text/x-wiki <languages /> [[Category:Abstract Wikipedia{{#translation:}}]] <span id="What_is_Abstract_Wikipedia?"></span> == Cos'è Abstract Wikipedia? == Abstract Wikipedia è un nuovo progetto fratello di Wikipedia. <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia's vision is a world in which everyone has access to the sum of all knowledge. Abstract Wikipedia will help the communities of volunteers contributing to Wikipedia and its related projects to more effectively close knowledge gaps. </div> Wikipedia contiene articoli su oltre 20 milioni di argomenti in più di 300 lingue. Tuttavia, nessuna di queste lingue, da sola, consente di accedere alle conoscenze relative a questi 20 milioni di argomenti: l’inglese conta oltre sette milioni di articoli, il croato 230.000 e lo swahili 100.000. A meno che non si parlino quelle lingue, tali conoscenze non sono facilmente accessibili. E per quanto la traduzione automatica sia migliorata grazie ai recenti progressi nell’intelligenza artificiale, non è ancora in grado di produrre traduzioni affidabili per molte combinazioni linguistiche. <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia does that without relying on AI. Each step of the way remains under human control, and is accessible and editable by the volunteers. There are no hallucinations, no inexplicable and unfixable mistakes: If anything is wrong, fixing it is just one step away, and there is full transparency about how the text has been created. It is not just a probabilistic model choosing the capital of Kenya per chance every time. It is human-curated and owned knowledge. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==How does Abstract Wikipedia work?== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles in Abstract Wikipedia are stored in a notation independent of human languages. The interface of Abstract Wikipedia allows volunteer contributors to create and maintain that language-independent notation. In a second step, this notation is being turned into text in human language. The steps required to make this happen are also created and maintained by a community of volunteers, on Wikifunctions. These steps can use the data on [[D:|Wikidata]], looking up population numbers, dates of birth, or irregular grammatical forms, which have been added to and are maintained on Wikidata by communities of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Special:MyLanguage/Help:How to create an article|Help:How to create an article]] for a step-by-step guide. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Let's follow one example: [[Q1033|Nigeria is the most populous country in Africa.]] In Abstract Wikipedia, this might be stored as: </div> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], Z27243K5)}} <span lang="en" dir="ltr" class="mw-content-ltr">Or, if we use English labels for these identifiers:</span> {{block indent|1=superlative(Nigeria, populous, country, Africa, language)}} <span lang="en" dir="ltr" class="mw-content-ltr">This is a call to a function on Wikifunctions. Based on the language, another function is being called. For English, we get the following function call:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1002|Z1002]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that results in the English text</span> {{block indent|1=''"Nigeria is the most populous country in Africa."''}} <span lang="en" dir="ltr" class="mw-content-ltr">If we had chosen German, another function would be called:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1430|Z1430]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that in turn would result in the following German text:</span> {{block indent|1=''"Nigeria ist das bevölkerungsreichste Land Afrikas."''}} <div lang="en" dir="ltr" class="mw-content-ltr"> An example with more languages can be found here.<!-- where?? --> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia brings together numerous communities from the Wikimedia Movement and allows them to work together. Basic lexical data and structured data about many topics from Wikidata, functions that capture the necessary computations from Wikifunctions, and images and maps from Wikimedia Commons are all tied together in Abstract Wikipedia and made available for the more than 300 language editions of Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The goal of Abstract Wikipedia is to make more knowledge available to more people in more languages, and to allow volunteer editors to be more effective and work across languages, no matter what language they speak. Improvements to the knowledge will automatically propagate to the Wikipedias, errors will be spotted faster and fixed more effectively, and collaborations across languages become possible. We are tearing down the language barriers which are keeping knowledge apart. </div> 0bisi6fujs43vxtjgvj0o1clfd7fa0v 14316 14314 2026-08-10T08:34:55Z Martinligabue 7079 Created page with "== Come funziona Abstract Wikipedia? ==" 14316 wikitext text/x-wiki <languages /> [[Category:Abstract Wikipedia{{#translation:}}]] <span id="What_is_Abstract_Wikipedia?"></span> == Cos'è Abstract Wikipedia? == Abstract Wikipedia è un nuovo progetto fratello di Wikipedia. <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia's vision is a world in which everyone has access to the sum of all knowledge. Abstract Wikipedia will help the communities of volunteers contributing to Wikipedia and its related projects to more effectively close knowledge gaps. </div> Wikipedia contiene articoli su oltre 20 milioni di argomenti in più di 300 lingue. Tuttavia, nessuna di queste lingue, da sola, consente di accedere alle conoscenze relative a questi 20 milioni di argomenti: l’inglese conta oltre sette milioni di articoli, il croato 230.000 e lo swahili 100.000. A meno che non si parlino quelle lingue, tali conoscenze non sono facilmente accessibili. E per quanto la traduzione automatica sia migliorata grazie ai recenti progressi nell’intelligenza artificiale, non è ancora in grado di produrre traduzioni affidabili per molte combinazioni linguistiche. <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia does that without relying on AI. Each step of the way remains under human control, and is accessible and editable by the volunteers. There are no hallucinations, no inexplicable and unfixable mistakes: If anything is wrong, fixing it is just one step away, and there is full transparency about how the text has been created. It is not just a probabilistic model choosing the capital of Kenya per chance every time. It is human-curated and owned knowledge. </div> <span id="How_does_Abstract_Wikipedia_work?"></span> == Come funziona Abstract Wikipedia? == <div lang="en" dir="ltr" class="mw-content-ltr"> Articles in Abstract Wikipedia are stored in a notation independent of human languages. The interface of Abstract Wikipedia allows volunteer contributors to create and maintain that language-independent notation. In a second step, this notation is being turned into text in human language. The steps required to make this happen are also created and maintained by a community of volunteers, on Wikifunctions. These steps can use the data on [[D:|Wikidata]], looking up population numbers, dates of birth, or irregular grammatical forms, which have been added to and are maintained on Wikidata by communities of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Special:MyLanguage/Help:How to create an article|Help:How to create an article]] for a step-by-step guide. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Let's follow one example: [[Q1033|Nigeria is the most populous country in Africa.]] In Abstract Wikipedia, this might be stored as: </div> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], Z27243K5)}} <span lang="en" dir="ltr" class="mw-content-ltr">Or, if we use English labels for these identifiers:</span> {{block indent|1=superlative(Nigeria, populous, country, Africa, language)}} <span lang="en" dir="ltr" class="mw-content-ltr">This is a call to a function on Wikifunctions. Based on the language, another function is being called. For English, we get the following function call:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1002|Z1002]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that results in the English text</span> {{block indent|1=''"Nigeria is the most populous country in Africa."''}} <span lang="en" dir="ltr" class="mw-content-ltr">If we had chosen German, another function would be called:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1430|Z1430]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that in turn would result in the following German text:</span> {{block indent|1=''"Nigeria ist das bevölkerungsreichste Land Afrikas."''}} <div lang="en" dir="ltr" class="mw-content-ltr"> An example with more languages can be found here.<!-- where?? --> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia brings together numerous communities from the Wikimedia Movement and allows them to work together. Basic lexical data and structured data about many topics from Wikidata, functions that capture the necessary computations from Wikifunctions, and images and maps from Wikimedia Commons are all tied together in Abstract Wikipedia and made available for the more than 300 language editions of Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The goal of Abstract Wikipedia is to make more knowledge available to more people in more languages, and to allow volunteer editors to be more effective and work across languages, no matter what language they speak. Improvements to the knowledge will automatically propagate to the Wikipedias, errors will be spotted faster and fixed more effectively, and collaborations across languages become possible. We are tearing down the language barriers which are keeping knowledge apart. </div> g08nrbrk2nj7wz3q6eoihlmrtm0tnzk 14318 14316 2026-08-10T08:35:48Z Martinligabue 7079 Created page with "Vedi [[$1|Aiuto:Come creare un articolo]] per una guida passo passo." 14318 wikitext text/x-wiki <languages /> [[Category:Abstract Wikipedia{{#translation:}}]] <span id="What_is_Abstract_Wikipedia?"></span> == Cos'è Abstract Wikipedia? == Abstract Wikipedia è un nuovo progetto fratello di Wikipedia. <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia's vision is a world in which everyone has access to the sum of all knowledge. Abstract Wikipedia will help the communities of volunteers contributing to Wikipedia and its related projects to more effectively close knowledge gaps. </div> Wikipedia contiene articoli su oltre 20 milioni di argomenti in più di 300 lingue. Tuttavia, nessuna di queste lingue, da sola, consente di accedere alle conoscenze relative a questi 20 milioni di argomenti: l’inglese conta oltre sette milioni di articoli, il croato 230.000 e lo swahili 100.000. A meno che non si parlino quelle lingue, tali conoscenze non sono facilmente accessibili. E per quanto la traduzione automatica sia migliorata grazie ai recenti progressi nell’intelligenza artificiale, non è ancora in grado di produrre traduzioni affidabili per molte combinazioni linguistiche. <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia does that without relying on AI. Each step of the way remains under human control, and is accessible and editable by the volunteers. There are no hallucinations, no inexplicable and unfixable mistakes: If anything is wrong, fixing it is just one step away, and there is full transparency about how the text has been created. It is not just a probabilistic model choosing the capital of Kenya per chance every time. It is human-curated and owned knowledge. </div> <span id="How_does_Abstract_Wikipedia_work?"></span> == Come funziona Abstract Wikipedia? == <div lang="en" dir="ltr" class="mw-content-ltr"> Articles in Abstract Wikipedia are stored in a notation independent of human languages. The interface of Abstract Wikipedia allows volunteer contributors to create and maintain that language-independent notation. In a second step, this notation is being turned into text in human language. The steps required to make this happen are also created and maintained by a community of volunteers, on Wikifunctions. These steps can use the data on [[D:|Wikidata]], looking up population numbers, dates of birth, or irregular grammatical forms, which have been added to and are maintained on Wikidata by communities of volunteers. </div> Vedi [[Special:MyLanguage/Help:How to create an article|Aiuto:Come creare un articolo]] per una guida passo passo. <div lang="en" dir="ltr" class="mw-content-ltr"> Let's follow one example: [[Q1033|Nigeria is the most populous country in Africa.]] In Abstract Wikipedia, this might be stored as: </div> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], Z27243K5)}} <span lang="en" dir="ltr" class="mw-content-ltr">Or, if we use English labels for these identifiers:</span> {{block indent|1=superlative(Nigeria, populous, country, Africa, language)}} <span lang="en" dir="ltr" class="mw-content-ltr">This is a call to a function on Wikifunctions. Based on the language, another function is being called. For English, we get the following function call:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1002|Z1002]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that results in the English text</span> {{block indent|1=''"Nigeria is the most populous country in Africa."''}} <span lang="en" dir="ltr" class="mw-content-ltr">If we had chosen German, another function would be called:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1430|Z1430]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that in turn would result in the following German text:</span> {{block indent|1=''"Nigeria ist das bevölkerungsreichste Land Afrikas."''}} <div lang="en" dir="ltr" class="mw-content-ltr"> An example with more languages can be found here.<!-- where?? --> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia brings together numerous communities from the Wikimedia Movement and allows them to work together. Basic lexical data and structured data about many topics from Wikidata, functions that capture the necessary computations from Wikifunctions, and images and maps from Wikimedia Commons are all tied together in Abstract Wikipedia and made available for the more than 300 language editions of Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The goal of Abstract Wikipedia is to make more knowledge available to more people in more languages, and to allow volunteer editors to be more effective and work across languages, no matter what language they speak. Improvements to the knowledge will automatically propagate to the Wikipedias, errors will be spotted faster and fixed more effectively, and collaborations across languages become possible. We are tearing down the language barriers which are keeping knowledge apart. </div> is2ioyvj21ushq06hvgu4403djz5m7k 14328 14318 2026-08-10T08:41:28Z Martinligabue 7079 Created page with "Abstract Wikipedia lo fa senza ricorrere all’intelligenza artificiale. Ogni fase del processo rimane sotto il controllo umano ed è accessibile e modificabile dai volontari. Non ci sono allucinazioni, né errori inspiegabili e impossibili da correggere: se qualcosa non va, basta un solo passo per correggerlo, e c’è piena trasparenza su come il testo è stato creato. Non si tratta semplicemente di un modello probabilistico che sceglie ogni volta a caso la capitale de..." 14328 wikitext text/x-wiki <languages /> [[Category:Abstract Wikipedia{{#translation:}}]] <span id="What_is_Abstract_Wikipedia?"></span> == Cos'è Abstract Wikipedia? == Abstract Wikipedia è un nuovo progetto fratello di Wikipedia. <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia's vision is a world in which everyone has access to the sum of all knowledge. Abstract Wikipedia will help the communities of volunteers contributing to Wikipedia and its related projects to more effectively close knowledge gaps. </div> Wikipedia contiene articoli su oltre 20 milioni di argomenti in più di 300 lingue. Tuttavia, nessuna di queste lingue, da sola, consente di accedere alle conoscenze relative a questi 20 milioni di argomenti: l’inglese conta oltre sette milioni di articoli, il croato 230.000 e lo swahili 100.000. A meno che non si parlino quelle lingue, tali conoscenze non sono facilmente accessibili. E per quanto la traduzione automatica sia migliorata grazie ai recenti progressi nell’intelligenza artificiale, non è ancora in grado di produrre traduzioni affidabili per molte combinazioni linguistiche. Abstract Wikipedia lo fa senza ricorrere all’intelligenza artificiale. Ogni fase del processo rimane sotto il controllo umano ed è accessibile e modificabile dai volontari. Non ci sono allucinazioni, né errori inspiegabili e impossibili da correggere: se qualcosa non va, basta un solo passo per correggerlo, e c’è piena trasparenza su come il testo è stato creato. Non si tratta semplicemente di un modello probabilistico che sceglie ogni volta a caso la capitale del Kenya. Si tratta di conoscenza curata e gestita dall’uomo. <span id="How_does_Abstract_Wikipedia_work?"></span> == Come funziona Abstract Wikipedia? == <div lang="en" dir="ltr" class="mw-content-ltr"> Articles in Abstract Wikipedia are stored in a notation independent of human languages. The interface of Abstract Wikipedia allows volunteer contributors to create and maintain that language-independent notation. In a second step, this notation is being turned into text in human language. The steps required to make this happen are also created and maintained by a community of volunteers, on Wikifunctions. These steps can use the data on [[D:|Wikidata]], looking up population numbers, dates of birth, or irregular grammatical forms, which have been added to and are maintained on Wikidata by communities of volunteers. </div> Vedi [[Special:MyLanguage/Help:How to create an article|Aiuto:Come creare un articolo]] per una guida passo passo. <div lang="en" dir="ltr" class="mw-content-ltr"> Let's follow one example: [[Q1033|Nigeria is the most populous country in Africa.]] In Abstract Wikipedia, this might be stored as: </div> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], Z27243K5)}} <span lang="en" dir="ltr" class="mw-content-ltr">Or, if we use English labels for these identifiers:</span> {{block indent|1=superlative(Nigeria, populous, country, Africa, language)}} <span lang="en" dir="ltr" class="mw-content-ltr">This is a call to a function on Wikifunctions. Based on the language, another function is being called. For English, we get the following function call:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1002|Z1002]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that results in the English text</span> {{block indent|1=''"Nigeria is the most populous country in Africa."''}} <span lang="en" dir="ltr" class="mw-content-ltr">If we had chosen German, another function would be called:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1430|Z1430]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that in turn would result in the following German text:</span> {{block indent|1=''"Nigeria ist das bevölkerungsreichste Land Afrikas."''}} <div lang="en" dir="ltr" class="mw-content-ltr"> An example with more languages can be found here.<!-- where?? --> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia brings together numerous communities from the Wikimedia Movement and allows them to work together. Basic lexical data and structured data about many topics from Wikidata, functions that capture the necessary computations from Wikifunctions, and images and maps from Wikimedia Commons are all tied together in Abstract Wikipedia and made available for the more than 300 language editions of Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The goal of Abstract Wikipedia is to make more knowledge available to more people in more languages, and to allow volunteer editors to be more effective and work across languages, no matter what language they speak. Improvements to the knowledge will automatically propagate to the Wikipedias, errors will be spotted faster and fixed more effectively, and collaborations across languages become possible. We are tearing down the language barriers which are keeping knowledge apart. </div> bfszx0malyt25yoy14p7kauwbjmr10c 14330 14328 2026-08-10T08:42:13Z Martinligabue 7079 Created page with "Gli articoli di Abstract Wikipedia sono memorizzati in una notazione indipendente dalle lingue umane. L'interfaccia di Abstract Wikipedia consente ai collaboratori volontari di creare e gestire tale notazione indipendente dalla lingua. In una seconda fase, questa notazione viene convertita in testo in una lingua umana. Anche i passaggi necessari per realizzare questa conversione vengono creati e gestiti da una comunità di volontari su Wikifunctions. Questi passaggi poss..." 14330 wikitext text/x-wiki <languages /> [[Category:Abstract Wikipedia{{#translation:}}]] <span id="What_is_Abstract_Wikipedia?"></span> == Cos'è Abstract Wikipedia? == Abstract Wikipedia è un nuovo progetto fratello di Wikipedia. <div lang="en" dir="ltr" class="mw-content-ltr"> Wikipedia's vision is a world in which everyone has access to the sum of all knowledge. Abstract Wikipedia will help the communities of volunteers contributing to Wikipedia and its related projects to more effectively close knowledge gaps. </div> Wikipedia contiene articoli su oltre 20 milioni di argomenti in più di 300 lingue. Tuttavia, nessuna di queste lingue, da sola, consente di accedere alle conoscenze relative a questi 20 milioni di argomenti: l’inglese conta oltre sette milioni di articoli, il croato 230.000 e lo swahili 100.000. A meno che non si parlino quelle lingue, tali conoscenze non sono facilmente accessibili. E per quanto la traduzione automatica sia migliorata grazie ai recenti progressi nell’intelligenza artificiale, non è ancora in grado di produrre traduzioni affidabili per molte combinazioni linguistiche. Abstract Wikipedia lo fa senza ricorrere all’intelligenza artificiale. Ogni fase del processo rimane sotto il controllo umano ed è accessibile e modificabile dai volontari. Non ci sono allucinazioni, né errori inspiegabili e impossibili da correggere: se qualcosa non va, basta un solo passo per correggerlo, e c’è piena trasparenza su come il testo è stato creato. Non si tratta semplicemente di un modello probabilistico che sceglie ogni volta a caso la capitale del Kenya. Si tratta di conoscenza curata e gestita dall’uomo. <span id="How_does_Abstract_Wikipedia_work?"></span> == Come funziona Abstract Wikipedia? == Gli articoli di Abstract Wikipedia sono memorizzati in una notazione indipendente dalle lingue umane. L'interfaccia di Abstract Wikipedia consente ai collaboratori volontari di creare e gestire tale notazione indipendente dalla lingua. In una seconda fase, questa notazione viene convertita in testo in una lingua umana. Anche i passaggi necessari per realizzare questa conversione vengono creati e gestiti da una comunità di volontari su Wikifunctions. Questi passaggi possono utilizzare i dati presenti su [[D:|Wikidata]], consultando dati demografici, date di nascita o forme grammaticali irregolari, che sono stati aggiunti e vengono gestiti su Wikidata da comunità di volontari. Vedi [[Special:MyLanguage/Help:How to create an article|Aiuto:Come creare un articolo]] per una guida passo passo. <div lang="en" dir="ltr" class="mw-content-ltr"> Let's follow one example: [[Q1033|Nigeria is the most populous country in Africa.]] In Abstract Wikipedia, this might be stored as: </div> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], Z27243K5)}} <span lang="en" dir="ltr" class="mw-content-ltr">Or, if we use English labels for these identifiers:</span> {{block indent|1=superlative(Nigeria, populous, country, Africa, language)}} <span lang="en" dir="ltr" class="mw-content-ltr">This is a call to a function on Wikifunctions. Based on the language, another function is being called. For English, we get the following function call:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1002|Z1002]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that results in the English text</span> {{block indent|1=''"Nigeria is the most populous country in Africa."''}} <span lang="en" dir="ltr" class="mw-content-ltr">If we had chosen German, another function would be called:</span> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1430|Z1430]])}} <span lang="en" dir="ltr" class="mw-content-ltr">And that in turn would result in the following German text:</span> {{block indent|1=''"Nigeria ist das bevölkerungsreichste Land Afrikas."''}} <div lang="en" dir="ltr" class="mw-content-ltr"> An example with more languages can be found here.<!-- where?? --> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Abstract Wikipedia brings together numerous communities from the Wikimedia Movement and allows them to work together. Basic lexical data and structured data about many topics from Wikidata, functions that capture the necessary computations from Wikifunctions, and images and maps from Wikimedia Commons are all tied together in Abstract Wikipedia and made available for the more than 300 language editions of Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The goal of Abstract Wikipedia is to make more knowledge available to more people in more languages, and to allow volunteer editors to be more effective and work across languages, no matter what language they speak. Improvements to the knowledge will automatically propagate to the Wikipedias, errors will be spotted faster and fixed more effectively, and collaborations across languages become possible. We are tearing down the language barriers which are keeping knowledge apart. </div> ng4htpm7vimzgfvfw9mbvx7gdm6u8du 1198 5157 14311 2026-08-10T08:28:25Z Martinligabue 7079 Created page with "Abstract Wikipedia è un nuovo progetto fratello di Wikipedia." 14311 wikitext text/x-wiki Abstract Wikipedia è un nuovo progetto fratello di Wikipedia. 498eeb31c4ez7yc7ah7vkhu312s0t07 1198 5158 14313 2026-08-10T08:32:56Z Martinligabue 7079 Created page with "Wikipedia contiene articoli su oltre 20 milioni di argomenti in più di 300 lingue. Tuttavia, nessuna di queste lingue, da sola, consente di accedere alle conoscenze relative a questi 20 milioni di argomenti: l’inglese conta oltre sette milioni di articoli, il croato 230.000 e lo swahili 100.000. A meno che non si parlino quelle lingue, tali conoscenze non sono facilmente accessibili. E per quanto la traduzione automatica sia migliorata grazie ai recenti progressi nell..." 14313 wikitext text/x-wiki Wikipedia contiene articoli su oltre 20 milioni di argomenti in più di 300 lingue. Tuttavia, nessuna di queste lingue, da sola, consente di accedere alle conoscenze relative a questi 20 milioni di argomenti: l’inglese conta oltre sette milioni di articoli, il croato 230.000 e lo swahili 100.000. A meno che non si parlino quelle lingue, tali conoscenze non sono facilmente accessibili. E per quanto la traduzione automatica sia migliorata grazie ai recenti progressi nell’intelligenza artificiale, non è ancora in grado di produrre traduzioni affidabili per molte combinazioni linguistiche. s00dtr2vfji97ikqf51q4jk8idwz965 1198 5159 14315 2026-08-10T08:34:55Z Martinligabue 7079 Created page with "== Come funziona Abstract Wikipedia? ==" 14315 wikitext text/x-wiki == Come funziona Abstract Wikipedia? == tlaa18qh95c7c333ah61ng407sz67p6 1198 5160 14317 2026-08-10T08:35:46Z Martinligabue 7079 Created page with "Vedi [[$1|Aiuto:Come creare un articolo]] per una guida passo passo." 14317 wikitext text/x-wiki Vedi [[$1|Aiuto:Come creare un articolo]] per una guida passo passo. gpuyc1ujtjvr0oa6pnjdcf26pr2zl50 1198 5161 14319 2026-08-10T08:39:14Z Ameisenigel 31 Created page with "Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten"." 14319 wikitext text/x-wiki Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten". 9vx6axvhk7gk3uvz3uaxl19wrq6nk8f 1198 5162 14321 2026-08-10T08:39:22Z Ameisenigel 31 Created page with "Start" 14321 wikitext text/x-wiki Start hfcmf6i1s8j8yatvdgjw2b37iz17hvr 1198 5163 14323 2026-08-10T08:40:45Z Ameisenigel 31 Created page with "Klicke auf das Symbol mit den drei Punkten und wähle dann "In die Zwischenablage kopieren"." 14323 wikitext text/x-wiki Klicke auf das Symbol mit den drei Punkten und wähle dann "In die Zwischenablage kopieren". 2715sq0mdk3cuel0ey3yilv1u3ydlgc 1198 5164 14325 2026-08-10T08:40:55Z Ameisenigel 31 Created page with "In die Zwischenablage kopieren" 14325 wikitext text/x-wiki In die Zwischenablage kopieren 6khnhrtkvfpg8bal4j6ef8gfduz2swa 1198 5165 14327 2026-08-10T08:41:27Z Martinligabue 7079 Created page with "Abstract Wikipedia lo fa senza ricorrere all’intelligenza artificiale. Ogni fase del processo rimane sotto il controllo umano ed è accessibile e modificabile dai volontari. Non ci sono allucinazioni, né errori inspiegabili e impossibili da correggere: se qualcosa non va, basta un solo passo per correggerlo, e c’è piena trasparenza su come il testo è stato creato. Non si tratta semplicemente di un modello probabilistico che sceglie ogni volta a caso la capitale de..." 14327 wikitext text/x-wiki Abstract Wikipedia lo fa senza ricorrere all’intelligenza artificiale. Ogni fase del processo rimane sotto il controllo umano ed è accessibile e modificabile dai volontari. Non ci sono allucinazioni, né errori inspiegabili e impossibili da correggere: se qualcosa non va, basta un solo passo per correggerlo, e c’è piena trasparenza su come il testo è stato creato. Non si tratta semplicemente di un modello probabilistico che sceglie ogni volta a caso la capitale del Kenya. Si tratta di conoscenza curata e gestita dall’uomo. owdtta7fjd8vxdg4ff776gtj6buvvr5 1198 5166 14329 2026-08-10T08:42:12Z Martinligabue 7079 Created page with "Gli articoli di Abstract Wikipedia sono memorizzati in una notazione indipendente dalle lingue umane. L'interfaccia di Abstract Wikipedia consente ai collaboratori volontari di creare e gestire tale notazione indipendente dalla lingua. In una seconda fase, questa notazione viene convertita in testo in una lingua umana. Anche i passaggi necessari per realizzare questa conversione vengono creati e gestiti da una comunità di volontari su Wikifunctions. Questi passaggi poss..." 14329 wikitext text/x-wiki Gli articoli di Abstract Wikipedia sono memorizzati in una notazione indipendente dalle lingue umane. L'interfaccia di Abstract Wikipedia consente ai collaboratori volontari di creare e gestire tale notazione indipendente dalla lingua. In una seconda fase, questa notazione viene convertita in testo in una lingua umana. Anche i passaggi necessari per realizzare questa conversione vengono creati e gestiti da una comunità di volontari su Wikifunctions. Questi passaggi possono utilizzare i dati presenti su [[$0|Wikidata]], consultando dati demografici, date di nascita o forme grammaticali irregolari, che sono stati aggiunti e vengono gestiti su Wikidata da comunità di volontari. 7clyz526v7fnae2nrwtmqtsi453if1s