(no title)
firasd | 29 days ago
For example the swatch internet time infobox is dynamically updated
{{short description|Alternate time system by watch maker Swatch}} {{Infobox | image = [[File:Swatch beat Logo.svg|200px|alt=Logo of Swatch Internet Time]] | caption = Logo of Swatch Internet Time | title = Time{{efn|at page generation }} {{purge|(update to view correct time)}} | label1 = 24-hour time (UTC) | data1 = {{nowrap|{{#time:H:i:s}}}} | label2 = 24-hour time (CET) | data2 = {{Time|CET|dst=no|df-cust=H:i:s|hide-refresh=yes}} | label3 = .beat time (BMT) | data3 = {{nowrap|@{{#expr: floor( {{#expr:{{#expr:{{#expr:{{#time:H|now + 1 hour}}3600}}+{{#expr:{{#time:i}}60}}+{{#time:s}}}}/86.4}} )}}}} }}
sph|29 days ago
Day 2: our users have complicated needs so we’ll basically reinvent Lisp expressions, but worse.
Day N: whatever this markup language is
——
I’ve seen this happen so many times it’s not even funny anymore. Well, at least it’s not YAML.
bawolff|28 days ago
Anyways, now a days you can use lua, so most of the wikisyntax is just glue code calling a lua program
Inityx|28 days ago
https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule
bawolff|29 days ago
notpushkin|29 days ago
But the spaces around | make it easier to read, than, say, CSV.
popalchemist|29 days ago
stogot|29 days ago
decimalenough|29 days ago
I'm not up to speed on my parsers anymore, but I believe Parsoid remains the most complete implementation, while mwlib is a reasonable compromise.
https://www.mediawiki.org/wiki/Alternative_parsers#Known_imp...