Sat, Sep 14
My bad. I assumed the number to be unformatted, and did not notice the comma.
Yes, my bad.
Fri, Sep 13
Wed, Sep 11
Further complaints at nowiki.
Tue, Sep 10
On the point “It can be based not only on successful interpretation but also on automated unit test: an assertion defined by the module author.” This is very tempting, but it is quite hard to do it right. The reason is that unit tests should be a contract on the interface, ie according to current use of the module, but when a module (or any code) is updated the unit tests are customary changed to facilitate the actual code. That code is not necessarily the same as the original code the current use depend upon. That is the unit tests follows the implementation and is not viewed as an interface contract. If the person coding (or debugging) a module can change the interface contract, then it makes no sense to block save because the interface contract is violated.
Not sure the wiki system admins (sysops?) should be allowed to add C-calls, but the argument that the current configuration is “have proven performant enough” seems dubious at best. We don't implement harder Lua code simply because Lua is capped – we lack performance.
Backporting features into an older language definition is not really a feasible solution, and should not be done. It goes against, and breaks, the core idea of a language version.
On the point “The same page can be in multiple versions of Lua, like 5.1,5.2,5.3, which means that the code is expected to work under any listed version of Lua.” Code written for specific versions should be dispatched to specific interpreters. Expecting code to work for several language versions is a nightmare. Declare which version the code is expected to run on, and make tracking categories for the versions. Ie., list the module pages that uses specific versions, thereby make it possible to find and update scripts.
Mon, Sep 9
Oki, just made the URL myself! :)
Sun, Sep 8
I believe I've said this data type is wrong a few times (!) back at WMDE. It tries to both be a representation for a scalar datatype with a precision, and a range datatype. It fails badly at both.
Sat, Sep 7
You can have a measure along some physical dimension, given in meter or foot, which would then nicely be split in a value and an unit. Conversion from meter to foot would then follow simple conversion factors. This is complicated when you have units that isn't well-defined, and can't easily be converted. In a lot of cases you can convert them with increased uncertainty, and in a few cases you cant convert them at all because you don't know enough about the historical units.
Tue, Sep 3
@Urbanecm I'm not sure what you are saying, do you say you veto a request from nnwiki? Note that the task is and was clearly marked as stalled on community consensus. The community asked for help, and this turned up as an issue, but if there is a problem just say so and I close the task and move on.
Mon, Sep 2
@Urbanecm and @DannyS712, community consensus is only formal, I doubt it will be anyone against. I should have tagged with Community-consensus-needed, and not only "stalled" while waiting for formal consensus.
Sun, Sep 1
Hold the execution until discussion is finished at w:nn:Wikipedia:Samfunnshuset#Slå på transwiki.
Sat, Aug 31
I posted the links, and a description, but I'm not going to invest more work into this.
Fri, Aug 30
The repo for my work on this is at Github: jeblad/TemplateData. I don't remember if it works as it is, it probably don't.
Wed, Aug 28
Result is 3 for use of this, and non against. (Utprøving av «reference previews») One of the three is me, so not exactly overwhelming response. ;)
Note that some of the more restrictive states of Firefox and Chrome may impact CentralAuth, and a person can be logged in at Wikipedia and still not being logged in at Wikidata. Thus logged in state must be checked on both repo and client.
Tue, Aug 27
Aug 19 2019
Made a poll at nnwiki.
Aug 18 2019
Sorry @Lea_WMDE, I did not notice the post. Norwegian Bokmål Wikipedia has 14 pro and none against the reference preview. (nowiki) I have updated the description with a link to the archive. If someone is against something at nowiki they tend to be very vocal, so this is a pretty sure consensus. Norwegian Nynorsk Wikipedia is slightly confusing, as only one admin has answered my post. (nnwiki) It is a much smaller community, and it is very much less arguing at nnwiki. I would say it is consensus when Ranveig has spoken, but I could be wrong. If you want me to set up a poll at nnwiki I can do it.
Aug 15 2019
Bugger, space hid it in search… Thanks for noting the duplicate!
Aug 12 2019
The “preview” button should load a preview page, but it does not.
Checked enwiki and nowiki, and works for me.
Aug 10 2019
Aug 5 2019
I don't have time for this.
Aug 4 2019
Also happen at nowiki.
Jul 3 2019
There are new complaints about this change at nowiki, w:no:Wikipedia:Torget#Merkelig når en skal opprette artikkel. Previous complaint at w:no:Wikipedia:Torget/Arkiv/2019/juni#Visual editor når man oppretter artikler.
Jun 25 2019
Jun 13 2019
Without going into specifics; some users will nearly always open a red-linked article in plain old wikitext editor because the initial editing consists mostly of non-content-text, it is mostly markup. Not sure what you would call “brødtekst” in English. For those users it is a major inconvenience to use the visual UI and try to navigate a pointer-based interface.
Jun 9 2019
For those that use all three editors, both VisualEditor and WikitextEditor2017 is unusable for template editing, this is a awkward change as it has now become pretty much random which editor is used. The reason it is pretty much random which editor opens is because it is pretty much random which editor the user last used. It seems like some devs thinks the choice is static, but it is not, users change back and forth all the time.
Jun 6 2019
It would be nice to be able to export a pandoc friendly mediawiki format, and thus be able to create several formats including epub.
Jun 2 2019
The solution in T224741#5228174 will fail badly when you have permutations of references. Permutations of references in such a list will spawn new entries in the references tag. This will be a real problem with references in infoboxes.
Jun 1 2019
May 31 2019
I have described a slight variant on T224741, or rather an extended functionality.
May 30 2019
May 13 2019
May 9 2019
Thanks to everyone! :D
May 6 2019
As I wrote as clarification, this also happen on enwiki, i follows the user language. Just click on the links and wait a few minutes. Most likely the message cache is somehow stuck in an outdated state.
May 5 2019
@Nikerabbit Could this be an error due to the translate update being turned off for a short time?