Abstract Wikipedia:Project chat - Abstract Wikipedia

Abstract Wikipedia:Project chat - Abstract Wikipedia
Jump to content
From Abstract Wikipedia
Latest comment:
2 hours ago
by Theki in topic
What are we called?
Shortcuts
Project:PC
Project:VP
This is the Abstract Wikipedia Project chat. This is where discussions on the project happen. Add your discussion below this line. More technical issues should go to
Abstract Wikipedia:Report a technical problem
. For older conversations, see the archives (
).
Put this on ice
edit
Latest comment:
7 days ago
14 comments
8 people in discussion
How are non-English speakers (who this project is specifically for) meant to develop this wiki's practices and policies if a) all project pages are only available in English, and discussion is largely done in English, and b) there's no attempt to get non-en.wiki communities onboard. At present this looks like it's just going to produce Anglocentric/Eurocentric content, which belies the whole point of having a wiki in one's native language. Yes it's early days and everyone is experimenting and bug-fixing, but the project has already been released to community control, with a predominantly English-speaking/European community. This needs to be put on ice until it can be launched properly with multilingual support and invitations to all wikis, particularly smaller ones.
Kowal2701
talk
11:44, 28 March 2026 (UTC)
Reply
Just because it's not perfect doesn't mean it needs to be shut down. These are all gradual processes.
Feeglgeef
talk
15:58, 28 March 2026 (UTC)
Reply
There’s being "not perfect" where things can be improved at a later date, and then there's having antithetical foundations. Also see
re functions.
Kowal2701
talk
16:15, 28 March 2026 (UTC)
Reply
You haven't named a single thing that can't be improved at a later date. We're hoping to be able to translate project pages. Non-enwiki communities can be gotten on board later. Function generation already works multilingually in many cases, and those where it does not can be improved.
Feeglgeef
talk
16:57, 28 March 2026 (UTC)
Reply
When the practices and policies will have already been developed, and informal positions of authority already filled.
Kowal2701
talk
17:04, 28 March 2026 (UTC)
Reply
Kowal2701
Thank you for your concerns. We are already aiming at less-served communities through specific calls to action to create more language functions and abstract content in their language. Just give the time to actually see these changes happen. Cheers,
Sannita (WMF)
talk
18:55, 28 March 2026 (UTC)
Reply
Hi Sannita, I'm just wondering how are AW project pages planned to be translated in the future? Is there going to be use of some kind of automated tool such as DeepL or Google Translate, or will it be a custom-designed system?
EatingCarBatteries
talk
20:39, 28 March 2026 (UTC)
Reply
EatingCarBatteries
We will enable the Translate extension soon, so everyone will be able to translate project pages into their own languages. Sorry for keeping you waiting on this.
Sannita (WMF)
talk
10:41, 29 March 2026 (UTC)
Reply
Kowal2701
: thank you for your concern and suggestion. When this Beta started, we have immediately
mentioned that there might be the possibility of restarting the project
. So that might indeed happen.
But so far, this early start of the not fully polished project allows us to learn so incredibly much. In the last few days we have learned so much more than we would have been able without the launch in months! And it helps us to focus on where to put our limited resources, so that we can make the overall project better quicker than would have been possible otherwise. From that perspective, this has been quite a success.
I am trying to understand your suggestion: what do you think would need to be in place before a possible relaunch? Which requirements would need to be met? --
DVrandecic (WMF)
talk
13:53, 29 March 2026 (UTC)
Reply
Thank you, I wasn't aware of that. Some uninformed thoughts below.
Re communication: ideally people would communicate using functions, and there'd be some kind of visual editor where people type in their native language and it gets translated into functions, but I realise that's a pipe dream. Something that allows people who don't have a mutual language to communicate is imo necessary, maybe there could be a tool that machine translates comments. Machine translation
sucks
, but so long as people get the gist of what is being said, that'd be better than nothing. I dread to think what disputes would be like though.
Re invitations, idk what has already been done, but I would've thought now would the time to get some people from smaller wikis editing and experimenting, just an invitation on a wiki's main noticeboard would probably do the trick (is there a
meta:MassMessage
service for updates re Abstract wiki that could be recommended?). Then a central or watchlist notice for the actual launch, hopefully by which time there'd already be a small group of editors able to assist the influx of newbies. An intuitive tutorial is also necessary, as well as an intuitive version of
f:Wikifunctions:Catalogue
Kowal2701
talk
18:14, 29 March 2026 (UTC)
Reply
What do you think about boilerplate templates. So writing a sentence and then marking the parts of the sentence what can be derived from Wikidataitems or the lexeme linked to it. This seems to me like an realistic approach for making it easier to contribute. I am happy you wrote about the predominantly English-speaking/European community involved in this project. It seems like it is different to contribute so far and I had the expectation people from small language versions come on their own and contribute also if they dont speak English. So far it seems to be not the case and I hope it will be easier to contribute. I think for the beginning the goal of Abstract Wikipedia should be generating sentences based on data. So supporting small language versions should be not the goal of the first phase as it seems to take some time and improvements of the structures to make it easier to contribute. Sharing the work and offering people help with creating an function for an specific sentence can be a important way of getting more content in Abstract Wikipedia. Maybe it is unrealistic to find a huge number of people who are interested in writing functions who generate text.
Hogü-456
talk
20:58, 29 March 2026 (UTC)
Reply
Abstract Wikipedia:Useful functions for article composition
is already available, as is
Help:How to create an article
, but they are not perfect.
Feeglgeef
talk
22:05, 29 March 2026 (UTC)
Reply
Wikidata has a project chat in many languages. We can do that in the future.
Immanuelle
talk
14:28, 16 April 2026 (UTC)
Reply
Anyone can write on this page in any language. Personally, I’d prefer to see the original and get it translated into English rather than trying to make sense of a poor machine translation without even knowing which language the original was in. For the same reason, I would generally reply in English.
GrounderUK
talk
23:18, 16 April 2026 (UTC)
Reply
Gendered languages
edit
Latest comment:
16 days ago
3 comments
3 people in discussion
I've created
Q79097672
, an article for a woman singer. In gendered languages however, it defaults to using masculine words. An example: in Portuguese, it reads "Arlo Parks é um cantor", when it should be "Arlo Parks é uma cantora". Is there any fix to this?
Skyshifter
talk
23:49, 28 March 2026 (UTC)
Reply
Yes. But each language is handled separately. I think Italian is doing it. German was started but got stuck… it should be working here soon.
GrounderUK
talk
00:48, 29 March 2026 (UTC)
Reply
Italian is not doing it. It is just a happy coincidence that for some reason "cantante" is always treated as feminine (I have to investigate why).
Dv103
talk
19:59, 7 April 2026 (UTC)
Reply
Why don't we just structure this with wikitemplates?
edit
Latest comment:
25 days ago
4 comments
2 people in discussion
I feel like the project could be done a lot better by using templates kind of like how wikipedia does them. Just the entire thing is templates that can be rendered in many languages. So like
Q106289265
would have the content
{{Z26039|Q7257}}
and could even have some aliasing done across languages so it could be
{{subject is|Q7257}}
. Code would be editable with a regular visual editor or code editor.
Immanuelle
talk
04:34, 29 March 2026 (UTC)
Reply
This is available in pages when Parsoid rendering is enabled. We don't use this becuase it doesn't make sense for constructing and editing massive articles.
Feeglgeef
talk
21:37, 29 March 2026 (UTC)
Reply
How do you do parsoid rendering? And why wouldn't it make sense? With aliases and everything could work great.
Immanuelle
talk
23:12, 29 March 2026 (UTC)
Reply
I believe it is enabled by default. If you do have it on:
you'll see this
Feeglgeef
talk
14:54, 30 March 2026 (UTC)
Reply
Automatically querying wikidata
edit
Latest comment:
4 days ago
4 comments
4 people in discussion
Is it possible in the future for this project to have things that automatically query wikidata? Like an infobox that gives people's spouses, or a function that queries a specific property on wikidata
Immanuelle
talk
20:10, 29 March 2026 (UTC)
Reply
Yes, that is the long term goal.
Feeglgeef
talk
21:37, 29 March 2026 (UTC)
Reply
What’s “long term” about it? We already have functions that query specific properties on Wikidata,
f:Z32431
being a simple example. A list of spouses seems like a fairly simple function too, although there might be performance issues if there are a lot of spouses.
GrounderUK
talk
22:01, 31 March 2026 (UTC)
Reply
I had exactly this question. One of the example here is
Q1033
where I read "Nigeria is the most populous country in Africa.". The problem is that this concept is hard-coded. What if its population will decrease and it will become the second-most populous country?
Wiso
talk
08:21, 20 April 2026 (UTC)
Reply
Searching for other namespaces in the search bar
edit
Latest comment:
25 days ago
4 comments
4 people in discussion
Something that has always irked me with Wikidata, Wikifunctions, and now Abstract Wiki is that there are no search suggestions when you are searching in other namespaces in the search bar. For example, if I were to type "Abstract Wikipedia:", nothing shows up. Whereas on enwiki, you can do this just fine. Is this because these sites are using a more "modified" version of MediaWiki?
EatingCarBatteries
talk
04:38, 30 March 2026 (UTC)
Reply
I also find this very annoying. I'm not sure if there's anything that can be done about it or if it is a result of technical limitations (
Jdforrester (WMF)
?).
Feeglgeef
talk
04:41, 30 March 2026 (UTC)
Reply
EatingCarBatteries
, @
Feeglgeef
: The search interface indeed is designed to only search the Wikidata concepts that would take up the main namespace. This is conceptually the same as the search on Wikidata.org. We'd welcome Phabricator tasks for ideas on how to additionally provide wikitext community page search, though implementing that might not be a priority.
Jdforrester (WMF)
talk
12:11, 30 March 2026 (UTC)
Reply
Hint: don’t use the Search bar…
When it is empty, click the adjacent Search button. This takes you to the Search page.
Type the namespace with final colon. You are prompted with available pages and the prompt is refined as you type.
Click a page title in the suggestions or click Search for a full search in the entered namespace.
A search with just a namespace will return no results. A search with a partial identifier will work only
with an appended asterisk
(delete the asterisk to see page suggestions).
GrounderUK
talk
13:11, 30 March 2026 (UTC)
Reply
List articles
edit
Latest comment:
21 days ago
2 comments
2 people in discussion
I am interested in creating list articles (
like this one
). But I have no idea what it needs and how to start.
GPSLeo
talk
19:58, 30 March 2026 (UTC)
Reply
An example I've created that you can copy and adapt is
Q11750
Feeglgeef
talk
01:27, 3 April 2026 (UTC)
Reply
Logo
edit
Latest comment:
3 days ago
3 comments
3 people in discussion
In vector2009 and monobook, the logo shows as the standard enwiki logo. Which is confusing as this is technically a whole other sisterproject. I suggest
this
be used as a temporary logo for these skins.
Kinopiko
talk
06:00, 31 March 2026 (UTC)
Reply
There's also the scalable favicon,
Abstract-Wikipedia-favicon.svg
Arlo Barnes
talk
01:54, 3 April 2026 (UTC)
Reply
This still appears to be as of yet unfixed. I understand this wiki is still very early in its lifespan so I'm not particularly miffed about it, it looking identical due to the logo is rather confusing at first but with separation with tab groups in my browser it becomes manageable. I am personally excited to see what logo(s) will be devised for this project; seeing the same thing happen for the other sister projects has been very fun to watch in the past.
rae
5e
talk
21:49, 20 April 2026 (UTC)
Reply
Extra spaces between sentences
edit
Latest comment:
13 days ago
4 comments
3 people in discussion
There should be no spaces between two sentences of Chinese and Japanese. —
内存溢出的猫
talk
12:38, 2 April 2026 (UTC)
Reply
I'm not sure how we plan to handle this. I'll bring it up on the Telegram/IRC. This applies to Korean too, yes?
Feeglgeef
talk
01:28, 3 April 2026 (UTC)
Reply
Tracked in
Phabricator
Task T
Please link to the corresponding Phabricator ticket when it’s raised. (Or I will, when I raise it). I think the technical issue is that the space is inserted between function calls. There may be two, but HTML reduces their appearance to one, which is one too many for certain languages.
GrounderUK
talk
08:58, 3 April 2026 (UTC)
Reply
No, your sentences should not be individual fragments.
Feeglgeef
talk
02:40, 11 April 2026 (UTC)
Reply
community curation of abstract articles of the week/month/etc.
edit
Latest comment:
17 days ago
5 comments
3 people in discussion
this thread
at WF mentions that WMF staff are refraining from content decisions at Abstract Wikipedia; so I thought that it might be a good idea to figure out if and how there will be editathons here focussed on a selection of articles. —
Arlo Barnes
talk
20:38, 2 April 2026 (UTC)
Reply
I would support this. —
Feeglgeef
talk
01:29, 3 April 2026 (UTC)
Reply
now I notice
abstract:featured article
in the same category as the project chat, so there's a location for a related concept already! (coming at it the other direction: recognizing already good articles versus barnraising that quality) —
Arlo Barnes
talk
01:48, 3 April 2026 (UTC)
Reply
I think it will be quite a while before we can support a “good” article, let a “featured” one. At this stage, I’d settle for “technically interesting”, to include “of archaeological interest” (like the first use of a particular function or function-call pattern).
GrounderUK
talk
08:51, 3 April 2026 (UTC)
Reply
one goal could be to make stubs and grow them for the basic concepts underlying Abstract Wikipedia, in an attempt to self-document.
Arlo Barnes
talk
02:45, 7 April 2026 (UTC)
Reply
JSON format
edit
Latest comment:
11 days ago
16 comments
5 people in discussion
The JSON format for Wikifunctions is described at
f:Wikifunctions:Function model
Is there such a documentation page for Abstract Wikipedia?
Amir E. Aharoni
talk
15:19, 2 April 2026 (UTC)
Reply
I imagine that it would be identical?
Feeglgeef
talk
02:39, 11 April 2026 (UTC)
Reply
No, they aren't.
Amir E. Aharoni
talk
02:50, 11 April 2026 (UTC)
Reply
Oh, I see, you're talking about the underlying text format? That isn't and (from what I've gathered, though
Jdforrester (WMF)
didn't respond last time I pinged him) will never be editable by users. The function model where the calls are actually made is identical to Wikifunctions.
Feeglgeef
talk
15:36, 11 April 2026 (UTC)
Reply
I'm not asking whether it's editable. I'm asking whether there is a page that documents what it is.
The JSON of the function calls is perhaps the same as Wikifunctions compositions, but there are also other things there, which are not the same as Wikifunctions.
Amir E. Aharoni
talk
22:40, 11 April 2026 (UTC)
Reply
I'm saying that I'm not sure why you'd
need
or
want
to understand it if you can't edit it and it doesn't impact the user experience in any way. Is there a specific problem that you are running into?
Feeglgeef
talk
00:28, 12 April 2026 (UTC)
Reply
I'm a very curious person.
Amir E. Aharoni
talk
01:19, 12 April 2026 (UTC)
Reply
This is an example JSON of an Abstract Wikipedia article, with only the
Echo function
, if you're curious: { "qid": "Q27318", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z801" } ] } } }.
The base has two key value pairs, "qid" and "sections". "sections" currently only contains one key-value pair as of now,
d:Q8776414
, aka lead section. "fragments" is where the Wikifunctions compositions are stored. I have no idea what "index" is.
Chaotic
Vermillion
converse
contribs
02:35, 12 April 2026 (UTC)
Reply
Yes, that's what I see. I can make educated guesses about those things, but if possible, I'd prefer to read an official reference documentation page. The one about Wikifunctions is fairly good. The one about Abstracts Wikipedia doesn't seem to exist.
Amir E. Aharoni
talk
03:25, 12 April 2026 (UTC)
Reply
I think the reason there's no documentation is that it's merely a curiosity, whereas the mainspace of the wiki is barely functional right now. Perhaps we'll get one later, or whenever/if ever we get the ability to edit it?
Feeglgeef
talk
19:09, 12 April 2026 (UTC)
Reply
Just to clarify (?), index is 0! I believe it can only be 0 at present, at least through the user interface, and I imagine
this ticket
is to allow a non-zero index to be set and modified (so long as it is positive and, in all likelihood, sequential).
GrounderUK
talk
14:00, 12 April 2026 (UTC)
Reply
Not yet. I think such a page on Abstract Wikipedia would be for the community to create and maintain. I don’t know how
these things
are decided upon, but I don’t see a task that would cover technical documentation of any kind.
The development team will no doubt respond with enthusiasm to any questions from the community on matters of technical detail, but I’d be inclined to let such interactions be led by the needs of on-wiki documentation, rather than a proliferation of Phabricator tasks and Project-chat topics.
Shall we ask once on
Abstract Wikipedia talk:Frequently Asked Questions
and see which questions should count among the frequently-asked?
GrounderUK
talk
13:37, 12 April 2026 (UTC)
Reply
GrounderUK
, this is quite definitely something that the extension developers are supposed to create and maintain.
Amir E. Aharoni
talk
20:32, 12 April 2026 (UTC)
Reply
Not as content on this wiki, was my point. Here, I suggest, we should reference any relevant technical documentation from whichever pages we, as a community, choose to create for such a purpose.
GrounderUK
talk
23:06, 12 April 2026 (UTC)
Reply
I don't care very much where it is. I'd just like to read it.
Amir E. Aharoni
talk
23:25, 12 April 2026 (UTC)
Reply
Amire80
: The Wikifunctions function model is documented (alongside its two JSON forms) because we anticipate people would (and should) build tools using it directly. Conversely, the vague expectation ("plan" would be too strong at this point) for Abstract Wikipedia, on the other hand, is that we'll provide APIs to interact with the content, but its serialisation will change over time as features are added to better support the Abstract Wikipedia community's wishes.
For a concrete example (
not a commitment!
) of how the serialisation might change, whilst the system kept working as before, we might in the future add a top-level concept for an abstract article's infobox, which would be shown, edited, and stored apart from the rest of the article's sections, and used differently downstream.
Jdforrester (WMF)
talk
19:27, 12 April 2026 (UTC)
Reply
Bot request
edit
Latest comment:
19 days ago
14 comments
4 people in discussion
Tracked in
Phabricator
Task T421151
Can someone smarter than me please create a bot that connects local items to Wikidata equivalents? Right now, we are growing and there are
hundreds of unconnected pages
here that are just 1:1 main namespace entries that have identical names at
d:
. I have connected several of these, but this seems like a very inefficient and silly thing to do manually. Can someone help here by making a bot that checks
Special:UnconnectedPages
regularly or even
Special:NewPages
and connects pages?
Koavf
talk
06:17, 3 April 2026 (UTC)
Reply
This doesn't sound like something that should be a bot, but like something more automatic and built-in.
Amir E. Aharoni
talk
11:27, 3 April 2026 (UTC)
Reply
Amire80
and
Koavf
: Would a bot be a good idea in the interim period before that can be added to the software?
JJP
Mas
ter
she
they
14:31, 3 April 2026 (UTC)
Reply
Yes, please. Granted, Amir, doing it automatically would be nice, but that feature doesn't exist. Until then, a bot would be very helpful and seems like it would be very difficult to cause problems.
Koavf
talk
14:57, 3 April 2026 (UTC)
Reply
Amire80
and
Koavf
: I've written some code for this purpose
here
Retrospective.py
is meant to be run once, and would connect all existing pages (once the trial run is over).
Prospective.py
would run once daily and connect any pages that have been created since the previous day. That is, until the Phabricator ticket is resolved, obviously.
JJP
Mas
ter
she
they
21:42, 3 April 2026 (UTC)
Reply
Boss. I'm so glad that you're smarter than me.
Koavf
talk
03:25, 4 April 2026 (UTC)
Reply
JJPMaster
You might want to use
'action'
'query'
'list'
'querypage'
'qppage'
'UnconnectedPages'
instead. That way, you won't have to maintain two scripts.
NguoiDungKhongDinhDanh
03:58, 4 April 2026 (UTC)
Reply
NguoiDungKhongDinhDanh
: This is
done
JJP
Mas
ter
she
they
05:01, 4 April 2026 (UTC)
Reply
JJPMaster
One more problem: You seem to be linking non-mainspace pages as well. Don't forget to check
page
'ns'
. Also, why
if
):
break
NguoiDungKhongDinhDanh
05:27, 4 April 2026 (UTC)
Reply
NguoiDungKhongDinhDanh
: The
if not qid.startswith("Q")
bit was supposed to address the namespace problem. The break statement is for the trial of the bot. The integer in the if statement will change once the request is made.
JJP
Mas
ter
she
they
17:04, 4 April 2026 (UTC)
Reply
JJPMaster
Special:UnconnectedPages
results are ordered by namespace, so checking for
page
'ns'
will also help prevent unnecessary iterations.
NguoiDungKhongDinhDanh
19:54, 4 April 2026 (UTC)
Reply
Amire80
Koavf
, and
NguoiDungKhongDinhDanh
: Is a Wikidata BRFA in order at this time?
JJP
Mas
ter
she
they
05:03, 4 April 2026 (UTC)
Reply
JJPMaster
Go ahead, please.
NguoiDungKhongDinhDanh
05:25, 4 April 2026 (UTC)
Reply
See
d:Wikidata:Requests for permissions/Bot/JJPMaster (bot)
JJP
Mas
ter
she
they
18:00, 4 April 2026 (UTC)
Reply
Wikifunctions & Abstract Wikipedia Newsletter #242 is out: Request for Discussion: Syntactic tables
edit
Latest comment:
21 days ago
1 comment
1 person in discussion
There is
a new update
for Abstract Wikipedia and Wikifunctions. Please, come and read it!
In this issue, we introduce a proposal for Natural Language Generation, we introduce a page for function suggestions from Abstract Wikipedia, we inform you that there will be a presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments.
Want to catch up with the previous updates? Check
our archive
Also, we remind you that if you have questions or ideas to discuss, the next
Volunteers' Corner
will be held on
April 13, at 17:30 UTC
link to the meeting
).
Enjoy the reading! --
User:Sannita (WMF)
talk
13:37, 3 April 2026 (UTC)
Reply
Way to specify population
edit
Latest comment:
13 days ago
2 comments
2 people in discussion
Hi! I was wondering if there was a function to specify the population of a place, possibly resembling the following:
N X live in Y.
N would be the population size, X would be what comprises the population (e.g., humans, frogs, etc.), and Y would be the location.
Babelball
talk
15:43, 3 April 2026 (UTC)
Reply
I don't believe we do. Thinking about it now, we should probably have a page where users can request linguistic functions in a more viable format than
f:WF:Suggest a function
Feeglgeef
talk
02:39, 11 April 2026 (UTC)
Reply
The problem of when "X is a Y" and Y is a phrase
edit
Latest comment:
13 days ago
2 comments
2 people in discussion
Consider
Q486972
, whose second sentence is supposed to be "A human settlement is a populated place," generated using the "Article-ful instantiating fragment" function. However, it fails, because the implementation
Z23414
inherently checks for a lexeme linked to the superclass ("
populated place
"). However, since "populated place" is a phrase whose meaning is reducible to the sum of its parts, there is no lexeme for it. Therefore, it's virtually impossible to say "An X is a Y" where Y is a non-idiomatic phrase.
Additionally, languages with grammatical gender are rendered particularly problematic. Consider
Q6636
. The first sentence of this article renders perfectly fine in English: "Homosexuality is a sexual orientation." However, it does not render at all in Spanish. That's because that language's NLG functions use lexicographic data to determine the gender of the phrase "sexual orientation." As there are no such data available for that phrase, it errors out. I did think about using
Z29743
(description of class with adjective and superclass) instead, but that didn't work, since there's no item linked to the adjective "sexual"!
Any ideas for how to avoid this?
JJP
Mas
ter
she
they
00:21, 4 April 2026 (UTC)
Reply
We'd the co-operation of Wikidata contributors here, I think.
Feeglgeef
talk
02:37, 11 April 2026 (UTC)
Reply
I made a desktop app that helps with editing
edit
Latest comment:
5 days ago
40 comments
9 people in discussion
now there's a screenshot available
I made a desktop app that helps with creating and editing Abstract Wikipedia pages. It pulls data from wikidata to form templates that it makes into wikitext, and it can round-trip articles into and from the wikitext. Here it is
User:Immanuelle/Abstract Wikipedia Editor
. I hope that it helps with editing. —
Immanuelle
talk
00:51, 6 April 2026 (UTC)
Reply
I've created
Abstract Wikipedia:Tools
for tracking these things.
Feeglgeef
talk
14:44, 7 April 2026 (UTC)
Reply
Immanuelle
But the main namespace is not for wikitext. Are you publishing this content there anyway?
Ainali
discussion
contributions
15:05, 7 April 2026 (UTC)
Reply
It's not actual wikitext. It's a custom template syntax that's kind of like wikitext, which gets converted into abstract content when you press "Push to Abstract Wikipedia."
JJP
Mas
ter
she
they
16:57, 7 April 2026 (UTC)
Reply
Ainali
JJPMaster
if you have syntax suggestions I am interested. I was in a rush with implementing this, and I want to in the future implement aliases for wikifunctions and possibly items, so that you can type things out yourself.
Immanuelle
talk
19:53, 7 April 2026 (UTC)
Reply
Ah, I see. IT was just the announcement that was ambiguous then.
Ainali
discussion
contributions
20:03, 7 April 2026 (UTC)
Reply
FYI anything made by a clanker AI robot is not "made by you." Thank you for your attention to this matter.
Feeglgeef
talk
15:18, 7 April 2026 (UTC)
Reply
Who, then?
Arlo Barnes
talk
20:16, 7 April 2026 (UTC)
Reply
The clanker AI robot.
Babelball
talk
16:42, 8 April 2026 (UTC)
Reply
I edited the Wikidata page for the tool to mention Claude.
Arlo Barnes
talk
21:35, 8 April 2026 (UTC)
Reply
FYI that LLM-generated code is not eligible for copyright, and therefore the MIT license by extension.
Feeglgeef
talk
17:59, 9 April 2026 (UTC)
Reply
I think the statements that Wikidata could make are limited by what references can be found.
This help page
makes it sound as if there are limited options for expressing a repo's licensing situation, so I am not surprised that MIT should be the blanket release, even if strictly speaking some of the code contained within is ineligible for copyright, or infringes on an existing copyright (which would need to be demonstrated). But I suppose
turnabout
is fair play? —
Arlo Barnes
talk
19:53, 9 April 2026 (UTC)
Reply
Arlo Barnes
I like the idea of the wikidata content being restricted based on sources provided. I will try to implement something like this in the next release. Any ideas of which particular statements are useful and should be imported more readily?
Immanuelle
talk
20:28, 9 April 2026 (UTC)
Reply
I meant in
the Wikidata item
for
AWE, but in general I think our articles should incorporate references early on, since even abstract content needs justification.
This help page
may be handy; '
statement supported by
' could be useful for linking to biographical articles in the manner "According to [source], [claim]" (obviously adjusted to the relevant language structures in each language for saying such things). —
Arlo Barnes
talk
20:42, 9 April 2026 (UTC)
Reply
Arlo Barnes
oh that makes sense. But as for the wikidata sources, actually providing the sources is something that is trivially easy as far as accessing wikidata is concerned, but I am not sure how to give sources for claims in wikilambdas. Do you know how?
Immanuelle
talk
20:44, 9 April 2026 (UTC)
Reply
I don't. Currently the distinction between content and format is unclear to me.
Arlo Barnes
talk
21:48, 9 April 2026 (UTC)
Reply
Arlo Barnes
what do you mean by content vs format?
Immanuelle
talk
21:52, 9 April 2026 (UTC)
Reply
In the most 'abstract' sense, an article would have as irreducible parts semantic content only (from Wikidata), with syntax handled by the group of functions responsible for getting things looking right in a given target language. In practice, the overall structuring of the article largely defines or limits the syntactic structures of language produced. This is sensible for an encyclopedia which has a fairly conventional or constrained sort of prose. Of course, a web encyclopedia needs more than prose. Hence the functions for making links and formatting text (right now directly to HTML, bypassing wikitext). Although this is a MediaWiki installation, no article has had media content added to it yet, since the formatting functions that would enable that aren't in place. So I would say that content and formatting are entangled, currently. A reference could be considered either: the text that provides the sourcing of a statement, or the formatting that enables this semantic content to read as a reference, perhaps inline or as a footnote, end note, or marginal note.
f:WF:type proposals#Representing abstract content
has a couple RfCs about this. —
Arlo Barnes
talk
01:45, 10 April 2026 (UTC)
Reply
Yeah I am very confused about what the intention of Abstract Wikipedia is and how much it lines up with the reality. I had thought that the articles would be mostly directly generated from wikidata.
Only particular direction I see clearly is that I think we need articles on all of these pages
d:Wikidata:List of articles that Abstract Wikipedia should have
since they will likely bring a lot of traffic to the site and since they have a lot of information, people will have a lot of reason to come to this site and come up with new ways of expressing things on the pages.
Immanuelle
talk
04:06, 10 April 2026 (UTC)
Reply
I am however really liking section headers like the one here
Q12539
and I am going to include them in the next release
Immanuelle
talk
04:13, 10 April 2026 (UTC)
Reply
Yes I think that adding sections to articles might be really the first part of the journey towards actually having somewhat readable articles. Although a lot of this is dependent on the article text actually rendering at all
Immanuelle
talk
04:21, 10 April 2026 (UTC)
Reply
Yeah I think I am getting the hang of things. Adding sections and paragraph breaks to the new versions. Denoted by
{{p}}
for a paragraph break
and
==QID==
for a subheading
All content is now generated within paragraphs, and the
{{p}}
splits the paragraphs up. Feeglgeef mentioned that the paragraphs are a significant accessibility feature, and the paragraphs are also easier to insert with the methods of the app.
Immanuelle
talk
04:36, 10 April 2026 (UTC)
Reply
I am also implementing "it" to avoid repeating the name of the article constantly, and I am implementing citation preservation on certain things.Meanwhile also trying to fix the accessibility issue that was criticized.
Immanuelle
talk
05:25, 10 April 2026 (UTC)
Reply
New release is out
Immanuelle
talk
07:42, 10 April 2026 (UTC)
Reply
I would suggest not to use
d:Q6091500
at the moment. In some languages, there might be multiple words for different uses of "it". If you are editing with only the English logic, it won't help build a multilingual wiki.
Sun8908
talk
17:42, 11 April 2026 (UTC)
Reply
Sun8908
fair. I had thought it would be dropped in pro-drop languages but I do not think that was a reasonable assumption.
Immanuelle
talk
19:47, 11 April 2026 (UTC)
Reply
I asked at the Monday meeting. Not sure if anything is being done about it though.
Immanuelle
talk
20:15, 15 April 2026 (UTC)
Reply
Nice work. I for one don't care how you made the tool, the important part to me is how it works and if it helps me/us edit AW.
So9q
talk
20:23, 11 April 2026 (UTC)
Reply
Article on wheat
Immanuelle
your tool is back at it again! I've asked you to test it before you use it to create a bunch of articles twice now. You, evidently, haven't listened! I understand you're probably acting in good faith, but you
have
to test your tool before you unleash it on the wiki.
Feeglgeef
talk
01:38, 18 April 2026 (UTC)
Reply
No, I did listen. I am not sure what your objection is, but this looks like intended behaviour. I was asked to make every single sentence into its own paragraph to make it easier to debug maintaining accessibility. Previous the tool grouped many sentences into a single paragraph.
Immanuelle
talk
02:49, 18 April 2026 (UTC)
Reply
Immanuelle
: You were asked to make each actual paragraph into a call of the "paragraph" function. You were not asked to make every individual sentence a paragraph. That is probably even less accessible than what we started with.
JJP
Mas
ter
she
they
03:06, 18 April 2026 (UTC)
Reply
The content itself needs refining. As it is, most articles have no value-added over the Wikidata triples plus labels; basically just slight readability improvements. We require complex structures sooner rather than later.
Arlo Barnes
talk
03:08, 18 April 2026 (UTC)
Reply
I thought that the rule was that we put every single sentence into a paragraph of its own because text readers need a paragraph to read the text. We cannot debug things if there are multiple sentences within a paragraph, because these sentences go up to the top and make it so that the paragraph itself fails to render.
So this was specifically an accessibility concern for people who are visually impaired, with an accepted reduction in readability for people with regular vision so that it can also be debugged.
Like this:
"What we might try is wrapping each sentence as a paragraph, with occasional pairing of closely related sentences. That keeps failure isolated while preserving at least some natural flow.
We could consider also implementing a “sentence” or “content unit” function that simply calls “paragraph”, so we can later tell where the intended paragraphs are."
Immanuelle
talk
04:11, 18 April 2026 (UTC)
Reply
We need to import the quote template
Immanuelle
talk
04:12, 18 April 2026 (UTC)
Reply
Does anybody want any other changes to be made to this tool? Things are still relatively up in the air about what an optimum article even is, and as a result it kind of makes us limited in what we can do with it. I'm changing the way that the paragraphs work to fit what I now perceive as the consensus.
Immanuelle
talk
18:11, 18 April 2026 (UTC)
Reply
I tried to run it on macOS 14.5, but it errored out when I clicked "Pull from Wikidata." It appears that this was because you hardcoded your Python path.
Error: Error invoking remote method 'generate-wikitext': Error: spawn C:/Users/Immanuelle/AppData/Local/Programs/Python/Python313/python.exe ENOENT
JJP
Mas
ter
she
they
11:56, 6 April 2026 (UTC)
Reply
For the record, the solution is to go into
src/main.ts
and change the Python path to something other than
C:/Users/Immanuelle/...
JJP
Mas
ter
she
they
12:05, 6 April 2026 (UTC)
Reply
TYSM!! I did have to debug the code a little first to get it working, but this will be so helpful for me. —
Chaotic
Vermillion
converse
contribs
11:59, 6 April 2026 (UTC)
Reply
I am so sorry and I fixed it so the new release should avoid that problem in the future. —
Immanuelle
talk
17:55, 6 April 2026 (UTC)
Reply
ChaoticVermillion
btw there is an update that has a lot more functions and I am not sure if you are using it. The new one allows you to undo edits or restore revisions. Something that I cannot figure out how to do in regular Abstract Wikipedia.
Immanuelle
talk
17:55, 8 April 2026 (UTC)
Reply
Wikiprojects
edit
Latest comment:
3 days ago
6 comments
3 people in discussion
Are there wiki projects here? Can I just make some in this namespace?
Immanuelle
talk
15:12, 10 April 2026 (UTC)
Reply
I don't see why not. It's a wiki, after all
:). Please just don't flood the talkspace with templates that don't exist.
Feeglgeef
talk
16:51, 10 April 2026 (UTC)
Reply
I've created a first Wikiproject (
Abstract Wikipedia:WikiProject Core articles
) and an explainer page (
Abstract Wikipedia:WikiProject
).
Feeglgeef
talk
17:11, 10 April 2026 (UTC)
Reply
I made this one too
Abstract Wikipedia:WikiProject Quality Prose
Immanuelle
talk
18:39, 10 April 2026 (UTC)
Reply
Feeglgeef
Are WikiProjects for specific languages OK? Responsibility seems to be stretched between maintaining Wikidata labels and lexemes alongside creating and maintaining functions on Wikifunctions, so I'm unsure if Abstract Wikipedia would be considered a good place to coordinate these things.
rae
5e
talk
21:56, 20 April 2026 (UTC)
Reply
There's no community consensus for or against, so, since this is a wiki, I don't see any reason why anyone would stop you
:).
Feeglgeef
talk
23:46, 20 April 2026 (UTC)
Reply
Wikifunctions & Abstract Wikipedia Newsletter #243 is out: Community proposals for capturing meaning
edit
Latest comment:
14 days ago
1 comment
1 person in discussion
There is
a new update
for Abstract Wikipedia and Wikifunctions. Please, come and read it!
In this issue, we report on three community proposals on syntactic approaches, we introduce a new Type (Complex numbers), we report on current hiccups on Abstract Wikipedia, we share more information about a presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments.
Want to catch up with the previous updates? Check
our archive
Also, we remind you that if you have questions or ideas to discuss, the next
Volunteers' Corner
will be held on
April 13, at 17:30 UTC
link to the meeting
).
Enjoy the reading! --
User:Sannita (WMF)
talk
15:35, 10 April 2026 (UTC)
Reply
Numerous errors have been introduced, possibly due to the "AWE" tool
edit
Latest comment:
5 days ago
43 comments
7 people in discussion
As
Fram
has
pointed out
over on the English Wikipedia in his usual style,
User:Immanuelle
has been breaking pages such as
Q711
with edits such as
Special:Diff/4383
. I was able to
fix this
by changing "it" to Wikidata item reference in "defining role sentence".
Immanuelle
: Judging by your edit history, you have introduced this error to a lot of pages. Before continuing with your work to make the rest of the articles from your list,
d:Wikidata:List of articles that Abstract Wikipedia should have
, I kindly ask you to fix the pages you've already made.
Warudo
talk
17:16, 10 April 2026 (UTC)
Reply
This is, of course, what happens when you use a slop-machine to write code. See existing discussion on
User talk:Immanuelle/Abstract Wikipedia Editor#Creates inaccessible content
Feeglgeef
talk
17:19, 10 April 2026 (UTC)
Reply
Feeglgeef
I thought you wanted everything nested in the paragraph things. That's why I did that, following your request that you linked to.
Immanuelle
talk
17:45, 10 April 2026 (UTC)
Reply
I know. In the future, can you test whatever the slop-machine gives you
on-wiki
to ensure you don't mass-vandalize it again? Thank you!
Feeglgeef
talk
17:52, 10 April 2026 (UTC)
Reply
Feeglgeef
the problem I faced is that I do not know how to actually understand error messages on this wiki. When every page fails to render, it is very difficult to know if I introduced an error, or the program introduced an error.
Immanuelle
talk
18:18, 10 April 2026 (UTC)
Reply
Warudo
I guess my question for you would be how did you figure out that this was an error on the page?
Immanuelle
talk
18:19, 10 April 2026 (UTC)
Reply
That's a fair question. The way things are now you can't be sure if the error is because of technical issues with the site or a bad page. In this case it was rather easy though. The "dependency" parameter of
f:Z28016
expects a reference to a Wikidata item but you passed the string "it" to it. That is an obvious mistake so it was easy to tell that it's not a random error.
Warudo
talk
19:23, 10 April 2026 (UTC)
Reply
That makes sense. I will try to be a lot more careful with error detection in the future. Hopefully the technical issues with the site are fixed and I can see the content issues more soon
Immanuelle
talk
20:08, 10 April 2026 (UTC)
Reply
I suggest that “vandalize” is an inappropriate choice of word in this case. Whatever your feelings about the quality of the code or the care with which it is being deployed, I think you could manage to assume good faith on the part of a fellow contributor. Thank you.
At a technical level, there is an issue with simply bracketing multiple calls together to yield a paragraph, since a failure in any one call will lead to the loss of the whole paragraph. In
f:Wikifunctions:Status updates/2026-03-26
, the advice given was:
“By the way, here’s one tip: currently, caching for Abstract Wikipedia happens on the level of the “fragment”. This means that by putting several sentences into a single paragraph, the paragraph as a whole is being run, may cause time-outs, and will be cached. Instead, if, for now, you put one sentence into each fragment, caching and evaluation can be more spread out and should allow for more content.”
GrounderUK
talk
19:00, 10 April 2026 (UTC)
Reply
GrounderUK
would you suggest removing the paragraph by default behavior in the editor over this?
Immanuelle
talk
19:50, 10 April 2026 (UTC)
Reply
What we might try is wrapping each sentence as a paragraph, with occasional pairing of closely related sentences. That keeps failure isolated while preserving at least some natural flow.
We could consider also implementing a “sentence” or “content unit” function that simply calls “paragraph”, so we can later tell where the intended paragraphs are.
GrounderUK
talk
21:23, 10 April 2026 (UTC)
Reply
This is not accessible for users with screen-readers, and thus not a viable work-around. Each paragraph must be in a paragraph tag.
Feeglgeef
talk
22:31, 10 April 2026 (UTC)
Reply
It’s sub-optimal, I agree, but every unit of meaning would be wrapped in p tags, which is more accessible than a series of bare fragments or failed function calls.
GrounderUK
talk
17:07, 11 April 2026 (UTC)
Reply
If you do need to make inaccessible articles, please at least give them a category on the talk page.
Feeglgeef
talk
21:21, 11 April 2026 (UTC)
Reply
We’d need to agree an accessibility standard first, but I’m not planning on creating any articles until there are suitable functions available.
GrounderUK
talk
22:36, 11 April 2026 (UTC)
Reply
I agree. Accessibility standards need to be established and not just assumed.
Immanuelle
talk
23:28, 11 April 2026 (UTC)
Reply
I definitely do agree that we need accessibility standards, but this isn't really a nice-to-have that you debate about but rather the floor.
Feeglgeef
talk
00:27, 12 April 2026 (UTC)
Reply
I took this thread as consensus that we need to have every sentence as its own paragraph. Is that incorrect? Do people want me to change it back to one paragraph per paragraph break? I removed that one because it covered up errors.
Immanuelle
talk
04:21, 18 April 2026 (UTC)
Reply
When someone "vandalizes" it is not necessarily intentional, see
wikt:vandalise
. I do understand that Immanuelle has good faith, but at the same time, the "deployment" caused tens of articles to be broken, and furthermore I don't suspect something this bad would have slipped through had a human carefully reviewed the code. When a contributor deploys a semi-automated tool and uses it to make edits at the rate
Immanuelle
was at this rate, you are morally obligated to test it. This wasn't the first time the slop-machine that they used caused them to mess up tens of articles, and if Immanuelle doesn't exercise extreme care in the future, I don't suspect it will be the last.
Feeglgeef
talk
22:25, 10 April 2026 (UTC)
Reply
It was a silent error that was only discovered by chance. What kind of testing would you have done to avoid this?
Immanuelle
talk
22:37, 10 April 2026 (UTC)
Reply
Feeglgeef
": On Wikipedia, "
Vandalism
" is a technical term that means "editing (or other behavior)
deliberately
intended to
obstruct or defeat
the
project's purpose
". Accidental disruptive editing is not considered vandalism.
Warudo
talk
22:52, 10 April 2026 (UTC)
Reply
Warudo
on the topic of this glitch. I think I have removed it from all pages that had it. Please tell me if there are more that you see.
Immanuelle
talk
23:29, 10 April 2026 (UTC)
Reply
Thanks for cleaning up
:)
So9q
talk
20:29, 11 April 2026 (UTC)
Reply
This isn't the English Wikipedia, or even a wikipedia at all, despite the domain. Unless a defined technical term related to Wikifunctions I'd consider words to have their natural language meaning.
Feeglgeef
talk
01:28, 11 April 2026 (UTC)
Reply
Feeglgeef
: Last time I checked, this was the Abstract
Wikipedia
. But in any case, this is the definition provided in
Wikifunctions
as well as
meta
. Vandalism has to be deliberate.
Warudo
talk
08:50, 11 April 2026 (UTC)
Reply
It's not
the
Abstract Wikipedia like
the
English Wikipedia, but just Abstract Wikipedia. It isn't a Wikipedia in and of itself (as in, it's not supposed to be viewed by end readers), but rather a tool for Wikipedias.
Feeglgeef
talk
15:33, 11 April 2026 (UTC)
Reply
It still has an independent editing community. Just because it draws from Wikidata and Wikifunctions doesn't mean content decisions aren't made here; it necessarily has to have some autonomy just like any language edition.
Arlo Barnes
talk
19:18, 11 April 2026 (UTC)
Reply
“Deliberately” is also the first word of section 3.3 of our Code of Conduct, linked at the foot of every page.
GrounderUK
talk
17:11, 11 April 2026 (UTC)
Reply
+1 Please assume good faith and keep it civil.
So9q
talk
20:27, 11 April 2026 (UTC)
Reply
Warudo
will hold off on page creation
Immanuelle
talk
17:43, 10 April 2026 (UTC)
Reply
Just a note @
Immanuelle
, the project is a Beta version, so, in my opinion, it's not a good idea to flood it with a large number of
article stubs
. Additionally, the natural language functions are still limited.--
Mdktb
talk
18:58, 10 April 2026 (UTC)
Reply
Mdktb
okay that is a good point. I think I was confused since I thought that we were more on the trying to get new users stage. I will stick to fixing up my errors and only making pages on things that I have a lot of stuff to say on.
Immanuelle
talk
19:20, 10 April 2026 (UTC)
Reply
Mdktb
and here is a wikiproject I made and tagged some pages with that is specifically related to developing more natural language
Abstract Wikipedia:WikiProject Quality Prose
Immanuelle
talk
19:27, 10 April 2026 (UTC)
Reply
Would you be willing to raise this in the project chat? I'm thinking we are in an experimentation state that will keep improving incrementally just like the first edition of Wikipedia did since January 15, 2001. Just like back then I don't think it's a good idea to arbitrarily limit good faith editing. We probably will have to revisit these articles later as more and better functions become available but that in itself is not a valid argument for refraining from edits.
So9q
talk
20:36, 11 April 2026 (UTC)
Reply
Already here
;)
Feeglgeef
talk
21:05, 11 April 2026 (UTC)
Reply
I agree with your stub-flooding comment, I don't think it's particularly useful to have a bunch of articles that say nothing. The concern right now should be testing. I expect that the way in which we write abstract articles will change drastically eventually, so writing hundreds of articles is not only a waste of time but a debt.
Feeglgeef
talk
21:07, 11 April 2026 (UTC)
Reply
We can always use
Special:AncientPages
to find them later on.
My expectation is that things will change, but we’ll be able to change the articles. They aren’t set in stone.
Immanuelle
talk
03:21, 18 April 2026 (UTC)
Reply
The error in question was that "it" ended up getting into the jsons as a string instead of the id for "it". This occurred due to an error with the program with function aliasing, functions and items can have aliases that are used to be human readable, and replaced with their codes during insertion. But apparently when you try to insert a nonexistent alias then it just inserts the text and there is no server side validation at all of edits.
My guess is that basically they do not have an api since they have no server side validation and were relying on solely client side, and did not anticipate someone building such a tool that accidentally bypassed client side validation through a cache injection which was motivated by UX purposes
I plan on attending the Monday volunteer meeting and asking about this issue.
Immanuelle
talk
22:45, 10 April 2026 (UTC)
Reply
> But apparently when you try to insert a nonexistent alias then it just inserts the text and there is no server side validation at all of edits.
This sounds like a bug. Would you be willing to create a ticket in phab with details?
So9q
talk
20:38, 11 April 2026 (UTC)
Reply
The team has already declined (or indicated that they had no plans) to do validation in this form, so I don't think a new ticket would be ideal. Either way, this shouldn't affect anyone besides those using a headless browser (or anyone using good, human-reviewed code and a headless browser), so I don't think it would be a priority anyway.
Feeglgeef
talk
21:19, 11 April 2026 (UTC)
Reply
Not sure what you are talking about. At the meeting they did not seem to be opposed to doing server side validation. They just said that they had a bit of concerns about infrastructure that was stopping it as an immediate thing.
Immanuelle
talk
20:14, 15 April 2026 (UTC)
Reply
The volunteer's corner? I unfortunately missed that, but it was more than a year ago that I believe they decided not to pursue it, so you're probably right.
Feeglgeef
talk
13:46, 16 April 2026 (UTC)
Reply
So I have resolved this issue, as I have resolved most of the issues that people brought up. The whole paragraph debate is something I am returning to the older version of. Does anybody want other changes to the way that it makes articles?
Immanuelle
talk
18:09, 18 April 2026 (UTC)
Reply
Sandbox page
edit
Latest comment:
12 days ago
4 comments
4 people in discussion
The previous discussion about bot-created pages does raise a question: is it possible to have sandbox pages here? As far as I can tell, one can only create pages in the main namespace, and it has to be one page per Wikidata item. So there's no good place to experiment. Or am I missing something?
The only other thing I can think of is to write the whole abstract article (or a part of it) as a function with a composition implementation on Wikifunctions and then to call it from a user-space sandbox page here. That, however, doesn't actually seem to work:
I've just tried to call a function from my user space
, and I just see "⏳ Function is being called…". That is possibly a bug that can be fixed (maybe
T422299
?), but even if it's fixed, it doesn't look like the best user experience.
Amir E. Aharoni
talk
18:48, 10 April 2026 (UTC)
Reply
phab:T421417
Feeglgeef
talk
18:52, 10 April 2026 (UTC)
Reply
For now
Q3938
can be used for test edits .
Chaotic
Vermillion
converse
contribs
02:06, 11 April 2026 (UTC)
Reply
We have
Q138864867
JJP
Mas
ter
she
they
23:30, 11 April 2026 (UTC)
Reply
I propose Q10693 for featured article
edit
Latest comment:
13 days ago
2 comments
2 people in discussion
I think
Q10693
is the best article here. Can I propose it for
Abstract Wikipedia:Featured article
Immanuelle
talk
22:24, 10 April 2026 (UTC)
Reply
We'd to come to a consensus on criteria first before we nominate anything. Anyway, the talk page of
Abstract Wikipedia:Featured article
would be a better place to decide this, not
everything
belongs on the project chat.
Feeglgeef
talk
02:36, 11 April 2026 (UTC)
Reply
REST API for editing?
edit
Latest comment:
4 days ago
5 comments
5 people in discussion
Hi, does anyone know if there is a ticket in phab for a public API endpoint that allows editing of AW content? It would be very useful to improve tooling and content.
So9q
talk
20:41, 11 April 2026 (UTC)
Reply
I don't believe so.
Feeglgeef
talk
21:03, 11 April 2026 (UTC)
Reply
I do not know why there isn't a REST API, but I had to
specifically work around it with my editing tool
. It will be very nice in the future to have a REST API.
I think that right now there isn't actually any server-side verification of whether an article is well-structured, and that might be the reason why there isn't a REST API yet.
Immanuelle
talk
23:46, 11 April 2026 (UTC)
Reply
What rest api are you talking about? Checkout
Special:RestSandbox
Tanbiruzzaman
talk
16:50, 12 April 2026 (UTC)
Reply
I would like to proudly announce that it can be done. See
Special:Diff/6102
. Here was my request:
"source"
"{\"qid\":\"Q100000\",\"sections\":{\"Q8776414\":{\"index\":0,\"fragments\":[\"Z89\"]}}}"
"title"
"Q100000"
"comment"
"Hello from MediaWiki REST API"
"content_model"
"abstractwiki"
"token"
"[token]"
JJP
Mas
ter
she
they
04:43, 20 April 2026 (UTC)
Reply
Spaces between sentences
edit
Latest comment:
8 days ago
11 comments
2 people in discussion
In abstract articles with two sentences or more, I usually see two spaces between the sentences. Why two? I usually write one space, and that's probably what most people do in English. I know that some people write two; I don't like it myself, but this practice does exist. But here, it raises a few more nuanced questions:
Where is it actually defined that there are supposed to be
any
spaces between the sentences? I might be wrong, but it probably comes from the extension code and not from the functions.
Can this be customized per language? I don't know all the rules for all the languages, but I strongly suspect that some languages use spaces between sentences differently, and no default is good for all the languages. I'd especially check if it's good for Thai, Burmese, Japanese, and Chinese.
When I examine the HTML code of the rendered sentences, each of them is a