Abstract Wikipedia abstractwiki https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page MediaWiki 1.47.0-wmf.11 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 12225 12215 2026-07-17T12:20:42Z 99of9 614 /* Feedback needed on constructing a new abstract article */ Reply 12225 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) ==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:intro for year|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 --> g28oatb3hw7p1b0a5p0cj7co1gjdvg8 12226 12225 2026-07-17T12:33:06Z HenkvD 1447 /* Feedback needed on constructing a new abstract article */ Reply 12226 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) ==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:intro for year|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 --> 2tjfvodmw7oqd30hxshzs33i8coolvd 12227 12226 2026-07-17T12:42:51Z 99of9 614 /* Feedback needed on constructing a new abstract article */ Reply 12227 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:intro for year|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 --> bw3lut4u9vijh0i991xnnl0uyslhow0 12228 12227 2026-07-17T12:43:28Z 99of9 614 /* Feedback needed on constructing a new abstract article */ 12228 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:intro for year|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 --> 4vw4nt0hbil4s16nzxeuzyytc3wqb9l 12229 12228 2026-07-17T12:44:35Z HenkvD 1447 /* Feedback on function I created */ linkfix 12229 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 --> n69jg0bb01ewamjzu83d9c0kukcsj67 4 450 12357 12125 2026-07-18T10:18:37Z HenkvD 1447 /* auto-created broken articles */ +379 articles of [[User:Immanuelle]] 12357 wikitext text/x-wiki __NEWSECTIONLINK__ This page is the venue to request for the deletion of pages that cannot be speedy deleted (see also [[Template:Delete]]). [[Category:Abstract Wikipedia administration]] == Scholarly articles == * [[Q67404404]] {{Q|67404404}} * [[Q50082993]] {{Q|50082993}} * [[Q68271926]] {{Q|68271926}} * [[Q114133712]] {{Q|114133712}} There is very little abstract encyclopedic content that can come out of a page about a specific, non-notable scholarly article. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 19:07, 18 May 2026 (UTC) :We currently don't have a community-ratified definition of notability. I've tried to kick off this discussion [[Project:Notability|here]]. For now, I ask that stewards/global sysops '''wait''' until we come to a consensus on a policy. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:10, 18 May 2026 (UTC) ::{{ping|JJPMaster}} very interesting request. I'm not entirely sure... I would tend to agree for these papers but not all of them ({{Q|Q30249683}} exists on 16 Wikipedias for instance), so where to put the threshold between notable and non-notable? on which criteria? Anyway, I agree to ''wait'' until the community reach a consensus on what is notable on AW. Also, I'm pinging {{ping|Immanuelle}} who created these articles. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 14:13, 30 May 2026 (UTC) *{{vd}} low quality, no response or improvement. The case for significance of these topics is not made in the articles. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:26, 15 July 2026 (UTC) == [[Q6489603]] == See [[Talk:Q6489603]]. This does not work as a category, it is more an article about a category. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 08:34, 31 May 2026 (UTC) : Under my [[Abstract Wikipedia:Notability|proposed notability guideline]], this would not be notable, so I {{s}} deletion [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:30, 31 May 2026 (UTC) ::@[[User:Ameisenigel|Ameisenigel]] @[[User:Feeglgeef|Feeglgeef]] Although the page has been deleted, I believe that the vague wording related to categories (and templates) should be clarified. Please review and improve the deletion policy to help current and future contributors better understand how categories are handled. Refer [[Abstract Wikipedia talk:Deletion policy#Categories]] [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:07, 18 June 2026 (UTC) :{{Done|Deleted}} <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 14:07, 17 June 2026 (UTC) == Creations by XeNivalys == [[user:XeNivalys]] has posted several pages as part of their cross-wiki spam crusade. Please delete them all and if possible issue a block. --[[User:Bedivere|Bedivere]] ([[User talk:Bedivere|talk]]) 04:53, 9 June 2026 (UTC) :{{Done|Deleted}}. 🪶-[[User:Tanbiruzzaman|<span style="font-family:monospace;color:#006400;letter-spacing:1px;">TΛNBIRUZZΛMΛN</span>]] ([[User talk:Tanbiruzzaman|💬]]) 08:33, 9 June 2026 (UTC) == auto-created broken articles == I suggest we do a bit of a cleanup of pages that were created by a software tool, using immature functions that have been deprecated for months, that would be very annoying to clean up by hand. So I propose deletion of the following (feel free to add to this list anything that matches this description). No prejudice to re-creation if anyone wants to make them good. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:20, 15 July 2026 (UTC) * [[Q11378973]] * [[Q11433427]] * [[Q11395853]] * [[Q11465292]] * [[Q11467693]] * [[Q7768]] [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:20, 15 July 2026 (UTC) : I thout the same, or even more: I would like to discuss if it is best to delete outdated articles. There is a lot of discussion and critique about a lot of those articles. I think in particular to articles created by @Immanuelle, that are not edited afterwards by somebody else. Those articles were a) created in mass and b) most of them with outdated functions. PS: I value the attempt of use:Immanuelle and hope to see him/her to continue on this project, now or later. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:44, 15 July 2026 (UTC) ::Ping [[User:Immanuelle]]. Do you mind if we heavily clean up some of your contributions? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:25, 15 July 2026 (UTC) : Articles created by [[User:Immanuelle]] and not edited after creation. I would likt to propet to delete these (if not already propede above): :*[[Q29682]] Sumiyoshi Shrine :*[[Q135040386]] Takeihakatsuno Shrine :*[[Q63471]] Omura Shrine :*[[Q65320]] Iwa Shrine :*[[Q94057]] Olive Shrine :*[[Q94317]] Kikuchi Shrine :*[[Q94760]] Kotohira-gū :*[[Q116140]] Tado Taisha :*[[Q133753]] Shiogama Shrine :*[[Q135732]] Ōagata Shrine :*[[Q137707]] Katō Shrine :*[[Q167136]] Kengun Shrine :*[[Q172253]] Amatsu Shrine :*[[Q195684]] Yahiko Shrine :*[[Q199699]] Tsurumine Hachiman Shrine :*[[Q211522]] Sannō Shrine :*[[Q246469]] Wakasa Shrine :*[[Q246479]] Ikoma Shrine :*[[Q246667]] Hakuto Shrine :*[[Q251160]] Ōgamiyama Shrine :*[[Q251682]] Yūtoku Inari Shrine :*[[Q276779]] Kifune Shrine :*[[Q276830]] Seimei Shrine :*[[Q276831]] Mitami Shrine :*[[Q283483]] Kanō Tenmangū :*[[Q288248]] Tokorozawa Shinmei Shrine :*[[Q703904]] Oyamazumi Shrine :*[[Q704219]] Terukuni Shrine :*[[Q704430]] Udo Jingū :*[[Q704622]] Kirishima Jingū :*[[Q704636]] Naminoue Shrine :*[[Q704686]] Miyazaki Jingū :*[[Q704702]] Shirayama Hime Shrine :*[[Q704855]] Hōkoku Shrine :*[[Q704865]] Hida Ichinomiya Minashi Shrine :*[[Q704876]] Kasama Inari Shrine :*[[Q704890]] Tosa Shrine :*[[Q704898]] Hōfu Tenmangū :*[[Q705136]] Tsushima Shrine :*[[Q705297]] Nishinomiya Shrine :*[[Q705303]] Shirahige Shrine :*[[Q705310]] Hakone Shrine :*[[Q705542]] Ōmiwa Shrine :*[[Q706499]] Kashima Jingū :*[[Q11360548]] Kamitakano Shrine :*[[Q11360577]] Shimonaka Hachiman :*[[Q11360668]] Shimohara-hachiman Shrine :*[[Q11360748]] Shimomasuda Shrine :*[[Q11360904]] Shimogoryō Shrine :*[[Q11361253]] Shimoshinmei Tenso Shrine :*[[Q11361494]] Shimodate Haguro Shrine :*[[Q11361528]] Shimoshiotsu Shrine :*[[Q11361819]] Fuba-hachimangu :*[[Q23548]] National Aeronautics and Space Administration :*[[Q11691]] stock exchange :*[[Q42274]] Google Earth :*[[Q80228]] bottle :*[[Q173799]] entertainment :*[[Q18123741]] infectious disease :*[[Q16550]] Breithorn :*[[Q569243]] Universiti Brunei Darussalam :*[[Q602]] Rhône :*[[Q15928]] Velenje :*[[Q45677]] Château de Choisy :*[[Q503530]] Sioma Ngwezi National Park :*[[Q499550]] Smith Islands National Park :*[[Q503518]] Lower Zambezi National Park :*[[Q150]] French :*[[Q404]] HTTP 404 :*[[Q42397345]] 307 Temporary Redirect :*[[Q38897603]] Observations on urethral infection in the male. :*[[Q379519]] Mid-Autumn Festival :*[[Q45470]] Sasuke Inari Shrine :*[[Q372380]] Katori Jingū :*[[Q385407]] Ōmi Jingū :*[[Q482065]] Atsuta Jingū :*[[Q521319]] Takekoma Inari Shrine :*[[Q631373]] Kashii-gū :*[[Q5151]] month :*[[Q444]] Lech Wałęsa :*[[Q555]] Rachel Maddow :*[[Q999]] astatine :*[[Q461391]] Gavin Newsom :*[[Q868]] Aristotle :*[[Q9181]] Abraham :*[[Q91]] Abraham Lincoln :*[[Q3783]] Amazon :*[[Q10987]] honey :*[[Q11663]] weather :*[[Q884]] South Korea :*[[Q7235]] Sophocles :*[[Q11002]] sugar :*[[Q376]] clock :*[[Q11391]] ultraviolet radiation :*[[Q9358]] Friedrich Nietzsche :*[[Q7317]] Giuseppe Verdi :*[[Q13217298]] Giza Necropolis :*[[Q2487]] Thirty Years' War :*[[Q8269]] The Tale of Genji :*[[Q9438]] Thomas Aquinas :*[[Q8743]] Thomas Edison :*[[Q12514]] Three Gorges Dam :*[[Q80]] Tim Berners-Lee :*[[Q8736]] Treaty of Versailles :*[[Q8467]] Umar ibn Al-Khattāb :*[[Q8740]] Vietnam War :*[[Q7355]] Yellow River :*[[Q11205]] arithmetic :*[[Q6206]] capitalism :*[[Q573]] day :*[[Q8047]] enzyme :*[[Q8597]] Akbar :*[[Q8409]] Alexander the Great :*[[Q7850]] Chinese :*[[Q8275]] Iliad :*[[Q37660]] South China Sea :*[[Q313]] Venus :*[[Q362]] World War II :*[[Q12078]] cancer :*[[Q199804]] chronic obstructive pulmonary disease :*[[Q8142]] currency :*[[Q7430]] deoxyribonucleic acid :*[[Q12493]] dome :*[[Q2095]] food :*[[Q937]] Albert Einstein :*[[Q12104]] Avena sativa :*[[Q612]] Dubai :*[[Q905]] Franz Kafka :*[[Q5588]] Frida Kahlo :*[[Q125851781]] Fâtih Sultan Mehemmed Han :*[[Q7742]] Louis XIV of France :*[[Q5816]] Mao Zedong :*[[Q1218]] Jerusalem :*[[Q12554]] Middle Ages :*[[Q517]] Napoleon :*[[Q5599]] Peter Paul Rubens :*[[Q5577]] Salvador Dalí :*[[Q12099]] Secale cereale :*[[Q9316]] Sikhism :*[[Q933]] South Pole :*[[Q254]] Wolfgang Amadeus Mozart :*[[Q9683]] Tang dynasty :*[[Q9121]] atom :*[[Q5322]] capacitor :*[[Q7164]] World Bank :*[[Q3559]] comet :*[[Q6186]] communism :*[[Q258]] South Africa :*[[Q317]] dictatorship :*[[Q11651]] electric current :*[[Q8162]] linguistics :*[[Q11468]] nanotechnology :*[[Q8461]] racism :*[[Q9165]] soul :*[[Q287]] wood :*[[Q6388]] swimming :*[[Q12214]] smallpox :*[[Q9794]] reggae :*[[Q7380]] primate :*[[Q11372]] physical chemistry :*[[Q9404]] nervous system :*[[Q382441]] marine mammal :*[[Q3]] life :*[[Q11028]] information :*[[Q7075]] library :*[[Q1072]] heart :*[[Q11364]] hormone :*[[Q8458]] human rights :*[[Q8492]] juice :*[[Q82571]] linear algebra :*[[Q12800]] machine gun :*[[Q12167]] malnutrition :*[[Q10990]] meat :*[[Q7269]] monarchy :*[[Q11426]] metal :*[[Q6235]] nationalism :*[[Q12739]] nuclear power :*[[Q11472]] paper :*[[Q12195]] poliomyelitis :*[[Q10998]] potato :*[[Q7372]] shark :*[[Q5916]] spaceflight :*[[Q42527]] spice :*[[Q7553]] translation :*[[Q808]] virus :*[[Q8072]] volcano :*[[Q12876]] tank :*[[Q8188]] syllable :*[[Q10737]] suicide :*[[Q1511]] Richard Wagner :*[[Q7315]] Pyotr Ilyich Tchaikovsky :*[[Q11518]] Pythagorean theorem :*[[Q11451199]] List of Shikinaisha in Aki Province :*[[Q11379]] energy :*[[Q9103]] female breast :*[[Q11435]] liquid :*[[Q86]] headache :*[[Q11573]] metre :*[[Q8495]] milk :*[[Q11009]] nut :*[[Q5994]] piano :*[[Q11474]] plastic :*[[Q11423]] mass :*[[Q11190]] medicine :*[[Q9492]] probability :*[[Q9465]] ethics :*[[Q619]] Nicolaus Copernicus :*[[Q1399]] Niccolò Machiavelli :*[[Q9049]] Noam Chomsky :*[[Q332]] Neptune :*[[Q7176]] Naguib Mahfouz :*[[Q5592]] Michelangelo :*[[Q5513]] Lake Baikal :*[[Q5679]] Lord Byron :*[[Q7071]] Li Bai :*[[Q7259]] Ada Lovelace :*[[Q7172]] League of Arab States :*[[Q5879]] Johann Wolfgang von Goethe :*[[Q169470]] physicist :*[[Q719665]] Inari :*[[Q276944]] Ōkuninushi :*[[Q386563]] Ōyamatsumi :*[[Q1474187]] Watatsumi :*[[Q352]] Adolf Hitler :*[[Q7251]] Alan Turing :*[[Q5484]] Caspian Sea :*[[Q9592]] Catholic Church :*[[Q160]] Cetacea :*[[Q3044]] Charlemagne :*[[Q7207]] Elizabeth I of England :*[[Q181765]] Holy Roman Emperor :*[[Q12138]] Gregorian calendar :*[[Q9089]] Hinduism :*[[Q7226]] Joan of Arc :*[[Q9317]] John Maynard Keynes :*[[Q5603]] Andy Warhol :*[[Q1357]] Araneae :*[[Q1828555]] Arabic script :*[[Q5685]] Anton Chekhov :*[[Q748]] Buddhism :*[[Q500]] Citrus × limon :*[[Q3503]] Congo :*[[Q8413]] Constantine the Great :*[[Q1043]] Carl Linnaeus :*[[Q303]] Elvis Presley :*[[Q9130]] Erwin Schrödinger :*[[Q8007]] Franklin Delano Roosevelt :*[[Q5432]] Francisco Goya :*[[Q5089]] Ganges :*[[Q8778]] Galen :*[[Q9235]] Georg Wilhelm Friedrich Hegel :*[[Q720]] Genghis Khan :*[[Q188]] German :*[[Q7895]] reproductive system :*[[Q15969]] Jean Améry :*[[Q20925]] 1986 Belgian Grand Prix :*[[Q96221]] Heinrich Ehrhardt :*[[Q77534]] Doris Pack :*[[Q454]] peace :*[[Q5251735]] defuzzification :*[[Q11408]] magnetic field :*[[Q9368]] liver :*[[Q9620]] nerve :*[[Q11756]] prehistory :*[[Q851]] Saudi Arabia :*[[Q9215]] Sigmund Freud :*[[Q332062]] Sorghum bicolor :*[[Q9202]] Statue of Liberty :*[[Q1049]] Sudan :*[[Q35355]] Sumer :*[[Q8251]] The Art of War :*[[Q1071]] geography :*[[Q5325]] inductor :*[[Q205]] infinity :*[[Q12140]] medication :*[[Q627]] nitrogen :*[[Q12802]] nuclear weapon :*[[Q569]] beryllium :*[[Q618]] boron :*[[Q650]] fluorine :*[[Q654]] neon :*[[Q658]] sodium :*[[Q663]] aluminium :*[[Q670]] silicon :*[[Q682]] sulfur :*[[Q706]] calcium :*[[Q722]] vanadium :*[[Q725]] chromium :*[[Q731]] manganese :*[[Q677]] iron :*[[Q740]] cobalt :*[[Q744]] nickel :*[[Q758]] zinc :*[[Q1304]] livermorium :*[[Q1103]] iodine :*[[Q1108]] caesium :*[[Q888]] krypton :*[[Q938]] strontium :*[[Q941]] yttrium :*[[Q1046]] niobium :*[[Q1053]] molybdenum :*[[Q1054]] technetium :*[[Q1086]] ruthenium :*[[Q1087]] rhodium :*[[Q1090]] silver :*[[Q1094]] indium :*[[Q1099]] antimony :*[[Q7159]] African Union :*[[Q9546]] Al-Ghazali :*[[Q5580]] Albrecht Dürer :*[[Q7374]] Alfred Hitchcock :*[[Q727]] Amsterdam :*[[Q1340]] Antonio Vivaldi :*[[Q7298]] Antonín Dvořák :*[[Q10872]] Archaea :*[[Q8589]] Ashoka :*[[Q8018]] Augustine of Hippo :*[[Q7768]] Association of Southeast Asian Nations :*[[Q1486]] Buenos Aires :*[[Q9045]] Chanakya Kautilya :*[[Q2042]] Charles de Gaulle :*[[Q882]] Charlie Chaplin :*[[Q7322]] Christopher Columbus :*[[Q81513]] Citrus :*[[Q8209]] Cyrillic script :*[[Q1067]] Dante Alighieri :*[[Q7939]] El Niño :*[[Q613]] Emirate of Dubai :*[[Q8272]] Epic of Gilgamesh :*[[Q115]] Ethiopia :*[[Q8747]] Euclid :*[[Q5683]] Geoffrey Chaucer :*[[Q8229]] Latin script :*[[Q4918]] Mediterranean Sea :*[[Q25326]] Mollusca :*[[Q9458]] Muhammad :*[[Q5185]] Nematoda :*[[Q11379325]] Izawa Shrine :*[[Q11379739]] Imari Shrine :*[[Q575650]] Rust :*[[Q34010]] Haskell :*[[Q978185]] TypeScript :*[[Q479833]] batch file :*[[Q42979]] BASIC :*[[Q131140]] COBOL :*[[Q648619]] F# :*[[Q334879]] Erlang :*[[Q83303]] Fortran :*[[Q2613697]] Julia :*[[Q207316]] Lua :*[[Q212587]] OCaml :*[[Q840410]] PowerShell :*[[Q235086]] Smalltalk :*[[Q17147733]] Swift :*[[Q582706]] Israeli settlement :*[[Q1107129]] sōja :*[[Q127866012]] A Simple Example for Linear Partial Differential Equations and Its Solution Using the Method of Separation of Variables :*[[Q30249683]] Attention Is All You Need :*[[Q210907]] Haida Gwaii :*[[Q9876]] Vught :*[[Q13489381]] effective altruism :*[[Q82945199]] Alfréd von Adda :*[[Q114133712]] Evaluating the biological validity of European river typology systems with least disturbed benthic macroinvertebrate communities :*[[Q68271926]] Spectroscopic evidence of infall and outflow around intermediate high-mass YSOs in the Mon OB1 dark cloud :*[[Q63308014]] (222315) 2000 ST367 :*[[Q50082993]] Comparison of the applicability of Demirjian and Willems methods for dental age estimation in children from the Thrace region, Turkey. :*[[Q31266481]] Cerro Guayaquil :*[[Q4180914]] Test d'évaluation du français :*[[Q12171]] menstruation :*[[Q8065]] natural disaster :*[[Q12184]] pandemic :*[[Q8183]] phoneme :*[[Q67404404]] Response of the rabbit vas deferens in vivo to vasoactive drugs :*[[Q8070]] tsunami :*[[Q7283]] terrorism :*[[Q139491990]] JEPA :*[[Q118876059]] Claude :*[[Q116758847]] Anthropic :*[[Q112508731]] Blake Lemoine : [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:18, 18 July 2026 (UTC) lvnswjgii2ko0yhpnmzqywurhwosqhy 12359 12357 2026-07-18T10:21:48Z HenkvD 1447 /* auto-created broken articles */ typos 12359 wikitext text/x-wiki __NEWSECTIONLINK__ This page is the venue to request for the deletion of pages that cannot be speedy deleted (see also [[Template:Delete]]). [[Category:Abstract Wikipedia administration]] == Scholarly articles == * [[Q67404404]] {{Q|67404404}} * [[Q50082993]] {{Q|50082993}} * [[Q68271926]] {{Q|68271926}} * [[Q114133712]] {{Q|114133712}} There is very little abstract encyclopedic content that can come out of a page about a specific, non-notable scholarly article. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 19:07, 18 May 2026 (UTC) :We currently don't have a community-ratified definition of notability. I've tried to kick off this discussion [[Project:Notability|here]]. For now, I ask that stewards/global sysops '''wait''' until we come to a consensus on a policy. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:10, 18 May 2026 (UTC) ::{{ping|JJPMaster}} very interesting request. I'm not entirely sure... I would tend to agree for these papers but not all of them ({{Q|Q30249683}} exists on 16 Wikipedias for instance), so where to put the threshold between notable and non-notable? on which criteria? Anyway, I agree to ''wait'' until the community reach a consensus on what is notable on AW. Also, I'm pinging {{ping|Immanuelle}} who created these articles. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 14:13, 30 May 2026 (UTC) *{{vd}} low quality, no response or improvement. The case for significance of these topics is not made in the articles. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:26, 15 July 2026 (UTC) == [[Q6489603]] == See [[Talk:Q6489603]]. This does not work as a category, it is more an article about a category. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 08:34, 31 May 2026 (UTC) : Under my [[Abstract Wikipedia:Notability|proposed notability guideline]], this would not be notable, so I {{s}} deletion [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:30, 31 May 2026 (UTC) ::@[[User:Ameisenigel|Ameisenigel]] @[[User:Feeglgeef|Feeglgeef]] Although the page has been deleted, I believe that the vague wording related to categories (and templates) should be clarified. Please review and improve the deletion policy to help current and future contributors better understand how categories are handled. Refer [[Abstract Wikipedia talk:Deletion policy#Categories]] [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:07, 18 June 2026 (UTC) :{{Done|Deleted}} <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 14:07, 17 June 2026 (UTC) == Creations by XeNivalys == [[user:XeNivalys]] has posted several pages as part of their cross-wiki spam crusade. Please delete them all and if possible issue a block. --[[User:Bedivere|Bedivere]] ([[User talk:Bedivere|talk]]) 04:53, 9 June 2026 (UTC) :{{Done|Deleted}}. 🪶-[[User:Tanbiruzzaman|<span style="font-family:monospace;color:#006400;letter-spacing:1px;">TΛNBIRUZZΛMΛN</span>]] ([[User talk:Tanbiruzzaman|💬]]) 08:33, 9 June 2026 (UTC) == auto-created broken articles == I suggest we do a bit of a cleanup of pages that were created by a software tool, using immature functions that have been deprecated for months, that would be very annoying to clean up by hand. So I propose deletion of the following (feel free to add to this list anything that matches this description). No prejudice to re-creation if anyone wants to make them good. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:20, 15 July 2026 (UTC) * [[Q11378973]] * [[Q11433427]] * [[Q11395853]] * [[Q11465292]] * [[Q11467693]] * [[Q7768]] [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:20, 15 July 2026 (UTC) : I thout the same, or even more: I would like to discuss if it is best to delete outdated articles. There is a lot of discussion and critique about a lot of those articles. I think in particular to articles created by @Immanuelle, that are not edited afterwards by somebody else. Those articles were a) created in mass and b) most of them with outdated functions. PS: I value the attempt of use:Immanuelle and hope to see him/her to continue on this project, now or later. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:44, 15 July 2026 (UTC) ::Ping [[User:Immanuelle]]. Do you mind if we heavily clean up some of your contributions? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:25, 15 July 2026 (UTC) : Articles created by [[User:Immanuelle]] and not edited after creation. I would like to propose to delete these (if not already mentioned above): :*[[Q29682]] Sumiyoshi Shrine :*[[Q135040386]] Takeihakatsuno Shrine :*[[Q63471]] Omura Shrine :*[[Q65320]] Iwa Shrine :*[[Q94057]] Olive Shrine :*[[Q94317]] Kikuchi Shrine :*[[Q94760]] Kotohira-gū :*[[Q116140]] Tado Taisha :*[[Q133753]] Shiogama Shrine :*[[Q135732]] Ōagata Shrine :*[[Q137707]] Katō Shrine :*[[Q167136]] Kengun Shrine :*[[Q172253]] Amatsu Shrine :*[[Q195684]] Yahiko Shrine :*[[Q199699]] Tsurumine Hachiman Shrine :*[[Q211522]] Sannō Shrine :*[[Q246469]] Wakasa Shrine :*[[Q246479]] Ikoma Shrine :*[[Q246667]] Hakuto Shrine :*[[Q251160]] Ōgamiyama Shrine :*[[Q251682]] Yūtoku Inari Shrine :*[[Q276779]] Kifune Shrine :*[[Q276830]] Seimei Shrine :*[[Q276831]] Mitami Shrine :*[[Q283483]] Kanō Tenmangū :*[[Q288248]] Tokorozawa Shinmei Shrine :*[[Q703904]] Oyamazumi Shrine :*[[Q704219]] Terukuni Shrine :*[[Q704430]] Udo Jingū :*[[Q704622]] Kirishima Jingū :*[[Q704636]] Naminoue Shrine :*[[Q704686]] Miyazaki Jingū :*[[Q704702]] Shirayama Hime Shrine :*[[Q704855]] Hōkoku Shrine :*[[Q704865]] Hida Ichinomiya Minashi Shrine :*[[Q704876]] Kasama Inari Shrine :*[[Q704890]] Tosa Shrine :*[[Q704898]] Hōfu Tenmangū :*[[Q705136]] Tsushima Shrine :*[[Q705297]] Nishinomiya Shrine :*[[Q705303]] Shirahige Shrine :*[[Q705310]] Hakone Shrine :*[[Q705542]] Ōmiwa Shrine :*[[Q706499]] Kashima Jingū :*[[Q11360548]] Kamitakano Shrine :*[[Q11360577]] Shimonaka Hachiman :*[[Q11360668]] Shimohara-hachiman Shrine :*[[Q11360748]] Shimomasuda Shrine :*[[Q11360904]] Shimogoryō Shrine :*[[Q11361253]] Shimoshinmei Tenso Shrine :*[[Q11361494]] Shimodate Haguro Shrine :*[[Q11361528]] Shimoshiotsu Shrine :*[[Q11361819]] Fuba-hachimangu :*[[Q23548]] National Aeronautics and Space Administration :*[[Q11691]] stock exchange :*[[Q42274]] Google Earth :*[[Q80228]] bottle :*[[Q173799]] entertainment :*[[Q18123741]] infectious disease :*[[Q16550]] Breithorn :*[[Q569243]] Universiti Brunei Darussalam :*[[Q602]] Rhône :*[[Q15928]] Velenje :*[[Q45677]] Château de Choisy :*[[Q503530]] Sioma Ngwezi National Park :*[[Q499550]] Smith Islands National Park :*[[Q503518]] Lower Zambezi National Park :*[[Q150]] French :*[[Q404]] HTTP 404 :*[[Q42397345]] 307 Temporary Redirect :*[[Q38897603]] Observations on urethral infection in the male. :*[[Q379519]] Mid-Autumn Festival :*[[Q45470]] Sasuke Inari Shrine :*[[Q372380]] Katori Jingū :*[[Q385407]] Ōmi Jingū :*[[Q482065]] Atsuta Jingū :*[[Q521319]] Takekoma Inari Shrine :*[[Q631373]] Kashii-gū :*[[Q5151]] month :*[[Q444]] Lech Wałęsa :*[[Q555]] Rachel Maddow :*[[Q999]] astatine :*[[Q461391]] Gavin Newsom :*[[Q868]] Aristotle :*[[Q9181]] Abraham :*[[Q91]] Abraham Lincoln :*[[Q3783]] Amazon :*[[Q10987]] honey :*[[Q11663]] weather :*[[Q884]] South Korea :*[[Q7235]] Sophocles :*[[Q11002]] sugar :*[[Q376]] clock :*[[Q11391]] ultraviolet radiation :*[[Q9358]] Friedrich Nietzsche :*[[Q7317]] Giuseppe Verdi :*[[Q13217298]] Giza Necropolis :*[[Q2487]] Thirty Years' War :*[[Q8269]] The Tale of Genji :*[[Q9438]] Thomas Aquinas :*[[Q8743]] Thomas Edison :*[[Q12514]] Three Gorges Dam :*[[Q80]] Tim Berners-Lee :*[[Q8736]] Treaty of Versailles :*[[Q8467]] Umar ibn Al-Khattāb :*[[Q8740]] Vietnam War :*[[Q7355]] Yellow River :*[[Q11205]] arithmetic :*[[Q6206]] capitalism :*[[Q573]] day :*[[Q8047]] enzyme :*[[Q8597]] Akbar :*[[Q8409]] Alexander the Great :*[[Q7850]] Chinese :*[[Q8275]] Iliad :*[[Q37660]] South China Sea :*[[Q313]] Venus :*[[Q362]] World War II :*[[Q12078]] cancer :*[[Q199804]] chronic obstructive pulmonary disease :*[[Q8142]] currency :*[[Q7430]] deoxyribonucleic acid :*[[Q12493]] dome :*[[Q2095]] food :*[[Q937]] Albert Einstein :*[[Q12104]] Avena sativa :*[[Q612]] Dubai :*[[Q905]] Franz Kafka :*[[Q5588]] Frida Kahlo :*[[Q125851781]] Fâtih Sultan Mehemmed Han :*[[Q7742]] Louis XIV of France :*[[Q5816]] Mao Zedong :*[[Q1218]] Jerusalem :*[[Q12554]] Middle Ages :*[[Q517]] Napoleon :*[[Q5599]] Peter Paul Rubens :*[[Q5577]] Salvador Dalí :*[[Q12099]] Secale cereale :*[[Q9316]] Sikhism :*[[Q933]] South Pole :*[[Q254]] Wolfgang Amadeus Mozart :*[[Q9683]] Tang dynasty :*[[Q9121]] atom :*[[Q5322]] capacitor :*[[Q7164]] World Bank :*[[Q3559]] comet :*[[Q6186]] communism :*[[Q258]] South Africa :*[[Q317]] dictatorship :*[[Q11651]] electric current :*[[Q8162]] linguistics :*[[Q11468]] nanotechnology :*[[Q8461]] racism :*[[Q9165]] soul :*[[Q287]] wood :*[[Q6388]] swimming :*[[Q12214]] smallpox :*[[Q9794]] reggae :*[[Q7380]] primate :*[[Q11372]] physical chemistry :*[[Q9404]] nervous system :*[[Q382441]] marine mammal :*[[Q3]] life :*[[Q11028]] information :*[[Q7075]] library :*[[Q1072]] heart :*[[Q11364]] hormone :*[[Q8458]] human rights :*[[Q8492]] juice :*[[Q82571]] linear algebra :*[[Q12800]] machine gun :*[[Q12167]] malnutrition :*[[Q10990]] meat :*[[Q7269]] monarchy :*[[Q11426]] metal :*[[Q6235]] nationalism :*[[Q12739]] nuclear power :*[[Q11472]] paper :*[[Q12195]] poliomyelitis :*[[Q10998]] potato :*[[Q7372]] shark :*[[Q5916]] spaceflight :*[[Q42527]] spice :*[[Q7553]] translation :*[[Q808]] virus :*[[Q8072]] volcano :*[[Q12876]] tank :*[[Q8188]] syllable :*[[Q10737]] suicide :*[[Q1511]] Richard Wagner :*[[Q7315]] Pyotr Ilyich Tchaikovsky :*[[Q11518]] Pythagorean theorem :*[[Q11451199]] List of Shikinaisha in Aki Province :*[[Q11379]] energy :*[[Q9103]] female breast :*[[Q11435]] liquid :*[[Q86]] headache :*[[Q11573]] metre :*[[Q8495]] milk :*[[Q11009]] nut :*[[Q5994]] piano :*[[Q11474]] plastic :*[[Q11423]] mass :*[[Q11190]] medicine :*[[Q9492]] probability :*[[Q9465]] ethics :*[[Q619]] Nicolaus Copernicus :*[[Q1399]] Niccolò Machiavelli :*[[Q9049]] Noam Chomsky :*[[Q332]] Neptune :*[[Q7176]] Naguib Mahfouz :*[[Q5592]] Michelangelo :*[[Q5513]] Lake Baikal :*[[Q5679]] Lord Byron :*[[Q7071]] Li Bai :*[[Q7259]] Ada Lovelace :*[[Q7172]] League of Arab States :*[[Q5879]] Johann Wolfgang von Goethe :*[[Q169470]] physicist :*[[Q719665]] Inari :*[[Q276944]] Ōkuninushi :*[[Q386563]] Ōyamatsumi :*[[Q1474187]] Watatsumi :*[[Q352]] Adolf Hitler :*[[Q7251]] Alan Turing :*[[Q5484]] Caspian Sea :*[[Q9592]] Catholic Church :*[[Q160]] Cetacea :*[[Q3044]] Charlemagne :*[[Q7207]] Elizabeth I of England :*[[Q181765]] Holy Roman Emperor :*[[Q12138]] Gregorian calendar :*[[Q9089]] Hinduism :*[[Q7226]] Joan of Arc :*[[Q9317]] John Maynard Keynes :*[[Q5603]] Andy Warhol :*[[Q1357]] Araneae :*[[Q1828555]] Arabic script :*[[Q5685]] Anton Chekhov :*[[Q748]] Buddhism :*[[Q500]] Citrus × limon :*[[Q3503]] Congo :*[[Q8413]] Constantine the Great :*[[Q1043]] Carl Linnaeus :*[[Q303]] Elvis Presley :*[[Q9130]] Erwin Schrödinger :*[[Q8007]] Franklin Delano Roosevelt :*[[Q5432]] Francisco Goya :*[[Q5089]] Ganges :*[[Q8778]] Galen :*[[Q9235]] Georg Wilhelm Friedrich Hegel :*[[Q720]] Genghis Khan :*[[Q188]] German :*[[Q7895]] reproductive system :*[[Q15969]] Jean Améry :*[[Q20925]] 1986 Belgian Grand Prix :*[[Q96221]] Heinrich Ehrhardt :*[[Q77534]] Doris Pack :*[[Q454]] peace :*[[Q5251735]] defuzzification :*[[Q11408]] magnetic field :*[[Q9368]] liver :*[[Q9620]] nerve :*[[Q11756]] prehistory :*[[Q851]] Saudi Arabia :*[[Q9215]] Sigmund Freud :*[[Q332062]] Sorghum bicolor :*[[Q9202]] Statue of Liberty :*[[Q1049]] Sudan :*[[Q35355]] Sumer :*[[Q8251]] The Art of War :*[[Q1071]] geography :*[[Q5325]] inductor :*[[Q205]] infinity :*[[Q12140]] medication :*[[Q627]] nitrogen :*[[Q12802]] nuclear weapon :*[[Q569]] beryllium :*[[Q618]] boron :*[[Q650]] fluorine :*[[Q654]] neon :*[[Q658]] sodium :*[[Q663]] aluminium :*[[Q670]] silicon :*[[Q682]] sulfur :*[[Q706]] calcium :*[[Q722]] vanadium :*[[Q725]] chromium :*[[Q731]] manganese :*[[Q677]] iron :*[[Q740]] cobalt :*[[Q744]] nickel :*[[Q758]] zinc :*[[Q1304]] livermorium :*[[Q1103]] iodine :*[[Q1108]] caesium :*[[Q888]] krypton :*[[Q938]] strontium :*[[Q941]] yttrium :*[[Q1046]] niobium :*[[Q1053]] molybdenum :*[[Q1054]] technetium :*[[Q1086]] ruthenium :*[[Q1087]] rhodium :*[[Q1090]] silver :*[[Q1094]] indium :*[[Q1099]] antimony :*[[Q7159]] African Union :*[[Q9546]] Al-Ghazali :*[[Q5580]] Albrecht Dürer :*[[Q7374]] Alfred Hitchcock :*[[Q727]] Amsterdam :*[[Q1340]] Antonio Vivaldi :*[[Q7298]] Antonín Dvořák :*[[Q10872]] Archaea :*[[Q8589]] Ashoka :*[[Q8018]] Augustine of Hippo :*[[Q7768]] Association of Southeast Asian Nations :*[[Q1486]] Buenos Aires :*[[Q9045]] Chanakya Kautilya :*[[Q2042]] Charles de Gaulle :*[[Q882]] Charlie Chaplin :*[[Q7322]] Christopher Columbus :*[[Q81513]] Citrus :*[[Q8209]] Cyrillic script :*[[Q1067]] Dante Alighieri :*[[Q7939]] El Niño :*[[Q613]] Emirate of Dubai :*[[Q8272]] Epic of Gilgamesh :*[[Q115]] Ethiopia :*[[Q8747]] Euclid :*[[Q5683]] Geoffrey Chaucer :*[[Q8229]] Latin script :*[[Q4918]] Mediterranean Sea :*[[Q25326]] Mollusca :*[[Q9458]] Muhammad :*[[Q5185]] Nematoda :*[[Q11379325]] Izawa Shrine :*[[Q11379739]] Imari Shrine :*[[Q575650]] Rust :*[[Q34010]] Haskell :*[[Q978185]] TypeScript :*[[Q479833]] batch file :*[[Q42979]] BASIC :*[[Q131140]] COBOL :*[[Q648619]] F# :*[[Q334879]] Erlang :*[[Q83303]] Fortran :*[[Q2613697]] Julia :*[[Q207316]] Lua :*[[Q212587]] OCaml :*[[Q840410]] PowerShell :*[[Q235086]] Smalltalk :*[[Q17147733]] Swift :*[[Q582706]] Israeli settlement :*[[Q1107129]] sōja :*[[Q127866012]] A Simple Example for Linear Partial Differential Equations and Its Solution Using the Method of Separation of Variables :*[[Q30249683]] Attention Is All You Need :*[[Q210907]] Haida Gwaii :*[[Q9876]] Vught :*[[Q13489381]] effective altruism :*[[Q82945199]] Alfréd von Adda :*[[Q114133712]] Evaluating the biological validity of European river typology systems with least disturbed benthic macroinvertebrate communities :*[[Q68271926]] Spectroscopic evidence of infall and outflow around intermediate high-mass YSOs in the Mon OB1 dark cloud :*[[Q63308014]] (222315) 2000 ST367 :*[[Q50082993]] Comparison of the applicability of Demirjian and Willems methods for dental age estimation in children from the Thrace region, Turkey. :*[[Q31266481]] Cerro Guayaquil :*[[Q4180914]] Test d'évaluation du français :*[[Q12171]] menstruation :*[[Q8065]] natural disaster :*[[Q12184]] pandemic :*[[Q8183]] phoneme :*[[Q67404404]] Response of the rabbit vas deferens in vivo to vasoactive drugs :*[[Q8070]] tsunami :*[[Q7283]] terrorism :*[[Q139491990]] JEPA :*[[Q118876059]] Claude :*[[Q116758847]] Anthropic :*[[Q112508731]] Blake Lemoine : [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:18, 18 July 2026 (UTC) 8egk83mpuezdba5w3ov4cez7vh1ygy7 12370 12359 2026-07-18T11:13:22Z 99of9 614 /* auto-created broken articles */ Reply 12370 wikitext text/x-wiki __NEWSECTIONLINK__ This page is the venue to request for the deletion of pages that cannot be speedy deleted (see also [[Template:Delete]]). [[Category:Abstract Wikipedia administration]] == Scholarly articles == * [[Q67404404]] {{Q|67404404}} * [[Q50082993]] {{Q|50082993}} * [[Q68271926]] {{Q|68271926}} * [[Q114133712]] {{Q|114133712}} There is very little abstract encyclopedic content that can come out of a page about a specific, non-notable scholarly article. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 19:07, 18 May 2026 (UTC) :We currently don't have a community-ratified definition of notability. I've tried to kick off this discussion [[Project:Notability|here]]. For now, I ask that stewards/global sysops '''wait''' until we come to a consensus on a policy. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:10, 18 May 2026 (UTC) ::{{ping|JJPMaster}} very interesting request. I'm not entirely sure... I would tend to agree for these papers but not all of them ({{Q|Q30249683}} exists on 16 Wikipedias for instance), so where to put the threshold between notable and non-notable? on which criteria? Anyway, I agree to ''wait'' until the community reach a consensus on what is notable on AW. Also, I'm pinging {{ping|Immanuelle}} who created these articles. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 14:13, 30 May 2026 (UTC) *{{vd}} low quality, no response or improvement. The case for significance of these topics is not made in the articles. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:26, 15 July 2026 (UTC) == [[Q6489603]] == See [[Talk:Q6489603]]. This does not work as a category, it is more an article about a category. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 08:34, 31 May 2026 (UTC) : Under my [[Abstract Wikipedia:Notability|proposed notability guideline]], this would not be notable, so I {{s}} deletion [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:30, 31 May 2026 (UTC) ::@[[User:Ameisenigel|Ameisenigel]] @[[User:Feeglgeef|Feeglgeef]] Although the page has been deleted, I believe that the vague wording related to categories (and templates) should be clarified. Please review and improve the deletion policy to help current and future contributors better understand how categories are handled. Refer [[Abstract Wikipedia talk:Deletion policy#Categories]] [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:07, 18 June 2026 (UTC) :{{Done|Deleted}} <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 14:07, 17 June 2026 (UTC) == Creations by XeNivalys == [[user:XeNivalys]] has posted several pages as part of their cross-wiki spam crusade. Please delete them all and if possible issue a block. --[[User:Bedivere|Bedivere]] ([[User talk:Bedivere|talk]]) 04:53, 9 June 2026 (UTC) :{{Done|Deleted}}. 🪶-[[User:Tanbiruzzaman|<span style="font-family:monospace;color:#006400;letter-spacing:1px;">TΛNBIRUZZΛMΛN</span>]] ([[User talk:Tanbiruzzaman|💬]]) 08:33, 9 June 2026 (UTC) == auto-created broken articles == I suggest we do a bit of a cleanup of pages that were created by a software tool, using immature functions that have been deprecated for months, that would be very annoying to clean up by hand. So I propose deletion of the following (feel free to add to this list anything that matches this description). No prejudice to re-creation if anyone wants to make them good. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:20, 15 July 2026 (UTC) * [[Q11378973]] * [[Q11433427]] * [[Q11395853]] * [[Q11465292]] * [[Q11467693]] * [[Q7768]] [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:20, 15 July 2026 (UTC) : I thout the same, or even more: I would like to discuss if it is best to delete outdated articles. There is a lot of discussion and critique about a lot of those articles. I think in particular to articles created by @Immanuelle, that are not edited afterwards by somebody else. Those articles were a) created in mass and b) most of them with outdated functions. PS: I value the attempt of use:Immanuelle and hope to see him/her to continue on this project, now or later. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:44, 15 July 2026 (UTC) ::Ping [[User:Immanuelle]]. Do you mind if we heavily clean up some of your contributions? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:25, 15 July 2026 (UTC) : Articles created by [[User:Immanuelle]] and not edited after creation. I would like to propose to delete these (if not already mentioned above): :*[[Q29682]] Sumiyoshi Shrine :*[[Q135040386]] Takeihakatsuno Shrine :*[[Q63471]] Omura Shrine :*[[Q65320]] Iwa Shrine :*[[Q94057]] Olive Shrine :*[[Q94317]] Kikuchi Shrine :*[[Q94760]] Kotohira-gū :*[[Q116140]] Tado Taisha :*[[Q133753]] Shiogama Shrine :*[[Q135732]] Ōagata Shrine :*[[Q137707]] Katō Shrine :*[[Q167136]] Kengun Shrine :*[[Q172253]] Amatsu Shrine :*[[Q195684]] Yahiko Shrine :*[[Q199699]] Tsurumine Hachiman Shrine :*[[Q211522]] Sannō Shrine :*[[Q246469]] Wakasa Shrine :*[[Q246479]] Ikoma Shrine :*[[Q246667]] Hakuto Shrine :*[[Q251160]] Ōgamiyama Shrine :*[[Q251682]] Yūtoku Inari Shrine :*[[Q276779]] Kifune Shrine :*[[Q276830]] Seimei Shrine :*[[Q276831]] Mitami Shrine :*[[Q283483]] Kanō Tenmangū :*[[Q288248]] Tokorozawa Shinmei Shrine :*[[Q703904]] Oyamazumi Shrine :*[[Q704219]] Terukuni Shrine :*[[Q704430]] Udo Jingū :*[[Q704622]] Kirishima Jingū :*[[Q704636]] Naminoue Shrine :*[[Q704686]] Miyazaki Jingū :*[[Q704702]] Shirayama Hime Shrine :*[[Q704855]] Hōkoku Shrine :*[[Q704865]] Hida Ichinomiya Minashi Shrine :*[[Q704876]] Kasama Inari Shrine :*[[Q704890]] Tosa Shrine :*[[Q704898]] Hōfu Tenmangū :*[[Q705136]] Tsushima Shrine :*[[Q705297]] Nishinomiya Shrine :*[[Q705303]] Shirahige Shrine :*[[Q705310]] Hakone Shrine :*[[Q705542]] Ōmiwa Shrine :*[[Q706499]] Kashima Jingū :*[[Q11360548]] Kamitakano Shrine :*[[Q11360577]] Shimonaka Hachiman :*[[Q11360668]] Shimohara-hachiman Shrine :*[[Q11360748]] Shimomasuda Shrine :*[[Q11360904]] Shimogoryō Shrine :*[[Q11361253]] Shimoshinmei Tenso Shrine :*[[Q11361494]] Shimodate Haguro Shrine :*[[Q11361528]] Shimoshiotsu Shrine :*[[Q11361819]] Fuba-hachimangu :*[[Q23548]] National Aeronautics and Space Administration :*[[Q11691]] stock exchange :*[[Q42274]] Google Earth :*[[Q80228]] bottle :*[[Q173799]] entertainment :*[[Q18123741]] infectious disease :*[[Q16550]] Breithorn :*[[Q569243]] Universiti Brunei Darussalam :*[[Q602]] Rhône :*[[Q15928]] Velenje :*[[Q45677]] Château de Choisy :*[[Q503530]] Sioma Ngwezi National Park :*[[Q499550]] Smith Islands National Park :*[[Q503518]] Lower Zambezi National Park :*[[Q150]] French :*[[Q404]] HTTP 404 :*[[Q42397345]] 307 Temporary Redirect :*[[Q38897603]] Observations on urethral infection in the male. :*[[Q379519]] Mid-Autumn Festival :*[[Q45470]] Sasuke Inari Shrine :*[[Q372380]] Katori Jingū :*[[Q385407]] Ōmi Jingū :*[[Q482065]] Atsuta Jingū :*[[Q521319]] Takekoma Inari Shrine :*[[Q631373]] Kashii-gū :*[[Q5151]] month :*[[Q444]] Lech Wałęsa :*[[Q555]] Rachel Maddow :*[[Q999]] astatine :*[[Q461391]] Gavin Newsom :*[[Q868]] Aristotle :*[[Q9181]] Abraham :*[[Q91]] Abraham Lincoln :*[[Q3783]] Amazon :*[[Q10987]] honey :*[[Q11663]] weather :*[[Q884]] South Korea :*[[Q7235]] Sophocles :*[[Q11002]] sugar :*[[Q376]] clock :*[[Q11391]] ultraviolet radiation :*[[Q9358]] Friedrich Nietzsche :*[[Q7317]] Giuseppe Verdi :*[[Q13217298]] Giza Necropolis :*[[Q2487]] Thirty Years' War :*[[Q8269]] The Tale of Genji :*[[Q9438]] Thomas Aquinas :*[[Q8743]] Thomas Edison :*[[Q12514]] Three Gorges Dam :*[[Q80]] Tim Berners-Lee :*[[Q8736]] Treaty of Versailles :*[[Q8467]] Umar ibn Al-Khattāb :*[[Q8740]] Vietnam War :*[[Q7355]] Yellow River :*[[Q11205]] arithmetic :*[[Q6206]] capitalism :*[[Q573]] day :*[[Q8047]] enzyme :*[[Q8597]] Akbar :*[[Q8409]] Alexander the Great :*[[Q7850]] Chinese :*[[Q8275]] Iliad :*[[Q37660]] South China Sea :*[[Q313]] Venus :*[[Q362]] World War II :*[[Q12078]] cancer :*[[Q199804]] chronic obstructive pulmonary disease :*[[Q8142]] currency :*[[Q7430]] deoxyribonucleic acid :*[[Q12493]] dome :*[[Q2095]] food :*[[Q937]] Albert Einstein :*[[Q12104]] Avena sativa :*[[Q612]] Dubai :*[[Q905]] Franz Kafka :*[[Q5588]] Frida Kahlo :*[[Q125851781]] Fâtih Sultan Mehemmed Han :*[[Q7742]] Louis XIV of France :*[[Q5816]] Mao Zedong :*[[Q1218]] Jerusalem :*[[Q12554]] Middle Ages :*[[Q517]] Napoleon :*[[Q5599]] Peter Paul Rubens :*[[Q5577]] Salvador Dalí :*[[Q12099]] Secale cereale :*[[Q9316]] Sikhism :*[[Q933]] South Pole :*[[Q254]] Wolfgang Amadeus Mozart :*[[Q9683]] Tang dynasty :*[[Q9121]] atom :*[[Q5322]] capacitor :*[[Q7164]] World Bank :*[[Q3559]] comet :*[[Q6186]] communism :*[[Q258]] South Africa :*[[Q317]] dictatorship :*[[Q11651]] electric current :*[[Q8162]] linguistics :*[[Q11468]] nanotechnology :*[[Q8461]] racism :*[[Q9165]] soul :*[[Q287]] wood :*[[Q6388]] swimming :*[[Q12214]] smallpox :*[[Q9794]] reggae :*[[Q7380]] primate :*[[Q11372]] physical chemistry :*[[Q9404]] nervous system :*[[Q382441]] marine mammal :*[[Q3]] life :*[[Q11028]] information :*[[Q7075]] library :*[[Q1072]] heart :*[[Q11364]] hormone :*[[Q8458]] human rights :*[[Q8492]] juice :*[[Q82571]] linear algebra :*[[Q12800]] machine gun :*[[Q12167]] malnutrition :*[[Q10990]] meat :*[[Q7269]] monarchy :*[[Q11426]] metal :*[[Q6235]] nationalism :*[[Q12739]] nuclear power :*[[Q11472]] paper :*[[Q12195]] poliomyelitis :*[[Q10998]] potato :*[[Q7372]] shark :*[[Q5916]] spaceflight :*[[Q42527]] spice :*[[Q7553]] translation :*[[Q808]] virus :*[[Q8072]] volcano :*[[Q12876]] tank :*[[Q8188]] syllable :*[[Q10737]] suicide :*[[Q1511]] Richard Wagner :*[[Q7315]] Pyotr Ilyich Tchaikovsky :*[[Q11518]] Pythagorean theorem :*[[Q11451199]] List of Shikinaisha in Aki Province :*[[Q11379]] energy :*[[Q9103]] female breast :*[[Q11435]] liquid :*[[Q86]] headache :*[[Q11573]] metre :*[[Q8495]] milk :*[[Q11009]] nut :*[[Q5994]] piano :*[[Q11474]] plastic :*[[Q11423]] mass :*[[Q11190]] medicine :*[[Q9492]] probability :*[[Q9465]] ethics :*[[Q619]] Nicolaus Copernicus :*[[Q1399]] Niccolò Machiavelli :*[[Q9049]] Noam Chomsky :*[[Q332]] Neptune :*[[Q7176]] Naguib Mahfouz :*[[Q5592]] Michelangelo :*[[Q5513]] Lake Baikal :*[[Q5679]] Lord Byron :*[[Q7071]] Li Bai :*[[Q7259]] Ada Lovelace :*[[Q7172]] League of Arab States :*[[Q5879]] Johann Wolfgang von Goethe :*[[Q169470]] physicist :*[[Q719665]] Inari :*[[Q276944]] Ōkuninushi :*[[Q386563]] Ōyamatsumi :*[[Q1474187]] Watatsumi :*[[Q352]] Adolf Hitler :*[[Q7251]] Alan Turing :*[[Q5484]] Caspian Sea :*[[Q9592]] Catholic Church :*[[Q160]] Cetacea :*[[Q3044]] Charlemagne :*[[Q7207]] Elizabeth I of England :*[[Q181765]] Holy Roman Emperor :*[[Q12138]] Gregorian calendar :*[[Q9089]] Hinduism :*[[Q7226]] Joan of Arc :*[[Q9317]] John Maynard Keynes :*[[Q5603]] Andy Warhol :*[[Q1357]] Araneae :*[[Q1828555]] Arabic script :*[[Q5685]] Anton Chekhov :*[[Q748]] Buddhism :*[[Q500]] Citrus × limon :*[[Q3503]] Congo :*[[Q8413]] Constantine the Great :*[[Q1043]] Carl Linnaeus :*[[Q303]] Elvis Presley :*[[Q9130]] Erwin Schrödinger :*[[Q8007]] Franklin Delano Roosevelt :*[[Q5432]] Francisco Goya :*[[Q5089]] Ganges :*[[Q8778]] Galen :*[[Q9235]] Georg Wilhelm Friedrich Hegel :*[[Q720]] Genghis Khan :*[[Q188]] German :*[[Q7895]] reproductive system :*[[Q15969]] Jean Améry :*[[Q20925]] 1986 Belgian Grand Prix :*[[Q96221]] Heinrich Ehrhardt :*[[Q77534]] Doris Pack :*[[Q454]] peace :*[[Q5251735]] defuzzification :*[[Q11408]] magnetic field :*[[Q9368]] liver :*[[Q9620]] nerve :*[[Q11756]] prehistory :*[[Q851]] Saudi Arabia :*[[Q9215]] Sigmund Freud :*[[Q332062]] Sorghum bicolor :*[[Q9202]] Statue of Liberty :*[[Q1049]] Sudan :*[[Q35355]] Sumer :*[[Q8251]] The Art of War :*[[Q1071]] geography :*[[Q5325]] inductor :*[[Q205]] infinity :*[[Q12140]] medication :*[[Q627]] nitrogen :*[[Q12802]] nuclear weapon :*[[Q569]] beryllium :*[[Q618]] boron :*[[Q650]] fluorine :*[[Q654]] neon :*[[Q658]] sodium :*[[Q663]] aluminium :*[[Q670]] silicon :*[[Q682]] sulfur :*[[Q706]] calcium :*[[Q722]] vanadium :*[[Q725]] chromium :*[[Q731]] manganese :*[[Q677]] iron :*[[Q740]] cobalt :*[[Q744]] nickel :*[[Q758]] zinc :*[[Q1304]] livermorium :*[[Q1103]] iodine :*[[Q1108]] caesium :*[[Q888]] krypton :*[[Q938]] strontium :*[[Q941]] yttrium :*[[Q1046]] niobium :*[[Q1053]] molybdenum :*[[Q1054]] technetium :*[[Q1086]] ruthenium :*[[Q1087]] rhodium :*[[Q1090]] silver :*[[Q1094]] indium :*[[Q1099]] antimony :*[[Q7159]] African Union :*[[Q9546]] Al-Ghazali :*[[Q5580]] Albrecht Dürer :*[[Q7374]] Alfred Hitchcock :*[[Q727]] Amsterdam :*[[Q1340]] Antonio Vivaldi :*[[Q7298]] Antonín Dvořák :*[[Q10872]] Archaea :*[[Q8589]] Ashoka :*[[Q8018]] Augustine of Hippo :*[[Q7768]] Association of Southeast Asian Nations :*[[Q1486]] Buenos Aires :*[[Q9045]] Chanakya Kautilya :*[[Q2042]] Charles de Gaulle :*[[Q882]] Charlie Chaplin :*[[Q7322]] Christopher Columbus :*[[Q81513]] Citrus :*[[Q8209]] Cyrillic script :*[[Q1067]] Dante Alighieri :*[[Q7939]] El Niño :*[[Q613]] Emirate of Dubai :*[[Q8272]] Epic of Gilgamesh :*[[Q115]] Ethiopia :*[[Q8747]] Euclid :*[[Q5683]] Geoffrey Chaucer :*[[Q8229]] Latin script :*[[Q4918]] Mediterranean Sea :*[[Q25326]] Mollusca :*[[Q9458]] Muhammad :*[[Q5185]] Nematoda :*[[Q11379325]] Izawa Shrine :*[[Q11379739]] Imari Shrine :*[[Q575650]] Rust :*[[Q34010]] Haskell :*[[Q978185]] TypeScript :*[[Q479833]] batch file :*[[Q42979]] BASIC :*[[Q131140]] COBOL :*[[Q648619]] F# :*[[Q334879]] Erlang :*[[Q83303]] Fortran :*[[Q2613697]] Julia :*[[Q207316]] Lua :*[[Q212587]] OCaml :*[[Q840410]] PowerShell :*[[Q235086]] Smalltalk :*[[Q17147733]] Swift :*[[Q582706]] Israeli settlement :*[[Q1107129]] sōja :*[[Q127866012]] A Simple Example for Linear Partial Differential Equations and Its Solution Using the Method of Separation of Variables :*[[Q30249683]] Attention Is All You Need :*[[Q210907]] Haida Gwaii :*[[Q9876]] Vught :*[[Q13489381]] effective altruism :*[[Q82945199]] Alfréd von Adda :*[[Q114133712]] Evaluating the biological validity of European river typology systems with least disturbed benthic macroinvertebrate communities :*[[Q68271926]] Spectroscopic evidence of infall and outflow around intermediate high-mass YSOs in the Mon OB1 dark cloud :*[[Q63308014]] (222315) 2000 ST367 :*[[Q50082993]] Comparison of the applicability of Demirjian and Willems methods for dental age estimation in children from the Thrace region, Turkey. :*[[Q31266481]] Cerro Guayaquil :*[[Q4180914]] Test d'évaluation du français :*[[Q12171]] menstruation :*[[Q8065]] natural disaster :*[[Q12184]] pandemic :*[[Q8183]] phoneme :*[[Q67404404]] Response of the rabbit vas deferens in vivo to vasoactive drugs :*[[Q8070]] tsunami :*[[Q7283]] terrorism :*[[Q139491990]] JEPA :*[[Q118876059]] Claude :*[[Q116758847]] Anthropic :*[[Q112508731]] Blake Lemoine : [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:18, 18 July 2026 (UTC) ::Some are okay. I clicked on two, and IMO both should be kept: [[Q188]] German, [[Q3503]] Congo (River). So I think we need to go through them not just mass delete. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:13, 18 July 2026 (UTC) ndrxxe5nntishbt1u4jxnkp830h44bf 4 451 12256 12192 2026-07-18T00:12:52Z Higa4 71 /* Administrator: 99of9 */ 12256 wikitext text/x-wiki {{/Header}} == Administrator == === Administrator: Bunnypranav === Hello folks! I would like to request administrator to be able to help out with deletion, respond to vandalism, and assist with any other administrative tasks. I currently serve as a sysop on Wikifunctions, a sister project intricately linked to this wiki. I actively respond to deletion requests there. While I haven't created many pages here, the administrative skills required overlap significantly with that of Wikifunctions. Thank you for your time and consideration! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 08:23, 9 June 2026 (UTC) : I'm not going to !vote yet. I trust you, I know that you know how to use the tools, and I would really like a local admin, but I'd be more comfortable supporting if you had more local edits (than 12) to show that you can exercise good judgement on this project specifically. You still have 6 days! : I'm also not sure about the assertion that "the administrative skills required overlap significantly with that of Wikifunctions". Of course, the skills necessary to be a sysop on any Wikimedia (or, really, MediaWiki) project overlap heavily, but I'd argue that Abstract Wikipedia is closer to concrete Wikipedias in deletion (often notability and spam/vandalism) than Wikifunctions (often author request and lack of use). : '''Optional question''' in this regard: of the three requests currently on [[Abstract:RFD]], open and closed, what would you do (or have done) with them as sysop if you ''had'' to make a decision without factoring in the existing comments? : Thanks, [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:29, 10 June 2026 (UTC) ::Thank you for your trust, and for taking the time to give me feedback. I agree that my current contribution is pretty limited for a sysop role in any regular wiki, and I understand if the community cannot trust me with these privileges. You are right in saying that Abstract Wikipedia is closer to other content wikis in terms of notability policies, since this hosts textual encyclopedic content at the end of the day (from a readers perspective at least). My initial statement was based on, in addition to general familiarity of sysop tools in MediaWiki systems, the similarity in the terms structure of pages. The system of functions, function calls, arguments, and other related features through the [[mw:Extension:WikiLambda|extension WikiLambda]] is the overlap I referred to. While not an excuse for the lesser number of edits in this wiki, I have gained a lot of experience in general notability and vandalism policies though my significant contributions in enwiki (non-wiki specific, not Abs. wiki specific, I know). Basically, this is to say I am not completely unaware about how content-related deletions take place. ::I would be happy to answer your optional question, any any follow ups you or others may have. However, I would like to say that for any non-emergency or non-spam deletion requests, which include the first and second request currently at RFD, I would never choose to make a decision without waiting for other user comments. Consensus runs in the DNA and blood of our wikis, and there is no need to ever not factor that in. In order of the requests (from [https://abstract.wikipedia.org/w/index.php?title=Abstract_Wikipedia:Requests_for_deletion&oldid=10008 permalink]) ::# This is of course the more harder request to evaluate comparatively. As said before, I would not like to proceed towards an outcome without hearing some other voices at RfD. Afterall, that is the point of deletion venues. Based on the proposed notability guideline, they do seem to be on the borderline, and leaning more towards a no, but I would not choose to make a decision without at least some amount of community input. ::# I would close this as deleted, since it does not seem to add any encyclopedic value in its current form of an article about an internal category. The deletion reason proposed by Ameisenigel seems pretty self explanatory. ::# ''Note: I cannot see the now-deleted pages'' Since this looks like a simple vandalism related deletion request, if the pages in question were actually clear pages of spam, which I would assume them to be since they were already deleted by a global sysop, I would also delete them and issue a block without waiting for any other user comments. ::Thank you once again for your time! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 06:35, 11 June 2026 (UTC) ::: {{weak support}} '''three or six months''', thank you for your detailed answers. We'll hopefully have a chance to review sysopship in a few months anyway. My experience is that, as you mentioned, you respect consensus well and don't take bold actions that are likely to be controversial. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 11 June 2026 (UTC) :{{s}} term-limited adminship. You have the right temperament and approach, and familiarity with the underlying project and aims helps a lot at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:43, 12 June 2026 (UTC) :{{S}} per above --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 18:04, 12 June 2026 (UTC) Closed as successful, 3 {{support}} 0 {{oppose}}. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:24, 17 June 2026 (UTC) ===Administrator: 99of9=== It looks like we are now in need of more administrative effort. We need to clean up some of our experiments, because outsiders are starting to judge the future viability of the project based on our current outputs. I believe my contributions show that I have the knowledge and temperament to do this. Any current users likely already know me. But if not, I'm Toby, from [[Q3130]], I'm a chemistry academic with research interests in computer simulation of materials and educational technology. I've been contributing to Wikimedia projects fairly regularly for almost 22 years, for the last 1000 days, much of it has been on Wikifunctions. So I've likely had a hand in many of the functions used here. I'm also involved in English Wikipedia, Commons and Wikidata. I hold or have held various advanced rights (admin/bureaucrat/...) on some of those projects. Feel free to ask questions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:51, 17 July 2026 (UTC) :{{strong support}} Super qualified <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 07:40, 17 July 2026 (UTC) :{{support}} [[User:Higa4|Higa4]] ([[User talk:Higa4|talk]]) 00:12, 18 July 2026 (UTC) == Interface administrator == == Translation administrator == == Bureaucrat == == Bot == == Miscellaneous requests == ==See also== * [[Abstract Wikipedia:User groups]] ** [[Special:ListGroupRights]] for the listing of rights per user group 93ykw0rg65633rk4am49kpykch3463f 12257 12256 2026-07-18T01:06:58Z 99of9 614 /* Administrator: 99of9 */ 12257 wikitext text/x-wiki {{/Header}} == Administrator == === Administrator: Bunnypranav === Hello folks! I would like to request administrator to be able to help out with deletion, respond to vandalism, and assist with any other administrative tasks. I currently serve as a sysop on Wikifunctions, a sister project intricately linked to this wiki. I actively respond to deletion requests there. While I haven't created many pages here, the administrative skills required overlap significantly with that of Wikifunctions. Thank you for your time and consideration! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 08:23, 9 June 2026 (UTC) : I'm not going to !vote yet. I trust you, I know that you know how to use the tools, and I would really like a local admin, but I'd be more comfortable supporting if you had more local edits (than 12) to show that you can exercise good judgement on this project specifically. You still have 6 days! : I'm also not sure about the assertion that "the administrative skills required overlap significantly with that of Wikifunctions". Of course, the skills necessary to be a sysop on any Wikimedia (or, really, MediaWiki) project overlap heavily, but I'd argue that Abstract Wikipedia is closer to concrete Wikipedias in deletion (often notability and spam/vandalism) than Wikifunctions (often author request and lack of use). : '''Optional question''' in this regard: of the three requests currently on [[Abstract:RFD]], open and closed, what would you do (or have done) with them as sysop if you ''had'' to make a decision without factoring in the existing comments? : Thanks, [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:29, 10 June 2026 (UTC) ::Thank you for your trust, and for taking the time to give me feedback. I agree that my current contribution is pretty limited for a sysop role in any regular wiki, and I understand if the community cannot trust me with these privileges. You are right in saying that Abstract Wikipedia is closer to other content wikis in terms of notability policies, since this hosts textual encyclopedic content at the end of the day (from a readers perspective at least). My initial statement was based on, in addition to general familiarity of sysop tools in MediaWiki systems, the similarity in the terms structure of pages. The system of functions, function calls, arguments, and other related features through the [[mw:Extension:WikiLambda|extension WikiLambda]] is the overlap I referred to. While not an excuse for the lesser number of edits in this wiki, I have gained a lot of experience in general notability and vandalism policies though my significant contributions in enwiki (non-wiki specific, not Abs. wiki specific, I know). Basically, this is to say I am not completely unaware about how content-related deletions take place. ::I would be happy to answer your optional question, any any follow ups you or others may have. However, I would like to say that for any non-emergency or non-spam deletion requests, which include the first and second request currently at RFD, I would never choose to make a decision without waiting for other user comments. Consensus runs in the DNA and blood of our wikis, and there is no need to ever not factor that in. In order of the requests (from [https://abstract.wikipedia.org/w/index.php?title=Abstract_Wikipedia:Requests_for_deletion&oldid=10008 permalink]) ::# This is of course the more harder request to evaluate comparatively. As said before, I would not like to proceed towards an outcome without hearing some other voices at RfD. Afterall, that is the point of deletion venues. Based on the proposed notability guideline, they do seem to be on the borderline, and leaning more towards a no, but I would not choose to make a decision without at least some amount of community input. ::# I would close this as deleted, since it does not seem to add any encyclopedic value in its current form of an article about an internal category. The deletion reason proposed by Ameisenigel seems pretty self explanatory. ::# ''Note: I cannot see the now-deleted pages'' Since this looks like a simple vandalism related deletion request, if the pages in question were actually clear pages of spam, which I would assume them to be since they were already deleted by a global sysop, I would also delete them and issue a block without waiting for any other user comments. ::Thank you once again for your time! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 06:35, 11 June 2026 (UTC) ::: {{weak support}} '''three or six months''', thank you for your detailed answers. We'll hopefully have a chance to review sysopship in a few months anyway. My experience is that, as you mentioned, you respect consensus well and don't take bold actions that are likely to be controversial. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 11 June 2026 (UTC) :{{s}} term-limited adminship. You have the right temperament and approach, and familiarity with the underlying project and aims helps a lot at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:43, 12 June 2026 (UTC) :{{S}} per above --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 18:04, 12 June 2026 (UTC) Closed as successful, 3 {{support}} 0 {{oppose}}. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:24, 17 June 2026 (UTC) ===Administrator: 99of9=== It looks like we are now in need of more administrative effort. We need to clean up some of our experiments, because outsiders are starting to judge the future viability of the project based on our current outputs. I believe my contributions show that I have the knowledge and temperament to do this. Any current users likely already know me. But if not, I'm Toby, from [[Q3130]], I'm a chemistry academic with research interests in computer simulation of materials and educational technology. I've been contributing to Wikimedia projects fairly regularly for almost 22 years. For the last 1000 days, much of it has been on Wikifunctions. So I've likely had a hand in many of the functions used here. I'm also involved in English Wikipedia, Commons and Wikidata. I hold or have held various advanced rights (admin/bureaucrat/...) on some of those projects. Feel free to ask questions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:51, 17 July 2026 (UTC) :{{strong support}} Super qualified <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 07:40, 17 July 2026 (UTC) :{{support}} [[User:Higa4|Higa4]] ([[User talk:Higa4|talk]]) 00:12, 18 July 2026 (UTC) == Interface administrator == == Translation administrator == == Bureaucrat == == Bot == == Miscellaneous requests == ==See also== * [[Abstract Wikipedia:User groups]] ** [[Special:ListGroupRights]] for the listing of rights per user group 74hky5rocarlbxip8mqhwr8g6wi7xtm 12259 12257 2026-07-18T03:32:03Z EatingCarBatteries 1378 /* Administrator: 99of9 */ Reply 12259 wikitext text/x-wiki {{/Header}} == Administrator == === Administrator: Bunnypranav === Hello folks! I would like to request administrator to be able to help out with deletion, respond to vandalism, and assist with any other administrative tasks. I currently serve as a sysop on Wikifunctions, a sister project intricately linked to this wiki. I actively respond to deletion requests there. While I haven't created many pages here, the administrative skills required overlap significantly with that of Wikifunctions. Thank you for your time and consideration! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 08:23, 9 June 2026 (UTC) : I'm not going to !vote yet. I trust you, I know that you know how to use the tools, and I would really like a local admin, but I'd be more comfortable supporting if you had more local edits (than 12) to show that you can exercise good judgement on this project specifically. You still have 6 days! : I'm also not sure about the assertion that "the administrative skills required overlap significantly with that of Wikifunctions". Of course, the skills necessary to be a sysop on any Wikimedia (or, really, MediaWiki) project overlap heavily, but I'd argue that Abstract Wikipedia is closer to concrete Wikipedias in deletion (often notability and spam/vandalism) than Wikifunctions (often author request and lack of use). : '''Optional question''' in this regard: of the three requests currently on [[Abstract:RFD]], open and closed, what would you do (or have done) with them as sysop if you ''had'' to make a decision without factoring in the existing comments? : Thanks, [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:29, 10 June 2026 (UTC) ::Thank you for your trust, and for taking the time to give me feedback. I agree that my current contribution is pretty limited for a sysop role in any regular wiki, and I understand if the community cannot trust me with these privileges. You are right in saying that Abstract Wikipedia is closer to other content wikis in terms of notability policies, since this hosts textual encyclopedic content at the end of the day (from a readers perspective at least). My initial statement was based on, in addition to general familiarity of sysop tools in MediaWiki systems, the similarity in the terms structure of pages. The system of functions, function calls, arguments, and other related features through the [[mw:Extension:WikiLambda|extension WikiLambda]] is the overlap I referred to. While not an excuse for the lesser number of edits in this wiki, I have gained a lot of experience in general notability and vandalism policies though my significant contributions in enwiki (non-wiki specific, not Abs. wiki specific, I know). Basically, this is to say I am not completely unaware about how content-related deletions take place. ::I would be happy to answer your optional question, any any follow ups you or others may have. However, I would like to say that for any non-emergency or non-spam deletion requests, which include the first and second request currently at RFD, I would never choose to make a decision without waiting for other user comments. Consensus runs in the DNA and blood of our wikis, and there is no need to ever not factor that in. In order of the requests (from [https://abstract.wikipedia.org/w/index.php?title=Abstract_Wikipedia:Requests_for_deletion&oldid=10008 permalink]) ::# This is of course the more harder request to evaluate comparatively. As said before, I would not like to proceed towards an outcome without hearing some other voices at RfD. Afterall, that is the point of deletion venues. Based on the proposed notability guideline, they do seem to be on the borderline, and leaning more towards a no, but I would not choose to make a decision without at least some amount of community input. ::# I would close this as deleted, since it does not seem to add any encyclopedic value in its current form of an article about an internal category. The deletion reason proposed by Ameisenigel seems pretty self explanatory. ::# ''Note: I cannot see the now-deleted pages'' Since this looks like a simple vandalism related deletion request, if the pages in question were actually clear pages of spam, which I would assume them to be since they were already deleted by a global sysop, I would also delete them and issue a block without waiting for any other user comments. ::Thank you once again for your time! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 06:35, 11 June 2026 (UTC) ::: {{weak support}} '''three or six months''', thank you for your detailed answers. We'll hopefully have a chance to review sysopship in a few months anyway. My experience is that, as you mentioned, you respect consensus well and don't take bold actions that are likely to be controversial. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 11 June 2026 (UTC) :{{s}} term-limited adminship. You have the right temperament and approach, and familiarity with the underlying project and aims helps a lot at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:43, 12 June 2026 (UTC) :{{S}} per above --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 18:04, 12 June 2026 (UTC) Closed as successful, 3 {{support}} 0 {{oppose}}. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:24, 17 June 2026 (UTC) ===Administrator: 99of9=== It looks like we are now in need of more administrative effort. We need to clean up some of our experiments, because outsiders are starting to judge the future viability of the project based on our current outputs. I believe my contributions show that I have the knowledge and temperament to do this. Any current users likely already know me. But if not, I'm Toby, from [[Q3130]], I'm a chemistry academic with research interests in computer simulation of materials and educational technology. I've been contributing to Wikimedia projects fairly regularly for almost 22 years. For the last 1000 days, much of it has been on Wikifunctions. So I've likely had a hand in many of the functions used here. I'm also involved in English Wikipedia, Commons and Wikidata. I hold or have held various advanced rights (admin/bureaucrat/...) on some of those projects. Feel free to ask questions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:51, 17 July 2026 (UTC) :{{strong support}} Super qualified <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 07:40, 17 July 2026 (UTC) :{{support}} [[User:Higa4|Higa4]] ([[User talk:Higa4|talk]]) 00:12, 18 July 2026 (UTC) :{{strong support}} [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 03:32, 18 July 2026 (UTC) == Interface administrator == == Translation administrator == == Bureaucrat == == Bot == == Miscellaneous requests == ==See also== * [[Abstract Wikipedia:User groups]] ** [[Special:ListGroupRights]] for the listing of rights per user group 3gajb5xb5ods6ofwck13eqv0tpcamdx 12264 12259 2026-07-18T07:05:45Z HenkvD 1447 /* Administrator: 99of9 */ strong support 12264 wikitext text/x-wiki {{/Header}} == Administrator == === Administrator: Bunnypranav === Hello folks! I would like to request administrator to be able to help out with deletion, respond to vandalism, and assist with any other administrative tasks. I currently serve as a sysop on Wikifunctions, a sister project intricately linked to this wiki. I actively respond to deletion requests there. While I haven't created many pages here, the administrative skills required overlap significantly with that of Wikifunctions. Thank you for your time and consideration! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 08:23, 9 June 2026 (UTC) : I'm not going to !vote yet. I trust you, I know that you know how to use the tools, and I would really like a local admin, but I'd be more comfortable supporting if you had more local edits (than 12) to show that you can exercise good judgement on this project specifically. You still have 6 days! : I'm also not sure about the assertion that "the administrative skills required overlap significantly with that of Wikifunctions". Of course, the skills necessary to be a sysop on any Wikimedia (or, really, MediaWiki) project overlap heavily, but I'd argue that Abstract Wikipedia is closer to concrete Wikipedias in deletion (often notability and spam/vandalism) than Wikifunctions (often author request and lack of use). : '''Optional question''' in this regard: of the three requests currently on [[Abstract:RFD]], open and closed, what would you do (or have done) with them as sysop if you ''had'' to make a decision without factoring in the existing comments? : Thanks, [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:29, 10 June 2026 (UTC) ::Thank you for your trust, and for taking the time to give me feedback. I agree that my current contribution is pretty limited for a sysop role in any regular wiki, and I understand if the community cannot trust me with these privileges. You are right in saying that Abstract Wikipedia is closer to other content wikis in terms of notability policies, since this hosts textual encyclopedic content at the end of the day (from a readers perspective at least). My initial statement was based on, in addition to general familiarity of sysop tools in MediaWiki systems, the similarity in the terms structure of pages. The system of functions, function calls, arguments, and other related features through the [[mw:Extension:WikiLambda|extension WikiLambda]] is the overlap I referred to. While not an excuse for the lesser number of edits in this wiki, I have gained a lot of experience in general notability and vandalism policies though my significant contributions in enwiki (non-wiki specific, not Abs. wiki specific, I know). Basically, this is to say I am not completely unaware about how content-related deletions take place. ::I would be happy to answer your optional question, any any follow ups you or others may have. However, I would like to say that for any non-emergency or non-spam deletion requests, which include the first and second request currently at RFD, I would never choose to make a decision without waiting for other user comments. Consensus runs in the DNA and blood of our wikis, and there is no need to ever not factor that in. In order of the requests (from [https://abstract.wikipedia.org/w/index.php?title=Abstract_Wikipedia:Requests_for_deletion&oldid=10008 permalink]) ::# This is of course the more harder request to evaluate comparatively. As said before, I would not like to proceed towards an outcome without hearing some other voices at RfD. Afterall, that is the point of deletion venues. Based on the proposed notability guideline, they do seem to be on the borderline, and leaning more towards a no, but I would not choose to make a decision without at least some amount of community input. ::# I would close this as deleted, since it does not seem to add any encyclopedic value in its current form of an article about an internal category. The deletion reason proposed by Ameisenigel seems pretty self explanatory. ::# ''Note: I cannot see the now-deleted pages'' Since this looks like a simple vandalism related deletion request, if the pages in question were actually clear pages of spam, which I would assume them to be since they were already deleted by a global sysop, I would also delete them and issue a block without waiting for any other user comments. ::Thank you once again for your time! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 06:35, 11 June 2026 (UTC) ::: {{weak support}} '''three or six months''', thank you for your detailed answers. We'll hopefully have a chance to review sysopship in a few months anyway. My experience is that, as you mentioned, you respect consensus well and don't take bold actions that are likely to be controversial. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 11 June 2026 (UTC) :{{s}} term-limited adminship. You have the right temperament and approach, and familiarity with the underlying project and aims helps a lot at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:43, 12 June 2026 (UTC) :{{S}} per above --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 18:04, 12 June 2026 (UTC) Closed as successful, 3 {{support}} 0 {{oppose}}. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:24, 17 June 2026 (UTC) ===Administrator: 99of9=== It looks like we are now in need of more administrative effort. We need to clean up some of our experiments, because outsiders are starting to judge the future viability of the project based on our current outputs. I believe my contributions show that I have the knowledge and temperament to do this. Any current users likely already know me. But if not, I'm Toby, from [[Q3130]], I'm a chemistry academic with research interests in computer simulation of materials and educational technology. I've been contributing to Wikimedia projects fairly regularly for almost 22 years. For the last 1000 days, much of it has been on Wikifunctions. So I've likely had a hand in many of the functions used here. I'm also involved in English Wikipedia, Commons and Wikidata. I hold or have held various advanced rights (admin/bureaucrat/...) on some of those projects. Feel free to ask questions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:51, 17 July 2026 (UTC) :{{strong support}} Super qualified <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 07:40, 17 July 2026 (UTC) :{{support}} [[User:Higa4|Higa4]] ([[User talk:Higa4|talk]]) 00:12, 18 July 2026 (UTC) :{{strong support}} [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 03:32, 18 July 2026 (UTC) :{{strong support}} [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:05, 18 July 2026 (UTC) == Interface administrator == == Translation administrator == == Bureaucrat == == Bot == == Miscellaneous requests == ==See also== * [[Abstract Wikipedia:User groups]] ** [[Special:ListGroupRights]] for the listing of rights per user group qb9n2mllsioz89nq7es33xgs9rzugxn 12273 12264 2026-07-18T08:13:47Z Ameisenigel 31 /* Administrator: 99of9 */ Support 12273 wikitext text/x-wiki {{/Header}} == Administrator == === Administrator: Bunnypranav === Hello folks! I would like to request administrator to be able to help out with deletion, respond to vandalism, and assist with any other administrative tasks. I currently serve as a sysop on Wikifunctions, a sister project intricately linked to this wiki. I actively respond to deletion requests there. While I haven't created many pages here, the administrative skills required overlap significantly with that of Wikifunctions. Thank you for your time and consideration! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 08:23, 9 June 2026 (UTC) : I'm not going to !vote yet. I trust you, I know that you know how to use the tools, and I would really like a local admin, but I'd be more comfortable supporting if you had more local edits (than 12) to show that you can exercise good judgement on this project specifically. You still have 6 days! : I'm also not sure about the assertion that "the administrative skills required overlap significantly with that of Wikifunctions". Of course, the skills necessary to be a sysop on any Wikimedia (or, really, MediaWiki) project overlap heavily, but I'd argue that Abstract Wikipedia is closer to concrete Wikipedias in deletion (often notability and spam/vandalism) than Wikifunctions (often author request and lack of use). : '''Optional question''' in this regard: of the three requests currently on [[Abstract:RFD]], open and closed, what would you do (or have done) with them as sysop if you ''had'' to make a decision without factoring in the existing comments? : Thanks, [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:29, 10 June 2026 (UTC) ::Thank you for your trust, and for taking the time to give me feedback. I agree that my current contribution is pretty limited for a sysop role in any regular wiki, and I understand if the community cannot trust me with these privileges. You are right in saying that Abstract Wikipedia is closer to other content wikis in terms of notability policies, since this hosts textual encyclopedic content at the end of the day (from a readers perspective at least). My initial statement was based on, in addition to general familiarity of sysop tools in MediaWiki systems, the similarity in the terms structure of pages. The system of functions, function calls, arguments, and other related features through the [[mw:Extension:WikiLambda|extension WikiLambda]] is the overlap I referred to. While not an excuse for the lesser number of edits in this wiki, I have gained a lot of experience in general notability and vandalism policies though my significant contributions in enwiki (non-wiki specific, not Abs. wiki specific, I know). Basically, this is to say I am not completely unaware about how content-related deletions take place. ::I would be happy to answer your optional question, any any follow ups you or others may have. However, I would like to say that for any non-emergency or non-spam deletion requests, which include the first and second request currently at RFD, I would never choose to make a decision without waiting for other user comments. Consensus runs in the DNA and blood of our wikis, and there is no need to ever not factor that in. In order of the requests (from [https://abstract.wikipedia.org/w/index.php?title=Abstract_Wikipedia:Requests_for_deletion&oldid=10008 permalink]) ::# This is of course the more harder request to evaluate comparatively. As said before, I would not like to proceed towards an outcome without hearing some other voices at RfD. Afterall, that is the point of deletion venues. Based on the proposed notability guideline, they do seem to be on the borderline, and leaning more towards a no, but I would not choose to make a decision without at least some amount of community input. ::# I would close this as deleted, since it does not seem to add any encyclopedic value in its current form of an article about an internal category. The deletion reason proposed by Ameisenigel seems pretty self explanatory. ::# ''Note: I cannot see the now-deleted pages'' Since this looks like a simple vandalism related deletion request, if the pages in question were actually clear pages of spam, which I would assume them to be since they were already deleted by a global sysop, I would also delete them and issue a block without waiting for any other user comments. ::Thank you once again for your time! <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 06:35, 11 June 2026 (UTC) ::: {{weak support}} '''three or six months''', thank you for your detailed answers. We'll hopefully have a chance to review sysopship in a few months anyway. My experience is that, as you mentioned, you respect consensus well and don't take bold actions that are likely to be controversial. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 11 June 2026 (UTC) :{{s}} term-limited adminship. You have the right temperament and approach, and familiarity with the underlying project and aims helps a lot at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 00:43, 12 June 2026 (UTC) :{{S}} per above --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 18:04, 12 June 2026 (UTC) Closed as successful, 3 {{support}} 0 {{oppose}}. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:24, 17 June 2026 (UTC) ===Administrator: 99of9=== It looks like we are now in need of more administrative effort. We need to clean up some of our experiments, because outsiders are starting to judge the future viability of the project based on our current outputs. I believe my contributions show that I have the knowledge and temperament to do this. Any current users likely already know me. But if not, I'm Toby, from [[Q3130]], I'm a chemistry academic with research interests in computer simulation of materials and educational technology. I've been contributing to Wikimedia projects fairly regularly for almost 22 years. For the last 1000 days, much of it has been on Wikifunctions. So I've likely had a hand in many of the functions used here. I'm also involved in English Wikipedia, Commons and Wikidata. I hold or have held various advanced rights (admin/bureaucrat/...) on some of those projects. Feel free to ask questions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:51, 17 July 2026 (UTC) :{{strong support}} Super qualified <span style="font-family:monospace;font-weight:bold">[[User:Bunnypranav|<span style="color:#63b3ed">~/Bunny</span><span style="color:#2c5282">pranav</span>]]:&lt;[[User talk:Bunnypranav|<span style="color:#63b3ed">ping</span>]]&gt;</span> 07:40, 17 July 2026 (UTC) :{{support}} [[User:Higa4|Higa4]] ([[User talk:Higa4|talk]]) 00:12, 18 July 2026 (UTC) :{{strong support}} [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 03:32, 18 July 2026 (UTC) :{{strong support}} [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:05, 18 July 2026 (UTC) :{{S}} --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 08:13, 18 July 2026 (UTC) == Interface administrator == == Translation administrator == == Bureaucrat == == Bot == == Miscellaneous requests == ==See also== * [[Abstract Wikipedia:User groups]] ** [[Special:ListGroupRights]] for the listing of rights per user group oteoiuy4go51qc82fht8oztf4dvfo9t 0 607 12262 3600 2026-07-18T06:28:52Z EatingCarBatteries 1378 12262 abstractwiki text/plain { "qid": "Q5", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q110551885" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q215627" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q164509" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q154954" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } an677i5xzosizg4bjxmdj6gjh8pw5ru 2 1117 12235 12190 2026-07-17T22:01:59Z HenkvD 1447 /* Overview of NLG functions I work(ed) upon */ 12235 wikitext text/x-wiki {| border="1" style="float: right; margin-left: 1em; margin-bottom: 0.5em; border: #99B3FF solid 1px; background: #F1F8F1; border-collapse: collapse; color:black" | | colspan="10" style="text-align:center;" | <div class="plainlinks">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''Gebruiker:HenkvD''' op [[commons:Template talk:Sisterlinks|zusterprojecten]]</div> |- | valign="top" align="center" | [[Image:Wikipedia-logo.png|18px]]<br>Wikipedia<br>[[:de:Benutzer:HenkvD|de:]] [[:en:User:HenkvD|en:]] [[:fr:Utilisateur:HenkvD|fr:]] '''[[:nl:User:HenkvD|nl:]]''' | valign="top" align="center" | [[Image:Wiktionary-logo-en.png|17px]]<br>Wiktionary<br>[[:wikt:en:User:HenkvD|en:]]<br />[http://www.omegawiki.org/index.php/User:HenkvD ΩWiki] | valign="top" align="center" | [[Image:Wikinews-logo.png|35px]]<br>Wikinews<br>[[wikinews:User:HenkvD|en:]] [[:n:nl:User:HenkvD|nl:]]<br><div class="plainlinks">[http://incubator.wikimedia.org/w/index.php?title=User:HenkvD nl: in incubator]</div> | valign="top" align="center" | [[Image:Wikiquote-logo.png|16px]]<br>Wikiquote<br>[[:q:en:User:HenkvD|en:]] |- | valign="top" align="center" | [[Image:Wikibooks-logo.png|18px]]<br>Wikibooks<br>[[:b:en:User:HenkvD|en:]] | valign="top" align="center" | [[Image:Wikisource-logo.png|18px]]<br>Wikisource<br>[[:s:en:User:HenkvD|en:]] '''[[:s:nl:Gebruiker:HenkvD|nl:]]''' <div class="plainlinks">[http://wikisource.org/wiki/User:HenkvD old]</div> | valign="top" align="center" | [[Image:Wikiversity-logo-en.svg|18px]]<br>Wikiversity<br>[[:de:v:User:HenkvD|de:]] [[:en:v:User:HenkvD|en:]] | valign="top" align="center" | [[Image:Wikimedia-logo.png|18px]]<br>[[:meta:User:HenkvD|Meta]]<br><div class="plainlinks">[http://strategy.wikimedia.org/wiki/User:HenkvD Strategy]<br><div class="plainlinks">'''[http://nl.wikimedia.org/wiki/Gebruiker:HenkvD nl:]'''</div></div> |- | valign="top" align="center" | [[Image:Wikivoyage-Logo-v3-icon.svg|16px]]<br>Wikivoyage<br>[[:en:voy:User:HenkvD|en:]] | valign="top" align="center" | [[File:Wikidata-logo.svg|19px|Wikidata]]<br><div class="plainlinks">[http://www.wikidata.org/wiki/User:HenkvD Wikidata]</div> | valign="top" align="center" | [[Image:Commons-logo.svg|14px]]<br>[[:Commons:User:HenkvD|Commons]] | valign="top" align="center" | [[File:Wikifunctions-logo.svg|14px]] [[File:Abstract-Wikipedia-wordmark.svg|42px]]<br>[[f:User:HenkvD|Wikifunctions]] <br>'''AbstractWiki''' |} My name is Henk, from [[Q55|the Netherlands]] ([[:nl:Gebruiker:HenkvD]]). I am interested in Abstract Wikipedia functionality and have general knowledge of the Dutch language (as native speaker). As most other Dutch persons I have good knowledge of English and some of German and a bit of French and Romance languages.<br> I have an IT background, and try to understand the programming in Wikifunctions.<br> I will try to analyse Wikifunction, Wikidata, lexemes and add Wikifunction tests if needed. In my opinion the initial goal is to have Abstract Wikipedia pages with simple lead section (like stubs), an infobox fully from Wikidata, one or more images and maybe some simple lists. The simple lead sentences should function for as many languages as possible. That will also need that many languages will have labels in Wikidata and lexemes with genders. That will be a difficult enough to achieve. In my opinion extensive prose will be very hard to achieve. <br clear=all> {{#babel:nl|en-3|de-2|fr-1}} ===Overview of NLG functions I work(ed) upon=== {| class="wikitable" ! ZID !! Example !! English !! Dutch || Other simple languages || Default |- | [[f:Z36625|Z36625]] third-person singular form of to be (simple) || || is || is || [[f:Z36627|f:]] en nl fy af bar bs eo frr is hsb mk nds os pap sr +fi +cs hr id zea || (is) |- | [[f:Z36622|Z36622]] indefinite article (simple) || || N/A || een || [[f:Z36624|f:]] nl af fy bar bs eo frr is hsb mk nds os pap sr +fi +cs hr id zea || (a) |- | [[f:Z36610|Z36610]] definite article (simple) || || the || N/A || [[f:Z36620|f:]] en af eo pap +fi +cs hr id || (the) |- | [[f:Z37311|Z37311]] String<br>and (indicating last entry of list) Simple || || and || en || 40 simple languages || (and) |- | [[f:Z32962|Z32962]] HTML [[f:Z26039|Z26039]] String<br>A is a B. || [[Q8739]] || Paris is a city. || Parijs is een stad || [[f:Z35523|f:]] af bar bs eo frr fy hsb is mk nds os pap sr +fi +zea || Y Magenta 🔧 |- | [[f:Z32965|Z32965]] HTML [[f:Z26095|Z26095]] Monlingual<br>an A is a B. || [[Q2102]] || A frog is an amphibian. || een hond is een dier || [[f:Z36875|f:]] af bar bs eo frr fy hsb is (nds) mk nl os pap sr +fi +id zea || Y Magenta 🔧 with ❌ |- | [[f:Z36983|Z36983]] HTML [[f:Z26570|Z26570]] String<br>A is a B in C. || [[Q55]] || Netherlands is a country in Europe || Nederland is een land in Europa. || [[f:Z35618|f:]] af bar eo frr fy mk pap +hr zea || Y magenta 🔧 |- | [[f:Z36987|Z36987]] HTML [[f:Z32581|Z32581]] Monolingual<br>A is a B by C. || [[Q12418]] || Mona Lisa is a painting by Leonardo da Vinci. || Mona Lisa is een schilderij van Leonardo da Vinci. || [[f:Z36168|f:]] af eo fy is mk os pap +cs hr id zea || Y Magenta 🔧 with ❌ |- | [[f:Z36993|Z36993]] HTML [[f:Z32982|Z32982]] Monlingual<br>A is a B of C. || [[Q718]] || Chess is a game of strategy. || Schaken is een spel van strategie. || [[f:Z36528|f:]] af eo fy mk nl pap +cs hr id zea || Y Magenta 🔧 with ❌ |- | [[f:Z37011|Z37011]] HTML [[f:Z28016|Z28016]] Monolingual<br>A is the B of C. || [[Q90]] || Paris is the capital of France. || Parijs is de hoofdstad van Frankrijk<br>❗Lexemes needed for nouns || [[f:Z36339|f:]] af eo mk pap +hr zea || Y Magenta 🔧 with ❌ |- | [[f:Z34282|Z34282]] A is a B. (automatic based on Wikidata class) || [[Q13924]] || Adriatic Sea is a sea || Adriatische Zee is een zee. || WIP Wrapper || N |- | [[f:Z34637|Z34637]] A is part of the B. (automatic based on Wikidata class) || [[Q13924]] || Adriatic Sea is part of the Mediterranean Sea. || || || Y |- | [[f:Z27243|Z27243]] Monolingual<br>Superlative A is the B-est C in D || [[Q319]] || Jupiter is the largest planet in the Solar System. || [[f:Z37022|f:]] Jupiter is de grootste planeet van het zonnestelsel.<br>❗Lexemes needed for nouns || [[f:Z37033|:f:]] eo || Y ⤒ large { planet ∩ Solar System } = Jupiter. |- | [[f:Z29591|Z29591]] Monolingual<br>entity with adjective / class || [[Q177749]] || Jupiter is a big planet || || || Y A ∈ { B ∩ C. }. |- | [[f:Z37005|Z37005]] Monolingual<br>A has parts (automatic based on Wikidata) || [[Q211391]] || Weekend consists of Saturday and Sunday. || Weekeinde bestaat uit zaterdag en zondag. || [[f:Z37328|f:]] 25 languages || Y |- | [[f:Z37289|Z37289]] Monolingual<br>join list of monolingual texts without Oxford comma || || A, B and C || A, B en C || 40 languages || Y |- | || [[Q11750]] || list of sovereign states || || || N/A |- ! '''Infoboxes''' !! !! !! !! !! |- | [[f:Z35167|Z35167]] Infobox person (1) || || OK || [https://www.wikifunctions.org/wiki/Z35167?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z35167%22%2C%22Z35167K1%22%3A%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6821%22%2C%22Z6821K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q154946%22%7D%7D%2C%22Z35167K2%22%3A%22Z1157%22%7D OK] || OK (some labels needed, via P1629)<br>Disconnected the old layout || N/A |- | [[f:Z35370|Z35370]] Infobox for person (1a, Wikidata item reference || || OK || OK || New layout, Also with dates || N/A |- | [[f:Z36678|Z36678]] infobox for city || [[Q90]] || Country France || Land Frankrijk || OK || N/A |- | [[f:Z37827|Z37827]] infobox for taxons || [[Q140]] || || || OK || N/A |- | [[f:Z37623|Z37623]] infobox row || [[Q90]] || Country France || Land Frankrijk || OK ? Seperate functions for date and string / test for combining || N/A |- | [[f:Z37866|Z37866]] infbox row property type || || || || OK || N/A |- | [[f:Z37782|Z37782]] infobox row, date || [[Q2407]] || || OK || Maybe to merge into general infobox row || N/A |- | [[f:Z37830|Z37830]] infobox row, string || [[Q140]] || || OK || Maybe to merge into general infobox row || N/A |- | [[f:Z37640|Z37640]] if (HTML output) || || || OK || || N/A |- | [[f:Z37644|Z37644]] Infobox section || || || OK || || N/A |- | [[f:Z37647|Z37647]] infobox color scheme || || || OK || || N/A |- | [[f:infobox 1 image|infobox 1 image]] infobox 1 image || || || Not possible yet? || || N/A |- | [[f:Z36218|Z36218]] specific property of subject is value from WD || [[Q922]]<br> [[Q408]] (load time might be long) || The area of Australia is 7,692,024 km². || De oppervlakte van Australië is 7692024 km²<br>❗Lexemes not yet available for nouns of almost all used properties || [[f:Z36684|f:]] af eo mk pap +cs hr id || Y oppervlakte(Australië) = 7692024 km². |- ! '''NLG Default''' !! !! !! !! !! |- | [[f:Z35921|Z35921]] NLG default text (string) || || OK || || || N/A |- | [[f:Z36911|Z36911]] NLG default text (monolingual text) || || OK || || || language "mul" |- | [[f:Z36909|Z36909]] NLG default text (HTML) || || OK || || || span lang="mul" style="color: #FF00FF;" |- | [[f:Z37454|Z37454]] monolingual text as HTML with lang & colour span || [[Q1370]] || || || || language daz <span lang="mul" style="color: #FF00FF;">⤒ Q138758272 { Q28575 ∩ Virginia } = Q341915</span> |} Steps to get Abstract Wikipedia started: * Basic functions on Wikifunctions * Wikidata labels * Link Wikidata Q-items to Lexemes / gender of lexemes on Wikidata * Link Wikidata P-items via Q-items to Lexemes / gender of lexemes on Wikidata Natural Language * [[f:Wikifunctions:NLG functions|Wikifunctions:NLG functions]] * [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]] Dutch language * [[f:Wikifunctions:Catalogue/Natural language operations/Dutch|Wikifunctions:Catalogue/Natural language operations/Dutch]] Wikidata queries * [https://query.wikidata.org/#%23%20Gender%20of%20City%20per%20langague%0ASELECT%20%3Fl%20%3Flemma%20%3Fsense%20%3Fgender%20%3FgenderLabel%20%28LANG%28%3Flemma%29%20AS%20%3Flanguage%29%0AWHERE%20%7B%0A%20%20%20%20%20%20%3Fsense%20wdt%3AP5137%20wd%3AQ515.%20%20%20%23%20City%0A%20%20%20%20%20%20%3Fl%20ontolex%3Asense%20%3Fsense.%0A%20%20%20%20%20%20%3Fl%20wikibase%3Alemma%20%3Flemma.%20%20%20%23%20FILTER%28LANG%28%3Flemma%29%3D%22de%22%29%0A%20%20%20%20%20%20%3Fl%20wdt%3AP5185%20%3Fgender.%0A%20%20%20%20%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%7D Gender of City per langague ] {{AbstractTestLemma}} {| class="wikitable" ! Function !! English !! Z1157 Dutch !! Z60 Local language |- | <nowiki>{{#function:</nowiki>[[f:Z26039|Z26039]]<nowiki>|Q64|Q515|Z1002}}</nowiki> | {{#function:Z26039|Q64|Q515|Z1002}} || {{#function:Z26039|Q64|Q515|Z1157}} || {{#function:Z26039|Q64|Q515|Z60}} |} Testing different NLG Default texts : <span lang="mul" style="color: #FF00FF;">NLG Default text</span> : ❌≪NLG Default text≫❌ krr978x3cc3g3rq4m6lq8kek5wh3mzs 12272 12235 2026-07-18T08:02:03Z HenkvD 1447 /* Overview of NLG functions I work(ed) upon */ 12272 wikitext text/x-wiki {| border="1" style="float: right; margin-left: 1em; margin-bottom: 0.5em; border: #99B3FF solid 1px; background: #F1F8F1; border-collapse: collapse; color:black" | | colspan="10" style="text-align:center;" | <div class="plainlinks">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''Gebruiker:HenkvD''' op [[commons:Template talk:Sisterlinks|zusterprojecten]]</div> |- | valign="top" align="center" | [[Image:Wikipedia-logo.png|18px]]<br>Wikipedia<br>[[:de:Benutzer:HenkvD|de:]] [[:en:User:HenkvD|en:]] [[:fr:Utilisateur:HenkvD|fr:]] '''[[:nl:User:HenkvD|nl:]]''' | valign="top" align="center" | [[Image:Wiktionary-logo-en.png|17px]]<br>Wiktionary<br>[[:wikt:en:User:HenkvD|en:]]<br />[http://www.omegawiki.org/index.php/User:HenkvD ΩWiki] | valign="top" align="center" | [[Image:Wikinews-logo.png|35px]]<br>Wikinews<br>[[wikinews:User:HenkvD|en:]] [[:n:nl:User:HenkvD|nl:]]<br><div class="plainlinks">[http://incubator.wikimedia.org/w/index.php?title=User:HenkvD nl: in incubator]</div> | valign="top" align="center" | [[Image:Wikiquote-logo.png|16px]]<br>Wikiquote<br>[[:q:en:User:HenkvD|en:]] |- | valign="top" align="center" | [[Image:Wikibooks-logo.png|18px]]<br>Wikibooks<br>[[:b:en:User:HenkvD|en:]] | valign="top" align="center" | [[Image:Wikisource-logo.png|18px]]<br>Wikisource<br>[[:s:en:User:HenkvD|en:]] '''[[:s:nl:Gebruiker:HenkvD|nl:]]''' <div class="plainlinks">[http://wikisource.org/wiki/User:HenkvD old]</div> | valign="top" align="center" | [[Image:Wikiversity-logo-en.svg|18px]]<br>Wikiversity<br>[[:de:v:User:HenkvD|de:]] [[:en:v:User:HenkvD|en:]] | valign="top" align="center" | [[Image:Wikimedia-logo.png|18px]]<br>[[:meta:User:HenkvD|Meta]]<br><div class="plainlinks">[http://strategy.wikimedia.org/wiki/User:HenkvD Strategy]<br><div class="plainlinks">'''[http://nl.wikimedia.org/wiki/Gebruiker:HenkvD nl:]'''</div></div> |- | valign="top" align="center" | [[Image:Wikivoyage-Logo-v3-icon.svg|16px]]<br>Wikivoyage<br>[[:en:voy:User:HenkvD|en:]] | valign="top" align="center" | [[File:Wikidata-logo.svg|19px|Wikidata]]<br><div class="plainlinks">[http://www.wikidata.org/wiki/User:HenkvD Wikidata]</div> | valign="top" align="center" | [[Image:Commons-logo.svg|14px]]<br>[[:Commons:User:HenkvD|Commons]] | valign="top" align="center" | [[File:Wikifunctions-logo.svg|14px]] [[File:Abstract-Wikipedia-wordmark.svg|42px]]<br>[[f:User:HenkvD|Wikifunctions]] <br>'''AbstractWiki''' |} My name is Henk, from [[Q55|the Netherlands]] ([[:nl:Gebruiker:HenkvD]]). I am interested in Abstract Wikipedia functionality and have general knowledge of the Dutch language (as native speaker). As most other Dutch persons I have good knowledge of English and some of German and a bit of French and Romance languages.<br> I have an IT background, and try to understand the programming in Wikifunctions.<br> I will try to analyse Wikifunction, Wikidata, lexemes and add Wikifunction tests if needed. In my opinion the initial goal is to have Abstract Wikipedia pages with simple lead section (like stubs), an infobox fully from Wikidata, one or more images and maybe some simple lists. The simple lead sentences should function for as many languages as possible. That will also need that many languages will have labels in Wikidata and lexemes with genders. That will be a difficult enough to achieve. In my opinion extensive prose will be very hard to achieve. <br clear=all> {{#babel:nl|en-3|de-2|fr-1}} ===Overview of NLG functions I work(ed) upon=== {| class="wikitable" ! ZID !! Example !! English !! Dutch || Other simple languages || Default |- | [[f:Z36625|Z36625]] third-person singular form of to be (simple) || || is || is || [[f:Z36627|f:]] en nl fy af bar bs eo frr is hsb mk nds os pap sr +fi +cs hr id zea || (is) |- | [[f:Z36622|Z36622]] indefinite article (simple) || || N/A || een || [[f:Z36624|f:]] nl af fy bar bs eo frr is hsb mk nds os pap sr +fi +cs hr id zea || (a) |- | [[f:Z36610|Z36610]] definite article (simple) || || the || N/A || [[f:Z36620|f:]] en af eo pap +fi +cs hr id || (the) |- | [[f:Z37311|Z37311]] String<br>and (indicating last entry of list) Simple || || and || en || 40 simple languages || (and) |- | [[f:Z32962|Z32962]] HTML [[f:Z26039|Z26039]] String<br>A is a B. || [[Q8739]] || Paris is a city. || Parijs is een stad || [[f:Z35523|f:]] af bar bs eo frr fy hsb is mk nds os pap sr +fi +zea || Y Magenta 🔧 |- | [[f:Z32965|Z32965]] HTML [[f:Z26095|Z26095]] Monlingual<br>an A is a B. || [[Q2102]] || A frog is an amphibian. || een hond is een dier || [[f:Z36875|f:]] af bar bs eo frr fy hsb is (nds) mk nl os pap sr +fi +id zea || Y Magenta 🔧 with ❌ |- | [[f:Z36983|Z36983]] HTML [[f:Z26570|Z26570]] String<br>A is a B in C. || [[Q55]] || Netherlands is a country in Europe || Nederland is een land in Europa. || [[f:Z35618|f:]] af bar eo frr fy mk pap +hr zea || Y magenta 🔧 |- | [[f:Z36987|Z36987]] HTML [[f:Z32581|Z32581]] Monolingual<br>A is a B by C. || [[Q12418]] || Mona Lisa is a painting by Leonardo da Vinci. || Mona Lisa is een schilderij van Leonardo da Vinci. || [[f:Z36168|f:]] af eo fy is mk os pap +cs hr id zea || Y Magenta 🔧 with ❌ |- | [[f:Z36993|Z36993]] HTML [[f:Z32982|Z32982]] Monlingual<br>A is a B of C. || [[Q718]] || Chess is a game of strategy. || Schaken is een spel van strategie. || [[f:Z36528|f:]] af eo fy mk nl pap +cs hr id zea || Y Magenta 🔧 with ❌ |- | [[f:Z37011|Z37011]] HTML [[f:Z28016|Z28016]] Monolingual<br>A is the B of C. || [[Q90]] || Paris is the capital of France. || Parijs is de hoofdstad van Frankrijk<br>❗Lexemes needed for nouns || [[f:Z36339|f:]] af eo mk pap +hr zea || Y Magenta 🔧 with ❌ |- | [[f:Z34282|Z34282]] A is a B. (automatic based on Wikidata class) || [[Q13924]] || Adriatic Sea is a sea || Adriatische Zee is een zee. || WIP Wrapper || N |- | [[f:Z34637|Z34637]] A is part of the B. (automatic based on Wikidata class) || [[Q13924]] || Adriatic Sea is part of the Mediterranean Sea. || || || Y |- | [[f:Z27243|Z27243]] Monolingual<br>Superlative A is the B-est C in D || [[Q319]] || Jupiter is the largest planet in the Solar System. || [[f:Z37022|f:]] Jupiter is de grootste planeet van het zonnestelsel.<br>❗Lexemes needed for nouns || [[f:Z37033|:f:]] eo || Y ⤒ large { planet ∩ Solar System } = Jupiter. |- | [[f:Z29591|Z29591]] Monolingual<br>entity with adjective / class || [[Q177749]] || Jupiter is a big planet || || || Y A ∈ { B ∩ C. }. |- | [[f:Z37005|Z37005]] Monolingual<br>A has parts (automatic based on Wikidata) || [[Q211391]] || Weekend consists of Saturday and Sunday. || Weekeinde bestaat uit zaterdag en zondag. || [[f:Z37328|f:]] 25 languages || Y |- | [[f:Z37289|Z37289]] Monolingual<br>join list of monolingual texts without Oxford comma || || A, B and C || A, B en C || 40 languages || Y |- | || [[Q11750]] || list of sovereign states || || || N/A |- ! '''Infoboxes''' !! !! !! !! !! |- | [[f:Z35167|Z35167]] Infobox person (1) || || OK || [https://www.wikifunctions.org/wiki/Z35167?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z35167%22%2C%22Z35167K1%22%3A%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6821%22%2C%22Z6821K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q154946%22%7D%7D%2C%22Z35167K2%22%3A%22Z1157%22%7D OK] || OK (some labels needed, via P1629)<br>Disconnected the old layout || N/A |- | [[f:Z35370|Z35370]] Infobox for person (1a, Wikidata item reference || || OK || OK || New layout, Also with dates || N/A |- | [[f:Z36678|Z36678]] infobox for city || [[Q90]] || Country France || Land Frankrijk || OK || N/A |- | [[f:Z37827|Z37827]] infobox for taxons || [[Q140]] || || || OK || N/A |- | [[f:Z37623|Z37623]] infobox row || [[Q90]] || Country France || Land Frankrijk || OK ? Seperate functions for date and string / test for combining || N/A |- | [[f:Z37866|Z37866]] infobox row property type || || || || OK || N/A |- | [[f:Z37880|Z37880]] infobox value QID || || || || OK || N/A |- | [[f:Z37883|Z37883]] infobox value string || || || || WIP || N/A |- | [[f:Z37782|Z37782]] infobox row, date || [[Q2407]] || || OK || Maybe to merge into general infobox row || N/A |- | [[f:Z37830|Z37830]] infobox row, string || [[Q140]] || || OK || Maybe to merge into general infobox row || N/A |- | [[f:Z37640|Z37640]] if (HTML output) || || || OK || || N/A |- | [[f:Z37644|Z37644]] Infobox section || || || OK || || N/A |- | [[f:Z37647|Z37647]] infobox color scheme || || || OK || || N/A |- | [[f:infobox 1 image|infobox 1 image]] infobox 1 image || || || Not possible yet? || || N/A |- | [[f:Z36218|Z36218]] specific property of subject is value from WD || [[Q922]]<br> [[Q408]] (load time might be long) || The area of Australia is 7,692,024 km². || De oppervlakte van Australië is 7692024 km²<br>❗Lexemes not yet available for nouns of almost all used properties || [[f:Z36684|f:]] af eo mk pap +cs hr id || Y oppervlakte(Australië) = 7692024 km². |- ! '''NLG Default''' !! !! !! !! !! |- | [[f:Z35921|Z35921]] NLG default text (string) || || OK || || || N/A |- | [[f:Z36911|Z36911]] NLG default text (monolingual text) || || OK || || || language "mul" |- | [[f:Z36909|Z36909]] NLG default text (HTML) || || OK || || || span lang="mul" style="color: #FF00FF;" |- | [[f:Z37454|Z37454]] monolingual text as HTML with lang & colour span || [[Q1370]] || || || || language daz <span lang="mul" style="color: #FF00FF;">⤒ Q138758272 { Q28575 ∩ Virginia } = Q341915</span> |} Steps to get Abstract Wikipedia started: * Basic functions on Wikifunctions * Wikidata labels * Link Wikidata Q-items to Lexemes / gender of lexemes on Wikidata * Link Wikidata P-items via Q-items to Lexemes / gender of lexemes on Wikidata Natural Language * [[f:Wikifunctions:NLG functions|Wikifunctions:NLG functions]] * [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]] Dutch language * [[f:Wikifunctions:Catalogue/Natural language operations/Dutch|Wikifunctions:Catalogue/Natural language operations/Dutch]] Wikidata queries * [https://query.wikidata.org/#%23%20Gender%20of%20City%20per%20langague%0ASELECT%20%3Fl%20%3Flemma%20%3Fsense%20%3Fgender%20%3FgenderLabel%20%28LANG%28%3Flemma%29%20AS%20%3Flanguage%29%0AWHERE%20%7B%0A%20%20%20%20%20%20%3Fsense%20wdt%3AP5137%20wd%3AQ515.%20%20%20%23%20City%0A%20%20%20%20%20%20%3Fl%20ontolex%3Asense%20%3Fsense.%0A%20%20%20%20%20%20%3Fl%20wikibase%3Alemma%20%3Flemma.%20%20%20%23%20FILTER%28LANG%28%3Flemma%29%3D%22de%22%29%0A%20%20%20%20%20%20%3Fl%20wdt%3AP5185%20%3Fgender.%0A%20%20%20%20%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%7D Gender of City per langague ] {{AbstractTestLemma}} {| class="wikitable" ! Function !! English !! Z1157 Dutch !! Z60 Local language |- | <nowiki>{{#function:</nowiki>[[f:Z26039|Z26039]]<nowiki>|Q64|Q515|Z1002}}</nowiki> | {{#function:Z26039|Q64|Q515|Z1002}} || {{#function:Z26039|Q64|Q515|Z1157}} || {{#function:Z26039|Q64|Q515|Z60}} |} Testing different NLG Default texts : <span lang="mul" style="color: #FF00FF;">NLG Default text</span> : ❌≪NLG Default text≫❌ czeoeigrdghp5x9y63b9ls1q6brvipt 0 1237 12346 3587 2026-07-18T10:09:00Z Jsamwrites 874 12346 abstractwiki text/plain { "qid": "Q9404", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } e8i8mqulgij19188nmmmsp3bm3rpnyl 0 1257 12348 3610 2026-07-18T10:12:19Z Jsamwrites 874 12348 abstractwiki text/plain { "qid": "Q11472", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q214609" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q3406743" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } se350zxrz3tgyuxfmasiiw8wb635tqg 12349 12348 2026-07-18T10:12:48Z Jsamwrites 874 12349 abstractwiki text/plain { "qid": "Q11472", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q214609" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q3406743" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 2hsjjpf7qjzg6v4kr3qgayu5gp1g4b2 0 1438 12344 8821 2026-07-18T10:07:21Z Jsamwrites 874 12344 abstractwiki text/plain { "qid": "Q8486", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q40050" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32982", "Z32982K1": { "Z1K1": "Z6091", "Z6091K1": "Q180289" }, "Z32982K2": { "Z1K1": "Z6091", "Z6091K1": "Q21146257" }, "Z32982K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32982K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } mxa8rypg63n5py3gsmdj47iqunqxud2 12345 12344 2026-07-18T10:07:42Z Jsamwrites 874 12345 abstractwiki text/plain { "qid": "Q8486", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q40050" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32982", "Z32982K1": { "Z1K1": "Z6091", "Z6091K1": "Q180289" }, "Z32982K2": { "Z1K1": "Z6091", "Z6091K1": "Q21146257" }, "Z32982K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32982K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 69v7sipj2fvtbm5ja8n2q7edsmhlr72 10 2080 12287 12203 2026-07-18T09:38:44Z ToadetteEdit 1508 Created page with "[[$1|2026-07-16]] ما وراء الجداول النحوية" 12287 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;ركن المتطوعين * سيكون ركن المتطوعين التالي في <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi> على <bdi lang="en" dir="ltr">Google Meet</bdi> في <bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi>. * [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|أحدث ركن المتطوعين]] متاح على كومنز. ; تحديثات الحالة الأخيرة حول ويكي الدوال <!--Keep this to the most recent 5 entries--> * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]] ما وراء الجداول النحوية * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: المضي قدماً نحو أولى محطات دمج ويكيبيديا المجردة * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: الدمج في ويكي الاختبار والخطة السنوية * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|2026-06-26]]: العمل على الدوال معاً * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|2026-06-19]]: الـ أم لا، هذا هو السؤال (أو السؤال؟) </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small">المزيد من الأخبار</span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> 4qfjur0f200h5j9iecl0tpofvi4te6l 12 2083 12289 11938 2026-07-18T09:39:28Z ToadetteEdit 1508 12289 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 1gfkrwrc6067igxj5i4k9vwn40a15r5 12291 12289 2026-07-18T09:39:32Z ToadetteEdit 1508 Created page with "نشر" 12291 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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 id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] jrktqb2unufxbyzmmdydmup114w2x2k 12293 12291 2026-07-18T09:39:46Z ToadetteEdit 1508 Created page with "أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى." 12293 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 39ii567ardgtt7z60s9rbfloczzt8ij 12295 12293 2026-07-18T09:39:59Z ToadetteEdit 1508 Created page with "تحقق من لغة أخرى" 12295 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] evebqbo5xnwt8hmc8rrf0vfmqkypfbm 12297 12295 2026-07-18T09:40:11Z ToadetteEdit 1508 Created page with "يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر"." 12297 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] po8zpkpble21gc81cwss00lrc0au5jr 12299 12297 2026-07-18T09:40:27Z ToadetteEdit 1508 Created page with "تحديث الوسائط" 12299 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 3y61zxm2glh9mmkitj30d687fi0lf34 12301 12299 2026-07-18T09:40:46Z ToadetteEdit 1508 Created page with "قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي." 12301 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] lotgrwk5bfkrjwvphvl8fvfab85vazh 12303 12301 2026-07-18T09:40:58Z ToadetteEdit 1508 Created page with "وسع الدالة/الدوال" 12303 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] g0w9mzqpubaxjkpfwav3g5mqovf70i8 12305 12303 2026-07-18T09:41:12Z ToadetteEdit 1508 Created page with "قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">")." 12305 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] dmzik5g4x05h3oj00ismqtzwu11xjzo 12307 12305 2026-07-18T09:41:24Z ToadetteEdit 1508 Created page with "لصق من الحافظة" 12307 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] lp7rx9i6ssctxd760wfrbe94qzgzo0j 12309 12307 2026-07-18T09:41:29Z ToadetteEdit 1508 Created page with "لصق من الحافظة" 12309 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] sowo31piq7tfmyjn2dn1hekkxtxb3qt 12311 12309 2026-07-18T09:41:43Z ToadetteEdit 1508 Created page with "حدد الجزء المنسوخ من الصف العلوي." 12311 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] qdz9qt2wt3rk8wmdneerm10pxui7ncl 12313 12311 2026-07-18T09:42:04Z ToadetteEdit 1508 Created page with "انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة"." 12313 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] kzcwr81qdxm29nvai8zdl8lrio7lgd4 12315 12313 2026-07-18T09:42:17Z ToadetteEdit 1508 Created page with "أضف جزءاً فارغاً" 12315 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 3ib9rc7jkw840tmaelps8tr5td14ze9 12317 12315 2026-07-18T09:42:52Z ToadetteEdit 1508 Created page with "سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment)." 12317 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] aajw8umdvmdoyfw6lwxc8s9t17iq7ve 12319 12317 2026-07-18T09:43:06Z ToadetteEdit 1508 Created page with "إنشاء مقالة جديدة" 12319 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 2t5n1qp5dskji96zj2n83t0mcv6tavf 12321 12319 2026-07-18T09:43:25Z ToadetteEdit 1508 Created page with "ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها." 12321 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] enjqnea3839utop3wdvwk2dpb79c44z 12323 12321 2026-07-18T09:43:33Z ToadetteEdit 1508 Created page with "نسخ إلى الحافظة" 12323 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|نسخ إلى الحافظة]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] quqp4lh862j5xu71u05503nqrmyxn3q 12325 12323 2026-07-18T09:43:56Z ToadetteEdit 1508 Created page with "انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة"." 12325 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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>]] انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|نسخ إلى الحافظة]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 2ujffcrjgv6rkqlwosk5t0tffy040fg 12327 12325 2026-07-18T09:44:08Z ToadetteEdit 1508 Created page with "ابدأ" 12327 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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|ابدأ]] انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|نسخ إلى الحافظة]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] g4fapobt2t9e63ry0rdlv0hxjv96nmt 12329 12327 2026-07-18T09:44:49Z ToadetteEdit 1508 Created page with "أولاً، ابحث عن مقالة موجودة في ويكيبيديا المجردة تشبه تلك التي تود إنشاءها؛ ويمكنك القيام بذلك باستخدام أداة البحث والنقر على عنصر يحمل اللاحقة "- AW" بجانبه. وبمجرد العثور عليها، انقر على خيار "تعديل المصدر"." 12329 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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> أولاً، ابحث عن مقالة موجودة في ويكيبيديا المجردة تشبه تلك التي تود إنشاءها؛ ويمكنك القيام بذلك باستخدام أداة البحث والنقر على عنصر يحمل اللاحقة "- AW" بجانبه. وبمجرد العثور عليها، انقر على خيار "تعديل المصدر". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|ابدأ]] انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|نسخ إلى الحافظة]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] b89lp8sk6e9yp7haxyuera457c6rvgp 12331 12329 2026-07-18T09:45:17Z ToadetteEdit 1508 Created page with "== خطوات إنشاء مقالة عن طريق النسخ واللصق ==" 12331 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <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> <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == خطوات إنشاء مقالة عن طريق النسخ واللصق == أولاً، ابحث عن مقالة موجودة في ويكيبيديا المجردة تشبه تلك التي تود إنشاءها؛ ويمكنك القيام بذلك باستخدام أداة البحث والنقر على عنصر يحمل اللاحقة "- AW" بجانبه. وبمجرد العثور عليها، انقر على خيار "تعديل المصدر". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|ابدأ]] انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|نسخ إلى الحافظة]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] qkv0szd3n7yisdqom7bznm67znzg681 12333 12331 2026-07-18T09:45:31Z ToadetteEdit 1508 Created page with "إنشاء مقالة من الصفر" 12333 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Create an article by copy and paste</span> # إنشاء مقالة من الصفر <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == خطوات إنشاء مقالة عن طريق النسخ واللصق == أولاً، ابحث عن مقالة موجودة في ويكيبيديا المجردة تشبه تلك التي تود إنشاءها؛ ويمكنك القيام بذلك باستخدام أداة البحث والنقر على عنصر يحمل اللاحقة "- AW" بجانبه. وبمجرد العثور عليها، انقر على خيار "تعديل المصدر". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|ابدأ]] انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|نسخ إلى الحافظة]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] otfaiynzyupm23s9ow00502892wucly 12335 12333 2026-07-18T09:45:46Z ToadetteEdit 1508 Created page with "إنشاء مقالة عن طريق النسخ واللصق" 12335 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. <div lang="en" dir="ltr" class="mw-content-ltr"> This help page describes two methods to create a new article </div> # إنشاء مقالة عن طريق النسخ واللصق # إنشاء مقالة من الصفر <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == خطوات إنشاء مقالة عن طريق النسخ واللصق == أولاً، ابحث عن مقالة موجودة في ويكيبيديا المجردة تشبه تلك التي تود إنشاءها؛ ويمكنك القيام بذلك باستخدام أداة البحث والنقر على عنصر يحمل اللاحقة "- AW" بجانبه. وبمجرد العثور عليها، انقر على خيار "تعديل المصدر". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|ابدأ]] انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|نسخ إلى الحافظة]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] gdhpqa22qtori1we8vtcjbvgaljwmsm 12337 12335 2026-07-18T09:46:38Z ToadetteEdit 1508 Created page with "تصف صفحة المساعدة هذه طريقتين لإنشاء مقالة جديدة." 12337 wikitext text/x-wiki <languages/> في ويكيبيديا المجردة، لا يمكنك إنشاء مقالات إلا حول المواضيع التي لها بالفعل عنصر في ويكي بيانات. إذا لم يكن الموضوع موجودًا بالفعل في ويكي بيانات، يمكنك التأكد من ذلك عن طريق [[d:special:search|البحث]]، ثم طالع [[d:Special:MyLanguage/help:items#Creating a new item|هذه الصفحة المساعدة]] لإنشاء عنصر جديد له. تصف صفحة المساعدة هذه طريقتين لإنشاء مقالة جديدة. # إنشاء مقالة عن طريق النسخ واللصق # إنشاء مقالة من الصفر <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == خطوات إنشاء مقالة عن طريق النسخ واللصق == أولاً، ابحث عن مقالة موجودة في ويكيبيديا المجردة تشبه تلك التي تود إنشاءها؛ ويمكنك القيام بذلك باستخدام أداة البحث والنقر على عنصر يحمل اللاحقة "- AW" بجانبه. وبمجرد العثور عليها، انقر على خيار "تعديل المصدر". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|ابدأ]] انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|نسخ إلى الحافظة]] ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|إنشاء مقالة جديدة]] سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). [[File:AW Help Copy Paste step 04.png|center|frameless|800px|أضف جزءاً فارغاً]] انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". [[File:AW Help Copy Paste step 05.png|center|frameless|800px|لصق من الحافظة]] حدد الجزء المنسوخ من الصف العلوي. [[File:AW Help Copy Paste step 06.png|center|frameless|400px|لصق من الحافظة]] قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">").[[File:AW Help Copy Paste step 07.png|center|frameless|800px|وسع الدالة/الدوال]] قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. [[File:AW Help Copy Paste step 08.png|center|frameless|800px|تحديث الوسائط]] يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". [[File:AW Help Copy Paste step 09.png|center|frameless|800px|تحقق من لغة أخرى]] أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. [[File:AW Help Copy Paste step 10.png|center|frameless|400px|نشر]] ا ا ة ااا <span id="Steps_to_create_an_article_from_scratch"></span> == خطوات إنشاء مقالة من الصفر == لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[Special:CreateAbstract|إنشاء مقالة مجردة جديدة]]. [[File:aw-tutorial-step-1.png|center|frameless|800px|اختيار موضوعًا]] اكتب لاختيار موضوع، ثم انقر على «أنشئ». [[File:aw-tutorial-step-2.png|center|frameless|800px|مقالة مجردة فارغة]] ستنتقل إلى شاشة جديدة. على الجانب الأيمن سترى المعاينة باللغة المختارة، وعلى الجانب الأيسر سترى المحتوى الموجز. [[File:aw-tutorial-step-3.png|center|frameless|800px|انقر على الرمز (+) لإضافة جزءًا.]] انقر على زر علامة الجمع (+) في اللوحة اليسرى لإضافة جزء جديد. حاليًا، سنضيف جزءًا فارغًا. [[File:aw-tutorial-step-4.png|center|frameless|800px|جزءاً فارغاً]] سيظهر هذا على النحو التالي، حيث يعرض استدعاء دالة دون تحديد دالة بعد. انقر على المربع المجاور لنص "تحديد دالة" الأحمر. [[File:aw-tutorial-step-5.png|center|frameless|800px|محدد الدوال مفتوح]] سيؤدي ذلك إلى فتح مُحدد الدوال. [[File:aw-tutorial-step-6.png|center|frameless|800px|اختيار دالة]] نختار دالة. يجب أن تكون هذه الدالة موجودة على ويكي الدالة، ويجب أن تُعيد جزءًا من كود HTML. في هذا المثال، نختار دالة "string to HTML fragment"، لأنها تسمح لنا بإدخال سلسلة نصية، أو اختيار دالة تُنشئ سلسلة نصية. [[File:aw-tutorial-step-7.png|center|frameless|800px|تم الاختيار الدالة «string to HTML fragment»]] لقد اخترنا الآن دالة. نحصل على حقول للوسائط. بدلاً من كتابة سلسلة نصية، نريد إضافة دالة أخرى، [[File:aw-tutorial-step-8.png|center|frameless|800px|غيّر وضع الوسيطة]] للقيام بذلك، نغير نمط الوسيط المسمى "string" بالنقر على النقاط الثلاث بجوار "string". يتيح لنا هذا التغيير من النمط الحالي، وهو "literal"، إلى استدعاء دالة. [[File:aw-tutorial-step-9.png|center|frameless|800px|اختيار الدالة الداخلية]] هنا يمكننا الآن اختيار دالة التي ترجع سلسلة نصية. [[File:aw-tutorial-step-10.png|center|frameless|800px|اختر دالة تُرجع سلسلة نصية]] نختار الدالة "Article-less instantiating fragment" - وهي دالة تُنشئ جملًا مثل "باريس مدينة". لاحظ أن اختيار الدالة "Article-less instantiating HTML fragment" كان سيسمح لنا بتجاوز استخدام الدالة "string to HTML fragment". [[File:aw-tutorial-step-10.png|center|frameless|800px|حجج لصالح دالة إنشاء الأجزاء بدون استخدام أدوات التعريف]] والآن نرى وسائط هذه الدالة. كما نحصل على وسائط مُلائمة مُعبأة تلقائيًا. وهذا يؤدي إلى الجملة "باريس هي باريس."، لأن الوسيطين "entity" و"class" يتم ملؤهما مسبقًا بالعنصر الذي نكتب عنه. [[File:aw-tutorial-step-11.png|center|frameless|800px|تغيير الوضع في وسيطة "الفئة"]] نحتاج إلى تغيير الوضع في وسيط "class" من القيمة المعبأة تلقائيًا (مرجع وسيط) إلى قيمة حرفية. [[File:aw-tutorial-step-12.png|center|frameless|800px|تم تغيير نمط "الفئة" إلى حرفي.]] وهذا يمنحنا الآن حقلاً لاختيار عنصر من عناصر ويكي بيانات لقيمة وسيطة "الفئة". [[File:aw-tutorial-step-13.png|center|frameless|800px|اختيار المدينة للوسيط الفئة]] نختار عنصر "المدينة" لوسيط الفئة. [[File:aw-tutorial-step-14.png|center|frameless|800px|يتم إنشاء الجملة الجديدة.]] بمجرد تحديد هذا الخيار، ستكون الجملة الأولى من المقال جاهزة. الآن، يمكنك النقر على "نشر" وستحصل على النسخة الأولى من المقال. يمكنك الآن النقر على "تعديل" لإضافة المزيد. <span id="This_is_far_too_complicated!"></span> == هذا معقد للغاية! == نعم، أتفق. هناك طريقتان ليجعل هذا أسهل: * تحسين تجربة المستخدم * تحسين قائمة الدوال بينما سيركز فريق التطوير في مؤسسة ويكيميديا ​​على النهج الأول (وسيُقدّر دائمًا أفكار تجربة المستخدم)، يمكن للمجتمع العمل على فهرس أكثر شمولًا وسهولة في الاستخدام للدوال في ويكي الدالة. نلاحظ هنا أهمية تسمية الوظائف والوسائط، وأننا على الأرجح نرغب في تجنب وجود عدد كبير جدًا من الدوال التي تُحوّل نوعًا إلى آخر في التسلسل المذكور أعلاه. لكن الأهم من ذلك، أن ويكيبيديا المجردة لا تزال في مرحلة تجريبية عامة مبكرة، ويصعب حاليًا إنشاء المقالات وتعديلها. لذا، علينا جميعًا العمل معًا لتحسين ذلك. إذا كانت لديكم أفكار لدوال جديدة، يُرجى اقتراحها على [[Abstract Wikipedia:Suggested functions|الدوال المقترحة]]. <span id="See_also"></span> == انظر أيضا == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] afjkou80x1q59itabezn8um132u1v74 1198 2120 12288 5579 2026-07-18T09:39:28Z ToadetteEdit 1508 12288 wikitext text/x-wiki لكي تنشئ مقالة من صفر، يمكنك الذهاب إلى [[$1|إنشاء مقالة مجردة جديدة]]. e5f0gnjw81yyba29f8wvuc4np4kal2k 4 2202 12339 11880 2026-07-18T09:47:52Z ToadetteEdit 1508 12339 wikitext text/x-wiki <languages /> <span id="What_is_Abstract_Wikipedia?"></span> == ما هي ويكيبيديا المجردة؟ == ويكيبيديا المجردة مشروع جديد من مشاريع ويكيميديا، يُمكّن المجتمعات من إنشاء مقالات مستقلة عن اللغة بلغتهم الأم بشكل تعاوني، ليتمكن الآخرون من الوصول إليها بلغاتهم. ويتم هذا التحويل باستخدام دوال من ويكي الدوال التي تصل إلى المحتوى المنظم من ويكي بيانات. <span id="What_is_an_abstract_article?"></span> == ما هي مقالة مجردة؟ == تُقدّم المقالة المجردة معلومات حول موضوع ما بصيغة منظمة ومستقلة عن اللغة. ويقوم المساهمون بدمج البيانات المنظمة من ويكي بيانات مع دوال اللغة من ويكي الدوال لإنتاج جمل بلغة طبيعية تصف الموضوع. <span id="How_is_Abstract_Wikipedia_different_from_Wikipedia?"></span> == كيف تختلف ويكيبيديا المجردة عن ويكيبيديا؟ == تُكتب مقالات ويكيبيديا مباشرة بلغة معينة. بدلاً من ذلك، تقوم ويكيبيديا المجردة بتخزين المعلومات في شكل منظم يمكنه إنشاء نص بلغات عديدة بمساعدة ويكي الدوال. <span id="How_does_Abstract_Wikipedia_relate_to_Wikidata_and_Wikifunctions?"></span> == كيف ترتبط ويكيبيديا المجردة بويكي بيانات وويكي الدوال؟ == تبني ويكيبيديا المجردة على هذه مشاريع ويكيميديا: * يوفر '''ويكي بيانات''' بيانات معجمية ومعلومات منظمة حول المواضيع، وبيانات اللغة الطبيعية (المعجمي). * يوفر '''ويكي الدوال''' (من بين أمور أخرى) دوال تقوم بإنشاء نصوص بلغة طبيعية في العديد من اللغات. * تجمع '''ويكيبيديا المجردة''' هذه العناصر لإنشاء مقالات يمكن إنشاؤها بلغات عديدة. <span id="Is_Abstract_Wikipedia_using_AI?"></span> == هل تستخدم ويكيبيديا المجردة الذكاء الاصطناعي؟ == لا. لا تقوم ويكيبيديا المجردة بإنشاء المقالات تلقائياً باستخدام الذكاء الاصطناعي. تُنشئ مقالات المجردة ويتم صيانتها من قبل المساهمين، وتقوم الدوال المكتوبة من قبل المجتمع بإنشاء النص من بيانات منظمة. <span id="Does_Abstract_Wikipedia_automatically_appear_on_other_Wikipedias?"></span> === هل تظهر ويكيبيديا المجردة على مواقع ويكيبيديا أخرى تلقائيًا؟ == لا. لا تقوم ويكيبيديا المجردة بإضافة محتوى تلقائياً إلى ويكيبيديا أخرى. كل مجتمع ويكيبيديا يحتفظ بالسيطرة الكاملة على محتواه، ولا يتم استبدال المقالات المحلية الموجودة مطلقاً. في المستقبل، سيتمكن كل مجتمع من مجتمعات ويكيبيديا من تحديد ما إذا كان يرغب في استخدام المحتوى المُنشأ من ويكيبيديا المجردة. <span id="Who_can_contribute_to_Abstract_Wikipedia?"></span> == من يستطيع المساهمة في ويكيبيديا المجردة؟ == مثل مشاريع ويكيميديا ​​الأخرى، يتم تحرير ويكيبيديا المجردة وصيانتها بواسطة متطوعين من المجتمع. يمكن للأشخاص المساهمة بطرق مختلفة، بما في ذلك إنشاء أو تحسين المقالات المجردة، وكتابة دوال اللغة في ويكي الدوال، وإضافة البيانات إلى ويكي بيانات، وتحسين الوثائق، والمساعدة في تشكيل كيفية تطور المشروع. <span id="Can_I_use_Abstract_Wikipedia_today?"></span> == هل يمكنني استخدام ويكيبيديا المجردة اليوم؟ == نعم. يمكنك استكشاف النسخة التجريبية المبكرة من ويكيبيديا المجردة (هذا الموقع). يمكنك إنشاء مقالات مجردة وعرض النص المُنشأ بلغات مختلفة. لا تزال ويكيبيديا المجردة في '''مرحلة مبكرة'''، لذا ستستمر جوانب عديدة من التجربة في التطور بناءً على آراء المجتمع وملاحظاته. سنعمل على تحسين قدرات الموقع وسهولة استخدامه بشكل كبير في المستقبل. قد تواجه أخطاءً تقنية، أو مشكلات في سهولة الاستخدام، أو انقطاعاً في الاتصال (بسبب انتهاء المهلة الزمنية)، أو مشكلات أخرى في الإصدار الحالي. يرجى [[Abstract Wikipedia:Project chat|إعلامنا]] في حال حدوث ذلك أو إذا كانت لديك أفكار للتحسين! في المستقبل، ستتمكن مجتمعات ويكيبيديا أيضًا من دمج المحتوى الذي تم إنشاؤه على ويكيبيديا المجردة في مواقع الويكي الخاصة بها، إذا رغبت في ذلك. [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] 5qqbenx3hxumov5g238p2k97ne2icv1 1198 2226 12338 5855 2026-07-18T09:47:52Z ToadetteEdit 1508 12338 wikitext text/x-wiki لا تزال ويكيبيديا المجردة في '''مرحلة مبكرة'''، لذا ستستمر جوانب عديدة من التجربة في التطور بناءً على آراء المجتمع وملاحظاته. سنعمل على تحسين قدرات الموقع وسهولة استخدامه بشكل كبير في المستقبل. قد تواجه أخطاءً تقنية، أو مشكلات في سهولة الاستخدام، أو انقطاعاً في الاتصال (بسبب انتهاء المهلة الزمنية)، أو مشكلات أخرى في الإصدار الحالي. يرجى [[$1|إعلامنا]] في حال حدوث ذلك أو إذا كانت لديك أفكار للتحسين! ler3tielv88j1o5gtirgx5ujy64gxay 0 2673 12224 11864 2026-07-17T12:19:33Z 99of9 614 These functions are not language-configured. There's no point trying to construct an English sentence. It has to work in all lanugages. This kind of work can be done on Wikifunctions to construct English renderers of a general function. 12224 abstractwiki text/plain { "qid": "Q81", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z11", { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q756" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q20136" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z33975", "Z33975K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z33975K2": { "Z1K1": "Z6091", "Z6091K1": "Q235352" }, "Z33975K3": { "Z1K1": "Z6091", "Z6091K1": "Q5401" }, "Z33975K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } elkbvl0hu5dfugjeu86k3ufy91t1x2u 0 3504 12233 9357 2026-07-17T21:59:45Z Jsamwrites 874 12233 abstractwiki text/plain { "qid": "Q8041", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } jluovs8sg3v94rv86wbrevh3h27271a 0 3506 12240 9360 2026-07-17T22:05:07Z Jsamwrites 874 12240 abstractwiki text/plain { "qid": "Q173136", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 0eak296tiinm0o0dlzrpbgoaes79j1j 0 3527 12236 9403 2026-07-17T22:02:29Z Jsamwrites 874 12236 abstractwiki text/plain { "qid": "Q698", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } csa5mekoosdohv3o43p5pjf34lnemyq 4 3758 12341 11875 2026-07-18T09:49:05Z ToadetteEdit 1508 12341 wikitext text/x-wiki <languages/> {{policy}} تصف '''سياسة الحذف''' كيفية تحديد المقالات والوسائط والصفحات الأخرى التي لا تستوفي المعايير ذات الصلة بمحتوى الموسوعة وإزالتها من ويكيبيديا المجردة. يؤدي حذف مقالة في ويكيبيديا المجردة إلى إزالة النسخة الحالية وجميع النسخ السابقة من العرض العام. يمكن لأي مستخدم إفراغ محتوى الصفحة (أو التراجع عن ذلك)، ولكن الإداريين وحدهم هم من يمكنهم إجراء الحذف، والاطلاع على الصفحات المحذوفة، والتراجع عن أي عملية حذف (أي استعادة الصفحة). وتُسجَّل جميع هذه الإجراءات (باستثناء الاطلاع على الصفحات) في سجل الحذف. وفي حال وجود شك بشأن وجود توافق في الآراء حول حذف صفحة ما، فإن الإداريين عادةً لا يقومون بحذفها. <span id="Reasons_for_deletion"></span> == أسباب للحذف == <!--NOTE: I've consciously chosen not to include: * content forks (should be addressed on WD, or the article repurposed if an item is misused) * articles that cannot possibly be attributed to reliable sources, including neologisms, original theories and conclusions, and hoaxes (should be addressed on WD) * Files that are unused, obsolete, or violate the non-free policy (we get our files exclusively from commons, so this might not be needed) * --> # <span class="anchor" id="1">انتهاكات حقوق الطبع والنشر</span> # <span class="anchor" id="2">التخريب</span> # <span class="anchor" id="3">الدعاية أو السبام</span> # <span class="anchor" id="4">مقالات فشلت محاولات جادة للعثور على مصادر موثوقة للتحقق منها</span> # <span class="anchor" id="5">المقالات التي تتناول مواضيع لا تستوفي [[Special:MyLanguage/Project:Notability|معايير الملحوظية]]</span> # <span class="anchor" id="6">سير ذاتية لأشخاص أحياء لا يمكن التحقق منها</span> # <span class="anchor" id="7">قوالب زائدة أو غير مفيدة</span> # <span class="anchor" id="8">تصانيف تمثل الإفراط في التصنيف</span> # <span class="anchor" id="9">أي استخدام آخر للمقالة أو القالب أو المشروع أو نطاق المستخدم يتعارض مع السياسة المنفصلة المعتمدة لذلك النطاق</span> # <span class="anchor" id="10">المقالات التي تتداخل مع أو تتسبب في تعطيل البرامج التي تدعم ويكيبيديا المجردة أو البنية التحتية لمؤسسة ويكيميديا</span> # <span class="anchor" id="11">أي محتوى آخر غير مناسب للموسوعة</span> <span id="Processes"></span> == العمليات == <span id="Copyright_violations"></span> === انتهاكات حقوق الملكية الفكرية === لأسباب قانونية، لا يمكن لويكيبيديا المجردة استضافة انتهاكات حقوق النشر. فمجرد تحويل نص إلى شكل ملخص لا يعني فقدان المؤلف لحقوق النشر، إلا إذا كان النص بيانًا أساسيًا لحقيقة ما. يحق لأي إداري حذف أي محتوى ينتهك حقوق النشر بغض النظر عن أي نقاش. إذا اكتشفت انتهاكًا لحقوق النشر، فأبلغ عنه في صفحة طلبات الحذف أو في لوحة إعلانات المسؤولين. قبل حذف صفحة بسبب انتهاكات حقوق النشر، يُرجى التفكير في إزالة مخالفة حقوق النشر من سجل الصفحة إذا كان بالإمكان استعادة أي جزء من محتواها. كما يُنصح بالتواصل مع مالك العمل لمعرفة ما إذا كان مستعدًا لنشره بموجب ترخيص مناسب أو جعله ملكًا عامًا. <span id="Speedy_deletion"></span> === الحذف السريع === <!--NOTE: consider more strict rules when necessary--> تُعتبر الصفحات التي تُمثل انتهاكات واضحة لا لبس فيها لأسباب الحذف من 2 إلى 3 ومن 9 إلى 11 مؤهلة للحذف السريع. ويحق لأي مسؤول حذف أي صفحة مؤهلة للحذف السريع. ويمكن ترشيح الصفحات غير المجردة للحذف السريع باستخدام قالب {{tl|delete}}. <span id="Deletion_discussion"></span> === نقاش الحذف === في جميع الحالات الأخرى، يتم الحذف من خلال نقاش على صفحة [[Abstract Wikipedia:Requests for deletion|ويكيبيديا المجردة:طلبات الحذف]]. يجب على مُرشِّح الصفحة للحذف إبلاغ مُنشئ الصفحة عند ترشيح المقالة للحذف. إذا تم التوصل إلى إجماع على إزالة المقالة، فسيتم حذفها، وإلا فسيتم الاحتفاظ بها. [[Category:Abstract Wikipedia administration{{#translation:}}|Deletion policy]] effxsfcspf99u3ji9iwpe0hl3o5xwtk 1198 3779 12340 10159 2026-07-18T09:49:05Z ToadetteEdit 1508 12340 wikitext text/x-wiki يؤدي حذف مقالة في ويكيبيديا المجردة إلى إزالة النسخة الحالية وجميع النسخ السابقة من العرض العام. يمكن لأي مستخدم إفراغ محتوى الصفحة (أو التراجع عن ذلك)، ولكن الإداريين وحدهم هم من يمكنهم إجراء الحذف، والاطلاع على الصفحات المحذوفة، والتراجع عن أي عملية حذف (أي استعادة الصفحة). وتُسجَّل جميع هذه الإجراءات (باستثناء الاطلاع على الصفحات) في سجل الحذف. وفي حال وجود شك بشأن وجود توافق في الآراء حول حذف صفحة ما، فإن الإداريين عادةً لا يقومون بحذفها. e67ini1rlmlgn20ad64j617qjxgbn57 0 3881 12223 12174 2026-07-17T12:13:18Z 99of9 614 Please don't. We're all aware that we need more accurate & expressive functions. This doesn't help. 12223 abstractwiki text/plain { "qid": "Q6517455", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36418", "Z36418K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } iz0i7n9yl7h5c0ukwv2j9hc6g524z9r 0 4209 12222 11353 2026-07-17T12:11:46Z HenkvD 1447 + infobox 12222 abstractwiki text/plain { "qid": "Q3183", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M150324506" }, "Z36038K2": { "Z1K1": "Z7", "Z7K1": "Z36270", "Z36270K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36270K2": { "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": "Q408" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36835", "Z36835K1": { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3206" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36835K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36835K3": { "Z1K1": "Z40", "Z40K1": "Z41" } }, { "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": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q485762" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1448" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q5865918" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q11267380" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P66" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q1516670" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q2221906" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q2725376" }, "Z32145K2": { "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": "Q1553864" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q55557858" }, { "Z1K1": "Z6091", "Z6091K1": "Q5589347" }, { "Z1K1": "Z6091", "Z6091K1": "Q2991162" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3365500" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P159" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q1371068" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P276" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32123", "Z32123K1": { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z10000", "Z10000K1": { "Z1K1": "Z7", "Z7K1": "Z36270", "Z36270K1": { "Z1K1": "Z6091", "Z6091K1": "Q3299260" }, "Z36270K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z10000K2": ":" } } }, { "Z1K1": "Z7", "Z7K1": "Z32179", "Z32179K1": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q606256" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q604332" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q606312" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q606246" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q736170" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q585453" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q543331" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1105257" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1136726" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q604376" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1455046" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1538602" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1703523" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1721949" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1794961" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q549764" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q476922" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1261226" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1490452" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1469756" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1855330" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1660264" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q2094463" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1671784" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q606236" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1857834" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1506748" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q604307" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q1573718" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32428", "Z32428K1": { "Z1K1": "Z6091", "Z6091K1": "Q543262" }, "Z32428K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q159810" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q5333808" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q8434" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q5341186" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q11033" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q11042" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q6942243" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q349" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q7579499" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q121359" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 1a61dxofd6ct326iybgq476fysu0iqj 2 4509 12219 12218 2026-07-17T11:59:24Z 99of9 614 /* From your favourite Wikipedia edition */ 12219 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] ::*[[Q3130]] ::*[[Q3183]] #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put spacers between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is Z36038. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is Z36270 and then you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call Z36218 with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use Z36218 Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have Z37683 if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) ===What makes an article well constructed=== 5z3kyuk85z0vafikgnc5qbfcm3m3lv7 12220 12219 2026-07-17T12:02:01Z 99of9 614 /* Things to avoid (at first) */ 12220 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] ::*[[Q3130]] ::*[[Q3183]] #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put spacers between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is Z36038. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is Z36270 and then you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call Z36218 with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use Z36218 Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have Z37683 if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong. ===Functions to try=== ===What makes an article well constructed=== 4z602vuklo7j58nxv7ehgm7t6tflvjh 12221 12220 2026-07-17T12:10:11Z HenkvD 1447 + city names and help page 12221 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put spacers between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is Z36038. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is Z36270 and then you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call Z36218 with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use Z36218 Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have Z37683 if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong. ===Functions to try=== ===What makes an article well constructed=== npxa0idzvrymft1ll7jx23uchxm2y03 12247 12221 2026-07-17T23:44:39Z 99of9 614 /* From Wikidata */ 12247 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put spacers between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is Z36038. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is Z36270 and then you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call Z36218 with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use Z36218 Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have Z37683 if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong. ===Functions to try=== ===What makes an article well constructed=== e5mqv2kizvqizm5gbdt1hvj1hr432s9 12248 12247 2026-07-17T23:46:10Z 99of9 614 [[:f:Z35672]] 12248 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is Z36038. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is Z36270 and then you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call Z36218 with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use Z36218 Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have Z37683 if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong. ===Functions to try=== ===What makes an article well constructed=== l6esb268uouc52ox9o76h8dl98ia7tg 12249 12248 2026-07-17T23:47:13Z 99of9 614 /* From Commons */ 12249 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is [[:f:Z36038]]. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is [[:f:Z36270]] for which you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call Z36218 with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use Z36218 Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have Z37683 if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong. ===Functions to try=== ===What makes an article well constructed=== ixk9i1piuh7r7nt6prb84dhca8kl6u6 12250 12249 2026-07-17T23:47:49Z 99of9 614 /* From Wikidata */ [[:f:Z36218]] 12250 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is [[:f:Z36038]]. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is [[:f:Z36270]] for which you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call [[:f:Z36218]] with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use Z36218 Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have Z37683 if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong. ===Functions to try=== ===What makes an article well constructed=== gbrhfe8a95ejjlatzjslskjmnk3pus4 12251 12250 2026-07-17T23:48:39Z 99of9 614 /* From your favourite Wikipedia edition */ 12251 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is [[:f:Z36038]]. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is [[:f:Z36270]] for which you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call [[:f:Z36218]] with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use [[:f:Z36218]] Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have Z37683 if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong. ===Functions to try=== ===What makes an article well constructed=== q2w27g8x9oy63yeymtqeqozjxph9bxt 12252 12251 2026-07-17T23:49:18Z 99of9 614 /* Things to avoid (at first) */ [[:f:Z37683]] 12252 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is [[:f:Z36038]]. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is [[:f:Z36270]] for which you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call [[:f:Z36218]] with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use [[:f:Z36218]] Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have [[:f:Z37683]] if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong. ===Functions to try=== ===What makes an article well constructed=== p66l8tzg60pcjxbxq6uwuba6nsf4tye 12253 12252 2026-07-17T23:50:30Z 99of9 614 /* Things to avoid (at first) */ 12253 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is [[:f:Z36038]]. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is [[:f:Z36270]] for which you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call [[:f:Z36218]] with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use [[:f:Z36218]] Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have [[:f:Z37683]] if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong ("Channel 7 is the television station in Sydney" vs "Channel 7 is a television station in Sydney"). ===Functions to try=== ===What makes an article well constructed=== ehnqf0kzusntw20r5e3y7mqy54ctc46 12254 12253 2026-07-17T23:50:52Z 99of9 614 /* Functions to try */ 12254 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is [[:f:Z36038]]. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is [[:f:Z36270]] for which you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call [[:f:Z36218]] with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use [[:f:Z36218]] Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have [[:f:Z37683]] if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong ("Channel 7 is the television station in Sydney" vs "Channel 7 is a television station in Sydney"). ==Functions to try== ===What makes an article well constructed=== 9fhzr6l0p746o5d9x8y67b2ohb01e82 12255 12254 2026-07-17T23:51:07Z 99of9 614 /* What makes an article well constructed */ 12255 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is [[:f:Z36038]]. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is [[:f:Z36270]] for which you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call [[:f:Z36218]] with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use [[:f:Z36218]] Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have [[:f:Z37683]] if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong ("Channel 7 is the television station in Sydney" vs "Channel 7 is a television station in Sydney"). ==Functions to try== ==What makes an article well constructed== nv1o8l1oclxv3r0yptqxv45fch813tp 12258 12255 2026-07-18T01:37:54Z 99of9 614 /* Functions to try */ 12258 wikitext text/x-wiki << IN DRAFT >> My advice for writing a simple Abstract Wikipedia article. (Current Context: a populated place, as requested on Project Chat.) #Find a comparable article that is well constructed (see later section) and has a similar theme. Here are some examples I've helped with or written: ::*[[Q17198982]] Diablo ::*[[Q3130]] Sydney ::*[[Q3183]] Perth #Much of the structure or even some of the statements can be copied directly across. Open both articles in edit mode. Left click on the triple dot of the fragment you want to copy, and choose "Copy to clipboard". Then in the article you're creating either click + then "empty fragment", or left click a triple dot and insert above or below. Finally left click the triple dot and "Paste from clipboard". See also: [[Help:How to create an article]] #Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured). You may need to change one of the arguments to adapt to your subject. #Put sentence separators ([[:f:Z35672]]) between sentences. (In some languages this will be no gap at all, but in most will provide a space.) ==Adding new content== ===From Commons=== Adding thumbnails makes articles look good. The function to use is [[:f:Z36038]]. You need to put a language-configured function in the alt-text, because a monolingual text that you typed in would just be monolingual. The simplest function to put in the alt text is [[:f:Z36270]] for which you need to pick a QID representing what the picture shows. ===From Wikidata=== Go through the main statements, and see if you can simply call [[:f:Z36218]] with the property you want. This is a very versatile and easy function to use and often gets you a nice result with a reference back to Wikidata very quickly. But even the English implementation cannot currently grammatically handle all 10k Wikidata properties. Surprisingly many work. Eventually each language may need case statement to send different properties to different renderers. But in concept it's well-defined, because almost all properties are already well defined on WD. So technically, your abstract call is correct and any poor rendering in English is not your fault. (Although personally I'd rather not add a statement until it renders well in at least one language!) ===From your favourite Wikipedia edition=== Consider implementing some of the structural elements: * Section headings directly from QIDs are usually well translated across many languages, and don't need much grammatical modification. Sometimes you'll want the plural, so there's a second function for that. * "Main articles" statements are an easy way to link to sub-items of a concept. These are almost all red-links for now, because they're even more specific than the article we're writing. But they are also often translated into many languages. Even though there's no sentence, the reader often learns something from the fact that this is an important sub-article (e.g. in the "economy" section of Australia, if there is a "main article: mining in Australia", then you have already learned that mining is an important part of the Australian economy). Scan through the article with an existing function in mind. If you're thinking about [[:f:Z36983]] ("A is a B located in C"), then you get up to a section that discusses the media coverage in your city, you can add "Channel 7 is a television station in Sydney." Note that even though the article is about Sydney, Sydney doesn't have to be subject A in your sentence, it can be object C. Similarly, you can use [[:f:Z36218]] Wikidata values from other items (you'll need to change the default subject to a different "Literal Wikidata Item Reference" ) if they're relevant to your topic (Perhaps your topic is the value of their WD statement, or perhaps you've already established the relation between your main subject and this concept you're now explaining in more detail). ==Things to avoid (at first)== #Don't try to join multiple sentences into a single paragraph call. That is too expensive for the orchestrator, so it will error. Instead each fragment should be either a new sentence, a sentence spacer, a picture, an infobox, or some other single call. #If possible, avoid composing function calls on AW. If wrapping or converting non-HTML types, this is usually better done on WF, so that other AW users can just make a single HTML call. We have already started wrapping quite a few of the monolinguals and strings, so find the HTML-returning versions of NLG functions. #Don't worry too much about wikilinks. The generic functions will tend to overlink your sentences. Later you will wrap these in a function which removes links to QIDs you specify. This kind of composition does have to be done on AW, because it is part of the editing process ("Do I really want a link to the concept of largeness in this superlative sentence"?) #Don't try to force a sentence into a broad or ill-defined function (e.g. subject-verb-object). If you want to say "Person X died in place Y" you might get tempted to bash an existing function with inputs [X, death, Y], but if it's not designed for the type of sentence you actually want, in some languages it may end up saying "X deathed Y" or something similarly useless. The fact is, we don't currently have a function specific to "Person X died in place Y". So skip that fact for now. (By the way, we do have [[:f:Z37683]] if you want to say someone was born in your location. It is currently immature, but at least it means exactly what you want it to mean.) #Even choosing the wrong function out of "defining role sentence" or "non-defining role sentence" can make it wrong ("Channel 7 is the television station in Sydney" vs "Channel 7 is a television station in Sydney"). ==Functions to try== Finding the right functions using search tools on Wikifunctions is currently not easy for a newcomer. Some that seem to have the right name don't work as intended. It is better to look through existing usage, or catalogues compiled by experienced users. I'll make a list of my own here. There are a few of these already (feel free to link to them). But even they may be a little out of date, because NLG functions are being written and have been changing quite rapidly since AW was released. We are still figuring out what is needed. Even many of the current generation of functions may eventually be replaced or reimplemented. ==What makes an article well constructed== tt7aaxplrg2p0q7xq9dgfyfzdm9jivc 0 4510 12230 2026-07-17T21:00:08Z Xalsier 6074 Added subject is a plant. 12230 abstractwiki text/plain { "qid": "Q4156126", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q756" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } ntoyau1pokj8p77ih9qb4wny7gfd2no 0 4511 12231 2026-07-17T21:03:57Z Xalsier 6074 Added subject is a plant 12231 abstractwiki text/plain { "qid": "Q17245167", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q756" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } hnkdzoqcuyj2gbq9qixiloy0fhylasy 12260 12231 2026-07-18T06:11:19Z Xalsier 6074 Photograph 12260 abstractwiki text/plain { "qid": "Q17245167", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M184621346" }, "Z36038K2": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "A photograph of Phlox Floridana." } } }, { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q756" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } tjq94owsolpeazndo8gymbd3ej2rq0y 2 4512 12232 2026-07-17T21:07:42Z Xalsier 6074 ToDo 12232 wikitext text/x-wiki == ToDo == * Find example articles to better understand how the functions work. hgd4dorvk9ra906pr0cie5rrtpsjt2c 12261 12232 2026-07-18T06:14:03Z Xalsier 6074 ToDo 12261 wikitext text/x-wiki == ToDo == * [[Q17245167]] - Phlox floridana * [[Q4156126]] - Skeleton flower kyhk2d3qj7zdoh3j3cnds1ccc2i3ho2 0 4513 12234 2026-07-17T22:01:12Z Jsamwrites 874 Created page with "{ "qid": "Q483604", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12234 abstractwiki text/plain { "qid": "Q483604", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } s0m4xbqcve99gtdisiu7r0xsulj83m0 0 4514 12237 2026-07-17T22:03:36Z Jsamwrites 874 Created page with "{ "qid": "Q48524", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12237 abstractwiki text/plain { "qid": "Q48524", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } iqg8svlyo7o5pmo7o33ty1o6nsluc7c 0 4515 12238 2026-07-17T22:04:07Z Jsamwrites 874 Created page with "{ "qid": "Q777", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12238 abstractwiki text/plain { "qid": "Q777", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 54wsswbbpr3ihymmloy55timtk9s0su 0 4516 12239 2026-07-17T22:04:37Z Jsamwrites 874 Created page with "{ "qid": "Q19841877", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12239 abstractwiki text/plain { "qid": "Q19841877", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 3uvd1ybhi81d2jj1kd8ufn9e35n91ke 12271 12239 2026-07-18T07:59:23Z Jsamwrites 874 12271 abstractwiki text/plain { "qid": "Q19841877", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } sdlv0ji2fmgtqxci1d4q67m4trdg6i9 0 4517 12241 2026-07-17T22:05:37Z Jsamwrites 874 Created page with "{ "qid": "Q604945", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12241 abstractwiki text/plain { "qid": "Q604945", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 14axd9xyw46m497p3ikqrn5te5h2349 0 4518 12242 2026-07-17T22:06:15Z Jsamwrites 874 Created page with "{ "qid": "Q131382", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12242 abstractwiki text/plain { "qid": "Q131382", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } jv91xo0bub4f718spm3t5sb9rtspdts 0 4519 12243 2026-07-17T22:06:44Z Jsamwrites 874 Created page with "{ "qid": "Q189722", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12243 abstractwiki text/plain { "qid": "Q189722", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } tfrl9frv4nzhdq7qqdw33mdiarmyj13 0 4520 12244 2026-07-17T22:07:38Z Jsamwrites 874 Created page with "{ "qid": "Q1165933", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12244 abstractwiki text/plain { "qid": "Q1165933", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 8lp2d9ppii6uz2tp7n54d30tvjotdeq 0 4521 12245 2026-07-17T22:08:03Z Jsamwrites 874 Created page with "{ "qid": "Q1431", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12245 abstractwiki text/plain { "qid": "Q1431", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 94uhvdain3rmxollnbkdo3z9pg389ry 0 4522 12246 2026-07-17T22:08:26Z Jsamwrites 874 Created page with "{ "qid": "Q44316", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12246 abstractwiki text/plain { "qid": "Q44316", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } ekbk7dda8vsqkz7azlwbd1m6d3la7rf 0 4523 12263 2026-07-18T06:58:15Z Jsamwrites 874 Created page with "{ "qid": "Q300662", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12263 abstractwiki text/plain { "qid": "Q300662", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } jsye16ddpn3kt7aip1pbqcwnyhz18qo 0 4524 12265 2026-07-18T07:26:48Z Jsamwrites 874 Created page with "{ "qid": "Q178565", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12265 abstractwiki text/plain { "qid": "Q178565", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } f40elauicq3qgqx816yogc6kllmlb0z 0 4525 12266 2026-07-18T07:27:25Z Jsamwrites 874 Created page with "{ "qid": "Q572226", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12266 abstractwiki text/plain { "qid": "Q572226", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } mp716207ibpqhiyytcscle31y7pnd52 0 4526 12267 2026-07-18T07:28:05Z Jsamwrites 874 Created page with "{ "qid": "Q816725", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12267 abstractwiki text/plain { "qid": "Q816725", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } tg65mpc1rift07da8zz10q8nmtv9nou 0 4527 12268 2026-07-18T07:29:25Z Jsamwrites 874 Created page with "{ "qid": "Q194501", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12268 abstractwiki text/plain { "qid": "Q194501", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } nxpy7jcux07a2s62f30doeg42yle7uj 0 4528 12269 2026-07-18T07:31:03Z Jsamwrites 874 Created page with "{ "qid": "Q1533275", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12269 abstractwiki text/plain { "qid": "Q1533275", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } kb5p38cugyrsgpk8spqvjjt185v5fzy 0 4529 12270 2026-07-18T07:31:47Z Jsamwrites 874 Created page with "{ "qid": "Q171477", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12270 abstractwiki text/plain { "qid": "Q171477", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } suszlu7o5sdjbe7ndysjmxnqhh8s6ob 0 4530 12274 2026-07-18T08:38:37Z Jsamwrites 874 Created page with "{ "qid": "Q8038", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12274 abstractwiki text/plain { "qid": "Q8038", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } m1pkmlvrlv22qhodmbj0ogu1ypxjrow 0 4531 12275 2026-07-18T08:39:52Z Jsamwrites 874 Created page with "{ "qid": "Q305892", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12275 abstractwiki text/plain { "qid": "Q305892", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } ajxqctaegf0ggn5c8m4rrabz4gt7fz4 0 4532 12276 2026-07-18T08:40:28Z Jsamwrites 874 Created page with "{ "qid": "Q230724", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12276 abstractwiki text/plain { "qid": "Q230724", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 85xiuca5ite29y8hlljbxfd56luvrwr 0 4533 12277 2026-07-18T08:41:11Z Jsamwrites 874 Created page with "{ "qid": "Q381", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12277 abstractwiki text/plain { "qid": "Q381", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } jckxpew7mh5a06615hv98pah41yx4lq 0 4534 12278 2026-07-18T08:41:49Z Jsamwrites 874 Created page with "{ "qid": "Q11250", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12278 abstractwiki text/plain { "qid": "Q11250", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 53wjbuywqs0q5fwsga0gn8b8cxxtpin 12279 12278 2026-07-18T08:42:13Z Jsamwrites 874 12279 abstractwiki text/plain { "qid": "Q11250", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } n5wfrqxt0yhrrql7of0uy1ef57t8ep5 0 4535 12280 2026-07-18T08:42:32Z Jsamwrites 874 Created page with "{ "qid": "Q11368", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12280 abstractwiki text/plain { "qid": "Q11368", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 935l21hfjqv0ey4b8k8jm8lg4nv5iag 0 4536 12281 2026-07-18T08:43:03Z Jsamwrites 874 Created page with "{ "qid": "Q14579", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12281 abstractwiki text/plain { "qid": "Q14579", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } ehp80nhof023c2am0e74qpucg1vy8c0 0 4537 12282 2026-07-18T08:44:38Z Jsamwrites 874 Created page with "{ "qid": "Q83", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12282 abstractwiki text/plain { "qid": "Q83", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 1h6yeb00vvciu2hf24sp4nv09l9ckms 0 4538 12283 2026-07-18T08:45:45Z Jsamwrites 874 Created page with "{ "qid": "Q178940", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12283 abstractwiki text/plain { "qid": "Q178940", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } rjxs8svj6qb3ictq6setse7nfap8xbk 0 4539 12284 2026-07-18T08:46:13Z Jsamwrites 874 Created page with "{ "qid": "Q193321", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12284 abstractwiki text/plain { "qid": "Q193321", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } mg7jm9w6idvfb3fd0rq1lfmusxqa8i1 12285 12284 2026-07-18T08:46:40Z Jsamwrites 874 12285 abstractwiki text/plain { "qid": "Q193321", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } fh61yvk3wza513pxwg2a9akbplt0ggx 1198 4540 12286 2026-07-18T09:38:44Z ToadetteEdit 1508 Created page with "[[$1|2026-07-16]] ما وراء الجداول النحوية" 12286 wikitext text/x-wiki [[$1|2026-07-16]] ما وراء الجداول النحوية 3hv5p49czqdc4kqxdn4kjbd2mopcavn 1198 4541 12290 2026-07-18T09:39:31Z ToadetteEdit 1508 Created page with "نشر" 12290 wikitext text/x-wiki نشر 3ud4vbwqm7zf8xfyupcz5e23e26cbnf 1198 4542 12292 2026-07-18T09:39:45Z ToadetteEdit 1508 Created page with "أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى." 12292 wikitext text/x-wiki أكمل العملية بإدخال ملخص موجز للتعديل يصف التغييرات التي أجريتها، ثم انقر على "نشر" مرة أخرى. 5t9ng53fk79wxbxebha4x4xie96kuy1 1198 4543 12294 2026-07-18T09:39:58Z ToadetteEdit 1508 Created page with "تحقق من لغة أخرى" 12294 wikitext text/x-wiki تحقق من لغة أخرى tua86gyd3fh4a0uhkzxn91s3nuw2yrw 1198 4544 12296 2026-07-18T09:40:11Z ToadetteEdit 1508 Created page with "يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر"." 12296 wikitext text/x-wiki يُوصى بشدة بالاطلاع على المعاينة بلغات أخرى لضمان صحة ترجمة الملخص. وبعد المراجعة، انقر على "نشر". oqkt8f9zhhpyfwcn3l49vunklc9uknw 1198 4545 12298 2026-07-18T09:40:26Z ToadetteEdit 1508 Created page with "تحديث الوسائط" 12298 wikitext text/x-wiki تحديث الوسائط a8k7mi2n5wbbyqpad4rma3ise60cxnd 1198 4546 12300 2026-07-18T09:40:46Z ToadetteEdit 1508 Created page with "قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي." 12300 wikitext text/x-wiki قم بتحديث المعاملات (arguments) بما يتناسب مع موضوعك. وكما هو موضح في الصورة، غيّر الكيان والموقع إلى "Utrecht" و"Netherlands". ستعرض المعاينة الآن النص المحدَّث باللغة التي تختارها (على سبيل المثال: "Utrecht is a city in the Netherlands"). لا تضغط على زر "نشر" في الوقت الحالي. kxggl0x7d99q779w9qyf1q389fb6xtv 1198 4547 12302 2026-07-18T09:40:58Z ToadetteEdit 1508 Created page with "وسع الدالة/الدوال" 12302 wikitext text/x-wiki وسع الدالة/الدوال jvuda5482z3kigodqcawfmyjuljt5l4 1198 4548 12304 2026-07-18T09:41:11Z ToadetteEdit 1508 Created page with "قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">")." 12304 wikitext text/x-wiki قم بتوسيع تفاصيل الدالة بالنقر على أيقونات السهم (">"). 63fe3ynrctvl7ofl9q36rgb5z7t2039 1198 4549 12306 2026-07-18T09:41:24Z ToadetteEdit 1508 Created page with "لصق من الحافظة" 12306 wikitext text/x-wiki لصق من الحافظة gxbfybla2tig3ju2zmhfowj3f9yhf9f 1198 4550 12308 2026-07-18T09:41:28Z ToadetteEdit 1508 Created page with "لصق من الحافظة" 12308 wikitext text/x-wiki لصق من الحافظة gxbfybla2tig3ju2zmhfowj3f9yhf9f 1198 4551 12310 2026-07-18T09:41:42Z ToadetteEdit 1508 Created page with "حدد الجزء المنسوخ من الصف العلوي." 12310 wikitext text/x-wiki حدد الجزء المنسوخ من الصف العلوي. eqyrvsji99ktrdpcqley0kjb4r3942e 1198 4552 12312 2026-07-18T09:42:03Z ToadetteEdit 1508 Created page with "انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة"." 12312 wikitext text/x-wiki انقر على أيقونة القائمة المكونة من ثلاث نقاط داخل الجزء (Fragment) الجديد، ثم اختر "لصق من الحافظة". tkj4djou2ibsy1linlufl161gzntyq1 1198 4553 12314 2026-07-18T09:42:16Z ToadetteEdit 1508 Created page with "أضف جزءاً فارغاً" 12314 wikitext text/x-wiki أضف جزءاً فارغاً fya9fnmbwpkoo62zv8c4elp8eyevade 1198 4554 12316 2026-07-18T09:42:51Z ToadetteEdit 1508 Created page with "سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment)." 12316 wikitext text/x-wiki سينقلك هذا إلى صفحة "إنشاء مقالة مجردة جديدة". اضغط على زر علامة الجمع ("+") واختر "إضافة جزء فارغ" (Add empty fragment). 1hl104g5ll44juoz0z345kyyrmzgw52 1198 4555 12318 2026-07-18T09:43:05Z ToadetteEdit 1508 Created page with "إنشاء مقالة جديدة" 12318 wikitext text/x-wiki إنشاء مقالة جديدة flfg6ce8kgjiajne2i8epievzggmuma 1198 4556 12320 2026-07-18T09:43:24Z ToadetteEdit 1508 Created page with "ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها." 12320 wikitext text/x-wiki ابحث عن الموضوع الذي ترغب في كتابة مقالة عنها. kztho4gjlbhlzx5ytdedm5az7mqiuk6 1198 4557 12322 2026-07-18T09:43:32Z ToadetteEdit 1508 Created page with "نسخ إلى الحافظة" 12322 wikitext text/x-wiki نسخ إلى الحافظة 3sepofqf1qap3krdhubzthske8kks9e 1198 4558 12324 2026-07-18T09:43:55Z ToadetteEdit 1508 Created page with "انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة"." 12324 wikitext text/x-wiki انقر على أيقونة القائمة المكونة من ثلاث نقاط، ثم اختر "نسخ إلى الحافظة". 19g30c2rnt20nsg0r4tid99ue0y7rym 1198 4559 12326 2026-07-18T09:44:08Z ToadetteEdit 1508 Created page with "ابدأ" 12326 wikitext text/x-wiki ابدأ kvef7job589cqhcamgwzeui3npo53rp 1198 4560 12328 2026-07-18T09:44:48Z ToadetteEdit 1508 Created page with "أولاً، ابحث عن مقالة موجودة في ويكيبيديا المجردة تشبه تلك التي تود إنشاءها؛ ويمكنك القيام بذلك باستخدام أداة البحث والنقر على عنصر يحمل اللاحقة "- AW" بجانبه. وبمجرد العثور عليها، انقر على خيار "تعديل المصدر"." 12328 wikitext text/x-wiki أولاً، ابحث عن مقالة موجودة في ويكيبيديا المجردة تشبه تلك التي تود إنشاءها؛ ويمكنك القيام بذلك باستخدام أداة البحث والنقر على عنصر يحمل اللاحقة "- AW" بجانبه. وبمجرد العثور عليها، انقر على خيار "تعديل المصدر". jfho095ppb51cgl3nfl97kgtxt4lkci 1198 4561 12330 2026-07-18T09:45:17Z ToadetteEdit 1508 Created page with "== خطوات إنشاء مقالة عن طريق النسخ واللصق ==" 12330 wikitext text/x-wiki == خطوات إنشاء مقالة عن طريق النسخ واللصق == myjlzmkme06q5a8373h4c7ayrlw8gaa 1198 4562 12332 2026-07-18T09:45:31Z ToadetteEdit 1508 Created page with "إنشاء مقالة من الصفر" 12332 wikitext text/x-wiki إنشاء مقالة من الصفر 7f44lgdm0heofty6exv0m3fauzdzf4l 1198 4563 12334 2026-07-18T09:45:46Z ToadetteEdit 1508 Created page with "إنشاء مقالة عن طريق النسخ واللصق" 12334 wikitext text/x-wiki إنشاء مقالة عن طريق النسخ واللصق ok8zo1vnjbe3qiew8i3tyzkicvi89iz 1198 4564 12336 2026-07-18T09:46:37Z ToadetteEdit 1508 Created page with "تصف صفحة المساعدة هذه طريقتين لإنشاء مقالة جديدة." 12336 wikitext text/x-wiki تصف صفحة المساعدة هذه طريقتين لإنشاء مقالة جديدة. 57pqipvcfz2frroo1crabhd707f2for 0 4565 12342 2026-07-18T10:03:22Z Jsamwrites 874 Created page with "{ "qid": "Q7561", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12342 abstractwiki text/plain { "qid": "Q7561", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } clm28iar6i1cczirzgj4jbh73ufgaaf 0 4566 12343 2026-07-18T10:06:13Z Jsamwrites 874 Created page with "{ "qid": "Q7802", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12343 abstractwiki text/plain { "qid": "Q7802", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } ry4j18ngbifw0m1spz7nwv5lfyjcbjh 0 4567 12347 2026-07-18T10:10:11Z Jsamwrites 874 Created page with "{ "qid": "Q11254", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12347 abstractwiki text/plain { "qid": "Q11254", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } sqg13n0owfprjduc121k41t62br2v4l 0 4568 12350 2026-07-18T10:13:25Z Jsamwrites 874 Created page with "{ "qid": "Q12200", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12350 abstractwiki text/plain { "qid": "Q12200", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 517ib2qtt8ee67plseae7h0v934zx34 0 4569 12351 2026-07-18T10:14:40Z Jsamwrites 874 Created page with "{ "qid": "Q13233", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12351 abstractwiki text/plain { "qid": "Q13233", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } ptparnvn3x7n464850j31w21vgnbevd 12352 12351 2026-07-18T10:15:33Z Jsamwrites 874 12352 abstractwiki text/plain { "qid": "Q13233", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } ac7ad8u4fz6j9kexy5ddia0zdtjko94 0 4570 12353 2026-07-18T10:16:23Z Jsamwrites 874 Created page with "{ "qid": "Q13253", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12353 abstractwiki text/plain { "qid": "Q13253", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } s06f9pdap0dxunorjbygdr0wrb4061g 12354 12353 2026-07-18T10:16:39Z Jsamwrites 874 12354 abstractwiki text/plain { "qid": "Q13253", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 7jib1nvgq3xo1llnrak2qysu3o4mh8j 0 4571 12355 2026-07-18T10:17:56Z Jsamwrites 874 Created page with "{ "qid": "Q13317", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12355 abstractwiki text/plain { "qid": "Q13317", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } t6jc7swiyaq7p21brixwxeyslha0skq 0 4572 12356 2026-07-18T10:18:41Z Jsamwrites 874 Created page with "{ "qid": "Q13266", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12356 abstractwiki text/plain { "qid": "Q13266", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 2epo72t14a64zxrjqvqbuy9sdb3az7z 12358 12356 2026-07-18T10:19:02Z Jsamwrites 874 12358 abstractwiki text/plain { "qid": "Q13266", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } fxmbonb5lra8uc6cbehcgjn1c8bnz4j 0 4573 12360 2026-07-18T10:52:15Z Jsamwrites 874 Created page with "{ "qid": "Q14674", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12360 abstractwiki text/plain { "qid": "Q14674", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } hojieky79ubrle7c3kgluz0hnqqxjgn 0 4574 12361 2026-07-18T10:53:01Z Jsamwrites 874 Created page with "{ "qid": "Q14968", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12361 abstractwiki text/plain { "qid": "Q14968", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 1j377kqesre1u6nez0ni6cpk16pdavx 12362 12361 2026-07-18T10:53:20Z Jsamwrites 874 12362 abstractwiki text/plain { "qid": "Q14968", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } mgnlznpn2bc8dqwh4l5kqd5vpxhvsxo 0 4575 12363 2026-07-18T10:54:14Z Jsamwrites 874 Created page with "{ "qid": "Q20129", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12363 abstractwiki text/plain { "qid": "Q20129", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 5gip0h90sxkp09cs9jtnm3dcoqy0bd5 12364 12363 2026-07-18T10:54:32Z Jsamwrites 874 12364 abstractwiki text/plain { "qid": "Q20129", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } t1mno9g9levvu0qd38go13w8qlnmsf3 0 4576 12365 2026-07-18T10:55:14Z Jsamwrites 874 Created page with "{ "qid": "Q23392", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12365 abstractwiki text/plain { "qid": "Q23392", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 0xrqdq77lxn2fl16t3bj8lh9m2vcev8 0 4577 12366 2026-07-18T10:56:41Z Jsamwrites 874 Created page with "{ "qid": "Q917574", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12366 abstractwiki text/plain { "qid": "Q917574", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } oq2mo45zxjput3hot3n71yqm4of8mz6 0 4578 12367 2026-07-18T10:57:14Z Jsamwrites 874 Created page with "{ "qid": "Q207832", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12367 abstractwiki text/plain { "qid": "Q207832", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } bjojscc99kuz3ipx8xpdgbp5v0f1ttx 12368 12367 2026-07-18T10:57:34Z Jsamwrites 874 12368 abstractwiki text/plain { "qid": "Q207832", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 3n1rah0fnc9v3fk7ej6jqvkildo8abv 0 4579 12369 2026-07-18T10:57:56Z Jsamwrites 874 Created page with "{ "qid": "Q1190838", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": {..." 12369 abstractwiki text/plain { "qid": "Q1190838", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37890", "Z37890K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37890K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } fstavm7eu802n2fczi38wfu632re1q2 3 4580 12371 2026-07-18T11:42:56Z HenkvD 1447 /* Comments */ new section 12371 wikitext text/x-wiki == Comments == Hi 99of9, I would like to make a few comments, especially about rendering on other languages. 1. Other languages. You state ''Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured).''. In [[Abstract:MOS/FUNC]] it is explicitly mentioned ''Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia.''. On [[Help:How to create an article]] I personally wrote ''It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".'' As Abstract Wikipedia is a multilingual project I think we should emphasize the multilingualism! So I respectfully disagree with the English centric message. 2. Combination of words like "timeline of Australian history" [[d:Q4501797]] should be avoided. It is OK as link to an article, but this does not render well in other languages. On Wikidata that is only translated in 7 languages worldwide, and is not expected to be translated into many more languages. Instead the rendered text should be partial sentence like "timeline" "of the" "history" "of" "Australia". Although an other example [[d:Q174825]] "history of Australia" is currently has the label translated in many languages, as AW might be used for minority languages the label for those languages is not expected to be translated into many more languages either. I don't think there currently is a function make a partial sentence for alternate texts of QID links, so I don't think that part of the article is well constructed. Emphasizing that is not a good idea either. 3. Advice for well constructed articles: As a minimum every sentence in English (or other language) should be a well formed sentence, with proper articles (a, the), capitals and a space between sentences (dependent on the language). All words should be in the required language, so no fallback languages, or default texts. Of course no technical errors, missing labels, lexemes etc. should occur. Current technical errors for Timeouts are excluded from that. For the rest the normal guidelines of any Wikipedia would apply. As stated at 1) the article should preferably be OK in an other language too, or at least each sentence should be correct in an other language. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:42, 18 July 2026 (UTC) 7frul2e28ldorruyhdbj92yriblzt3f 12372 12371 2026-07-18T11:46:08Z HenkvD 1447 12372 wikitext text/x-wiki == Comments == Hi 99of9, I would like to make a few comments, especially about rendering on other languages. 1. Other languages. You state ''Once a fragment is in, check if it renders well (in English at this stage since it is the only language in which functions can be expected to be configured).''. In [[Abstract:MOS/FUNC]] it is explicitly mentioned ''Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia.''. On [[Help:How to create an article]] I personally wrote ''It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".'' As Abstract Wikipedia is a multilingual project I think we should emphasize the multilingualism! So I respectfully disagree with the English centric message. 2. Combination of words like "timeline of Australian history" [[d:Q4501797]] should be avoided. It is OK as link to an article, but this does not render well in other languages. On Wikidata that is only translated in 7 languages worldwide, and is not expected to be translated into many more languages. Instead the rendered text should be partial sentence like "timeline" "of the" "history" "of" "Australia". Those words should be found in a dictionary (or proper nouns). Although an other example [[d:Q174825]] "history of Australia" is currently has the label translated in many languages, as AW might be used for minority languages the label for those languages is not expected to be translated into many more languages either. I don't think there currently is a function make a partial sentence for alternate texts of QID links, so I don't think that part of the article is well constructed. Emphasizing that is not a good idea either. 3. Advice for well constructed articles: As a minimum every sentence in English (or other language) should be a well formed sentence, with proper articles (a, the), capitals and a space between sentences (dependent on the language). All words should be in the required language, so no fallback languages, or default texts. Of course no technical errors, missing labels, lexemes etc. should occur. Current technical errors for Timeouts are excluded from that. For the rest the normal guidelines of any Wikipedia would apply. As stated at 1) the article should preferably be OK in an other language too, or at least each sentence should be correct in an other language. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:42, 18 July 2026 (UTC) 65rcotclkhmjrzoupaxxsmagu09mfim